--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/releases/NOTE-prov-aq-20130430/diff.html Thu Apr 25 09:43:39 2013 +0200
@@ -0,0 +1,14251 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+ <title>PROV-AQ: Provenance Access and Query</title>
+ <style>/* --- EXAMPLES --- */
+div.example-title {
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.example-title span {
+ text-transform: uppercase;
+}
+aside.example, div.example, div.illegal-example {
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+ border-color: #e0cb52;
+ background: #fcfaee;
+}
+
+aside.example div.example {
+ border-left-width: .1em;
+ border-color: #999;
+ background: #fff;
+}
+aside.example div.example div.example-title {
+ color: #999;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+ padding-right: 1em;
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #2b2; }
+div.issue-title span, div.note-title span {
+ text-transform: uppercase;
+}
+div.note, div.issue {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+}
+div.issue, div.note {
+ padding: 1em 1.2em 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+ border-color: #e05252;
+ background: #fbe9e9;
+}
+.note {
+ border-color: #52e052;
+ background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" type="text/css" href="css/prov-aq.css">
+ <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-aq">
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+<!-- Use common W3C-hosted version of ReSpec.js:
+-->
+
+<!--
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+
+ Use local version of ReSpec.js for debugging:
+ <script src="js/respec.js" class="remove"></script>
+ <script src="file:///usr/workspace/w3c-provenance/prov/paq/js/respec.js" class="remove"></script>
+-->
+ <!-- Include bibliography file defined for PROV-DM: -->
+
+
+
+ <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+<style type='text/css'>
+.diff-old-a {
+ font-size: smaller;
+ color: red;
+}
+
+.diff-new { background-color: yellow; }
+.diff-chg { background-color: lime; }
+.diff-new:before,
+.diff-new:after
+ { content: "\2191" }
+.diff-chg:before, .diff-chg:after
+ { content: "\2195" }
+.diff-old { text-decoration: line-through; background-color: #FBB; }
+.diff-old:before,
+.diff-old:after
+ { content: "\2193" }
+:focus { border: thin red solid}
+</style>
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+ <body><div class="head">
+<p>
+<a href="http://www.w3.org/">
+<img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C">
+</a>
+</p>
+<h1 class="title" id="title">
+PROV-AQ:
+Provenance
+Access
+and
+Query
+</h1>
+<h2 id="w3c-working-group-note-30-april-2013">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Working
+<del class="diff-old">Draft
+12
+March
+</del>
+<ins class="diff-chg">Group
+Note
+30
+April
+</ins>
+2013
+</h2>
+<dl>
+<dt>
+This
+version:
+</dt>
+<dd>
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-aq-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/
+</ins>
+</a>
+</dd>
+<dt>
+Latest
+published
+version:
+</dt>
+<dd>
+<a href="http://www.w3.org/TR/prov-aq/">
+http://www.w3.org/TR/prov-aq/
+</a>
+</dd>
+<dt>
+<del class="diff-old">Latest
+editor's
+draft:
+http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html
+</del>
+Previous
+version:
+</dt>
+<dd>
+<del class="diff-old">http://www.w3.org/TR/2012/WD-prov-aq-20120619/
+</del>
+<a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/WD-prov-aq-20130312/
+</ins>
+</a>
+</dd>
+<dt>
+Editors:
+</dt>
+<dd>
+<span>
+Graham
+Klyne
+</span>,
+<a href="http://www.ox.ac.uk/">
+University
+of
+Oxford
+</a>
+</dd>
+<dd>
+<a href="http://www.few.vu.nl/~pgroth/">
+Paul
+Groth
+<del class="diff-old">,
+</del>
+</a>,
+<a href="http://www.vu.nl/">
+VU
+University
+Amsterdam
+</a>
+</dd>
+<dt>
+Authors:
+</dt>
+<dd>
+<a href="http://www.ecs.soton.ac.uk/~lavm/">
+Luc
+Moreau
+</a>,
+University
+of
+Southampton
+</dd>
+<dd>
+<a href="http://olafhartig.de/">
+Olaf
+Hartig
+</a>,
+Invited
+Expert
+</dd>
+<dd>
+<span>
+Yogesh
+Simmhan
+</span>,
+Invited
+Expert
+</dd>
+<dd>
+<a href="http://www.rpi.edu/research/ccni/">
+James
+Myers
+</a>,
+Rensselaer
+Polytechnic
+Institute
+</dd>
+<dd>
+<a href="http://tw.rpi.edu/web/person/TimLebo">
+Timothy
+Lebo
+</a>,
+Rensselaer
+Polytechnic
+Institute
+</dd>
+<dd>
+<a href="http://semanticweb.org/wiki/Khalid_Belhajjame">
+Khalid
+Belhajjame
+</a>,
+<a href="http://www.cs.manchester.ac.uk/">
+University
+of
+Manchester
+</a>
+</dd>
+<dd>
+<a href="http://www.inf.kcl.ac.uk/staff/simonm/">
+Simon
+Miles
+</a>,
+Invited
+Expert
+</dd>
+<dd>
+<a href="http://soiland-reyes.com/stian/">
+Stian
+Soiland-Reyes
+</a>,
+<a href="http://www.cs.manchester.ac.uk/">
+University
+of
+Manchester
+</a>
+</dd>
+</dl>
+<p class="copyright">
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
+Copyright
+</a>
+©
+2013
+<a href="http://www.w3.org/">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+</a>
+<sup>
+®
+</sup>
+(
+<a href="http://www.csail.mit.edu/">
+<abbr title="Massachusetts Institute of Technology">
+MIT
+</abbr>
+</a>,
+<a href="http://www.ercim.eu/">
+<abbr title="European Research Consortium for Informatics and Mathematics">
+ERCIM
+</abbr>
+</a>,
+<a href="http://www.keio.ac.jp/">
+Keio
+</a>,
+<a href="http://ev.buaa.edu.cn/">
+Beihang
+</a>
+),
+All
+Rights
+Reserved.
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">
+liability
+</a>,
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">
+trademark
+</a>
+and
+<a href="http://www.w3.org/Consortium/Legal/copyright-documents">
+document
+use
+</a>
+rules
+apply.
+</p>
+<hr>
+</div>
+<section id="abstract" class="introductory">
+<h2>
+Abstract
+</h2>
+This
+document
+specifies
+how
+to
+use
+standard
+Web
+protocols,
+including
+HTTP,
+to
+obtain
+information
+about
+the
+provenance
+of
+resources
+on
+the
+Web.
+We
+describe
+both
+simple
+access
+mechanisms
+for
+locating
+provenance
+records
+associated
+with
+web
+pages
+or
+resources,
+and
+provenance
+query
+services
+for
+more
+complex
+deployments.
+This
+is
+part
+of
+the
+larger
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+PROV
+provenance
+family
+of
+documents.
+<p>
+The
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+PROV
+Document
+Overview
+</a>
+describes
+the
+overall
+state
+of
+PROV,
+and
+should
+be
+read
+before
+other
+PROV
+documents.
+</p>
+</section>
+<section id="sotd" class="introductory">
+<h2>
+Status
+of
+This
+Document
+</h2>
+<p>
+<em>
+This
+section
+describes
+the
+status
+of
+this
+document
+at
+the
+time
+of
+its
+publication.
+Other
+documents
+may
+supersede
+this
+document.
+A
+list
+of
+current
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+publications
+and
+the
+latest
+revision
+of
+this
+technical
+report
+can
+be
+found
+in
+the
+<a href="http://www.w3.org/TR/">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+technical
+reports
+index
+</a>
+at
+http://www.w3.org/TR/.
+</em>
+</p>
+<h4 id="prov-family-of-documents">
+PROV
+Family
+of
+Documents
+</h4>
+This
+document
+is
+part
+of
+the
+PROV
+family
+of
+documents,
+a
+set
+of
+documents
+defining
+various
+aspects
+that
+are
+necessary
+to
+achieve
+the
+vision
+of
+inter-operable
+interchange
+of
+provenance
+information
+in
+heterogeneous
+environments
+such
+as
+the
+Web.
+These
+documents
+are
+listed
+below.
+Please
+consult
+the
+[
+<cite>
+<a class="bibref" href="#bib-PROV-OVERVIEW">
+PROV-OVERVIEW
+</a>
+</cite>
+]
+for
+a
+guide
+to
+reading
+these
+documents.
+<ul>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+PROV-OVERVIEW
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+an
+overview
+of
+the
+PROV
+family
+of
+documents
+[
+<cite>
+<a class="bibref" href="#bib-PROV-OVERVIEW">
+PROV-OVERVIEW
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">
+PROV-PRIMER
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+a
+primer
+for
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-PRIMER">
+PROV-PRIMER
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">
+PROV-O
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+the
+PROV
+ontology,
+an
+OWL2
+ontology
+allowing
+the
+mapping
+of
+<ins class="diff-new">the
+</ins>
+PROV
+<ins class="diff-new">data
+model
+</ins>
+to
+RDF
+[
+<cite>
+<a class="bibref" href="#bib-PROV-O">
+PROV-O
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">
+PROV-DM
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+the
+PROV
+data
+model
+for
+<del class="diff-old">provenance;
+</del>
+<ins class="diff-chg">provenance
+</ins>
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+<del class="diff-old">]
+</del>
+<ins class="diff-chg">];
+</ins>
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">
+PROV-N
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+a
+notation
+for
+provenance
+aimed
+at
+human
+consumption
+[
+<cite>
+<a class="bibref" href="#bib-PROV-N">
+PROV-N
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">
+PROV-CONSTRAINTS
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+a
+set
+of
+constraints
+applying
+to
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-CONSTRAINTS">
+PROV-CONSTRAINTS
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">
+PROV-XML
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+an
+XML
+schema
+for
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-XML">
+PROV-XML
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">
+PROV-AQ
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+the
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+mechanisms
+for
+accessing
+and
+querying
+provenance
+(this
+document);
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">
+PROV-DICTIONARY
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note)
+</del>
+<ins class="diff-chg">(Note)
+</ins>
+introduces
+a
+specific
+type
+of
+collection,
+consisting
+of
+key-entity
+pairs
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DICTIONARY">
+PROV-DICTIONARY
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">
+PROV-DC
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note)
+</del>
+<ins class="diff-chg">(Note)
+</ins>
+provides
+a
+mapping
+between
+<del class="diff-old">PROV
+</del>
+<ins class="diff-chg">PROV-O
+</ins>
+and
+<del class="diff-old">Dublic
+</del>
+<ins class="diff-chg">Dublin
+</ins>
+Core
+Terms
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DC">
+PROV-DC
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">
+PROV-SEM
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+a
+declarative
+specification
+in
+terms
+of
+first-order
+logic
+of
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-SEM">
+PROV-SEM
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">
+PROV-LINKS
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note)
+</del>
+<ins class="diff-chg">(Note)
+</ins>
+introduces
+a
+mechanism
+to
+link
+across
+bundles
+[
+<cite>
+<a class="bibref" href="#bib-PROV-LINKS">
+PROV-LINKS
+</a>
+</cite>
+].
+</li>
+</ul>
+<del class="diff-old">Third
+Public
+Working
+Draft
+</del>
+<h4 id="implementations-encouraged">
+<ins class="diff-chg">Implementations
+Encouraged
+</ins>
+</h4>
+<p>
+<del class="diff-old">This
+is
+the
+third
+public
+working.
+This
+revision
+introduces
+a
+new
+definition
+</del>
+<ins class="diff-chg">The
+Provenance
+Working
+Group
+encourages
+implementation
+</ins>
+of
+<del class="diff-old">a
+provenance
+pingback
+service
+as
+well
+as
+making
+various
+clarifications
+about
+</del>
+the
+<del class="diff-old">definition
+of
+service
+descriptions
+</del>
+<ins class="diff-chg">material
+defined
+in
+this
+document.
+Although
+work
+on
+this
+document
+by
+the
+Provenance
+Working
+Group
+is
+complete,
+errors
+may
+be
+recorded
+in
+the
+</ins><a href="http://www.w3.org/2011/prov/errata.html"><ins class="diff-chg">
+errata
+</ins></a><ins class="diff-chg">
+or
+</ins>
+and
+<del class="diff-old">how
+they
+are
+retrieved.
+</del>
+<ins class="diff-chg">these
+may
+be
+addressed
+in
+future
+revisions.
+</ins>
+</p>
+<h4 id="please-send-comments">
+<ins class="diff-new">Please
+Send
+Comments
+</ins></h4>
+<p>
+This
+document
+was
+published
+by
+the
+<a href="http://www.w3.org/2011/prov">
+Provenance
+Working
+Group
+</a>
+as
+a
+Working
+<del class="diff-old">Draft.
+</del>
+<ins class="diff-chg">Group
+Note.
+</ins>
+If
+you
+wish
+to
+make
+comments
+regarding
+this
+document,
+please
+send
+them
+to
+<a href="mailto:public-prov-comments@w3.org">
+public-prov-comments@w3.org
+</a>
+(
+<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">
+subscribe
+</a>,
+<a href="http://lists.w3.org/Archives/Public/public-prov-comments/">
+archives
+</a>
+).
+All
+comments
+are
+welcome.
+</p>
+<p>
+Publication
+as
+a
+Working
+<del class="diff-old">Draft
+</del>
+<ins class="diff-chg">Group
+Note
+</ins>
+does
+not
+imply
+endorsement
+by
+the
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Membership.
+This
+is
+a
+draft
+document
+and
+may
+be
+updated,
+replaced
+or
+obsoleted
+by
+other
+documents
+at
+any
+time.
+It
+is
+inappropriate
+to
+cite
+this
+document
+as
+other
+than
+work
+in
+progress.
+</p>
+<p>
+This
+document
+was
+produced
+by
+a
+group
+operating
+under
+the
+<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">
+5
+February
+2004
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Patent
+Policy
+</a>.
+<del class="diff-old">The
+group
+does
+not
+expect
+this
+document
+to
+become
+a
+W3C
+Recommendation.
+</del>
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+maintains
+a
+<a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">
+public
+list
+of
+any
+patent
+disclosures
+</a>
+made
+in
+connection
+with
+the
+deliverables
+of
+the
+group;
+that
+page
+also
+includes
+instructions
+for
+disclosing
+a
+patent.
+An
+individual
+who
+has
+actual
+knowledge
+of
+a
+patent
+which
+the
+individual
+believes
+contains
+<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
+Essential
+Claim(s)
+</a>
+must
+disclose
+the
+information
+in
+accordance
+with
+<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
+section
+6
+of
+the
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Patent
+Policy
+</a>.
+</p>
+</section>
+<section id="toc">
+<h2 class="introductory">
+Table
+of
+Contents
+</h2>
+<ul class="toc">
+<li class="tocline">
+<a href="#introduction" class="tocxref">
+<span class="secno">
+1.
+</span>
+Introduction
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#concepts" class="tocxref">
+<span class="secno">
+1.1
+</span>
+Concepts
+</a>
+</li>
+<li class="tocline">
+<a href="#provenance-and-resources" class="tocxref">
+<span class="secno">
+1.2
+</span>
+Provenance
+and
+resources
+</a>
+</li>
+<li class="tocline">
+<a href="#interpreting-provenance-records" class="tocxref">
+<span class="secno">
+1.3
+</span>
+Interpreting
+provenance
+records
+</a>
+</li>
+<li class="tocline">
+<a href="#uri-types-and-dereferencing" class="tocxref">
+<span class="secno">
+1.4
+</span>
+URI
+types
+and
+dereferencing
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#accessing-provenance-records" class="tocxref">
+<span class="secno">
+2.
+</span>
+Accessing
+provenance
+records
+</a>
+</li>
+<li class="tocline">
+<a href="#locating-provenance-records" class="tocxref">
+<span class="secno">
+3.
+</span>
+Locating
+provenance
+records
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#resource-accessed-by-http" class="tocxref">
+<span class="secno">
+3.1
+</span>
+Resource
+accessed
+by
+HTTP
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#specifying-provenance-query-services" class="tocxref">
+<span class="secno">
+3.1.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</a>
+</li>
+<li class="tocline">
+<a href="#content-negotiation-redirection-and-link-headers" class="tocxref">
+<span class="secno">
+3.1.2
+</span>
+Content
+negotiation,
+redirection
+and
+Link:
+headers
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#resource-represented-as-html" class="tocxref">
+<span class="secno">
+3.2
+</span>
+Resource
+represented
+as
+HTML
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#specifying-provenance-query-services-1" class="tocxref">
+<span class="secno">
+3.2.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#resource-represented-as-rdf" class="tocxref">
+<span class="secno">
+3.3
+</span>
+Resource
+represented
+as
+RDF
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#provenance-query-services" class="tocxref">
+<span class="secno">
+4.
+</span>
+Provenance
+query
+services
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#provenance-query-service-description" class="tocxref">
+<span class="secno">
+4.1
+</span>
+Provenance
+query
+service
+description
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#direct-http-query-service-description" class="tocxref">
+<span class="secno">
+4.1.1
+</span>
+Direct
+HTTP
+query
+service
+description
+</a>
+</li>
+<li class="tocline">
+<a href="#sparql-query-service-description" class="tocxref">
+<span class="secno">
+4.1.2
+</span>
+SPARQL
+query
+service
+description
+</a>
+</li>
+<li class="tocline">
+<a href="#service-description-example" class="tocxref">
+<span class="secno">
+4.1.3
+</span>
+Service
+description
+example
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#direct-http-query-service-invocation" class="tocxref">
+<span class="secno">
+4.2
+</span>
+Direct
+HTTP
+query
+service
+invocation
+</a>
+</li>
+<li class="tocline">
+<a href="#provenance-query-service-discovery" class="tocxref">
+<span class="secno">
+4.3
+</span>
+Provenance
+query
+service
+discovery
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#provenance-pingback" class="tocxref">
+<span class="secno">
+5.
+</span>
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>
+</li>
+<li class="tocline">
+<a href="#security-considerations" class="tocxref">
+<span class="secno">
+6.
+</span>
+Security
+considerations
+</a>
+</li>
+<li class="tocline">
+<a href="#acknowledgements" class="tocxref">
+<span class="secno">
+A.
+</span>
+Acknowledgements
+</a>
+</li>
+<li class="tocline">
+<a href="#terms-added-to-prov-namespace" class="tocxref">
+<span class="secno">
+B.
+</span>
+Terms
+added
+to
+prov:
+namespace
+</a>
+</li>
+<li class="tocline">
+<del class="diff-old">C.
+Changes
+log
+C.1
+Changes
+since
+20120619
+publication
+</del>
+<a href="#references" class="tocxref">
+<span class="secno">
+<del class="diff-old">D.
+</del>
+<ins class="diff-chg">C.
+</ins>
+</span>
+References
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#informative-references" class="tocxref">
+<span class="secno">
+<del class="diff-old">D.1
+</del>
+<ins class="diff-chg">C.1
+</ins>
+</span>
+Informative
+references
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</section>
+<section id="introduction">
+<h2>
+<span class="secno">
+1.
+</span>
+Introduction
+</h2>
+<p>
+The
+Provenance
+Data
+Model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+],
+Provenance
+Ontology
+[
+<cite>
+<a class="bibref" href="#bib-PROV-O">
+PROV-O
+</a>
+</cite>
+]
+and
+related
+specifications
+define
+how
+to
+represent
+provenance
+<del class="diff-old">in
+</del>
+<ins class="diff-chg">on
+</ins>
+the
+World
+Wide
+Web
+(see
+the
+[
+<cite>
+<a class="bibref" href="#bib-PROV-OVERVIEW">
+PROV-OVERVIEW
+</a>
+</cite>
+]).
+</p>
+<p>
+This
+note
+describes
+how
+standard
+web
+protocols
+may
+be
+used
+to
+locate,
+retrieve
+and
+query
+provenance
+records:
+</p>
+<ul>
+<li>
+Simple
+mechanisms
+for
+retrieving
+and
+discovering
+provenance
+records
+are
+described
+in
+<a href="#accessing-provenance-records" class="sectionRef sec-ref">
+section
+2.
+Accessing
+provenance
+records
+</a>
+and
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>
+.
+</li>
+<li>
+Provenance
+query
+mechanisms
+that
+may
+be
+used
+for
+more
+demanding
+deployments
+are
+described
+in
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>.
+</li>
+<li>
+A
+simple
+"ping-back"
+mechanism
+allowing
+for
+discovery
+of
+<del class="diff-old">"forward
+provenance"
+(i.e.
+</del>
+<ins class="diff-chg">additional
+provenance
+that
+would
+otherwise
+be
+unknown
+to
+the
+publisher
+of
+the
+resource
+(e.g.
+</ins>
+provenance
+about
+future
+entities
+that
+are
+based
+upon
+or
+influenced
+by
+a
+resource)
+is
+described
+in
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>.
+</li>
+</ul>
+<p>
+Most
+mechanisms
+described
+in
+this
+note
+are
+independent
+of
+the
+provenance
+format
+used,
+and
+may
+be
+used
+to
+access
+provenance
+in
+any
+available
+format.
+For
+interoperable
+provenance
+publication,
+use
+of
+<del class="diff-old">PROV-O
+</del>
+<ins class="diff-chg">PROV
+</ins>
+represented
+in
+<del class="diff-old">a
+standardized
+RDF
+format
+</del>
+<ins class="diff-chg">any
+of
+its
+specified
+formats
+</ins>
+is
+recommended.
+Where
+alternative
+formats
+are
+available,
+selection
+may
+be
+made
+by
+<ins class="diff-new">HTTP
+</ins>
+content
+<del class="diff-old">negotiation.
+</del>
+<ins class="diff-chg">negotiation
+[
+</ins><cite><a class="bibref" href="#bib-HTTP11"><ins class="diff-chg">
+HTTP11
+</ins></a></cite><ins class="diff-chg">
+].
+</ins>
+</p>
+<p>
+For
+ease
+of
+reference,
+the
+main
+body
+of
+this
+document
+contains
+some
+links
+to
+external
+web
+pages.
+Such
+links
+are
+distinguished
+from
+internal
+references
+thus:
+<a href="http://www.w3.org/2011/prov/wiki/Main_Page" class="externalRef">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Provenance
+Working
+Group
+</a>.
+</p>
+<p>
+<ins class="diff-new">This
+document
+is
+a
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+Note,
+not
+a
+formal
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+Specification.
+However,
+to
+clarify
+the
+description
+of
+intended
+behaviours,
+it
+does
+use
+the
+key
+words
+</ins><em class="rfc2119" title="MUST"><ins class="diff-new">
+MUST
+</ins></em>,<em class="rfc2119" title="MUST NOT"><ins class="diff-new">
+MUST
+NOT
+</ins></em>,<em class="rfc2119" title="REQUIRED"><ins class="diff-new">
+REQUIRED
+</ins></em>,<em class="rfc2119" title="SHOULD"><ins class="diff-new">
+SHOULD
+</ins></em>,<em class="rfc2119" title="SHOULD NOT"><ins class="diff-new">
+SHOULD
+NOT
+</ins></em>,<em class="rfc2119" title="RECOMMENDED"><ins class="diff-new">
+RECOMMENDED
+</ins></em>,<em class="rfc2119" title="MAY"><ins class="diff-new">
+MAY
+</ins></em><ins class="diff-new">
+and
+</ins><em class="rfc2119" title="OPTIONAL"><ins class="diff-new">
+OPTIONAL
+</ins></em><ins class="diff-new">
+as
+described
+in
+[
+</ins><cite><a class="bibref" href="#bib-RFC2119"><ins class="diff-new">
+RFC2119
+</ins></a></cite><ins class="diff-new">
+].
+</ins></p>
+<section id="concepts">
+<h3>
+<span class="secno">
+1.1
+</span>
+Concepts
+</h3>
+<p>
+<ins class="diff-new">This
+document
+uses
+the
+term
+URI
+for
+web
+resource
+identifiers,
+as
+this
+is
+the
+term
+used
+in
+many
+of
+the
+currently
+ratified
+specifications
+that
+this
+document
+builds
+upon.
+In
+many
+situations,
+a
+URI
+may
+also
+be
+an
+IRI
+[
+</ins><cite><a class="bibref" href="#bib-RFC3987"><ins class="diff-new">
+RFC3987
+</ins></a></cite><ins class="diff-new">
+],
+which
+is
+a
+generalisation
+of
+a
+URI
+allowing
+a
+wider
+range
+of
+Unicode
+characters.
+Every
+absolute
+URI
+is
+an
+IRI,
+but
+not
+every
+IRI
+is
+an
+URI.
+When
+IRIs
+are
+used
+in
+situations
+that
+require
+a
+URI,
+they
+must
+first
+be
+converted
+according
+to
+the
+mapping
+defined
+in
+section
+3.1
+of
+[
+</ins><cite><a class="bibref" href="#bib-RFC3987"><ins class="diff-new">
+RFC3987
+</ins></a></cite><ins class="diff-new">
+].
+A
+notable
+example
+is
+retrieval
+over
+the
+HTTP
+protocol.
+The
+mapping
+involves
+UTF-8
+encoding
+of
+non-ASCII
+characters,
+%-encoding
+of
+octets
+not
+allowed
+in
+URIs,
+and
+Punycode-encoding
+of
+domain
+names.
+</ins></p><p>
+In
+defining
+the
+specification
+below,
+we
+make
+use
+of
+the
+following
+concepts.
+</p>
+<dl>
+<dt>
+<a href="#dfn-resource">
+<dfn id="dfn-resource">
+Resource
+</dfn>
+</a>
+</dt>
+<dd>
+a
+resource
+in
+the
+general
+sense
+of
+"whatever
+might
+be
+identified
+by
+a
+URI",
+as
+described
+by
+the
+Architecture
+of
+the
+World
+Wide
+Web
+[
+<cite>
+<a class="bibref" href="#bib-WEBARCH">
+WEBARCH
+</a>
+</cite>
+],
+<a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">
+section
+2.2
+</a>.
+A
+resource
+may
+be
+associated
+with
+multiple
+instances
+or
+views
+(
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+s)
+with
+differing
+provenance.
+</dd>
+<dt>
+<a href="#dfn-constrained-resource">
+<dfn id="dfn-constrained-resource">
+Constrained
+resource
+</dfn>
+</a>
+</dt>
+<dd>
+a
+specialization
+(e.g.
+an
+aspect,
+version
+or
+instance)
+of
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>,
+about
+which
+one
+may
+wish
+to
+present
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+s.
+For
+example,
+a
+weather
+report
+for
+a
+given
+date
+may
+be
+an
+aspect
+of
+a
+resource
+that
+is
+maintained
+as
+the
+current
+weather
+report.
+A
+constrained
+resource
+is
+itself
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>,
+and
+may
+have
+its
+own
+URI
+different
+from
+that
+of
+the
+original.
+See
+also
+<a class="sectionRef sec-ref" href="#provenance-and-resources">
+section
+1.2
+Provenance
+and
+resources
+</a>,
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+]
+<a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">
+section
+5.5.1
+</a>,
+and
+[
+<cite>
+<a class="bibref" href="#bib-WEBARCH">
+WEBARCH
+</a>
+</cite>
+]
+<a href="http://www.w3.org/TR/webarch/#representation-reuse" class="externalRef">
+section
+2.3.2
+</a>.
+</dd>
+<dt>
+<a href="#dfn-target-uri">
+<dfn id="dfn-target-uri">
+Target-URI
+</dfn>
+</a>
+</dt>
+<dd>
+a
+URI
+denoting
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>
+(including
+any
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+),
+and
+which
+identifies
+that
+resource
+for
+the
+purpose
+of
+expressing
+provenance.
+Such
+a
+resource
+is
+typically
+an
+<a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">
+entity
+</a>
+in
+the
+sense
+of
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+],
+but
+may
+be
+something
+else
+described
+by
+provenance
+records,
+such
+as
+an
+<a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">
+activity
+</a>.
+</dd>
+<dt>
+<a href="#dfn-provenance-record">
+<dfn id="dfn-provenance-record">
+Provenance
+record
+</dfn>
+</a>
+</dt>
+<dd>
+refers
+to
+provenance
+represented
+in
+some
+fashion.
+</dd>
+<dt>
+<a href="#dfn-provenance-uri">
+<dfn id="dfn-provenance-uri">
+Provenance-URI
+</dfn>
+</a>
+</dt>
+<dd>
+a
+URI
+denoting
+some
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>.
+</dd>
+<dt>
+<a href="#dfn-provenance-query-service">
+<dfn id="dfn-provenance-query-service">
+Provenance
+query
+service
+</dfn>
+</a>
+</dt>
+<dd>
+a
+service
+that
+accesses
+provenance
+given
+a
+query
+containing
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+or
+other
+information
+that
+identifies
+the
+desired
+provenance.
+</dd>
+<dt>
+<a href="#dfn-service-uri">
+<dfn id="dfn-service-uri">
+Service-URI
+</dfn>
+</a>
+</dt>
+<dd>
+the
+URI
+of
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>.
+</dd>
+<dt>
+<del class="diff-old">Forward
+provenance
+provenance
+describing
+how
+a
+resource
+is
+used
+after
+it
+has
+been
+created
+</del>
+<a href="#dfn-pingback-uri">
+<dfn id="dfn-pingback-uri">
+Pingback-URI
+</dfn>
+</a>
+</dt>
+<dd>
+the
+URI
+of
+a
+provenance
+pingback
+service
+that
+can
+receive
+references
+to
+<del class="diff-old">forward
+</del>
+<ins class="diff-chg">additional
+</ins>
+provenance
+<del class="diff-old">.
+</del>
+<ins class="diff-chg">related
+to
+an
+entity.
+</ins>
+</dd>
+<dt>
+<a href="#dfn-accessing">
+<dfn id="dfn-accessing">
+Accessing
+</dfn>
+</a>
+provenance
+records
+</dt>
+<dd>
+given
+the
+identity
+of
+a
+resource,
+the
+process
+of
+discovering
+and
+retrieving
+some
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+(s)
+about
+that
+resource.
+This
+may
+involve
+<a class="internalDFN" href="#dfn-locating">
+locating
+</a>
+a
+provenance
+record,
+then
+performing
+an
+HTTP
+GET
+to
+retrieve
+it,
+or
+locating
+and
+using
+a
+query
+service
+for
+provenance
+about
+an
+identified
+resource,
+or
+some
+other
+mechanism
+not
+covered
+in
+this
+document.
+</dd>
+<dt>
+<a href="#dfn-locating">
+<dfn id="dfn-locating">
+Locating
+</dfn>
+</a>
+provenance
+records
+</dt>
+<dd>
+given
+the
+identity
+of
+a
+resource,
+discovery
+of
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+or
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+that
+may
+be
+used
+to
+obtain
+a
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+about
+that
+resource.
+</dd>
+<dt>
+provenance
+<a href="#dfn-provider">
+<dfn id="dfn-provider">
+provider
+</dfn>
+</a>
+</dt>
+<dd>
+is
+an
+agent
+that
+makes
+available
+provenance
+records.
+</dd>
+<dt>
+provenance
+<a href="#dfn-consumer">
+<dfn id="dfn-consumer">
+consumer
+</dfn>
+</a>
+</dt>
+<dd>
+is
+an
+agent
+that
+receives
+and
+interprets
+provenance
+records.
+</dd>
+</dl>
+<del class="diff-old">The
+pingback
+definition
+is
+new.
+Review
+is
+encouraged.
+This
+document
+uses
+the
+term
+URI
+for
+web
+resource
+identifiers,
+as
+this
+is
+the
+term
+used
+in
+many
+of
+the
+currently
+ratified
+specifications
+that
+this
+document
+builds
+upon.
+In
+many
+situations,
+a
+URI
+may
+also
+be
+an
+IRI
+[
+RFC3987
+],
+which
+is
+a
+generalisation
+of
+a
+URI
+allowing
+a
+wider
+range
+of
+Unicode
+characters.
+Every
+absolute
+URI
+is
+an
+IRI,
+but
+not
+every
+IRI
+is
+an
+URI.
+When
+IRIs
+are
+used
+in
+situations
+that
+require
+a
+URI,
+they
+must
+first
+be
+converted
+according
+to
+the
+mapping
+defined
+in
+section
+3.1
+of
+[
+RFC3987
+].
+A
+notable
+example
+is
+retrieval
+over
+the
+HTTP
+protocol.
+The
+mapping
+involves
+UTF-8
+encoding
+of
+non-ASCII
+characters,
+%-encoding
+of
+octets
+not
+allowed
+in
+URIs,
+and
+Punycode-encoding
+of
+domain
+names.
+</del>
+</section>
+<section id="provenance-and-resources">
+<h3 id="provenance-entities-resources">
+<span class="secno">
+1.2
+</span>
+Provenance
+and
+resources
+</h3>
+<p>
+Fundamentally,
+a
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+is
+<em>
+about
+</em>
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>
+s.
+In
+general,
+resources
+may
+vary
+over
+time
+and
+context.
+E.g.,
+a
+resource
+describing
+the
+weather
+in
+London
+changes
+from
+day-to-day,
+or
+a
+listing
+of
+restaurants
+near
+you
+will
+vary
+depending
+on
+your
+location.
+</p>
+<p>
+Provenance
+records
+a
+history
+of
+the
+entities,
+activities,
+and
+people
+involved
+in
+producing
+an
+artifact,
+and
+may
+be
+collected
+from
+several
+sources
+at
+different
+<del class="diff-old">times.
+</del>
+<ins class="diff-chg">times
+[
+</ins><cite><a class="bibref" href="#bib-PROV-DM"><ins class="diff-chg">
+PROV-DM
+</ins></a></cite><ins class="diff-chg">
+].
+</ins>
+In
+order
+to
+create
+a
+meaningful
+history,
+the
+individual
+provenance
+records
+used
+must
+<del class="diff-old">remain
+valid
+and
+correct
+</del>
+<ins class="diff-chg">retain
+their
+intended
+meaning
+</ins>
+when
+interpreted
+in
+a
+context
+other
+than
+that
+in
+which
+they
+were
+collected.
+<del class="diff-old">Yet
+</del>
+<ins class="diff-chg">Yet,
+</ins>
+we
+may
+still
+want
+to
+make
+provenance
+assertions
+about
+dynamic
+or
+context-dependent
+resources
+(e.g.
+a
+weather
+forecast
+for
+London
+on
+a
+particular
+day
+may
+have
+been
+derived
+from
+a
+particular
+set
+of
+Meteorological
+Office
+data).
+</p>
+<p>
+Provenance
+records
+for
+dynamic
+and
+context-dependent
+resources
+are
+possible
+through
+a
+notion
+of
+constrained
+resources.
+A
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+is
+simply
+a
+resource
+(in
+the
+sense
+defined
+by
+[
+<cite>
+<a class="bibref" href="#bib-WEBARCH">
+WEBARCH
+</a>
+</cite>
+],
+<a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">
+section
+2.2
+</a>
+)
+that
+is
+a
+specialization
+or
+instance
+of
+some
+other
+resource.
+For
+example,
+a
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+specification
+typically
+undergoes
+several
+public
+revisions
+before
+it
+is
+finalized.
+A
+URI
+that
+refers
+to
+the
+"current"
+revision
+might
+be
+thought
+of
+as
+denoting
+the
+specification
+throughout
+its
+lifetime.
+Each
+individual
+revision
+would
+also
+have
+its
+own
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+denoting
+the
+specification
+at
+that
+particular
+stage
+in
+its
+development.
+Using
+these,
+we
+can
+make
+provenance
+assertions
+that
+a
+particular
+revision
+was
+published
+on
+a
+particular
+date,
+and
+was
+last
+modified
+by
+a
+particular
+editor.
+Target-URIs
+may
+use
+any
+URI
+scheme,
+and
+are
+not
+required
+to
+be
+dereferencable.
+</p>
+<p>
+Requests
+for
+provenance
+about
+a
+resource
+may
+return
+provenance
+records
+that
+use
+one
+or
+more
+target-URIs
+to
+refer
+to
+versions
+of
+that
+resource,
+such
+as
+when
+there
+are
+assertions
+referring
+to
+the
+same
+underlying
+resource
+in
+different
+contexts.
+For
+example,
+a
+provenance
+record
+for
+a
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+document
+might
+include
+information
+about
+all
+revisions
+of
+the
+document
+using
+statements
+that
+use
+the
+different
+target-URIs
+of
+the
+various
+revisions.
+</p>
+<p>
+These
+ideas
+are
+represented
+in
+the
+provenance
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+]
+by
+the
+concepts
+<a href="http://www.w3.org/TR/prov-dm/#term-entity" class="externalRef">
+entity
+</a>
+and
+<a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">
+specialization
+</a>.
+In
+particular,
+an
+entity
+may
+be
+a
+specialization
+of
+some
+resource
+whose
+"fixed
+aspects"
+provide
+sufficient
+constraint
+for
+expressed
+provenance
+about
+the
+resource
+to
+be
+invariant
+with
+respect
+to
+that
+entity.
+This
+entity
+is
+itself
+just
+another
+resource
+(e.g.
+the
+weather
+forecast
+for
+a
+give
+date
+as
+opposed
+to
+the
+current
+weather
+forecast),
+with
+its
+own
+URI
+for
+referring
+to
+it
+within
+a
+provenance
+record.
+</p>
+</section>
+<section id="interpreting-provenance-records">
+<h3>
+<span class="secno">
+1.3
+</span>
+Interpreting
+provenance
+records
+</h3>
+<del class="diff-old">Review
+second
+para
+below.
+</del>
+<p>
+The
+mechanisms
+described
+in
+this
+document
+are
+intended
+to
+allow
+a
+provider
+to
+supply
+information
+that
+allows
+a
+consumer
+to
+access
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+s,
+which
+themselves
+explicitly
+identify
+the
+<a class="internalDFN" href="#dfn-entity">
+entities
+</a>
+they
+describe.
+A
+provenance
+record
+may
+contain
+information
+about
+several
+entities,
+referring
+to
+them
+using
+their
+various
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+s.
+<del class="diff-old">Thus
+</del>
+<ins class="diff-chg">Thus,
+</ins>
+a
+consumer
+should
+be
+selective
+in
+its
+use
+of
+the
+information
+provided
+when
+interpreting
+a
+provenance
+record.
+</p>
+<p>
+A
+provenance
+record
+consumer
+will
+need
+to
+isolate
+information
+about
+the
+specific
+entity
+or
+entities
+of
+interest.
+These
+may
+be
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+s
+identified
+by
+separate
+target-URIs
+<del class="diff-old">than
+</del>
+<ins class="diff-chg">that
+differ
+from
+</ins>
+the
+<del class="diff-old">original
+resource,
+</del>
+<ins class="diff-chg">resource
+URI,
+</ins>
+in
+which
+case
+<del class="diff-old">it
+will
+need
+to
+know
+about
+</del>
+the
+<del class="diff-old">target-URIs
+used.
+</del>
+<ins class="diff-chg">consumer
+needs
+to
+discover
+those
+target-URIs.
+</ins>
+The
+mechanisms
+defined
+later
+allow
+a
+provider
+to
+expose
+such
+URIs.
+</p>
+<p>
+While
+a
+provider
+should
+avoid
+giving
+spurious
+information,
+there
+are
+no
+fixed
+semantics,
+particularly
+when
+multiple
+resources
+are
+indicated,
+and
+a
+client
+should
+not
+assume
+that
+a
+specific
+given
+provenance-URI
+will
+yield
+information
+about
+a
+specific
+target-URI.
+In
+the
+general
+case,
+a
+client
+presented
+with
+multiple
+provenance-URIs
+and
+multiple
+target-URIs
+should
+look
+at
+all
+of
+the
+provenance-URIs
+for
+information
+about
+any
+or
+all
+of
+the
+target-URIs.
+</p>
+<p>
+A
+provenance
+record
+is
+not
+of
+itself
+guaranteed
+to
+be
+authoritative
+or
+correct.
+Trust
+in
+provenance
+records
+must
+be
+determined
+separately
+from
+trust
+in
+the
+original
+resource.
+Just
+as
+in
+the
+web
+at
+large,
+it
+is
+a
+user's
+responsibility
+to
+determine
+an
+appropriate
+level
+of
+trust
+in
+any
+other
+resource;
+e.g.
+based
+on
+the
+domain
+that
+serves
+it,
+or
+an
+associated
+digital
+signature.
+(See
+also
+<a href="#security-considerations" class="sectionRef sec-ref">
+section
+6.
+Security
+considerations
+</a>.)
+</p>
+</section>
+<section id="uri-types-and-dereferencing">
+<h3>
+<span class="secno">
+1.4
+</span>
+URI
+types
+and
+dereferencing
+</h3>
+<p>
+A
+number
+of
+resource
+types
+are
+described
+above
+in
+<a href="#concepts" class="sectionRef sec-ref">
+section
+1.1
+Concepts
+</a>.
+The
+table
+below
+summarizes
+what
+these
+various
+URIs
+are
+intended
+to
+denote,
+and
+the
+kind
+of
+information
+that
+should
+be
+returned
+if
+they
+are
+dereferenced:
+</p>
+<table>
+<tbody>
+<tr>
+<th>
+</th>
+<th>
+Denotes
+</th>
+<th>
+Dereferences
+to
+</th>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-target-uri">
+Target-URI
+</a>
+</td>
+<td>
+Any
+resource
+that
+is
+described
+by
+some
+provenance
+-
+typically
+an
+<a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">
+entity
+</a>
+(in
+the
+sense
+of
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+<del class="diff-old">],
+</del>
+<ins class="diff-chg">]),
+</ins>
+but
+may
+be
+<del class="diff-old">an
+</del>
+<ins class="diff-chg">of
+another
+type
+(such
+as
+[
+</ins><cite><a class="bibref" href="#bib-PROV-DM"><ins class="diff-chg">
+PROV-DM
+</ins></a></cite><ins class="diff-chg">
+]
+</ins>
+activity).
+</td>
+<td>
+<del class="diff-old">If
+the
+</del>
+<ins class="diff-chg">Not
+specified
+(the
+</ins>
+URI
+is
+<del class="diff-old">dereferencable,
+it
+should
+return
+a
+representation
+or
+description
+of
+the
+resource
+for
+which
+provenance
+is
+provided.
+</del>
+<ins class="diff-chg">not
+even
+required
+to
+be
+dereferencable).
+</ins>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-provenance-uri">
+Provenance-URI
+</a>
+</td>
+<td>
+A
+provenance
+record,
+or
+provenance
+description,
+in
+the
+sense
+described
+by
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+]
+(
+<a href="http://www.w3.org/TR/prov-dm/#section-prov-overview" class="externalRef">
+PROV
+Overview
+</a>
+).
+</td>
+<td>
+A
+provenance
+record
+in
+any
+defined
+format,
+selectable
+via
+content
+negotiation.
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-service-uri">
+Service-URI
+</a>
+</td>
+<td>
+A
+provenance
+query
+service.
+The
+service-URI
+is
+the
+initial
+URI
+used
+when
+accessing
+a
+provenance
+query
+service;
+following
+REST
+API
+style
+[
+<cite>
+<a class="bibref" href="#bib-REST-APIs">
+REST-APIs
+</a>
+</cite>
+],
+URIs
+for
+accessing
+provenance
+are
+determined
+via
+the
+service
+description.
+</td>
+<td>
+A
+provenance
+query
+service
+description
+per
+<a href="#provenance-query-service-description" class="sectionRef sec-ref">
+section
+4.1
+Provenance
+query
+service
+description
+</a>.
+Alternative
+formats
+may
+be
+offered
+via
+HTTP
+content
+negotiation.
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-pingback-uri">
+Pingback-URI
+</a>
+</td>
+<td>
+A
+provenance
+pingback
+service.
+This
+is
+a
+service
+to
+which
+provenance
+pingback
+information
+can
+be
+submitted
+using
+an
+HTTP
+POST
+operation
+per
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>.
+No
+other
+operations
+are
+specified.
+</td>
+<td>
+None
+specified
+(the
+owner
+of
+a
+provenance
+pingback
+URI
+may
+choose
+to
+return
+useful
+information,
+but
+is
+not
+required
+to
+do
+so.)
+</td>
+</tr>
+</tbody>
+</table>
+<p>
+</p>
+</section>
+</section>
+<section id="accessing-provenance-records">
+<h2>
+<span class="secno">
+2.
+</span>
+Accessing
+provenance
+records
+</h2>
+<p>
+This
+specification
+describes
+two
+ways
+to
+access
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+s:
+</p>
+<ol>
+<li>
+Direct
+access:
+given
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>,
+simply
+dereference
+it,
+and
+</li>
+<li>
+Indirectly
+via
+a
+query
+service:
+given
+the
+URIs
+of
+some
+resource
+(or
+maybe
+other
+information)
+and
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>,
+use
+the
+service
+to
+access
+provenance
+of
+the
+resource.
+</li>
+</ol>
+<p>
+Web
+applications
+may
+access
+a
+provenance
+record
+in
+the
+same
+way
+as
+any
+resource
+on
+the
+Web,
+by
+dereferencing
+its
+URI
+(commonly
+using
+an
+HTTP
+GET
+operation).
+Thus,
+any
+provenance
+record
+may
+be
+associated
+with
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>,
+and
+may
+be
+accessed
+by
+dereferencing
+that
+URI
+using
+web
+mechanisms.
+How
+much
+or
+how
+little
+provenance
+is
+returned
+in
+a
+provenance
+record
+is
+a
+matter
+for
+the
+provider,
+taking
+account
+that
+a
+provenance
+trace
+may
+extend
+as
+linked
+data
+across
+multiple
+provenance
+records.
+</p>
+<p>
+When
+there
+is
+no
+easy
+way
+to
+associate
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+with
+a
+resource
+(e.g.
+for
+resources
+not
+directly
+web-accessible,
+or
+whose
+publication
+mechanism
+is
+controlled
+by
+someone
+else),
+a
+provenance
+description
+may
+be
+obtained
+using
+a
+provenance
+query
+service
+at
+an
+indicated
+<a class="internalDFN" href="#dfn-service-uri">
+service-uri
+</a>.
+A
+REST
+protocol
+for
+provenance
+queries
+is
+defined
+in
+Section
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+;
+also
+described
+there
+is
+a
+mechanism
+for
+locating
+a
+SPARQL
+query
+service
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+].
+</p>
+<p>
+When
+publishing
+provenance,
+corresponding
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+s
+or
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+s
+should
+be
+discoverable
+using
+one
+or
+more
+of
+the
+mechanisms
+described
+in
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>.
+</p>
+<div class="note">
+<div class="note-title" role="heading" aria-level="3">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Provenance
+may
+be
+presented
+as
+a
+<a href="http://www.w3.org/TR/prov-dm/#component4" class="externalRef">
+bundle
+</a>,
+which
+is
+"
+<cite>
+a
+named
+set
+of
+provenance
+descriptions,
+and
+is
+itself
+an
+entity,
+so
+allowing
+provenance
+of
+provenance
+to
+be
+expressed
+</cite>
+"
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+].
+A
+provenance
+description
+at
+a
+dereferencable
+provenance-URI
+may
+be
+treated
+as
+a
+bundle,
+and
+this
+is
+a
+good
+way
+to
+make
+provenance
+easily
+accessible.
+But
+there
+are
+other
+possible
+implementations
+of
+a
+bundle,
+such
+as
+a
+named
+graph
+in
+an
+RDF
+dataset
+[
+<cite>
+<a class="bibref" href="#bib-RDF-CONCEPTS11">
+RDF-CONCEPTS11
+</a>
+</cite>
+],
+for
+which
+the
+bundle
+URI
+may
+not
+be
+directly
+dereferencable.
+<br>
+<br>
+When
+a
+bundle
+is
+published
+as
+part
+of
+an
+RDF
+Dataset,
+to
+access
+it
+would
+require
+accessing
+the
+RDF
+Dataset
+and
+then
+extracting
+the
+identified
+graph
+component;
+this
+in
+turn
+would
+require
+knowing
+a
+URI
+or
+some
+other
+way
+to
+retrieve
+the
+RDF
+dataset.
+This
+specification
+does
+not
+describe
+a
+specific
+mechanism
+for
+extracting
+components
+from
+a
+document
+containing
+multiple
+graphs.
+<br>
+<br>
+The
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Linked
+Data
+Platform
+group
+(
+<a href="http://www.w3.org/2012/ldp/" class="externalRef">
+www.w3.org/2012/ldp/
+</a>
+)
+is
+chartered
+to
+produce
+a
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Recommendation
+for
+HTTP-based
+(RESTful)
+application
+integration
+patterns
+using
+read/write
+Linked
+Data;
+we
+anticipate
+that
+they
+may
+address
+access
+to
+RDF
+Datasets
+in
+due
+course.
+</p>
+</div>
+</section>
+<section id="locating-provenance-records">
+<h2>
+<span class="secno">
+3.
+</span>
+Locating
+provenance
+records
+</h2>
+<p>
+A
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+can
+be
+accessed
+using
+direct
+web
+retrieval,
+given
+its
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>.
+If
+this
+is
+known
+in
+advance,
+there
+is
+nothing
+more
+to
+specify.
+If
+a
+provenance-URI
+is
+not
+known
+then
+a
+mechanism
+to
+discover
+one
+must
+be
+based
+on
+information
+that
+is
+available
+to
+the
+would-be
+accessor.
+Likewise,
+provenance
+may
+be
+exposed
+by
+a
+query
+service,
+in
+which
+case,
+the
+corresponding
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+must
+be
+discovered.
+</p>
+<p>
+Three
+mechanisms
+are
+defined
+for
+a
+provenance
+<a class="internalDFN" href="#dfn-consumer">
+consumer
+</a>
+to
+find
+information
+about
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+or
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>,
+along
+with
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>:
+</p>
+<ol>
+<li>
+The
+consumer
+knows
+the
+resource
+URI
+<em>
+and
+</em>
+the
+resource
+is
+accessible
+using
+HTTP
+</li>
+<li>
+The
+consumer
+has
+a
+copy
+of
+a
+resource
+represented
+as
+HTML
+or
+XHTML
+</li>
+<li>
+The
+consumer
+has
+a
+copy
+of
+a
+resource
+represented
+as
+RDF
+(including
+the
+range
+of
+possible
+RDF
+syntaxes,
+such
+as
+HTML
+with
+embedded
+RDFa)
+</li>
+</ol>
+<p>
+These
+particular
+cases
+are
+selected
+as
+corresponding
+to
+current
+primary
+web
+protocol
+and
+data
+formats.
+Similar
+approaches
+may
+be
+defined
+for
+other
+protocols
+or
+resource
+formats.
+</p>
+<p>
+Provenance
+records
+may
+be
+offered
+by
+several
+<a class="internalDFN" href="#dfn-provider">
+provider
+</a>
+s
+other
+than
+that
+of
+the
+original
+resource
+publisher,
+each
+with
+different
+concerns,
+and
+presenting
+provenance
+at
+different
+locations.
+It
+is
+possible
+that
+these
+different
+providers
+may
+present
+contradictory
+provenance.
+</p>
+<section id="resource-accessed-by-http">
+<h3>
+<span class="secno">
+3.1
+</span>
+Resource
+accessed
+by
+HTTP
+</h3>
+<p>
+For
+a
+resource
+accessible
+using
+HTTP,
+a
+provenance
+record
+may
+be
+indicated
+using
+an
+HTTP
+<code>
+Link
+</code>
+header
+field,
+as
+defined
+by
+<a href="http://tools.ietf.org/html/rfc5988#section-5" class="externalRef">
+Web
+Linking
+(RFC
+5988)
+</a>
+[
+<cite>
+<a class="bibref" href="#bib-LINK-REL">
+LINK-REL
+</a>
+</cite>
+].
+The
+<code>
+Link
+</code>
+header
+field
+is
+included
+in
+the
+HTTP
+response
+to
+a
+GET
+or
+HEAD
+operation
+(other
+HTTP
+operations
+are
+not
+excluded,
+but
+are
+not
+considered
+here).
+</p>
+<p>
+A
+<code>
+has_provenance
+</code>
+link
+relation
+type
+for
+referencing
+a
+provenance
+record
+may
+be
+used
+thus:
+</p>
+ <pre class="pattern">Link: <<cite>provenance-URI</cite>>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+anchor="
+<cite>
+target-URI
+</cite>
+"
+</pre>
+<p>
+When
+used
+in
+conjunction
+with
+an
+HTTP
+success
+response
+code
+(
+<code>
+2xx
+</code>
+),
+this
+HTTP
+header
+field
+indicates
+that
+<code>
+<cite>
+provenance-URI
+</cite>
+</code>
+is
+the
+URI
+of
+a
+provenance
+record
+about
+the
+originally
+requested
+resource,
+and
+that
+the
+requested
+resource
+is
+identified
+within
+the
+provenance
+record
+as
+<code>
+<cite>
+target-URI
+</cite>
+</code>.
+(See
+also
+<a href="#interpreting-provenance-records" class="sectionRef sec-ref">
+section
+1.3
+Interpreting
+provenance
+records
+</a>.)
+</p>
+<p>
+If
+no
+<code>
+anchor
+</code>
+parameter
+is
+provided
+then
+the
+<code>
+<cite>
+target-URI
+</cite>
+</code>
+is
+assumed
+to
+be
+the
+URI
+of
+the
+requested
+resource
+used
+in
+the
+corresponding
+HTTP
+request.
+</p>
+<p>
+This
+<del class="diff-old">specification
+</del>
+<ins class="diff-chg">note
+</ins>
+does
+not
+define
+the
+meaning
+of
+these
+links
+returned
+with
+other
+HTTP
+response
+codes:
+future
+revisions
+may
+define
+interpretations
+for
+these.
+</p>
+<p>
+An
+HTTP
+response
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+include
+multiple
+<code>
+has_provenance
+</code>
+link
+header
+fields,
+indicating
+a
+number
+of
+different
+provenance
+resources
+(and
+anchors)
+that
+are
+known
+to
+the
+responding
+server,
+each
+referencing
+a
+provenance
+record
+about
+the
+accessed
+resource.
+</p>
+<p>
+The
+presence
+of
+a
+<code>
+has_provenance
+</code>
+link
+in
+an
+HTTP
+response
+does
+not
+preclude
+the
+possibility
+that
+other
+providers
+<ins class="diff-new">also
+</ins>
+may
+offer
+provenance
+records
+about
+the
+same
+resource.
+In
+such
+cases,
+discovery
+of
+the
+additional
+provenance
+records
+must
+use
+other
+means
+(e.g.
+see
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+).
+</p>
+<p>
+An
+example
+<del class="diff-old">request
+</del>
+<ins class="diff-chg">HTTP
+response
+</ins>
+including
+provenance
+headers
+<del class="diff-old">in
+its
+response
+</del>
+might
+look
+like
+this
+(where
+<code>
+C:
+</code>
+and
+<code>
+S:
+</code>
+prefixes
+indicate
+client
+and
+server
+emitted
+data
+respectively):
+</p>
+<del class="diff-old"> C: GET http://example.com/resource/ HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+<del class="diff-old">S: Link: <http://example.com/resource/provenance/>;
+</del>
+<ins class="diff-chg">S: Link: <http://example.com/resource123/provenance/>;
+</ins>
+ rel="http://www.w3.org/ns/prov#has_provenance";
+<del class="diff-old"> anchor="http://example.com/resource/"
+</del>
+<ins class="diff-chg"> anchor="http://example.com/resource123/"
+</ins>
+S:
+S: <html ...>
+S: :
+S:
+</html>
+</pre>
+</div>
+<del class="diff-old">Tim
+comment
+(14):
+Should
+a
+reference
+to
+the
+forward
+provenance
+section
+be
+included,
+too?
+[GK]
+I
+don't
+see
+the
+need.
+Forward
+provenance
+is
+not
+primarily
+*about*
+the
+same
+resource,
+IMO,
+and
+I
+think
+mentioning
+it
+here
+could
+be
+more
+confusing
+than
+helpful.
+</del>
+<section id="specifying-provenance-query-services">
+<h4>
+<span class="secno">
+3.1.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</h4>
+<p>
+The
+resource
+provider
+may
+indicate
+that
+provenance
+records
+about
+the
+resource
+are
+provided
+by
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>.
+This
+is
+done
+through
+the
+use
+of
+a
+<code>
+has_query_service
+</code>
+link
+relation
+type
+following
+the
+same
+pattern
+as
+above:
+</p>
+ <pre class="pattern">Link: <<cite>service-URI</cite>>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="<cite>target-URI</cite>"
+</pre>
+<p>
+The
+<code>
+has_query_service
+</code>
+link
+identifies
+the
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>.
+Dereferencing
+this
+URI
+yields
+a
+service
+description
+that
+provides
+further
+information
+to
+enable
+a
+client
+to
+submit
+a
+query
+to
+retrieve
+a
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+for
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>
+;
+see
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+for
+more
+details.
+</p>
+ <div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+<ins class="diff-new">C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource123/provenance-query/>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://example.com/resource123/"
+S:
+S: <html ...>
+S: :
+S:
+</html>
+</ins></pre></div>
+<p>
+There
+<del class="diff-old">may
+</del>
+<em class="rfc2119" title="MAY">
+<ins class="diff-chg">MAY
+</ins></em>
+be
+multiple
+<code>
+has_query_service
+</code>
+link
+header
+fields,
+and
+these
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+appear
+in
+an
+HTTP
+response
+together
+with
+<code>
+has_provenance
+</code>
+link
+header
+fields.
+</p>
+<del class="diff-old"> C: GET http://example.com/resource/ HTTP/1.1
+C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource/provenance/>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://example.com/resource/"
+S:
+S: <html ...>
+S: :
+S:
+</html>
+</del>
+</section>
+<section id="content-negotiation-redirection-and-link-headers">
+<h4>
+<span class="secno">
+3.1.2
+</span>
+Content
+negotiation,
+redirection
+and
+Link:
+headers
+</h4>
+<p>
+When
+performing
+content
+negotiation
+for
+a
+resource,
+it
+is
+common
+for
+HTTP
+302
+or
+303
+redirect
+response
+codes
+to
+be
+used
+to
+direct
+a
+client
+to
+an
+appropriately-formatted
+resource.
+When
+accessing
+a
+resource
+for
+which
+provenance
+is
+available,
+link
+headers
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+included
+with
+the
+response
+to
+the
+final
+redirected
+request,
+and
+not
+on
+the
+intermediate
+303
+responses.
+(When
+accessing
+a
+resource
+from
+a
+browser
+using
+Javascript,
+the
+intermediate
+303
+responses
+are
+usually
+handled
+transparently
+by
+the
+browser
+and
+are
+not
+visible
+to
+the
+HTTP
+client
+code.)
+</p>
+<p>
+Following
+content
+negotiation,
+any
+provenance
+link
+returned
+refers
+to
+the
+resource
+whose
+URI
+is
+used
+in
+the
+corresponding
+HTTP
+request,
+or
+the
+given
+anchor
+parameter
+if
+that
+is
+different.
+</p>
+<p>
+An
+example
+transaction
+using
+content
+negotiation
+and
+redirection
+might
+look
+like
+this
+(where
+<code>
+C:
+</code>
+and
+<code>
+S:
+</code>
+prefixes
+indicate
+client
+and
+server
+emitted
+data
+respectively):
+</p>
+<del class="diff-old"> C: GET http://example.com/resource/ HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+S: HTTP/1.1 302 Found
+<del class="diff-old">S: Location: /resource/content.html
+</del>
+<ins class="diff-chg">S: Location: /resource123/content.html
+</ins>
+S: Vary: Accept
+S:
+<del class="diff-old">S: HTML content for http://example.com/resource/
+S: is available at http://example.com/resource/content.html
+</del>
+<ins class="diff-chg">S: HTML content for http://example.com/resource123/
+S: is available at http://example.com/resource123/content.html
+</ins>
+<del class="diff-old">C: GET http://example.com/resource/content.html HTTP/1.1
+</del>
+<ins class="diff-chg">C: GET http://example.com/resource123/content.html HTTP/1.1
+</ins>
+C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+<del class="diff-old">S: Link: <http://example.com/resource/provenance/>;
+</del>
+<ins class="diff-chg">S: Link: <http://example.com/resource123/provenance/>;
+</ins>
+ rel="http://www.w3.org/ns/prov#has_provenance";
+<del class="diff-old"> anchor="http://example.com/resource/20130226/content.html"
+</del>
+<ins class="diff-chg"> anchor="http://example.com/resource123/20130226/content.html"
+</ins>
+S:
+S: <html>
+S: <!-- HTML content here... -->
+S:
+</html>
+</pre>
+</div>
+<p>
+<ins class="diff-new">This
+example
+indicates
+a
+provenance
+record
+at
+</ins><code><ins class="diff-new">
+http://example.com/resource123/provenance/
+</ins></code>,<ins class="diff-new">
+which
+uses
+</ins><code><ins class="diff-new">
+http://example.com/resource123/20130226/content.html
+</ins></code><ins class="diff-new">
+as
+the
+target-URI
+for
+the
+requested
+resource.
+If
+the
+</ins><code><ins class="diff-new">
+anchor=
+</ins></code><ins class="diff-new">
+parameter
+were
+to
+be
+omitted
+from
+the
+</ins><code><ins class="diff-new">
+Link
+</ins></code><ins class="diff-new">
+header
+field,
+the
+indicated
+target-URI
+would
+be
+</ins><code><ins class="diff-new">
+http://example.com/resource123/content.html
+</ins></code>.</p>
+</section>
+</section>
+<section id="resource-represented-as-html">
+<h3>
+<span class="secno">
+3.2
+</span>
+Resource
+represented
+as
+HTML
+</h3>
+<div>
+For
+a
+document
+presented
+as
+HTML
+or
+XHTML,
+without
+regard
+for
+how
+it
+has
+been
+obtained,
+a
+provenance
+record
+may
+be
+associated
+with
+a
+resource
+by
+adding
+a
+<code>
+<link>
+</code>
+element
+to
+the
+HTML
+<code>
+<head>
+</code>
+section.
+Two
+link
+relation
+types
+for
+referencing
+provenance
+may
+be
+used:
+<del class="diff-old"> <html xmlns="http://www.w3.org/1999/xhtml">
+</del>
+ <pre class="pattern"> <html>
+ <head>
+ <b><link rel="http://www.w3.org/ns/prov#has_provenance" href="<cite>provenance-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ <!-- HTML content here... -->
+ </body>
+</html>
+</pre>
+</div>
+<p>
+The
+<code>
+<cite>
+provenance-URI
+</cite>
+</code>
+given
+by
+the
+first
+link
+element
+(
+<code>
+#has_provenance
+</code>
+)
+identifies
+the
+provenance-URI
+for
+the
+document.
+</p>
+<p>
+The
+<code>
+<cite>
+target-URI
+</cite>
+</code>
+given
+by
+the
+second
+link
+element
+(
+<code>
+#has_anchor
+</code>
+)
+specifies
+an
+identifier
+for
+the
+document
+that
+may
+be
+used
+within
+the
+provenance
+record
+when
+referring
+to
+the
+document.
+</p>
+<p>
+If
+no
+<code>
+<cite>
+target-URI
+</cite>
+</code>
+is
+provided
+(via
+a
+<code>
+#has_anchor
+</code>
+link
+element)
+then
+is
+it
+is
+assumed
+to
+be
+the
+URI
+of
+the
+document.
+It
+is
+<em class="rfc2119" title="RECOMMENDED">
+RECOMMENDED
+</em>
+that
+this
+convention
+be
+used
+only
+when
+the
+document
+has
+a
+URI
+that
+is
+reasonably
+expected
+to
+be
+known
+or
+easily
+discoverable
+by
+a
+consumer
+of
+the
+document
+(e.g.
+when
+delivered
+from
+a
+web
+server,
+or
+as
+part
+of
+a
+MIME
+structure
+containing
+content
+identifiers
+[
+<cite>
+<a class="bibref" href="#bib-RFC2392">
+RFC2392
+</a>
+</cite>
+]).
+</p>
+<p>
+An
+HTML
+document
+header
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+present
+multiple
+<code>
+<cite>
+provenance-URI
+</cite>
+</code>
+s
+over
+several
+<code>
+#has_provenance
+</code>
+link
+elements,
+indicating
+a
+number
+of
+different
+provenance
+records
+that
+are
+known
+to
+the
+publisher
+of
+the
+document,
+each
+of
+which
+may
+provide
+provenance
+about
+the
+document
+(see
+<a href="#interpreting-provenance-records" class="sectionRef sec-ref">
+section
+1.3
+Interpreting
+provenance
+records
+</a>
+).
+</p>
+<del class="diff-old">Check
+</del>
+<div class="note">
+<div class="note-title" role="heading" aria-level="4">
+<span>
+<ins class="diff-chg">Note
+</ins></span></div><p class=""><ins class="diff-chg">
+The
+mechanisms
+used
+</ins>
+with
+<del class="diff-old">Dong:
+I
+think
+the
+cross
+reference
+should
+make
+the
+assumptions
+explicit.
+I,
+too,
+feel
+this
+material
+is
+not
+strictly
+needed,
+but
+was
+previously
+asked
+</del>
+<ins class="diff-chg">HTTP
+and
+HTML/RDF
+are
+slightly
+inconsistent
+in
+their
+approach
+</ins>
+to
+<del class="diff-old">add
+some
+clarification
+about
+mutliple
+links.
+</del>
+<ins class="diff-chg">specifying
+</ins><code><cite><ins class="diff-chg">
+target-URI
+</ins></cite></code><ins class="diff-chg">
+values.
+In
+HTTP
+</ins><code><ins class="diff-chg">
+Link
+</ins></code><ins class="diff-chg">
+header
+fields,
+an
+optional
+</ins><code><ins class="diff-chg">
+anchor=
+</ins></code><ins class="diff-chg">
+parameter
+may
+be
+supplied
+for
+each
+such
+header.
+In
+HTML
+and
+RDF,
+separate
+</ins><code><ins class="diff-chg">
+#has_anchor
+</ins></code><ins class="diff-chg">
+relations
+are
+defined.
+It
+was
+felt
+that
+avoiding
+reinvention
+of
+existing
+mechanisms
+was
+more
+important
+than
+being
+completely
+consistent.
+If
+anchors
+are
+processed
+as
+described
+in
+</ins><a href="#interpreting-provenance-records" class="sectionRef sec-ref"><ins class="diff-chg">
+section
+1.3
+Interpreting
+provenance
+records
+</ins></a><ins class="diff-chg">
+(3rd
+paragraph),
+observable
+behaviour
+across
+all
+approaches
+should
+be
+consistent.
+</ins>
+</p>
+</div>
+<section id="specifying-provenance-query-services-1">
+<h4>
+<span class="secno">
+3.2.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</h4>
+<p>
+The
+document
+creator
+may
+specify
+that
+the
+provenance
+about
+the
+document
+is
+provided
+by
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>.
+This
+is
+done
+through
+the
+use
+of
+a
+third
+link
+relation
+type
+following
+the
+same
+pattern
+as
+above:
+</p>
+ <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <b><link rel="http://www.w3.org/ns/prov#has_query_service" href="<cite>service-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ <!-- HTML content here... -->
+ </body>
+</html>
+</pre>
+<p>
+The
+<code>
+has_query_service
+</code>
+link
+element
+identifies
+the
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>.
+Dereferencing
+this
+URI
+yields
+a
+service
+description
+that
+provides
+further
+information
+to
+enable
+a
+client
+to
+query
+for
+provenance
+about
+a
+resource;
+see
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+for
+more
+details.
+</p>
+<p>
+There
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+be
+multiple
+<code>
+#has_query_service
+</code>
+link
+elements,
+and
+these
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+appear
+in
+the
+same
+document
+as
+<code>
+#has_provenance
+</code>
+link
+elements
+(though
+we
+do
+not
+anticipate
+that
+<code>
+#has_provenance
+</code>
+and
+<code>
+#has_query_service
+</code>
+link
+relations
+will
+commonly
+be
+used
+together).
+</p>
+<del class="diff-old">Check
+with
+Dong:
+This
+test
+was
+already
+revised
+in
+response
+to
+earlier
+comment.
+I,
+too,
+feel
+this
+material
+is
+not
+strictly
+needed,
+but
+was
+previously
+asked
+to
+add
+some
+clarification.
+</del>
+</section>
+</section>
+<section id="resource-represented-as-rdf">
+<h3>
+<span class="secno">
+3.3
+</span>
+Resource
+represented
+as
+RDF
+</h3>
+<p>
+If
+a
+resource
+is
+represented
+as
+RDF
+(in
+any
+of
+its
+recognized
+syntaxes,
+including
+RDFa),
+it
+may
+contain
+references
+to
+its
+own
+provenance
+using
+additional
+RDF
+statements.
+For
+this
+<del class="diff-old">purpose
+</del>
+<ins class="diff-chg">purpose,
+</ins>
+the
+link
+relations
+introduced
+above
+(
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>
+)
+may
+be
+used
+as
+RDF
+properties:
+<code>
+prov:has_provenance
+</code>,
+<code>
+prov:has_anchor
+</code>,
+and
+<code>
+prov:has_query_service
+</code>,
+where
+the
+<code>
+prov:
+</code>
+prefix
+here
+indicates
+the
+PROV
+namespace
+URI
+<code>
+http://www.w3.org/ns/prov#
+</code>.
+</p>
+<p>
+The
+RDF
+property
+<code>
+prov:has_provenance
+</code>
+is
+a
+relation
+between
+two
+resources,
+where
+the
+object
+of
+the
+property
+is
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+that
+denotes
+a
+provenance
+record
+about
+the
+subject
+resource.
+Multiple
+<code>
+prov:has_provenance
+</code>
+assertions
+may
+be
+made
+about
+a
+subject
+resource.
+</p>
+<p>
+Property
+<code>
+prov:has_anchor
+</code>
+specifies
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+used
+in
+the
+indicated
+provenance
+to
+refer
+to
+the
+containing
+RDF
+document.
+</p>
+<p>
+Property
+<code>
+prov:has_query_service
+</code>
+specifies
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+for
+provenance
+queries.
+</p>
+ <div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example code">@prefix prov: <http://www.w3.org/ns/prov#>.
+<> dcterms:title "Welcome to example.com" ;
+ prov:has_anchor <http://example.com/data/resource.rdf> ;
+ prov:has_provenance <http://example.com/provenance/resource.rdf> ;
+ prov:has_query_service <http://example.com/provenance-query-service/> .
+#
+(More
+RDF
+data
+...)
+</pre>
+</div>
+<p>
+(The
+above
+example
+uses
+Turtle
+RDF
+syntax
+[
+<cite>
+<a class="bibref" href="#bib-TURTLE">
+TURTLE
+</a>
+</cite>
+].)
+</p>
+<div class="note">
+<div class="note-title" role="heading" aria-level="4">
+<span>
+Note
+</span>
+</div>
+<p class="">
+These
+terms
+(
+<code>
+prov:has_provenance
+</code>,
+<code>
+prov:has_anchor
+</code>,
+and
+<code>
+prov:has_query_service
+</code>
+)
+may
+be
+also
+used
+in
+RDF
+statements
+with
+other
+subjects
+to
+indicate
+provenance
+of
+other
+resources,
+but
+discussion
+of
+such
+use
+is
+beyond
+the
+scope
+of
+this
+document.
+<br>
+<br>
+<ins class="diff-new">See
+also
+the
+note
+about
+target-URIs
+at
+the
+end
+of
+</ins><a href="#resource-represented-as-html" class="sectionRef sec-ref"><ins class="diff-new">
+section
+3.2
+Resource
+represented
+as
+HTML
+</ins></a>.
+</p>
+</div>
+</section>
+</section>
+<section id="provenance-query-services">
+<h2>
+<span class="secno">
+4.
+</span>
+Provenance
+query
+services
+</h2>
+<p>
+This
+section
+describes
+a
+simple
+HTTP
+query
+protocol
+for
+accessing
+provenance
+records,
+and
+also
+a
+mechanism
+for
+locating
+a
+SPARQL
+service
+endpoint
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+].
+The
+HTTP
+<ins class="diff-new">query
+</ins>
+protocol
+specifies
+HTTP
+operations
+<ins class="diff-new">[
+</ins><cite><a class="bibref" href="#bib-HTTP11"><ins class="diff-new">
+HTTP11
+</ins></a></cite><ins class="diff-new">
+]
+</ins>
+for
+retrieving
+provenance
+records
+from
+a
+provenance
+query
+service,
+following
+the
+approach
+of
+the
+SPARQL
+Graph
+Store
+HTTP
+Protocol
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-HTTP">
+SPARQL-HTTP
+</a>
+</cite>
+].
+</p>
+<p>
+The
+introduction
+of
+query
+services
+is
+motivated
+by
+the
+following
+possible
+considerations:
+</p>
+<ul>
+<li>
+third-party
+providers
+of
+provenance
+descriptions
+may
+be
+unable
+to
+use
+the
+mechanisms
+of
+Section
+3
+because
+the
+corresponding
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+is
+outside
+their
+control;
+</li>
+<li>
+services
+unknown
+to
+the
+original
+publisher
+may
+have
+provenance
+records
+about
+the
+same
+resource;
+</li>
+<li>
+there
+is
+no
+known
+dereferencable
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+or
+a
+particular
+entity;
+</li>
+<li>
+query
+services
+may
+provide
+additional
+filters
+over
+what
+provenance
+is
+returned;
+and
+</li>
+<li>
+query
+services
+may
+support
+more
+expressive
+selections,
+such
+as
+"which
+entities
+were
+derived
+from
+entities
+attributed
+to
+agent
+X".
+</li>
+</ul>
+<p>
+The
+patterns
+for
+using
+provenance
+query
+services
+are
+designed
+around
+REST
+principles
+[
+<cite>
+<a class="bibref" href="#bib-REST">
+REST
+</a>
+</cite>
+],
+which
+aim
+to
+minimize
+coupling
+between
+client
+and
+server
+implementation
+details.
+</p>
+<p>
+The
+query
+mechanisms
+provided
+by
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>
+are
+described
+by
+a
+service
+description,
+which
+is
+obtained
+by
+dereferencing
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>.
+A
+service
+description
+may
+contain
+information
+about
+additional
+mechanisms
+that
+are
+not
+described
+here.
+In
+keeping
+with
+REST
+practice
+for
+web
+applications,
+alternative
+service
+descriptions
+using
+different
+formats
+may
+be
+offered
+and
+accessed
+using
+HTTP
+content
+negotiation.
+We
+describe
+below
+a
+service
+description
+format
+that
+uses
+RDF
+to
+describe
+two
+query
+mechanisms.
+</p>
+<p>
+The
+general
+procedure
+for
+using
+a
+provenance
+query
+service
+is:
+</p>
+<ol>
+<li>
+retrieve
+the
+service
+description;
+</li>
+<li>
+within
+the
+service
+description,
+locate
+information
+about
+a
+recognized
+query
+mechanism
+(ignoring
+unrecognized
+descriptions
+if
+the
+description
+covers
+multiple
+service
+options);
+</li>
+<li>
+if
+a
+recognized
+query
+mechanism
+is
+found,
+extract
+information
+needed
+to
+use
+that
+mechanism
+(e.g.
+a
+URI
+template
+or
+a
+SPARQL
+service
+endpoint
+URI);
+and
+</li>
+<li>
+use
+the
+information
+obtained
+to
+query
+for
+required
+provenance,
+using
+the
+selected
+query
+mechanism.
+</li>
+</ol>
+<p>
+The
+remainder
+of
+this
+section
+covers
+the
+following
+topics:
+</p>
+<ul>
+<li>
+<a class="sectionRef sec-ref" href="#provenance-query-service-description">
+section
+4.1
+Provenance
+query
+service
+description
+</a>
+-
+describes
+an
+RDF-based
+service
+description
+format
+and
+vocabularies
+to
+convey
+information
+about
+direct
+HTTP
+query
+and/or
+SPARQL
+service
+options.
+<ul>
+<li>
+<a class="sectionRef sec-ref" href="#direct-http-query-service-description">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>
+-
+RDF
+structure
+for
+describing
+a
+direct
+HTTP
+query
+service.
+</li>
+</ul>
+<ul>
+<li>
+<a class="sectionRef sec-ref" href="#sparql-query-service-description">
+section
+4.1.2
+SPARQL
+query
+service
+description
+</a>
+-
+RDF
+structure
+for
+describing
+a
+SPARQL
+query
+service.
+</li>
+</ul>
+</li>
+<li>
+<a class="sectionRef sec-ref" href="#direct-http-query-service-invocation">
+section
+4.2
+Direct
+HTTP
+query
+service
+invocation
+</a>
+-
+describes
+how
+to
+perform
+a
+direct
+HTTP
+query
+for
+provenance,
+using
+information
+obtained
+from
+the
+service
+description.
+</li>
+<li>
+<a class="sectionRef sec-ref" href="#provenance-query-service-discovery">
+section
+4.3
+Provenance
+query
+service
+discovery
+</a>
+-
+briefly
+discusses
+some
+possible
+approaches
+to
+discovery
+of
+provenance
+query
+services.
+</li>
+</ul>
+<section id="provenance-query-service-description">
+<h3>
+<span class="secno">
+4.1
+</span>
+Provenance
+query
+service
+description
+</h3>
+<del class="diff-old">Review.
+Stian
+suggests
+recommending
+use
+of
+JSON-LD.
+I
+am
+resisting
+this
+because
+it
+is
+clearly
+allowed
+by
+"RDF
+(in
+any
+of
+its
+common
+serializations
+as
+determined
+by
+HTTP
+content
+negotiation)",
+focusing
+on
+a
+particular
+format
+as
+part
+of
+the
+underlying
+mechanism
+seems
+to
+go
+against
+REST
+principles,
+and
+at
+this
+stage
+it
+seems
+that
+promoting
+any
+particular
+format
+will
+draw
+objections
+from
+proponents
+of
+other
+formats.
+I've
+taken
+a
+different
+tack,
+making
+the
+text
+more
+open
+about
+possible
+service
+description
+formats,
+while
+specifically
+presenting
+a
+description
+based
+on
+the
+RDF
+model.
+</del>
+<p>
+Dereferencing
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+yields
+a
+service
+description.
+The
+service
+description
+<del class="diff-old">presented
+here
+</del>
+may
+be
+<del class="diff-old">supplied
+as
+RDF
+(in
+</del>
+<ins class="diff-chg">in
+</ins>
+any
+<del class="diff-old">of
+its
+common
+serializations
+as
+determined
+by
+HTTP
+</del>
+<ins class="diff-chg">format
+selectable
+through
+</ins>
+content
+<del class="diff-old">negotiation),
+</del>
+<ins class="diff-chg">negotiation,
+</ins>
+and
+it
+may
+contain
+descriptions
+of
+one
+or
+more
+available
+query
+mechanisms.
+<del class="diff-old">Each
+</del>
+<ins class="diff-chg">The
+format
+described
+here
+uses
+RDF,
+serialized
+as
+Turtle
+[
+</ins><cite><a class="bibref" href="#bib-TURTLE"><ins class="diff-chg">
+TURTLE
+</ins></a></cite><ins class="diff-chg">
+],
+but
+any
+selectable
+RDF
+serialization
+could
+be
+used.
+In
+this
+RDF
+service
+description,
+each
+</ins>
+query
+mechanism
+is
+associated
+with
+an
+RDF
+type,
+as
+explained
+below.
+<del class="diff-old">(The
+presentation
+here
+of
+RDF
+service
+descriptions
+does
+not
+preclude
+use
+of
+non-RDF
+formats
+selectable
+by
+HTTP
+content
+negotiation.)
+</del>
+</p>
+<p>
+The
+overall
+structure
+of
+a
+service
+description
+is
+as
+follows:
+</p>
+ <pre class="pattern"><<cite>service-URI</cite>> a prov:ServiceDescription ;
+ prov:describesService <<cite>direct-query-description</cite>>, <<cite>sparql-query-description</cite>> .
+<<cite>direct-query-description</cite>> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "<cite>direct-query-template</cite>"
+ .
+<<cite>sparql-query-description</cite>> a sd:Service ;
+ sd:endpoint <<cite>sparql-query</cite>> ;
+ # other details...
+ .
+</pre>
+<p>
+We
+see
+here
+that
+the
+<code>
+<cite>
+service-URI
+</cite>
+</code>
+identifies
+a
+resource
+of
+type
+<code>
+prov:ServiceDescription
+</code>,
+which
+collects
+descriptions
+of
+one
+or
+more
+provenance
+query
+mechanisms.
+Each
+associated
+mechanism
+is
+indicated
+by
+a
+<code>
+prov:describesService
+</code>
+statement.
+</p>
+<del class="diff-old">Note
+We
+expect
+the
+presentation
+of
+service
+descriptions
+to
+be
+considered
+by
+the
+W3C
+Linked
+Data
+Platform
+group
+(
+www.w3.org/2012/ldp/
+);
+at
+the
+time
+of
+writing,
+there
+is
+no
+consensus
+(cf.
+message
+at
+lists.w3.org/Archives/Public/public-ldp/2012Nov/0036.html
+and
+responses).
+As
+and
+when
+such
+consensus
+emerges,
+we
+recommend
+that
+provenance
+query
+service
+implementers
+consider
+adopting
+it,
+or
+at
+least
+consider
+making
+their
+implementations
+compatible
+with
+it.
+</del>
+<section id="direct-http-query-service-description">
+<h4>
+<span class="secno">
+4.1.1
+</span>
+Direct
+HTTP
+query
+service
+description
+</h4>
+<p>
+A
+direct
+HTTP
+query
+service
+is
+described
+by
+an
+RDF
+resource
+of
+type
+<code>
+prov:DirectQueryService
+</code>.
+It
+allows
+for
+accessing
+provenance
+about
+a
+specified
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>.
+The
+query
+URI
+to
+use
+is
+described
+by
+a
+URI
+Template
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+]
+(level
+2
+or
+above)
+in
+which
+<del class="diff-old">which
+</del>
+the
+variable
+<cite>
+<code>
+uri
+</code>
+</cite>
+stands
+for
+the
+<del class="diff-old">target-URI;
+e.g.
+</del>
+<ins class="diff-chg">target-URI.
+The
+URI
+template
+is
+specified
+as:
+</ins>
+</p>
+<del class="diff-old"> @prefix prov: <http://www.w3c.org/ns/prov#>
+<direct-query-description> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "?target={+uri}" .
+</del>
+ <pre class="pattern"><direct-query-description> a prov:DirectQueryService ;
+<ins class="diff-chg"> prov:provenanceUriTemplate "<cite>uri-template</cite>" .
+</ins>
+</pre>
+<p>
+where
+<del class="diff-old">query-URI
+is
+the
+base
+URI
+of
+the
+direct
+query
+service,
+and
+</del>
+<code>
+<cite>
+direct-query-description
+</cite>
+</code>
+is
+any
+distinct
+RDF
+subject
+node
+(i.e.
+a
+blank
+node
+or
+a
+<del class="diff-old">URI).
+</del>
+<ins class="diff-chg">URI),
+and
+</ins><code><cite><ins class="diff-chg">
+uri-template
+</ins></cite></code><ins class="diff-chg">
+is
+a
+URI
+template
+[
+</ins><cite><a class="bibref" href="#bib-RFC3986"><ins class="diff-chg">
+RFC3986
+</ins></a></cite><ins class="diff-chg">
+].
+</ins>
+</p>
+<p>
+The
+URI
+template
+indicated
+by
+<code>
+prov:provenanceUriTemplate
+</code>
+may
+expand
+to
+an
+absolute
+or
+relative
+URI
+reference.
+A
+URI
+for
+the
+desired
+provenance
+record
+is
+obtained
+by
+expanding
+the
+URI
+template
+with
+the
+variable
+<cite>
+<code>
+uri
+</code>
+</cite>
+set
+to
+the
+target-URI
+for
+which
+provenance
+is
+requested.
+In
+this
+example,
+if
+the
+target-URI
+contains
+'#'
+or
+'&'
+these
+must
+be
+%-escaped
+as
+<code>
+%23
+</code>
+or
+<code>
+%26
+</code>
+respectively
+before
+template
+expansion
+[
+<cite>
+<a class="bibref" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+].
+If
+the
+result
+is
+a
+relative
+reference,
+it
+is
+interpreted
+per
+[
+<cite>
+<a class="bibref" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+]
+(section
+5.2)
+using
+the
+URI
+of
+the
+service
+description
+as
+its
+base
+URI
+(which
+is
+generally
+the
+same
+as
+the
+query
+service-URI,
+unless
+HTTP
+redirection
+has
+been
+invoked).
+</p>
+ <div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+<ins class="diff-new"> prov:describesService _:direct .
+_:direct a prov:DirectQueryService ;
+ prov:provenanceUriTemplate
+"http://www.example.com/provenance/service?target={uri}"
+.
+</ins></pre></div>
+<p>
+A
+provenance
+query
+service
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+recognize
+additional
+parameters
+encoded
+as
+part
+of
+a
+URI
+for
+the
+provenance
+record.
+If
+it
+does,
+it
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+include
+these
+in
+the
+provenance
+URI
+template
+in
+the
+service
+description,
+so
+that
+clients
+may
+discover
+how
+a
+URI
+is
+formed
+using
+this
+additional
+information.
+For
+example,
+a
+query
+service
+might
+offer
+to
+include
+just
+the
+immediate
+provenance
+of
+a
+target,
+or
+to
+also
+supply
+provenance
+of
+other
+resources
+from
+which
+the
+target
+is
+derived.
+Suppose
+a
+service
+accepts
+an
+additional
+parameter
+<code>
+steps
+</code>
+that
+defines
+the
+number
+of
+previous
+steps
+to
+include
+in
+a
+provenance
+trace,
+it
+might
+publish
+its
+service
+description
+thus:
+</p>
+<del class="diff-old"> > a prov:DirectQueryService ;
+</del>
+ <div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+<ins class="diff-chg"> prov:describesService _:direct .
+_:direct a prov:DirectQueryService ;
+</ins>
+ prov:provenanceUriTemplate
+<del class="diff-old">"http://www.example.com/provenance/service?target={+uri}{&steps}"
+</del>
+<ins class="diff-chg">"http://www.example.com/provenance/service?target={uri}{&steps}"
+</ins>
+.
+</pre>
+</div>
+<p>
+<del class="diff-old">which
+might
+result
+in
+an
+HTTP
+query
+for
+provenance
+information
+that
+looks
+like
+this:
+Example
+6
+GET
+http://example.com/provenance/service?
+target
+=http://www.example.com/entity&
+steps
+=2
+HTTP/1.1
+</del>
+(Note
+that
+in
+this
+case,
+a
+"level
+3"
+URI
+template
+feature
+is
+used
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+].)
+</p>
+<p>
+<ins class="diff-new">Section
+</ins><a href="#direct-http-query-service-invocation" class="sectionRef sec-ref"><ins class="diff-new">
+section
+4.2
+Direct
+HTTP
+query
+service
+invocation
+</ins></a><ins class="diff-new">
+discusses
+how
+a
+client
+interacts
+with
+a
+direct
+HTTP
+query
+service.
+</ins></p>
+</section>
+<section id="sparql-query-service-description">
+<h4>
+<span class="secno">
+4.1.2
+</span>
+SPARQL
+query
+service
+description
+</h4>
+<p>
+A
+SPARQL
+query
+service
+is
+described
+by
+an
+RDF
+resource
+of
+type
+<code>
+sd:Service
+</code>
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+].
+</p>
+<p>
+It
+allows
+for
+accessing
+provenance
+information
+using
+a
+SPARQL
+query,
+which
+may
+be
+constructed
+to
+retrieve
+provenance
+for
+a
+particular
+resource,
+or
+for
+multiple
+resources.
+The
+query
+may
+be
+formulated
+using
+the
+PROV-O
+vocabulary
+terms
+[
+<cite>
+<a class="bibref" href="#bib-PROV-O">
+PROV-O
+</a>
+</cite>
+],
+and
+others
+supported
+by
+the
+SPARQL
+endpoint
+as
+appropriate.
+</p>
+<p>
+The
+SPARQL
+query
+service
+description
+is
+constructed
+as
+defined
+by
+<cite>
+SPARQL
+1.1
+Service
+Description
+</cite>
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+];
+e.g.
+</p>
+<del class="diff-old"> a sd:Service ;
+ sd:endpoint </sparql/> ;
+</del>
+ <div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+<ins class="diff-chg"> prov:describesService _:sparql .
+_:sparql a sd:Service ;
+ sd:endpoint <http://www.example.com/provenance/sparql> ;
+</ins>
+sd:supportedLanguage
+sd:SPARQL11Query
+.
+</pre>
+</div>
+<p>
+where
+<code>
+<del class="diff-old">query-URI
+</del>
+<ins class="diff-chg">http://www.example.com/provenance/sparql
+</ins>
+</code>
+is
+the
+<del class="diff-old">base
+</del>
+URI
+of
+<del class="diff-old">the
+</del>
+<ins class="diff-chg">a
+</ins>
+provenance
+query
+<del class="diff-old">service,
+and
+sparql-query-description
+is
+any
+distinct
+RDF
+subject
+node
+(i.e.
+a
+blank
+node
+or
+a
+URI).
+</del>
+<ins class="diff-chg">SPARQL
+endpoint.
+</ins>
+</p>
+<p>
+The
+SPARQL
+service
+description
+may
+be
+detailed
+or
+sparse,
+provided
+that
+it
+includes
+at
+<ins class="diff-new">least
+</ins>
+a
+<del class="diff-old">minimum
+</del>
+<code>
+<ins class="diff-chg">sd:endpoint
+</ins></code><ins class="diff-chg">
+statement
+with
+</ins>
+the
+<del class="diff-old">following:
+</del>
+<ins class="diff-chg">SPARQL
+service
+endpoint
+URI.
+</ins>
+</p>
+<del class="diff-old"> a sd:Service ;
+ sd:endpoint <(SPARQL service endpoint URI reference)> .
+</del>
+<p>
+The
+endpoint
+may
+be
+given
+as
+an
+absolute
+or
+relative
+URI
+reference.
+If
+a
+relative
+reference
+is
+given,
+it
+is
+interpreted
+in
+the
+normal
+way
+for
+the
+RDF
+format
+used,
+which
+will
+commonly
+be
+relative
+to
+the
+URI
+of
+the
+service
+document
+itself.
+</p>
+</section>
+<section id="service-description-example">
+<h4>
+<span class="secno">
+4.1.3
+</span>
+Service
+description
+example
+</h4>
+<p>
+The
+following
+service
+description
+example
+uses
+Turtle
+[
+<cite>
+<a class="bibref" href="#bib-TURTLE">
+TURTLE
+</a>
+</cite>
+]
+syntax
+to
+describe
+both
+direct
+HTTP
+and
+SPARQL
+query
+services:
+</p>
+<del class="diff-old"> @prefix prov: <http://www.w3c.org/ns/prov#>
+@prefix dcterms: <http://purl.org/dc/terms/>
+@prefix foaf: <http://xmlns.com/foaf/0.1/>
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#>
+</del>
+ <div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example code">@prefix prov: <http://www.w3c.org/ns/prov#> .
+<ins class="diff-chg">@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#> .
+</ins>
+<> a prov:ServiceDescription ;
+ prov:describesService <#direct>, <#sparql> ;
+ dcterms:publisher <#us>
+ .
+<#us> a foaf:Organization ;
+ foaf:name "and not a service!"
+ .
+<#direct> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "/direct?target={+uri}"
+ .
+<#sparql> a sd:Service ;
+ sd:endpoint </sparql/> ;
+ sd:supportedLanguage sd:SPARQL11Query ;
+ sd:resultFormat <http://www.w3.org/ns/formats/RDF_XML> ,
+ <http://www.w3.org/ns/formats/Turtle> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_XML> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_JSON> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_CSV> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_TSV>
+.
+</pre>
+</div>
+</section>
+</section>
+<section id="direct-http-query-service-invocation">
+<h3>
+<span class="secno">
+4.2
+</span>
+Direct
+HTTP
+query
+service
+invocation
+</h3>
+<p>
+This
+<del class="diff-old">protocol
+combines
+</del>
+<ins class="diff-chg">section
+describes
+</ins>
+the
+<ins class="diff-chg">interaction
+between
+a
+client
+and
+a
+direct
+HTTP
+query
+service
+whose
+service
+description
+is
+as
+presented
+in
+</ins><a href="#direct-http-query-service-description" class="sectionRef sec-ref"><ins class="diff-chg">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</ins></a>,<ins class="diff-chg">
+once
+the
+service
+description
+has
+been
+analyzed
+and
+its
+URI
+template
+has
+been
+extracted.
+</ins></p><p><ins class="diff-chg">
+The
+</ins><a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+<del class="diff-old">with
+a
+</del>
+<ins class="diff-chg">for
+which
+provenance
+is
+required
+is
+used
+in
+the
+expansion
+of
+the
+</ins>
+supplied
+URI
+template
+<ins class="diff-new">[
+</ins><cite><a class="bibref" href="#bib-RFC3986"><ins class="diff-new">
+RFC3986
+</ins></a></cite><ins class="diff-new">
+]
+</ins>
+to
+formulate
+an
+HTTP
+GET
+request.
+</p>
+<p>
+Thus,
+<del class="diff-old">if
+the
+URI
+template
+extracted
+from
+</del>
+<ins class="diff-chg">in
+</ins>
+the
+<ins class="diff-new">first
+service
+description
+example
+in
+</ins><a href="#direct-http-query-service-description" class="sectionRef sec-ref"><ins class="diff-new">
+section
+4.1.1
+Direct
+HTTP
+query
+</ins>
+service
+description
+</a>,
+<ins class="diff-new">the
+URI
+template
+</ins>
+is
+<code>
+<del class="diff-old">http://example.com/provenance/service?target={uri}
+and
+</del>
+<ins class="diff-chg">http://www.example.com/provenance/service?target={uri}
+</ins></code>.<ins class="diff-chg">
+If
+</ins>
+the
+supplied
+target-URI
+is
+<code>
+http://www.example.com/entity123
+</code>,
+<ins class="diff-new">this
+would
+be
+used
+as
+</ins>
+the
+<ins class="diff-new">value
+for
+variable
+</ins><code><ins class="diff-new">
+uri
+</ins></code><ins class="diff-new">
+when
+expanding
+the
+template.
+The
+</ins>
+resulting
+HTTP
+request
+<ins class="diff-new">used
+to
+retrieve
+a
+provenance
+record
+</ins>
+would
+be:
+</p>
+ <div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example code">GET /provenance/service?<b>target</b>=http%3A%2F%2Fwww.example.com%2Fentity123 HTTP/1.1
+Host:
+example.com
+</pre>
+</div>
+<p>
+Any
+server
+that
+implements
+this
+protocol
+and
+receives
+a
+request
+URI
+in
+<del class="diff-old">this
+</del>
+<ins class="diff-chg">a
+</ins>
+form
+<ins class="diff-new">corresponding
+to
+its
+published
+URI
+template
+</ins>
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+return
+a
+provenance
+record
+for
+the
+<del class="diff-old">target-URI
+</del>
+embedded
+<del class="diff-old">in
+the
+query
+component,
+where
+that
+URI
+</del>
+<ins class="diff-chg">target-URI.
+The
+target-URI
+</ins>
+is
+<del class="diff-old">the
+result
+of
+</del>
+<ins class="diff-chg">obtained
+by
+</ins>
+percent-decoding
+[
+<cite>
+<a class="bibref" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+]
+the
+part
+of
+the
+request
+URI
+corresponding
+to
+<ins class="diff-new">occurrences
+of
+the
+variable
+</ins>
+<code>
+<del class="diff-old">{var}
+</del>
+<ins class="diff-chg">uri
+</ins>
+</code>
+in
+the
+URI
+template.
+E.g.,
+in
+the
+above
+example,
+the
+decoded
+target-URI
+is
+<code>
+http://www.example.com/entity123
+</code>.
+The
+target-URI
+<em class="rfc2119" title="MUST">
+MUST
+</em>
+be
+an
+absolute
+URI,
+and
+the
+server
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+respond
+with
+<code>
+400
+Bad
+Request
+</code>
+if
+it
+is
+not.
+</p>
+<p>
+A
+server
+<em class="rfc2119" title="SHOULD NOT">
+SHOULD
+NOT
+</em>
+offer
+a
+template
+containing
+<code>
+{+uri}
+</code>
+or
+other
+non-simple
+variable
+expansion
+options
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+]
+unless
+all
+valid
+target-URIs
+for
+which
+it
+can
+provide
+provenance
+do
+not
+contain
+problematic
+characters
+like
+<code>
+'#'
+</code>
+or
+<code>
+'&'
+</code>.
+</p>
+<div class="note">
+<div class="note-title" role="heading" aria-level="4">
+<span>
+Note
+</span>
+</div>
+<p class="">
+The
+defined
+URI
+template
+expansion
+process
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+]
+generally
+takes
+care
+of
+%-escaping
+characters
+that
+are
+not
+permitted
+in
+URIs.
+However,
+when
+expanding
+a
+template
+with
+<code>
+{+uri}
+<del class="diff-old">,
+</del>
+</code>
+<ins class="diff-chg">(or
+other
+non-simple
+variable
+expansion
+options),
+</ins>
+some
+permitted
+characters
+such
+as
+<code>
+'#'
+</code>
+and
+<code>
+'&'
+</code>
+are
+not
+escaped.
+If
+the
+supplied
+target-URI
+contains
+these
+characters,
+then
+they
+may
+disrupt
+interpretation
+of
+the
+resulting
+query
+URI.
+<del class="diff-old">To
+prevent
+this,
+'#'
+and
+'&'
+characters
+in
+the
+target-URI
+may
+be
+replaced
+with
+%23
+and
+%26
+respectively,
+before
+performing
+the
+URI
+template
+expansion.
+An
+alternative,
+simpler
+and
+</del>
+<ins class="diff-chg">A
+generally
+</ins>
+more
+reliable
+approach
+is
+to
+use
+<code>
+{uri}
+</code>
+in
+the
+URI
+template
+string,
+which
+will
+cause
+all
+URI-reserved
+characters
+to
+be
+%-escaped
+as
+part
+of
+the
+URI-template
+expansion,
+as
+in
+the
+example
+above.
+</p>
+</div>
+<p>
+If
+the
+provenance
+described
+by
+the
+request
+is
+unknown
+to
+the
+server,
+a
+suitable
+error
+response
+code
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+returned.
+In
+the
+absence
+of
+any
+security
+of
+privacy
+concerns
+about
+the
+resource,
+that
+might
+be
+<code>
+404
+Not
+Found
+</code>.
+But
+if
+the
+existence
+or
+non-existence
+of
+a
+resource
+is
+considered
+private
+or
+sensitive,
+an
+authorization
+failure
+or
+other
+<del class="diff-old">error
+</del>
+response
+may
+be
+returned.
+</p>
+<p>
+The
+direct
+HTTP
+query
+service
+may
+return
+provenance
+in
+any
+available
+format.
+For
+interoperable
+provenance
+publication,
+use
+of
+<del class="diff-old">the
+PROV-O
+vocabulary
+[
+PROV-O
+]
+</del>
+<ins class="diff-chg">PROV
+</ins>
+represented
+in
+<del class="diff-old">a
+standardized
+RDF
+format
+</del>
+<ins class="diff-chg">any
+of
+its
+specified
+formats
+</ins>
+is
+recommended.
+Where
+alternative
+formats
+are
+available,
+selection
+may
+be
+made
+by
+content
+negotiation,
+using
+<code>
+Accept:
+</code>
+header
+fields
+in
+the
+HTTP
+request.
+Services
+<em class="rfc2119" title="MUST">
+MUST
+</em>
+identify
+the
+<code>
+Content-Type
+</code>
+of
+the
+provenance
+returned.
+</p>
+<p>
+Additional
+URI
+query
+parameters
+may
+be
+used
+as
+indicated
+by
+the
+service
+description
+in
+<a href="#direct-http-query-service-description" class="sectionRef sec-ref">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>.
+<ins class="diff-new">The
+second
+service
+description
+example
+specifies
+a
+URI
+template
+with
+an
+additional
+variable
+which
+may
+be
+used
+to
+control
+the
+scope
+of
+provenance
+information
+returned:
+</ins><code><ins class="diff-new">
+http://www.example.com/provenance/service?target={+uri}{&steps}
+</ins></code>.<ins class="diff-new">
+Following
+[
+</ins><cite><a class="bibref" href="#bib-RFC3986"><ins class="diff-new">
+RFC3986
+</ins></a></cite><ins class="diff-new">
+],
+if
+no
+value
+for
+variable
+</ins><code><ins class="diff-new">
+steps
+</ins></code><ins class="diff-new">
+is
+provided
+when
+expanding
+the
+template,
+this
+extra
+element
+is
+effectively
+ignored.
+But
+if
+a
+</ins><code><ins class="diff-new">
+steps
+</ins></code><ins class="diff-new">
+value
+of
+(say)
+</ins><code><ins class="diff-new">
+2
+</ins></code><ins class="diff-new">
+is
+provided,
+then
+the
+resulting
+HTTP
+query
+would
+be:
+</ins>
+</p>
+<div class="example">
+<div class="example-title">
+<span>
+<ins class="diff-new">Example
+10
+</ins></span></div><pre class="example code"><ins class="diff-new">
+GET
+http://example.com/provenance/service?
+</ins><b><ins class="diff-new">
+target
+</ins></b><ins class="diff-new">
+=http://www.example.com/entity&
+</ins><b><ins class="diff-new">
+steps
+</ins></b><ins class="diff-new">
+=2
+HTTP/1.1
+</ins></pre></div><div class="note"><div class="note-title" role="heading" aria-level="4"><span><ins class="diff-new">
+Note
+</ins></span></div><p class=""><ins class="diff-new">
+The
+use
+of
+any
+specific
+URI
+template
+variable
+other
+than
+</ins><code><ins class="diff-new">
+uri
+</ins></code><ins class="diff-new">
+for
+the
+target-URI
+is
+a
+matter
+for
+agreement
+between
+the
+client
+and
+query
+service,
+and
+is
+not
+specified
+in
+this
+note.
+It
+is
+mentioned
+here
+simply
+to
+show
+that
+the
+possibility
+exists
+to
+formulate
+more
+detailed
+queries.
+</ins></p></div>
+</section>
+<section id="provenance-query-service-discovery">
+<h3>
+<span class="secno">
+4.3
+</span>
+Provenance
+query
+service
+discovery
+</h3>
+<p>
+Previously,
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>
+has
+described
+use
+of
+HTTP
+<code>
+Link:
+</code>
+header
+fields,
+HTML
+<code>
+<link>
+</code>
+elements
+and
+RDF
+statements
+to
+indicate
+provenance
+query
+services.
+Beyond
+that,
+this
+specification
+does
+not
+define
+any
+specific
+mechanism
+for
+discovering
+query
+services.
+Applications
+may
+use
+any
+appropriate
+mechanism,
+including
+but
+not
+limited
+to:
+prior
+configuration,
+search
+engines,
+service
+registries,
+etc.
+</p>
+<p>
+To
+facilitate
+service
+discovery,
+we
+recommend
+that
+RDF
+publication
+of
+dataset
+and
+service
+descriptions
+use
+the
+property
+<code>
+prov:has_query_service
+</code>
+and
+the
+provenance
+service
+type
+<code>
+prov:ServiceDescription
+</code>
+as
+appropriate
+(see
+the
+appendix
+<a href="#prov-namespace" class="sectionRef">
+section
+B.
+</a>
+).
+</p>
+<p>
+For
+example,
+a
+VoID
+description
+[
+<cite>
+<a class="bibref" href="#bib-VoID">
+VoID
+</a>
+</cite>
+]
+of
+a
+dataset
+might
+indicate
+a
+provenance
+query
+service
+providing
+information
+about
+that
+dataset:
+</p>
+ <pre class="pattern"> <http://example.org/dataset/> a void:Dataset ;
+prov:has_query_service
+<http://example.org/provenance/>
+.
+</pre>
+<p>
+The
+RDF
+service
+description
+example
+in
+<a href="#service-description-example" class="sectionRef sec-ref">
+section
+4.1.3
+Service
+description
+example
+</a>
+shows
+use
+of
+the
+<code>
+prov:ServiceDescription
+</code>
+type.
+</p>
+</section>
+</section>
+<section id="provenance-pingback">
+<h2>
+<span class="secno">
+5.
+</span>
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</h2>
+<del class="diff-old">REVIEW.
+</del>
+<p>
+This
+section
+describes
+<del class="diff-old">an
+"at-risk"
+feature
+whose
+final
+inclusion
+in
+this
+document
+is
+undecided.
+Does
+the
+use
+of
+</del>
+a
+<del class="diff-old">"ping-back"
+for
+discovering
+forward
+</del>
+<ins class="diff-chg">mechanism
+that
+may
+be
+used
+to
+discover
+related
+</ins>
+provenance
+<del class="diff-old">fall
+under
+</del>
+<ins class="diff-chg">information
+that
+</ins>
+the
+<del class="diff-old">remit
+</del>
+<ins class="diff-chg">publisher
+</ins>
+of
+<del class="diff-old">"provenance
+access
+and
+query"?
+Is
+it
+</del>
+a
+<del class="diff-old">useful
+feature
+to
+define?
+This
+section
+describes
+a
+discovery
+mechanism
+for
+forward
+provenance
+;
+i.e.
+</del>
+<ins class="diff-chg">resource
+does
+not
+otherwise
+know
+about;
+e.g.
+</ins>
+provenance
+describing
+how
+<del class="diff-old">a
+resource
+</del>
+<ins class="diff-chg">it
+</ins>
+is
+used
+after
+it
+has
+been
+<del class="diff-old">created
+.
+</del>
+<ins class="diff-chg">created.
+</ins>
+</p>
+<p>
+The
+mechanisms
+discussed
+in
+previous
+sections
+are
+primarily
+concerned
+with
+<ins class="diff-new">the
+publisher
+enabling
+</ins>
+access
+to
+<del class="diff-old">historical
+provenance,
+dealing
+</del>
+<ins class="diff-chg">known
+provenance
+about
+an
+entity,
+answering
+</ins>
+with
+questions
+such
+as:
+</p>
+<ul>
+<li>
+what
+was
+this
+resource
+based
+upon?
+</li>
+<li>
+how
+was
+it
+constructed?
+</li>
+<li>
+who
+made
+it?
+</li>
+<li>
+when
+was
+it
+made?
+</li>
+</ul>
+<p>
+These
+questions
+can
+be
+<del class="diff-old">turned
+around
+</del>
+<ins class="diff-chg">opened
+up
+</ins>
+to
+consider
+<del class="diff-old">a
+publisher's
+forward-looking
+use
+of
+a
+resource,
+</del>
+<ins class="diff-chg">provenance
+information
+created
+by
+unrelated
+third
+parties,
+</ins>
+like:
+</p>
+<ul>
+<li>
+what
+new
+resources
+are
+based
+on
+this
+resource?
+</li>
+<li>
+what
+has
+this
+resource
+been
+used
+for?
+</li>
+<li>
+who
+has
+used
+it?
+</li>
+<li>
+<del class="diff-old">etc.
+</del>
+<ins class="diff-chg">what
+other
+resources
+are
+derived
+from
+the
+same
+sources
+as
+this
+resource?
+</ins>
+</li>
+</ul>
+<p>
+The
+ability
+to
+answer
+<del class="diff-old">forward-looking
+</del>
+<ins class="diff-chg">such
+broader
+</ins>
+questions
+requires
+some
+cooperation
+among
+the
+parties
+who
+use
+a
+resource;
+for
+example,
+a
+consumer
+could
+report
+use
+directly
+to
+the
+publisher,
+or
+a
+search
+engine
+could
+discover
+and
+report
+<del class="diff-old">such
+</del>
+downstream
+resource
+usage.
+To
+facilitate
+such
+cooperation,
+a
+<del class="diff-old">publisher
+of
+a
+</del>
+resource
+<ins class="diff-new">publisher
+</ins>
+may
+<del class="diff-old">implement
+a
+"ping-back"
+capability.
+</del>
+<ins class="diff-chg">receive
+provenance
+"ping-backs".
+(The
+mechanism
+described
+here
+is
+inspired
+by
+</ins><a href="http://www.hixie.ch/specs/pingback/pingback" class="externalRef"><ins class="diff-chg">
+blog
+pingbacks
+</ins></a>,<ins class="diff-chg">
+but
+avoids
+the
+need
+for
+XML-RPC
+and
+is
+specific
+for
+provenance
+records.)
+</ins>
+</p>
+<p>
+A
+resource
+may
+have
+an
+associated
+<del class="diff-old">"ping-back"
+URI
+</del>
+<ins class="diff-chg">provenance
+ping-back
+URI,
+</ins>
+which
+<del class="diff-old">can
+</del>
+<ins class="diff-chg">may
+</ins>
+be
+presented
+with
+references
+to
+provenance
+about
+the
+resource.
+The
+ping-back
+URI
+is
+associated
+with
+a
+resource
+using
+mechanisms
+similar
+to
+those
+used
+for
+presenting
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>,
+but
+using
+a
+<code>
+<del class="diff-old">pingback
+</del>
+<ins class="diff-chg">prov:pingback
+</ins>
+</code>
+link
+relation
+instead
+of
+<code>
+<del class="diff-old">has_provenance
+</del>
+<ins class="diff-chg">prov:has_provenance
+</ins>
+</code>.
+A
+consumer
+of
+the
+resource,
+or
+some
+other
+system,
+may
+perform
+an
+HTTP
+POST
+operation
+to
+the
+pingback
+URI,
+with
+a
+request
+body
+containing
+a
+list
+of
+provenance-URIs
+for
+provenance
+records
+describing
+uses
+of
+the
+resource.
+</p>
+<p>
+For
+example,
+consider
+a
+resource
+that
+is
+published
+by
+<code>
+acme.example.com
+</code>,
+and
+is
+subsequently
+used
+by
+<code>
+<del class="diff-old">wile-e.example.org
+</del>
+<ins class="diff-chg">coyote.example.org
+</ins>
+</code>
+in
+the
+construction
+of
+some
+new
+entity;
+we
+might
+see
+an
+exchange
+along
+the
+following
+lines.
+We
+start
+with
+<code>
+<del class="diff-old">wile-e.example.org
+</del>
+<ins class="diff-chg">coyote.example.org
+</ins>
+</code>
+retrieving
+a
+copy
+of
+<code>
+acme.example.org
+</code>
+'s
+resource:
+</p>
+<del class="diff-old"> C: GET http://acme.example.org/super-widget HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example code">C: GET http://acme.example.org/super-widget123 HTTP/1.1
+<del class="diff-old"> S: 200 OK
+ S: Link: <http://acme.example.org/super-widget/provenance>;
+ rel=http://www.w3.org/ns/prov#has_provenance
+ S: Link: <http://acme.example.org/super-widget/pingback>;
+ rel=http://www.w3.org/ns/prov#pingback
+ :
+(super-widget
+</del>
+<ins class="diff-chg">S: 200 OK
+S: Link: <http://acme.example.org/super-widget123/provenance>;
+ rel="http://www.w3.org/ns/prov#has_provenance"
+S: Link: <http://acme.example.org/super-widget123/pingback>;
+ rel="http://www.w3.org/ns/prov#pingback"
+ :
+(super-widget123
+</ins>
+resource
+data)
+</pre>
+</div>
+<p>
+The
+first
+of
+the
+links
+in
+the
+response
+is
+a
+<code>
+has_provenance
+</code>
+link
+with
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+that
+has
+been
+described
+previously
+(
+<a href="#resource-accessed-by-http" class="sectionRef sec-ref">
+section
+3.1
+Resource
+accessed
+by
+HTTP
+</a>
+).
+The
+second
+is
+a
+distinct
+resource
+that
+exists
+to
+receive
+provenance
+pingbacks.
+Later,
+when
+a
+new
+resource
+has
+been
+created
+or
+<ins class="diff-new">some
+related
+</ins>
+action
+performed
+based
+upon
+the
+<code>
+<del class="diff-old">acme.example.org/super-widget
+</del>
+<ins class="diff-chg">acme.example.org/super-widget123
+</ins>
+</code>,
+a
+client
+<del class="diff-old">MAY
+</del>
+<ins class="diff-chg">may
+</ins>
+post
+a
+pingback
+request
+to
+<del class="diff-old">any
+</del>
+<ins class="diff-chg">the
+</ins>
+supplied
+<code>
+pingback
+</code>
+URI:
+</p>
+<del class="diff-old"> C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
+C: Content-Type: text/uri-list
+C:
+<del class="diff-old">C: http://wile-e.example.org/contraption/provenance
+C: http://wile-e.example.org/another/provenance
+</del>
+<ins class="diff-chg">C: http://coyote.example.org/contraption/provenance
+C: http://coyote.example.org/another/provenance
+</ins>
+<del class="diff-old">S: 204 No Content
+S: Link: <http://acme.example.org/super-widget/provenance>;
+ rel=http://www.w3.org/ns/prov#has_provenance;
+anchor="http://acme.example.org/super-widget"
+</del>
+<ins class="diff-chg">S:
+204
+No
+Content
+</ins>
+</pre>
+</div>
+<p>
+The
+pingback
+request
+supplies
+a
+list
+of
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+s
+from
+which
+<del class="diff-old">forward
+</del>
+<ins class="diff-chg">additional
+</ins>
+provenance
+may
+be
+retrieved.
+The
+pingback
+service
+may
+do
+as
+it
+chooses
+with
+these
+URIs;
+e.g.,
+it
+may
+choose
+to
+save
+them
+for
+later
+use,
+to
+retrieve
+the
+associated
+provenance
+and
+save
+that,
+to
+publish
+the
+URIs
+along
+with
+other
+provenance
+information
+about
+the
+original
+entity
+to
+which
+they
+relate,
+or
+even
+to
+ignore
+them.
+</p>
+<p>
+<del class="diff-old">The
+client
+MAY
+further
+supply
+has_query_service
+links
+indicating
+provenance
+query
+services
+that
+can
+describe
+the
+target-URI.
+The
+anchor
+MUST
+be
+included,
+and
+SHOULD
+be
+the
+target-URI
+of
+the
+resource
+to
+which
+this
+pingback
+service
+belongs,
+or
+some
+related
+resource
+with
+relevant
+provenance.
+ C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+C: Link: <http://wile-e.example.org/sparql>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://acme.example.org/super-widget"
+C: Content-Type: text/uri-list
+C: Content-Length: 0
+C:
+S: 204 No Content
+S: Link: <http://acme.example.org/super-widget/provenance>;
+ rel=http://www.w3.org/ns/prov#has_provenance;
+anchor="http://acme.example.org/super-widget"
+In
+the
+above
+example,
+the
+client
+did
+not
+submit
+any
+provenance-URIs
+and
+the
+URI
+list
+is
+therefore
+empty.
+The
+client
+MAY
+similarly
+include
+has_provenance
+links
+to
+specify
+provenance
+records
+with
+a
+different
+anchor.
+The
+provenance-URIs
+of
+those
+headers
+SHOULD
+also
+be
+included
+in
+the
+content
+if
+the
+POSTed
+Content-type
+is
+text/uri-list
+.
+Does
+this
+SHOULD
+requirement
+serve
+any
+useful
+purpose?
+</del>
+There
+is
+no
+required
+information
+in
+the
+server
+response
+to
+a
+pingback
+POST
+request.
+In
+the
+examples
+<del class="diff-old">above,
+</del>
+<ins class="diff-chg">here,
+</ins>
+the
+pingback
+service
+responds
+<ins class="diff-new">positively
+</ins>
+with
+<code>
+<ins class="diff-new">204
+No
+Content
+</ins></code><ins class="diff-new">
+and
+</ins>
+an
+empty
+response
+<del class="diff-old">body,
+and
+links
+to
+provenance
+for
+the
+original
+resource.
+(Note
+that
+the
+</del>
+<ins class="diff-chg">body.
+Other
+HTTP
+status
+values
+like
+</ins>
+<code>
+<del class="diff-old">Link:
+header
+returned
+contains
+an
+explicit
+</del>
+<ins class="diff-chg">200
+OK
+</ins></code>,
+<code>
+<del class="diff-old">anchor
+parameter
+with
+the
+URI
+of
+the
+original
+resource;
+without
+this,
+the
+link
+would
+relate
+the
+indicated
+URI
+to
+the
+pingback
+URI
+</del>
+<ins class="diff-chg">201
+Created
+</ins></code>,
+<code>
+<del class="diff-old">http://acme.example.org/super-widget/pingback
+</del>
+<ins class="diff-chg">202
+Accepted
+</ins></code>,<ins class="diff-chg">
+and
+</ins><code><ins class="diff-chg">
+303
+See
+Other
+</ins>
+</code>
+<del class="diff-old">rather
+than
+</del>
+<ins class="diff-chg">might
+also
+be
+appropriate
+positive
+responses
+depending
+on
+</ins>
+the
+<del class="diff-old">original
+resource.)
+</del>
+<ins class="diff-chg">domain
+and
+application.
+</ins>
+</p>
+<p>
+The
+only
+defined
+operation
+on
+a
+pingback-URI
+is
+POST,
+which
+supplies
+links
+to
+provenance
+information
+or
+services
+as
+described
+above.
+A
+pingback-URI
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+respond
+to
+other
+requests,
+but
+no
+requirements
+are
+imposed
+on
+how
+it
+responds.
+In
+particular,
+it
+is
+not
+specified
+here
+how
+a
+pingback
+resource
+should
+respond
+to
+an
+HTTP
+GET
+request.
+<del class="diff-old">This
+leaves
+open
+</del>
+</p>
+<p>
+<ins class="diff-chg">The
+pingback
+client
+</ins><em class="rfc2119" title="MAY"><ins class="diff-chg">
+MAY
+</ins></em><ins class="diff-chg">
+include
+extra
+</ins><code><ins class="diff-chg">
+has_provenance
+</ins></code><ins class="diff-chg">
+links
+to
+indicate
+provenance
+records
+related
+to
+</ins>
+a
+<del class="diff-old">possibility
+</del>
+<ins class="diff-chg">different
+resources,
+specified
+with
+correspondingly
+different
+anchor
+URIs.
+These
+</ins><em class="rfc2119" title="MAY"><ins class="diff-chg">
+MAY
+</ins></em><ins class="diff-chg">
+indicate
+further
+provenance
+about
+existing
+resources,
+or
+about
+new
+resources
+(such
+as
+new
+entities
+derived
+or
+specialized
+from
+</ins>
+that
+<ins class="diff-new">for
+which
+</ins>
+the
+pingback
+<del class="diff-old">resource
+</del>
+<ins class="diff-chg">URI
+was
+provided).
+For
+example:
+</ins></p> <div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1<ins class="diff-chg">
+C: Link: <http://coyote.example.org/extra/provenance>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+ anchor="http://acme.example.org/extra-widget"
+C: Content-Type: text/uri-list
+C:
+C: http://coyote.example.org/contraption/provenance
+C: http://coyote.example.org/another/provenance
+C: http://coyote.example.org/extra/provenance
+S:
+204
+No
+Content
+</ins></pre></div><p><ins class="diff-chg">
+The
+client
+</ins>
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+<del class="diff-old">have
+</del>
+<ins class="diff-chg">also
+supply
+</ins><code><ins class="diff-chg">
+has_query_service
+</ins></code><ins class="diff-chg">
+links
+indicating
+provenance
+query
+services
+that
+can
+describe
+</ins>
+the
+<del class="diff-old">same
+URI
+as
+</del>
+<ins class="diff-chg">target-URI.
+The
+anchor
+</ins><em class="rfc2119" title="MUST"><ins class="diff-chg">
+MUST
+</ins></em><ins class="diff-chg">
+be
+included,
+and
+</ins><em class="rfc2119" title="SHOULD"><ins class="diff-chg">
+SHOULD
+</ins></em><ins class="diff-chg">
+be
+either
+</ins>
+the
+<del class="diff-old">original
+resource,
+</del>
+<ins class="diff-chg">target-URI
+of
+the
+resource
+for
+which
+the
+pingback
+URI
+was
+</ins>
+provided
+<ins class="diff-new">(from
+the
+examples
+above,
+</ins>
+that
+<ins class="diff-new">would
+be
+</ins><code><ins class="diff-new">
+http://acme.example.org/super-widget123
+</ins></code><ins class="diff-new">
+),
+or
+some
+related
+resource
+with
+relevant
+provenance.
+For
+example:
+</ins></p> <div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1<ins class="diff-new">
+C: Link: <http://coyote.example.org/sparql>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://acme.example.org/super-widget123"
+C: Content-Type: text/uri-list
+C: Content-Length: 0
+C:
+S:
+204
+No
+Content
+</ins></pre></div><p><ins class="diff-new">
+Here,
+</ins>
+the
+<del class="diff-old">original
+does
+</del>
+<ins class="diff-chg">pingback
+client
+has
+supplied
+a
+query
+service
+URI,
+but
+did
+</ins>
+not
+<del class="diff-old">respond
+</del>
+<ins class="diff-chg">submit
+any
+provenance-URIs
+and
+the
+URI
+list
+is
+therefore
+empty.
+The
+</ins><code><ins class="diff-chg">
+Link
+</ins></code><ins class="diff-chg">
+header
+field
+indicates
+that
+the
+resource
+</ins><code><ins class="diff-chg">
+http://acme.example.org/super-widget123/provenance
+</ins></code><ins class="diff-chg">
+contains
+provenance
+information
+relating
+</ins>
+to
+<del class="diff-old">POST
+in
+some
+different
+way.
+</del>
+<code>
+<ins class="diff-chg">http://acme.example.org/super-widget123
+</ins></code><ins class="diff-chg">
+(that
+being
+the
+URI
+of
+the
+resource
+for
+which
+the
+pingback
+URI
+was
+provided).
+</ins>
+</p>
+</section>
+<section id="security-considerations">
+<h2>
+<span class="secno">
+6.
+</span>
+Security
+considerations
+</h2>
+<p>
+Provenance
+is
+central
+to
+establishing
+trust
+in
+data.
+If
+provenance
+is
+corrupted,
+it
+may
+lead
+agents
+(human
+or
+software)
+to
+draw
+inappropriate
+and
+possibly
+harmful
+conclusions.
+Therefore,
+care
+is
+needed
+to
+ensure
+that
+the
+integrity
+of
+provenance
+is
+maintained.
+Just
+as
+provenance
+can
+help
+determine
+a
+level
+of
+trust
+in
+some
+information,
+a
+provenance
+record
+related
+to
+the
+provenance
+itself
+("provenance
+of
+provenance")
+can
+help
+determine
+trust
+in
+the
+provenance.
+</p>
+<p>
+<ins class="diff-new">The
+</ins><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec15.html" class="externalRef"><ins class="diff-new">
+HTTP
+security
+considerations
+</ins></a><ins class="diff-new">
+[
+</ins><cite><a class="bibref" href="#bib-HTTP11"><ins class="diff-new">
+HTTP11
+</ins></a></cite><ins class="diff-new">
+]
+generally
+apply
+for
+all
+of
+the
+resources
+and
+services
+located
+through
+the
+mechanism
+in
+this
+document.
+</ins></p><p>
+Secure
+HTTP
+(https)
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+used
+across
+unsecured
+networks
+when
+accessing
+provenance
+that
+may
+be
+used
+as
+a
+basis
+for
+trust
+decisions,
+or
+to
+obtain
+a
+provenance
+URI
+for
+same.
+</p>
+<p>
+When
+retrieving
+a
+provenance
+URI
+from
+a
+document,
+steps
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+taken
+to
+ensure
+the
+document
+itself
+is
+an
+accurate
+copy
+of
+the
+original
+whose
+author
+is
+being
+trusted
+(e.g.
+signature
+checking,
+or
+use
+of
+a
+trusted
+secure
+web
+service).
+(See
+also
+<a class="sectionRef sec-ref" href="#interpreting-provenance-records">
+section
+1.3
+Interpreting
+provenance
+records
+</a>.)
+</p>
+<p>
+Provenance
+may
+present
+a
+route
+for
+leakage
+of
+privacy-related
+information,
+combining
+as
+it
+does
+a
+diversity
+of
+information
+types
+with
+possible
+personally-identifying
+information;
+e.g.
+editing
+timestamps
+may
+provide
+clues
+to
+the
+working
+patterns
+of
+document
+editors,
+or
+derivation
+traces
+might
+indicate
+access
+to
+sensitive
+materials.
+In
+particular,
+note
+that
+the
+fact
+that
+a
+resource
+is
+openly
+accessible
+does
+not
+mean
+that
+its
+provenance
+should
+also
+be.
+When
+publishing
+provenance,
+its
+sensitivity
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+considered
+and
+appropriate
+access
+controls
+applied
+where
+necessary.
+When
+a
+provenance-aware
+publishing
+service
+accepts
+some
+resource
+for
+publication,
+the
+contributors
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+have
+some
+opportunity
+to
+review
+and
+correct
+or
+conceal
+any
+provenance
+that
+they
+don't
+wish
+to
+be
+exposed.
+Provenance
+management
+systems
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+embody
+mechanisms
+for
+enforcement
+and
+auditing
+of
+privacy
+policies
+as
+they
+apply
+to
+provenance.
+<ins class="diff-new">Implementations
+</ins><em class="rfc2119" title="MAY"><ins class="diff-new">
+MAY
+</ins></em><ins class="diff-new">
+choose
+to
+use
+standard
+HTTP
+authorization
+mechanisms
+to
+restrict
+access
+to
+resources,
+returning
+</ins><code><ins class="diff-new">
+401
+Unauthorized
+</ins></code>,<code><ins class="diff-new">
+403
+Forbidden
+</ins></code><ins class="diff-new">
+or
+</ins><code><ins class="diff-new">
+404
+Not
+Found
+</ins></code><ins class="diff-new">
+as
+appropriate.
+</ins>
+</p>
+<p>
+Provenance
+may
+be
+used
+by
+audits
+to
+establish
+accountability
+for
+information
+use
+[
+<cite>
+<a class="bibref" href="#bib-INFO-ACC">
+INFO-ACC
+</a>
+</cite>
+]
+and
+to
+verify
+use
+of
+proper
+processes
+in
+information
+processing
+activities.
+Thus,
+provenance
+management
+systems
+can
+provide
+mechanisms
+to
+support
+auditing
+and
+enforcement
+of
+information
+handling
+policies.
+In
+such
+cases,
+provenance
+itself
+may
+be
+a
+valuable
+target
+for
+attack
+by
+malicious
+agents,
+and
+care
+must
+be
+taken
+to
+ensure
+it
+is
+stored
+securely
+and
+in
+a
+fashion
+that
+resists
+attempts
+to
+tamper
+with
+it.
+</p>
+<p>
+The
+pingback
+service
+described
+in
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>
+might
+be
+abused
+for
+"link
+spamming"
+(similar
+to
+the
+way
+that
+weblog
+ping-backs
+have
+been
+used
+to
+direct
+viewers
+to
+spam
+sites).
+As
+with
+many
+such
+services,
+an
+application
+needs
+to
+find
+a
+balance
+between
+maintaining
+ease
+of
+submission
+for
+useful
+information
+and
+blocking
+unwanted
+information.
+We
+have
+no
+easy
+solutions
+for
+this
+problem,
+and
+the
+caveats
+noted
+above
+about
+establishing
+integrity
+of
+provenance
+records
+apply
+similarly
+to
+information
+provided
+by
+ping-back
+calls.
+</p>
+<p>
+When
+clients
+and
+servers
+are
+retrieving
+submitted
+URIs
+such
+as
+provenance
+descriptions
+and
+following
+or
+registering
+links;
+reasonable
+care
+should
+be
+taken
+to
+prevent
+malicious
+use
+such
+as
+distributed
+denial
+of
+service
+attacks
+(DDoS),
+cross-site
+request
+forgery
+(CSRF),
+spamming
+and
+hosting
+of
+inappropriate
+materials.
+Reasonable
+preventions
+might
+include
+same-origin
+policy,
+HTTP
+authorization,
+SSL,
+rate-limiting,
+spam
+filters,
+moderation
+queues,
+user
+acknowledgements
+and
+validation.
+It
+is
+out
+of
+scope
+for
+this
+document
+to
+specify
+how
+such
+mechanisms
+work
+and
+should
+be
+applied.
+</p>
+<del class="diff-old">Is
+CSRF
+</del>
+<p>
+<ins class="diff-chg">Provenance
+pingback
+uses
+an
+HTTP
+POST
+operation,
+which
+may
+be
+used
+for
+non-"safe"
+interactions
+in
+the
+sense
+of
+[
+</ins><cite><a class="bibref" href="#bib-WEBARCH"><ins class="diff-chg">
+WEBARCH
+</ins></a></cite><ins class="diff-chg">
+]
+(
+</ins><a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#safe-interaction" class="externalRef"><ins class="diff-chg">
+section
+3.4
+</ins></a><ins class="diff-chg">
+).
+Care
+needs
+to
+be
+taken
+that
+user
+agents
+are
+not
+tricked
+into
+POSTing
+to
+incorrect
+URIs
+in
+such
+</ins>
+a
+<del class="diff-old">real
+threat
+here?
+How?
+</del>
+<ins class="diff-chg">way
+that
+may
+incur
+unintended
+effects
+or
+obligations.
+For
+example,
+a
+malicious
+site
+may
+present
+a
+pingback
+URI
+that
+executes
+an
+instruction
+on
+a
+different
+web
+site.
+Risks
+of
+such
+abuse
+may
+be
+mitigated
+by:
+performing
+pingbacks
+only
+to
+URIs
+from
+trusted
+sources;
+performing
+pingbacks
+only
+to
+the
+same
+origin
+as
+the
+provider
+of
+the
+pingback
+URI
+(like
+in-browser
+javascript
+same-origin
+restrictions),
+not
+sending
+credentials
+with
+pingback
+requests
+that
+were
+not
+obtained
+specifically
+for
+that
+purpose,
+and
+any
+other
+measures
+that
+may
+be
+appropriate.
+</ins>
+</p>
+<p>
+Accessing
+provenance
+services
+might
+reveal
+to
+the
+service
+and
+third-parties
+information
+which
+is
+considered
+private,
+including
+which
+resources
+a
+client
+has
+taken
+interest
+in.
+For
+instance,
+a
+browser
+extension
+which
+collects
+all
+provenance
+data
+for
+a
+resource
+which
+is
+being
+saved
+to
+the
+local
+disk,
+could
+be
+revealing
+user
+interest
+in
+a
+sensitive
+resource
+to
+a
+third-party
+site
+listed
+by
+<code>
+prov:has_provenance
+</code>
+or
+<code>
+prov:has_query_service
+</code>
+relation.
+A
+detailed
+query
+submitted
+to
+a
+third-party
+provenance
+query
+service
+might
+be
+revealing
+personal
+information
+such
+as
+social
+security
+numbers.
+Accordingly,
+user
+agents
+in
+particular
+<em class="rfc2119" title="SHOULD NOT">
+SHOULD
+NOT
+</em>
+follow
+provenance
+and
+provenance
+service
+links
+without
+first
+obtaining
+the
+user's
+explicit
+permission
+to
+do
+so.
+</p>
+</section>
+<section class="appendix" id="acknowledgements">
+<h2>
+<span class="secno">
+A.
+</span>
+Acknowledgements
+</h2>
+<p>
+The
+editors
+acknowledge
+the
+contribution
+and
+review
+from
+members
+of
+the
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Provenance
+working
+group
+for
+their
+feedback
+throughout
+the
+development
+of
+this
+specification.
+</p>
+<p>
+<del class="diff-old">The
+provenance
+query
+service
+description
+</del>
+<ins class="diff-chg">Thanks
+to
+Erik
+Wilde
+</ins>
+and
+<del class="diff-old">forward
+provenance
+specifications
+are
+substantially
+based
+on
+proposals
+by
+Stian
+Soiland-Reyes
+(University
+</del>
+<ins class="diff-chg">other
+members
+</ins>
+of
+<del class="diff-old">Manchester).
+</del>
+<ins class="diff-chg">the
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-chg">
+W3C
+</ins></abbr><ins class="diff-chg">
+Linked
+Data
+Platform
+working
+group
+for
+an
+extended
+discussion
+of
+REST
+service
+design
+issues,
+which
+has
+informed
+some
+aspects
+of
+the
+provenance
+service
+mechanisms.
+</ins>
+</p>
+<p>
+Thanks
+to
+Robin
+Berjon
+for
+making
+our
+lives
+easier
+with
+his
+<a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html" class="externalRef">
+ReSpec
+</a>
+tool.
+</p>
+<p>
+<ins class="diff-new">Members
+of
+the
+PROV
+Working
+Group
+at
+the
+time
+of
+publication
+of
+this
+document
+were:
+Ilkay
+Altintas
+(Invited
+expert),
+Reza
+B'Far
+(Oracle
+Corporation),
+Khalid
+Belhajjame
+(University
+of
+Manchester),
+James
+Cheney
+(University
+of
+Edinburgh,
+School
+of
+Informatics),
+Sam
+Coppens
+(iMinds
+-
+Ghent
+University),
+David
+Corsar
+(University
+of
+Aberdeen,
+Computing
+Science),
+Stephen
+Cresswell
+(The
+National
+Archives),
+Tom
+De
+Nies
+(iMinds
+-
+Ghent
+University),
+Helena
+Deus
+(DERI
+Galway
+at
+the
+National
+University
+of
+Ireland,
+Galway,
+Ireland),
+Simon
+Dobson
+(Invited
+expert),
+Martin
+Doerr
+(Foundation
+for
+Research
+and
+Technology
+-
+Hellas(FORTH)),
+Kai
+Eckert
+(Invited
+expert),
+Jean-Pierre
+EVAIN
+(European
+Broadcasting
+Union,
+EBU-UER),
+James
+Frew
+(Invited
+expert),
+Irini
+Fundulaki
+(Foundation
+for
+Research
+and
+Technology
+-
+Hellas(FORTH)),
+Daniel
+Garijo
+(Ontology
+Engineering
+Group,
+Universidad
+Politécnica
+de
+Madrid,
+Spain),
+Yolanda
+Gil
+(Invited
+expert),
+Ryan
+Golden
+(Oracle
+Corporation),
+Paul
+Groth
+(Vrije
+Universiteit),
+Olaf
+Hartig
+(Invited
+expert),
+David
+Hau
+(National
+Cancer
+Institute,
+NCI),
+Sandro
+Hawke
+(
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+/
+</ins><abbr title="Massachusetts Institute of Technology"><ins class="diff-new">
+MIT
+</ins></abbr><ins class="diff-new">
+),
+Jörn
+Hees
+(German
+Research
+Center
+for
+Artificial
+Intelligence
+(DFKI)
+Gmbh),
+Ivan
+Herman,
+(
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+/
+</ins><abbr title="European Research Consortium for Informatics and Mathematics"><ins class="diff-new">
+ERCIM
+</ins></abbr><ins class="diff-new">
+),
+Ralph
+Hodgson
+(TopQuadrant),
+Hook
+Hua
+(Invited
+expert),
+Trung
+Dong
+Huynh
+(University
+of
+Southampton),
+Graham
+Klyne
+(University
+of
+Oxford),
+Michael
+Lang
+(Revelytix,
+Inc.),
+Timothy
+Lebo
+(Rensselaer
+Polytechnic
+Institute),
+James
+McCusker
+(Rensselaer
+Polytechnic
+Institute),
+Deborah
+McGuinness
+(Rensselaer
+Polytechnic
+Institute),
+Simon
+Miles
+(Invited
+expert),
+Paolo
+Missier
+(School
+of
+Computing
+Science,
+Newcastle
+university),
+Luc
+Moreau
+(University
+of
+Southampton),
+James
+Myers
+(Rensselaer
+Polytechnic
+Institute),
+Vinh
+Nguyen
+(Wright
+State
+University),
+Edoardo
+Pignotti
+(University
+of
+Aberdeen,
+Computing
+Science),
+Paulo
+da
+Silva
+Pinheiro
+(Rensselaer
+Polytechnic
+Institute),
+Carl
+Reed
+(Open
+Geospatial
+Consortium),
+Adam
+Retter
+(Invited
+Expert),
+Christine
+Runnegar
+(Invited
+expert),
+Satya
+Sahoo
+(Invited
+expert),
+David
+Schaengold
+(Revelytix,
+Inc.),
+Daniel
+Schutzer
+(FSTC,
+Financial
+Services
+Technology
+Consortium),
+Yogesh
+Simmhan
+(Invited
+expert),
+Stian
+Soiland-Reyes
+(University
+of
+Manchester),
+Eric
+Stephan
+(Pacific
+Northwest
+National
+Laboratory),
+Linda
+Stewart
+(The
+National
+Archives),
+Ed
+Summers
+(Library
+of
+Congress),
+Maria
+Theodoridou
+(Foundation
+for
+Research
+and
+Technology
+-
+Hellas(FORTH)),
+Ted
+Thibodeau
+(OpenLink
+Software
+Inc.),
+Curt
+Tilmes
+(National
+Aeronautics
+and
+Space
+Administration),
+Craig
+Trim
+(IBM
+Corporation),
+Stephan
+Zednik
+(Rensselaer
+Polytechnic
+Institute),
+Jun
+Zhao
+(University
+of
+Oxford),
+Yuting
+Zhao
+(University
+of
+Aberdeen,
+Computing
+Science).
+</ins></p>
+</section>
+<section class="appendix" id="terms-added-to-prov-namespace">
+<h2 id="prov-namespace">
+<span class="secno">
+B.
+</span>
+Terms
+added
+to
+prov:
+namespace
+</h2>
+<del class="diff-old">Possible
+renaming
+of
+service
+description
+relations
+to
+lowercase-only
+forms?
+</del>
+<p>
+This
+specification
+defines
+the
+following
+additional
+names
+in
+the
+provenance
+namespace
+with
+URI
+<a href="http://www.w3.org/ns/prov#" class="externalRef">
+http://www.w3.org/ns/prov#
+</a>.
+</p>
+<table>
+<tbody>
+<tr>
+<th>
+Name
+</th>
+<th>
+Description
+</th>
+<th>
+Definition
+ref
+</th>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+ServiceDescription
+</code>
+</td>
+<td>
+Type
+for
+a
+generic
+provenance
+query
+service.
+Mainly
+for
+use
+in
+RDF
+provenance
+query
+service
+descriptions,
+to
+facilitate
+discovery
+in
+linked
+data
+environments.
+</td>
+<td>
+<a href="#provenance-query-service-discovery" class="sectionRef sec-ref">
+section
+4.3
+Provenance
+query
+service
+discovery
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+DirectQueryService
+</code>
+</td>
+<td>
+Type
+for
+a
+direct
+HTTP
+query
+service
+description.
+Mainly
+for
+use
+in
+RDF
+provenance
+query
+service
+descriptions,
+to
+distinguish
+direct
+HTTP
+query
+service
+descriptions
+from
+other
+query
+service
+descriptions.
+</td>
+<td>
+<a href="#direct-http-query-service-description" class="sectionRef sec-ref">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+has_anchor
+</code>
+</td>
+<td>
+Indicates
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+for
+an
+resource,
+used
+by
+an
+associated
+provenance
+record.
+</td>
+<td>
+<a href="#resource-represented-as-html" class="sectionRef sec-ref">
+section
+3.2
+Resource
+represented
+as
+HTML
+</a>,
+<a href="#resource-represented-as-rdf" class="sectionRef sec-ref">
+section
+3.3
+Resource
+represented
+as
+RDF
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+has_provenance
+</code>
+</td>
+<td>
+Indicates
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+for
+a
+resource;
+the
+resource
+identified
+by
+this
+property
+presents
+a
+provenance
+record
+about
+its
+subject
+or
+anchor
+resource.
+</td>
+<td>
+<a href="#resource-accessed-by-http" class="sectionRef sec-ref">
+section
+3.1
+Resource
+accessed
+by
+HTTP
+</a>,
+<a href="#resource-represented-as-html" class="sectionRef sec-ref">
+section
+3.2
+Resource
+represented
+as
+HTML
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+has_query_service
+</code>
+</td>
+<td>
+Indicates
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>
+that
+can
+access
+provenance
+related
+to
+its
+subject
+or
+anchor
+resource.
+</td>
+<td>
+<a href="#specifying-provenance-query-services" class="sectionRef sec-ref">
+section
+3.1.1
+Specifying
+Provenance
+Query
+Services
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+describesService
+</code>
+</td>
+<td>
+relates
+a
+generic
+provenance
+query
+service
+resource
+(type
+<code>
+prov:ServiceDescription
+</code>
+)
+to
+a
+specific
+query
+service
+description
+(e.g.
+a
+<code>
+prov:DirectQueryService
+</code>
+or
+a
+<code>
+sd:Service
+</code>
+).
+</td>
+<td>
+<a href="#provenance-query-service-description" class="sectionRef sec-ref">
+section
+4.1
+Provenance
+query
+service
+description
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+provenanceUriTemplate
+</code>
+</td>
+<td>
+Indicates
+a
+URI
+template
+string
+for
+constructing
+provenance-URIs
+</td>
+<td>
+<a href="#direct-http-query-service-description" class="sectionRef sec-ref">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+pingback
+</code>
+</td>
+<td>
+Relates
+a
+resource
+to
+a
+provenance
+pingback
+service
+that
+may
+receive
+<del class="diff-old">forward
+</del>
+<ins class="diff-chg">additional
+</ins>
+provenance
+links
+about
+the
+resource.
+</td>
+<td>
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>
+</td>
+</tr>
+</tbody>
+</table>
+<p>
+The
+ontology
+describing
+these
+terms
+is
+<del class="diff-old">at
+paq/prov-aq.ttl
+or
+paq/prov-aq.owl
+Update
+when
+location
+and
+copy
+finalized.
+</del>
+<ins class="diff-chg">available
+</ins><a href="http://www.w3.org/ns/prov-aq" class="externalRef"><ins class="diff-chg">
+here
+</ins></a>.
+</p>
+</section>
+<section id="references" class="appendix">
+<h2>
+<span class="secno">
+C.
+</span>
+<del class="diff-old">Changes
+log
+</del>
+<ins class="diff-chg">References
+</ins>
+</h2>
+<del class="diff-old">Always
+update
+copy
+of
+mercurial
+change
+log.
+Below
+are
+changes
+since
+19
+June.
+</del>
+<section id="informative-references">
+<h3>
+<span class="secno">
+C.1
+</span>
+<del class="diff-old">Changes
+since
+20120619
+publication
+2013-02-27
+16:23
++0000
+35385cbbfb9f
+Graham
+Klyne
+Further
+refinements
+and
+bug
+fixes
+in
+the
+forward
+provenance
+section
+2013-02-27
+15:33
++0000
+2dfd7fac85c9
+Graham
+Klyne
+Merge
+2013-02-27
+15:19
++0000
+bae275eaaf81
+Stian
+Soiland-Reyes
+Added
+Stian
+as
+PROV-AQ
+author
+2013-02-27
+15:33
++0000
+ecf3af571f1e
+Graham
+Klyne
+Changed
+entity-URI
+back
+to
+target-URI,
+and
+updated
+concept
+definition
+to
+indicate
+it
+may
+also
+denote
+an
+activity
+2013-02-27
+13:02
++0000
+d6085196a22d
+Graham
+Klyne
+Some
+tidying
+up
+of
+section
+decsribing
+provenance
+pingback
+2013-02-27
+12:26
++0000
+018e25f63183
+Graham
+Klyne
+Changed
+all
+normative
+</del>
+<ins class="diff-chg">Informative
+</ins>
+references
+<del class="diff-old">to
+informative
+(this
+being
+a
+NOTE)
+2013-02-27
+12:23
++0000
+33eea34f1863
+Graham
+Klyne
+Renamed
+link
+relations
+'hasProvenance',
+'hasAnchor'
+and
+'hasQueryService'
+to
+'has_provenance',
+'has_anchor'
+and
+'has_query_service'
+respectively.
+This
+is
+because
+RFC5988
+strongly
+recommends
+link
+relations
+to
+be
+all
+lowercase.
+2013-02-26
+18:42
++0000
+25eb1149862f
+Graham
+Klyne
+Add
+placeholder
+links
+to
+ontology;
+deleted
+note
+in
+Appendiox
+B
+2013-02-26
+18:33
++0000
+473af1a90df2
+Graham
+Klyne
+Added
+describesService
+in
+appendix
+B
+2013-02-26
+18:24
++0000
+211ff39ee699
+Graham
+Klyne
+Add
+to
+security
+considerations:
+possible
+malicious
+use
+of
+links;
+possible
+information
+leakage
+when
+provenance
+links
+are
+folloiwed,
+or
+services
+used.
+(Stian:58,59)
+2013-02-26
+18:12
++0000
+ec95bc31a43b
+Graham
+Klyne
+Incorporate
+Stian's
+revised
+pingback
+proposal:
+accept
+links
+rather
+than
+actual
+provenance.
+2013-02-26
+17:19
++0000
+eadbf7c04b31
+Graham
+Klyne
+Renamed
+prov:provPingback
+as
+just
+prov:pingback
+(Stian:55)
+2013-02-26
+17:07
++0000
+4fd6242c151c
+Graham
+Klyne
+</del>
+</h3>
+<del class="diff-old">Re-worked
+description
+of
+direct
+HTTP
+query,
+particularly
+escaping
+of
+URI
+special
+characters
+and
+provenance
+formats
+returned.
+Revise
+description
+of
+return
+codes.
+(Section
+4.2)
+2013-02-26
+16:10
++0000
+bbef7256bc91
+Graham
+Klyne
+</del>
+<dl class="bibliography">
+<del class="diff-old">Rename
+prov:ProvenanceQueryService
+to
+prov:ServiceDescription
+2013-02-26
+15:53
++0000
+206caf60d43a
+Graham
+Klyne
+</del>
+<dt id="bib-HTTP11">
+<ins class="diff-chg">[HTTP11]
+</ins>
+</dt>
+<dd>
+<del class="diff-old">Incorporarted
+Stian's
+proposal
+for
+a
+service
+description
+property
+2013-02-26
+14:40
++0000
+ae119d2377ca
+Graham
+Klyne
+</del>
+<ins class="diff-chg">R.
+Fielding
+et
+al.
+</ins><a href="http://www.ietf.org/rfc/rfc2616.txt">
+<del class="diff-old">Query
+service
+</del>
+<cite>
+<ins class="diff-chg">Hypertext
+Transfer
+Protocol
+</ins>
+-
+<del class="diff-old">editorial
+updates
+per
+Stian's
+comments
+35-41,
+including
+re-work
+of
+motivation
+2013-02-26
+13:34
++0000
+1a0bded232fb
+Graham
+Klyne
+Edirtorial
+updates
+in
+response
+to
+Luc's
+comments;
+updated
+CSS
+for
+external
+link
+2013-02-26
+11:26
++0000
+52d0f60610aa
+Graham
+Klyne
+Editorial
+updates
+in
+response
+to
+comments
+by
+Dong
+2013-02-26
+10:44
++0000
+a87d5f3c056c
+Graham
+Klyne
+Moved
+entire
+discussion
+of
+bundles
+in
+section
+2
+to
+a
+NOTE,
+and
+simplified.
+2013-02-26
+10:24
++0000
+fd2f1476c795
+Graham
+Klyne
+Further
+editorial
+changes
+suggestred
+by
+Stian's
+comments
+28,29,30,33;
+quote
+anchor
+parameters
+in
+Link:
+header
+examples
+2013-02-21
+19:16
++0000
+2a38eacd1735
+Graham
+Klyne
+Section
+3,
+editorial
+changes
+and
+reorganization
+of
+text
+suggested
+by
+Stian's
+comments
+(15,16,17,18,19,20,21,22,23,24,25,26,27).
+Moved
+some
+more
+material
+from
+sect
+3
+to
+sect
+1.3,
+and
+trimmed.
+Removed
+duplicate
+material
+about
+authority
+guarantees
+from
+section
+2.
+Added
+URI/IRI
+discussion
+to
+concepts.
+Added
+HTTP
+examples.
+Included
+'#'
+in
+shorthand
+references
+to
+link
+relations.
+2013-02-21
+17:27
++0000
+6c7dc767652a
+Graham
+Klyne
+More
+trimming
+of
+material
+onprovenance
+interpretation
+2013-02-21
+15:57
++0000
+be8f6ec8a2d5
+Graham
+Klyne
+Section
+3,
+editorial
+changes
+and
+reorganization
+of
+text
+suggested
+by
+Stian's
+comments
+(10,11,12,13,14).
+provider
+abnd
+consumer
+definitions
+moved
+to
+1.1.
+Further
+discussion
+of
+provenance
+interpretation
+moved
+to
+section
+1.3.
+2013-02-21
+15:31
++0000
+7e2c896d5b3b
+Graham
+Klyne
+Section
+2,
+non-substantive
+editorial
+changes
+suggested
+by
+Stian's
+comments
+(8,9)
+2013-02-21
+15:22
++0000
+9afefa103a72
+Graham
+Klyne
+Non-substantive
+editorial
+changes
+suggested
+by
+Stian's
+comments
+(4,6,7)
+2013-02-21
+15:07
++0000
+27cf75d7a6f2
+Graham
+Klyne
+Changed
+'target-URI'
+to
+'entity-URI',
+and
+revised
+some
+associated
+text
+to
+describe
+provenance
+access
+with
+respect
+to
+entities.
+Stian's
+comment
+(2)
+2013-02-21
+14:06
++0000
+cc0ec03fed0e
+Graham
+Klyne
+Update
+Turtle
+reference
+to
+CR
+2013-02-21
+13:33
++0000
+2d42fb73e214
+Graham
+Klyne
+Add
+placeholder
+appendix
+for
+change
+log
+2013-02-07
+18:26
++0000
+ae85f08dcda4
+Graham
+Klyne
+Further
+editorial
+fixes
+suggested
+by
+Tim
+2013-02-07
+17:43
++0000
+266d233ce54c
+Graham
+Klyne
+Move
+text
+about
+isolating
+information
+from
+section
+3
+(locating)
+to
+1.3
+(interpreting).
+Tim's
+comment
+(13)
+2013-02-07
+17:29
++0000
+a53fb5b58d8f
+Graham
+Klyne
+Section
+2
+editorial
+rework
+including
+suggestions
+by
+Tim
+2013-02-07
+16:41
++0000
+cf11871bb9ba
+Graham
+Klyne
+Editorial
+fixes
+suggested
+by
+Tim,
+and
+replace
+'provenance
+description'
+with
+'provenance
+record',
+following
+PROV-DM
+2013-02-07
+15:53
++0000
+4d16b451fc1a
+Graham
+Klyne
+Editorial
+fixes
+suggested
+by
+Simon
+2013-02-07
+15:42
++0000
+9406759adad3
+Graham
+Klyne
+Editorial
+fixes
+suggested
+by
+Simon
+2013-02-07
+14:50
++0000
+d5e7a0c76495
+Graham
+Klyne
+Minor
+editorial
+fixes
+suggested
+by
+Ivan
+2013-02-07
+13:44
++0000
+d4cf95c11dcd
+Graham
+Klyne
+Minor
+editorial
+fixes
+suggested
+by
+Ivan
+2013-01-10
+15:43
++0100
+cb49c07522ff
+Paul
+Groth
+updated
+to
+fix
+minor
+editorial
+errors
+2013-01-04
+14:23
++0000
+47a1f3baf67a
+Graham
+Klyne
+Editorial
+tweaks
+2013-01-04
+13:26
++0000
+a374c48027b9
+Graham
+Klyne
+Separate
+prov:DirectQueryService
+(specifric
+mechanism)
+from
+prov:ProvenanceQueryService
+(generic)
+2013-01-04
+13:11
++0000
+7b4580bd6d52
+Graham
+Klyne
+Fix
+some
+section
+cross-references;
+rename
+'prov:hasProvenanceService'
+as
+'prov:hasQueryService'
+2013-01-04
+13:03
++0000
+f00efdbb4f6e
+Graham
+Klyne
+Reorganize
+provenance
+query
+service
+description
+to
+accommodate
+SPARQL
+(ISSUE
+601);
+'rename
+provenance
+service'
+as
+'provenance
+query
+service';
+rename
+'prov:ProvenanceService'
+as
+'prov:ProivenanceQueryService'
+2012-12-10
+22:40
++0000
+08deb1462a7c
+Graham
+Klyne
+Fix
+apostrophe
+2012-12-10
+19:03
++0000
+f0f315c6781c
+Graham
+Klyne
+Fold
+in
+Jun's
+editorial
+comments.
+Remove
+reference
+to
+POWDER
+2012-11-26
+14:43
++0000
+23f86dc89992
+Graham
+Klyne
+Change
+'provenance
+information'
+to
+'provenance
+description'
+(ISSUE
+601);
+extensive
+editorial
+changes
+should
+be
+reviewed
+2012-11-26
+12:07
++0000
+4bbf03ed4eff
+Graham
+Klyne
+Add
+note
+about
+service
+description
+and
+LDP
+consideration
+thereof
+2012-11-26
+11:49
++0000
+72ec0c88ede8
+Graham
+Klyne
+Add
+non-commital
+paragraph
+about
+accessing
+provenance
+bundles
+2012-11-26
+11:08
++0000
+b811ccb53b45
+Graham
+Klyne
+Update
+forward
+provenance
+(pingback)
+in
+response
+to
+comments;
+fix
+text
+around
+VoID
+example
+2012-11-20
+16:00
++0000
+839d503bd064
+Graham
+Klyne
+Added
+specification
+for
+pingback
+link
+header
+(ISSUE
+600)
+2012-11-20
+14:15
++0000
+0e668b4ce436
+Graham
+Klyne
+Tidy
+up
+some
+text
+2012-11-20
+14:03
++0000
+3cba6f76b797
+Graham
+Klyne
+Expanded
+discussion
+of
+provenance
+service
+discovery
+to
+include
+prov:hasProvenanceService
+2012-11-20
+12:22
++0000
+44586518f842
+Graham
+Klyne
+Remove
+speculative
+non-specification
+text
+to
+be
+covered
+in
+FAQ
+(ISSUES
+426,
+598)
+2012-11-20
+11:36
++0000
+2f1a8ca558a8
+Graham
+Klyne
+Added
+section
+with
+table
+of
+URIs
+and
+what
+they
+dereference
+to
+(ISSUE
+424)
+2012-11-20
+10:37
++0000
+d2acceb63c0b
+Graham
+Klyne
+Make
+treatment
+of
+direct
+retrieval
+and
+service
+for
+provenance
+access
+more
+equally
+visible
+(ISSUE
+422)
+2012-11-19
+18:53
++0000
+69d2ba847f40
+Graham
+Klyne
+Point
+out
+that
+provenance
+services
+can
+accept
+paraneters
+other
+than
+just
+'target'
+(ISSUE
+420)
+2012-11-19
+18:10
++0000
+6a283fe7b70c
+Graham
+Klyne
+Added
+definitions
+for
+accessung
+and
+locating
+(ISSUE
+417)
+2012-11-19
+13:23
++0000
+45683a007809
+Graham
+Klyne
+More
+CSS
+tweaking
+to
+override
+RewSopec.js
+colouring
+2012-11-19
+13:06
++0000
+390df423d8b3
+Graham
+Klyne
+Formatting
+and
+CSS
+colour
+tweaks
+for
+examples
+2012-11-19
+12:58
++0000
+7f6c1a541631
+Graham
+Klyne
+Added
+section
+on
+Link:
+headers
+and
+content
+negotiation
+(ISSUE
+416)
+2012-11-19
+12:17
++0000
+9c24773fd6c7
+Graham
+Klyne
+Revert
+to
+W3C
+-hosted
+ReSpec.js
+2012-11-19
+11:48
++0000
+10c290a46ee0
+Graham
+Klyne
+Added
+icon
+to
+distibguish
+external
+links
+(ISSUE
+400)
+2012-11-16
+16:29
++0000
+5f35560288e7
+Graham
+Klyne
+Updsate
+and
+cross-link
+table
+of
+prov:
+URIs
+defined
+2012-11-16
+16:01
++0000
+3144d9093733
+Graham
+Klyne
+Changed
+link
+relations
+to
+URIs;
+removed
+IANA
+considerations
+section
+2012-11-10
+19:03
++0000
+77c849e3d67d
+Graham
+Klyne
+Hyperlink
+concept
+definitions
+to
+themselves
+(per
+request
+from
+Tim
+2012-06-05)
+2012-11-10
+18:26
++0000
+aff3d2fcf8f5
+Graham
+Klyne
+Update
+security
+considerations
+with
+note
+about
+use
+of
+provenance
+as
+part
+of
+audit/enforcement
+mechanism
+2012-11-10
+18:07
++0000
+84864eeceffb
+Graham
+Klyne
+Update
+list
+of
+PROV
+documents,
+copied
+from
+PROV-DM
+2012-11-10
+02:08
++0000
+beb278a59b28
+Graham
+Klyne
+Revert
+JS
+import
+to
+W3C
+server
+2012-11-08
+22:36
++0000
+35ee2d7209ea
+Graham
+Klyne
+Adjust
+TODO
+notes
+2012-11-08
+22:27
++0000
+d269fcdfc9fd
+Graham
+Klyne
+Cut
+back
+on
+verbiage
+in
+sect
+3,4
+rbitrary
+data
+2012-11-08
+22:24
++0000
+aba651f6da5e
+Graham
+Klyne
+Adjust
+TODO
+notes
+2012-11-08
+22:20
++0000
+06627e013264
+Graham
+Klyne
+Revised
+section
+3
+descriptions
+in
+terms
+of
+prodcuers
+and
+consumers
+2012-11-08
+12:12
++0000
+098e7be8b4d5
+Graham
+Klyne
+Updated
+security
+considerations
+to
+mention
+audit
+2012-11-06
+17:04
++0000
+96247e20c8b4
+Graham
+Klyne
+Add
+TODO
+for
+producer/consumer
+roles,
+add
+note
+about
+multiple
+links,
+add
+reference
+to
+RFC3986
+for
+%-escaping
+2012-11-06
+15:17
++0000
+4fbe51a47591
+Graham
+Klyne
+Update
+security
+considerations,
+note
+about
+non-RDF
+service
+desription,
+PROV-O
+link,
+acknowledgements
+2012-06-20
+14:27
+-0700
+d0af0446868d
+Paul
+Groth
+</del>
+<ins class="diff-chg">HTTP/1.1
+</ins></cite>
+<del class="diff-old">updated
+to
+reflect
+newly
+published
+version
+</del>
+</a>.
+<ins class="diff-chg">June
+1999.
+RFC
+2616.
+URL:
+</ins><a href="http://www.ietf.org/rfc/rfc2616.txt"><ins class="diff-chg">
+http://www.ietf.org/rfc/rfc2616.txt
+</ins></a>
+</dd>
+<del class="diff-old">D.
+References
+D.1
+Informative
+references
+</del>
+<dt id="bib-INFO-ACC">
+[INFO-ACC]
+</dt>
+<dd>
+Weitzner,
+Abelson,
+Berners-Lee,
+Feigenbaum,
+Hendler,
+and
+Sussman.
+<a href="http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf">
+<cite>
+Information
+Accountability
+</cite>
+</a>.
+Communications
+of
+the
+ACM,
+Jun.
+2008,
+82-87,
+<a href="http://doi.acm.org/10.1145/1349026.1349043">
+http://doi.acm.org/10.1145/1349026.1349043
+</a>,
+<a href="http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf">
+http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf
+</a>
+(alt)
+</dd>
+<dt id="bib-LINK-REL">
+[LINK-REL]
+</dt>
+<dd>
+M.
+Nottingham,
+<a href="http://www.ietf.org/rfc/rfc5988.txt">
+<cite>
+Web
+Linking
+</cite>
+</a>,
+October
+2010,
+Internet
+RFC
+5988.
+URL:
+<a href="http://www.ietf.org/rfc/rfc5988.txt">
+http://www.ietf.org/rfc/rfc5988.txt
+</a>
+</dd>
+<dt id="bib-PROV-CONSTRAINTS">
+[PROV-CONSTRAINTS]
+</dt>
+<dd>
+James
+Cheney;
+Paolo
+Missier;
+Luc
+Moreau;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">
+<cite>
+Constraints
+of
+the
+PROV
+Data
+Model
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-DC">
+[PROV-DC]
+</dt>
+<dd>
+Daniel
+Garijo;
+Kai
+Eckert;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">
+<cite>
+Dublin
+Core
+to
+PROV
+Mapping
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-dc-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-DICTIONARY">
+[PROV-DICTIONARY]
+</dt>
+<dd>
+Tom
+De
+Nies;
+Sam
+Coppens;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">
+<cite>
+PROV
+<ins class="diff-new">Dictionary:
+Modeling
+Provenance
+for
+</ins>
+Dictionary
+<ins class="diff-new">Data
+Structures
+</ins>
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-DM">
+[PROV-DM]
+</dt>
+<dd>
+Luc
+Moreau;
+Paolo
+Missier;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">
+<cite>
+PROV-DM:
+The
+PROV
+Data
+Model
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-dm-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-dm-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-LINKS">
+[PROV-LINKS]
+</dt>
+<dd>
+Luc
+Moreau;
+Timothy
+Lebo;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">
+<cite>
+Linking
+Across
+Provenance
+Bundles
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-links-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-N">
+[PROV-N]
+</dt>
+<dd>
+Luc
+Moreau;
+Paolo
+Missier;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">
+<cite>
+PROV-N:
+The
+Provenance
+Notation
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-n-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-n-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-O">
+[PROV-O]
+</dt>
+<dd>
+Timothy
+Lebo;
+Satya
+Sahoo;
+Deborah
+McGuinness;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">
+<cite>
+PROV-O:
+The
+PROV
+Ontology
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-o-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-o-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-OVERVIEW">
+[PROV-OVERVIEW]
+</dt>
+<dd>
+Paul
+Groth;
+Luc
+Moreau;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+<cite>
+PROV-OVERVIEW:
+An
+Overview
+of
+the
+PROV
+Family
+of
+Documents
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-overview-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-PRIMER">
+[PROV-PRIMER]
+</dt>
+<dd>
+Yolanda
+Gil;
+Simon
+Miles;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">
+<cite>
+PROV
+Model
+Primer
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-primer-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-SEM">
+[PROV-SEM]
+</dt>
+<dd>
+James
+Cheney;
+ed.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">
+<cite>
+Semantics
+of
+the
+PROV
+Data
+Model
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-sem-20130312
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430
+</ins>
+</a>.
+</dd>
+<dt id="bib-PROV-XML">
+[PROV-XML]
+</dt>
+<dd>
+Hook
+Hua;
+Curt
+Tilmes;
+Stephan
+Zednik;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">
+<cite>
+PROV-XML:
+The
+PROV
+XML
+Schema
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-xml-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-RDF-CONCEPTS11">
+[RDF-CONCEPTS11]
+</dt>
+<dd>
+Richard
+Cyganiak,
+David
+Wood,
+eds.
+<a href="http://www.w3.org/TR/rdf11-concepts/">
+<cite>
+RDF
+1.1
+Concepts
+and
+Abstract
+Syntax
+</cite>
+</a>.
+Working
+Draft.
+URL:
+<a href="http://www.w3.org/TR/rdf11-concepts/">
+http://www.w3.org/TR/rdf11-concepts/
+</a>
+</dd>
+<dt id="bib-REST">
+[REST]
+</dt>
+<dd>
+R.
+Fielding.
+<a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">
+<cite>
+Representational
+State
+Transfer
+(REST)
+</cite>
+</a>.
+2000,
+Ph.D.
+dissertation.
+URL:
+<a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">
+http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
+</a>
+</dd>
+<dt id="bib-REST-APIs">
+[REST-APIs]
+</dt>
+<dd>
+R.
+Fielding.
+<a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">
+<cite>
+REST
+APIs
+must
+be
+hypertext
+driven
+</cite>
+</a>.
+October
+2008
+(blog
+post),
+URL:
+<a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">
+http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
+</a>
+</dd>
+<dt id="bib-RFC2119">
+<ins class="diff-new">[RFC2119]
+</ins></dt><dd><ins class="diff-new">
+S.
+Bradner.
+</ins><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite><ins class="diff-new">
+Key
+words
+for
+use
+in
+RFCs
+to
+Indicate
+Requirement
+Levels.
+</ins></cite></a><ins class="diff-new">
+March
+1997.
+Internet
+RFC
+2119.
+URL:
+</ins><a href="http://www.ietf.org/rfc/rfc2119.txt"><ins class="diff-new">
+http://www.ietf.org/rfc/rfc2119.txt
+</ins></a></dd>
+<dt id="bib-RFC2392">
+[RFC2392]
+</dt>
+<dd>
+E.
+Levinson.
+<a href="http://www.ietf.org/rfc/rfc2392.txt">
+<cite>
+Content-ID
+and
+Message-ID
+Uniform
+Resource
+Locators.
+</cite>
+</a>
+August
+1998.
+Internet
+RFC
+2392.
+URL:
+<a href="http://www.ietf.org/rfc/rfc2392.txt">
+http://www.ietf.org/rfc/rfc2392.txt
+</a>
+</dd>
+<dt id="bib-RFC3986">
+[RFC3986]
+</dt>
+<dd>
+T.
+Berners-Lee;
+R.
+Fielding;
+L.
+Masinter.
+<a href="http://www.ietf.org/rfc/rfc3986.txt">
+<cite>
+Uniform
+Resource
+Identifier
+(URI):
+Generic
+Syntax
+<ins class="diff-new">(RFC
+3986)
+</ins>
+</cite>
+</a>.
+January
+2005.
+<del class="diff-old">RFC
+3986.
+</del>
+<ins class="diff-chg">RFC.
+</ins>
+URL:
+<a href="http://www.ietf.org/rfc/rfc3986.txt">
+http://www.ietf.org/rfc/rfc3986.txt
+</a>
+</dd>
+<dt id="bib-RFC3987">
+[RFC3987]
+</dt>
+<dd>
+M.
+Dürst;
+M.
+Suignard.
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+<cite>
+Internationalized
+Resource
+Identifiers
+(IRIs)
+<ins class="diff-new">(RFC
+3987)
+</ins>
+</cite>
+</a>.
+January
+2005.
+<del class="diff-old">RFC
+3987.
+</del>
+<ins class="diff-chg">RFC.
+</ins>
+URL:
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+http://www.ietf.org/rfc/rfc3987.txt
+</a>
+</dd>
+<dt id="bib-SPARQL-HTTP">
+[SPARQL-HTTP]
+</dt>
+<dd>
+Chimezie
+Ogbuji.
+<a href="http://www.w3.org/TR/sparql11-http-rdf-update/">
+<cite>
+SPARQL
+1.1
+Graph
+Store
+HTTP
+Protocol
+</cite>
+</a>.
+<ins class="diff-new">21
+March
+2013,
+</ins>
+W3C
+<del class="diff-old">Candidate
+Recommendation
+8
+November
+2012,
+</del>
+<ins class="diff-chg">Recommendation.
+</ins>
+URL:
+<a href="http://www.w3.org/TR/sparql11-http-rdf-update/">
+http://www.w3.org/TR/sparql11-http-rdf-update/
+</a>
+</dd>
+<dt id="bib-SPARQL-SD">
+[SPARQL-SD]
+</dt>
+<dd>
+G.
+T.
+Williams.
+<a href="http://www.w3.org/TR/sparql11-service-description/">
+<cite>
+SPARQL
+1.1
+Service
+Description
+</cite>
+</a>.
+<del class="diff-old">2011,
+Work
+in
+progress.
+</del>
+<ins class="diff-chg">21
+March
+2013,
+W3C
+Recommendation.
+</ins>
+URL:
+<a href="http://www.w3.org/TR/sparql11-service-description/">
+http://www.w3.org/TR/sparql11-service-description/
+</a>
+</dd>
+<dt id="bib-TURTLE">
+[TURTLE]
+</dt>
+<dd>
+Eric
+Prud'hommeaux,
+Gavin
+Carothers.
+<a href="http://www.w3.org/TR/turtle/">
+<cite>
+Turtle:
+Terse
+RDF
+Triple
+Language
+</cite>
+</a>.
+19
+February
+2013.
+W3C
+Candidate
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/turtle/">
+http://www.w3.org/TR/turtle/
+</a>
+</dd>
+<dt id="bib-URI-template">
+[URI-template]
+</dt>
+<dd>
+J.
+Gregorio;
+R.
+Fielding;
+M.
+Hadley;
+M.
+Nottingham;
+D.
+Orchard.
+<a href="http://tools.ietf.org/html/rfc6570">
+<cite>
+URI
+Template
+</cite>
+</a>.
+March
+2012,
+Internet
+RFC
+6570.
+URL:
+<a href="http://tools.ietf.org/html/rfc6570/">
+<cite>
+http://tools.ietf.org/html/rfc6570
+</cite>
+</a>
+</dd>
+<dt id="bib-VoID">
+[VoID]
+</dt>
+<dd>
+Keith
+Alexander,
+Richard
+Cyganiak,
+Michael
+Hausenblas,
+Jun
+Zhao.
+<a href="http://www.w3.org/TR/void/">
+<cite>
+Describing
+Linked
+Datasets
+with
+the
+VoID
+Vocabulary
+</cite>
+</a>,
+W3C
+Interest
+Group
+Note
+03
+March
+2011,
+<a href="http://www.w3.org/TR/void/">
+http://www.w3.org/TR/void/
+</a>
+</dd>
+<dt id="bib-WEBARCH">
+[WEBARCH]
+</dt>
+<dd>
+Norman
+Walsh;
+Ian
+Jacobs.
+<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">
+<cite>
+Architecture
+of
+the
+World
+Wide
+Web,
+Volume
+One
+</cite>
+</a>.
+15
+December
+2004.
+W3C
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">
+http://www.w3.org/TR/2004/REC-webarch-20041215/
+</a>
+</dd>
+</dl>
+</section>
+</section>
+</body>
+</html>
+
+