Difference between revisions of "ProvenanceAccessScenarioUsingPAQ"

From Provenance WG Wiki
Jump to: navigation, search
Line 3: Line 3:
 
== Online HTML Documents D1 and D2 ''(Resource provider aware of provenance)'' ==
 
== Online HTML Documents D1 and D2 ''(Resource provider aware of provenance)'' ==
 
* '''Obtaining the document D'''
 
* '''Obtaining the document D'''
* HTML documents '''[https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html D1]''' and '''[http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/att-0031/crime.html D2]''' are accessed using HTTP GET, and the web servers return '''Link:''' headers as follows. We show examples using both the alternate proposals for anchor as a ''parameter'' and as a ''relation''.
+
* HTML documents '''[https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html D1]''' and '''[http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/att-0031/crime.html D2]''' are accessed using HTTP GET, and the web servers return ''provenance'' and ''anchor'' '''Link:''' headers. We show examples using both the alternate proposals for anchor as a ''parameter'' and as a ''relation''.
 
''Using anchor parameter''
 
''Using anchor parameter''
 
  GET https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html HTTP/1.1
 
  GET https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html HTTP/1.1
Line 39: Line 39:
  
 
* '''Enacting the "Oh yeah?" feature'''
 
* '''Enacting the "Oh yeah?" feature'''
* ''A user requests a web browser (W) used to obtain the web documents (D1-2) to enact the "Oh yeah?" feature on the whole documents''
+
* ''A user requests a web browser ('''W''') used to obtain the web documents (D1-2) to enact the "Oh yeah?" feature on the whole documents''
 
*# The web browser examines the HTTP response headers of the web documents to identify '''Link:''' headers and selects those that contain the relations, ''provenance'' or ''anchor''.
 
*# The web browser examines the HTTP response headers of the web documents to identify '''Link:''' headers and selects those that contain the relations, ''provenance'' or ''anchor''.
 
*# The browser extracts the ''provenance-uri'' information, '''I_P''', from the ''provenance'' relation header. In the above example, '''I_P''' is ''http://example.com/provenance/d1.prov'' for '''D1''' and ''http://example.com/provenance/d2.prov'' for '''D2'''.
 
*# The browser extracts the ''provenance-uri'' information, '''I_P''', from the ''provenance'' relation header. In the above example, '''I_P''' is ''http://example.com/provenance/d1.prov'' for '''D1''' and ''http://example.com/provenance/d2.prov'' for '''D2'''.
Line 45: Line 45:
  
 
* '''Accessing the provenance'''
 
* '''Accessing the provenance'''
* '''What information (I) does the clients (W) need in order to access and retrieve the provenance for the documents D1-2?''
+
* ''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-uris'' '''I_P''' for the two documents, which in our example is using a HTTP GET to retrieve the provenance document '''P'''.
 
* The browser uses the default mechanism for dereferencing the ''provenance-uris'' '''I_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-uri'' '''I_C''' that is relevant for the documents '''D1''' and '''D2'''.
 
* The browser examines the provenance document '''P''' to locate the "section" that corresponds to the ''context-uri'' '''I_C''' that is relevant for the documents '''D1''' and '''D2'''.
  
 
== Online Image Document D3 ''(Resource provider aware of provenance)'' ==
 
== Online Image Document D3 ''(Resource provider aware of provenance)'' ==
 +
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.
  
== Online Image Document D4 ''(Resource provider NOT aware of provenance)'' ==
+
''Using anchor parameter''
 +
GET https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png HTTP/1.1
 +
...
 +
 +
HTTP/1.1 200 OK
 +
...
 +
Link: http://example.com/provenance/d1.prov; rel="provenance"; anchor="https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png"
 +
 +
 +
''Using anchor relation''
 +
GET https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png HTTP/1.1
 +
...
 +
 +
HTTP/1.1 200 OK
 +
...
 +
Link: http://example.com/provenance/d1.prov; rel="provenance";
 +
Link: https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png; rel="anchor"
 +
 
  
== Email attachments of HTML and Image Documents D5 and D6 ==
+
== HTML Documents D5 and D7 as Email attachments or in File System ==
 +
* '''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.
 +
 
 +
* ''Enacting the "Oh yeah?" feature''
 +
* ''A user requests an email client ('''E''') and a command shell ('''S''') used to obtain the HTML document (D5, D7) to enact the "Oh yeah?" feature on the whole documents''
 +
*
 +
 
 +
== Online Image Document D4 ''(Resource provider NOT aware of provenance)'' ==
  
== HTML and Image Documents D7 and D8 in File System ==
+
== Image Documents D6 and D8 as Email attachments or in File System ==

Revision as of 12:37, 18 August 2011

Walk through of how the Provenance Access Scenario is satisfied using the Provenance Access and Query (W3C Editor's Draft 17 August 2011) proposal.

Online HTML Documents D1 and D2 (Resource provider aware of provenance)

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

Using anchor parameter

GET https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html HTTP/1.1
...

HTTP/1.1 200 OK
...
Link: http://example.com/provenance/d1.prov; rel="provenance"; anchor="https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html"

GET http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/att-0031/crime.html HTTP/1.1
...

HTTP/1.1 200 OK
...
Link: http://example.com/provenance/d2.prov; rel="provenance"; anchor="http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/att-0031/crime.html"

Using anchor relation

GET https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html HTTP/1.1
...

HTTP/1.1 200 OK
...
Link: http://example.com/provenance/d1.prov; rel="provenance"; 
Link: https://github.com/timrdf/vsr/raw/master/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.html; rel="anchor" 

GET http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/att-0031/crime.html HTTP/1.1
...

HTTP/1.1 200 OK
...
Link: http://example.com/provenance/d2.prov; rel="provenance"; 
Link: http://lists.w3.org/Archives/Public/public-prov-wg/2011Jul/att-0031/crime.html; rel="anchor" 
  • Accessing the provenance
  • 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-uris I_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-uri I_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.

Using anchor parameter

GET https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png HTTP/1.1
...

HTTP/1.1 200 OK
...
Link: http://example.com/provenance/d1.prov; rel="provenance"; anchor="https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png"


Using anchor relation

GET https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png HTTP/1.1
...

HTTP/1.1 200 OK
...
Link: http://example.com/provenance/d1.prov; rel="provenance"; 
Link: https://github.com/timrdf/vsr/raw/11e4a2ab0315ba7808a393e2a0b5f69f952b7235/data/source/tim-lebo/london-crime/version/2011-Jul-07/manual/crime.png; rel="anchor" 
 

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

  • Enacting the "Oh yeah?" feature
  • A user requests an email client (E) and a command shell (S) used to obtain the HTML document (D5, D7) to enact the "Oh yeah?" feature on the whole documents

Online Image Document D4 (Resource provider NOT aware of provenance)

Image Documents D6 and D8 as Email attachments or in File System