This case is similar to the previous in all respects. The fact that the document '''[https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png D3]''' is an image and not a HTML document makes no difference. The HTTP GET request and response are shown as example.

+

This case is similar to the previous in all respects. The fact that the document '''[https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png D3]''' is an image and not a HTML document makes no difference. The HTTP GET request and response are shown as example. The means for enacting the ''"Oh yeah?"'' button and accessing the provenance are the same as before.

''Using anchor parameter''

''Using anchor parameter''

Line 73:

Line 73:

== HTML Documents D5 and D7 as Email attachments or in File System ==

== HTML Documents D5 and D7 as Email attachments or in File System ==

* '''Obtaining the document D'''

* '''Obtaining the document D'''

−

* HTML documents '''D5''' arrived as an email attachment (''http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/0031.html'') while '''D7''' is preset in the file system (''//acme/downloads/crime.html''). The contents of these documents are accessible to the local client.

+

* HTML document '''D5''' arrived as an attachment to the email ''http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/0031.html'' while HTML document '''D7''' is present in the file system at ''//acme/downloads/crime.html''. The contents of these documents are accessible to the local client.

+

* The HTML documents have ''Link'' elements embedded under in their HTML ''HEAD'' section as follows:

HTML documents D1 and D2 are accessed using HTTP GET, and the web servers return provenance and anchorLink: headers. We show examples using both the alternate proposals for anchor as a parameter and as a relation.

What information (I) does the clients (W) need in order to access and retrieve the provenance for the documents D1-2?

The browser uses the default mechanism for dereferencing the provenance-urisI_P for the two documents, which in our example is using a HTTP GET to retrieve the provenance document P.

The browser examines the provenance document P to locate the "section" that corresponds to the context-uriI_C that is relevant for the documents D1 and D2.

Online Image Document D3 (Resource provider aware of provenance)

This case is similar to the previous in all respects. The fact that the document D3 is an image and not a HTML document makes no difference. The HTTP GET request and response are shown as example. The means for enacting the "Oh yeah?" button and accessing the provenance are the same as before.