Difference between revisions of "F2F1 Access and Query Proposal"

From Provenance WG Wiki
Jump to: navigation, search
(Scope)
(Scope)
Line 5: Line 5:
 
== Scope ==
 
== Scope ==
  
Consider the following scenario. A user gains access to a resource through browsing the web and downloading it, by receiving by email, transferring it via FTP, or by some other protocol. The client software (browser, email client etc.) offers an "Oh yeah?" button, by which the provenance of the resource will be retrieved and displayed. What does the client do on the button being clicked, what information does it need in order to perform the retrieval, and where does that information come from?
+
Consider the following scenario. A user gains access to an online resource through browsing the web and downloading it, by receiving by email, transferring it via FTP, or by some other protocol. The client software (browser, email client etc.) offers an "Oh yeah?" button, by which the provenance of the resource will be retrieved and displayed. What does the client do on the button being clicked, what information does it need in order to perform the retrieval, and where does that information come from?
  
 
To meet time constraints before the F2F meeting, this document will concern two questions only:
 
To meet time constraints before the F2F meeting, this document will concern two questions only:

Revision as of 19:50, 5 June 2011

Access and Query Proposal for the F2F1

This page concerns provenance access and query in preparation for the first F2F meeting, focusing on a limited range of aims, proposing solutions and presenting open issues regarding those aims. The wider objectives of the access and query task force will be clarified in discussion after the meeting.

Scope

Consider the following scenario. A user gains access to an online resource through browsing the web and downloading it, by receiving by email, transferring it via FTP, or by some other protocol. The client software (browser, email client etc.) offers an "Oh yeah?" button, by which the provenance of the resource will be retrieved and displayed. What does the client do on the button being clicked, what information does it need in order to perform the retrieval, and where does that information come from?

To meet time constraints before the F2F meeting, this document will concern two questions only:

  1. Given the identity, I, of a resource state representation and a location, L, from which to retrieve provenance, how do we obtain the provenance of the representation from the location?
  2. How can a browser find I and L (as above) for an HTML document that was downloaded, so that its provenance may be retrieved?

Obtaining the provenance of a document from its identity

Proposals to meet the first aim

Obtaining the provenance of an HTML document

Proposals to meet the second aim

The identity of the HTML document and the location from which to download its provenance can be embedded in the HTML itself.

Issues regarding the above

Open discussions, informative notes, criticisms, etc. regarding the proposals above. These would ideally be articulated as short specific questions which can be discussed individually at the F2F meeting.

Issues beyond scope

Issues about provenance access and query that go beyond the two specific aims above. These will either be discussed at the F2F meeting if there is time, or else postponed until after.