ProvenanceAccessScenario

From Provenance WG Wiki
Revision as of 13:55, 14 July 2011 by Ysimmhan (Talk | contribs)

Jump to: navigation, search

Created by the Access and Query Task Force at the F2F1 to allow the WG to compare the different access proposals prepared and discussed at the meeting.

Abstract Description

  • A user obtains a document (D). The initial scenario will focus on an html document without inclusions such as javascript or images.
  • The client software (browser, email client etc.) offers an "Oh yeah?" feature, by which provenance (P) of the document is accessed and maybe retrieved by the client software.
  • Provenance for the complete document is accessed from the document provider as well as from third-parties.
  • What does the client do when the feature is enacted?
    • what information (I) does it need in order to perform the retrieval/access of provenance?
    • where does information I come from?
  • We should consider that document (D) was downloaded from the web, obtained from an email attachment, or found on a USB stick.
  • We should consider that access control over provenance may be required
  • Multiple formats for provenance may be available from the provider or third parties. The "Oh yeah?" feature may want to select which format to retrieve.


Issues to consider in the future:

  • Could we rephrase without reference to provenance, say it refers to trust?
  • Should we consider getting the provenance of the whole document or part of it?
  • It is out of scope to reconcile potentially conflicting provenance
  • How to retrieve provenance partially

Scenario rationale

  • email/USB don't have a URL
  • http/email have in band metadata

Concrete Example

As a concrete example for this access scenario, we start with a minimal document D whose text is:

<html>
   <body>
      <p>There was a lot of crime in London last month.</p>
   </body> 
</html>

The text There was a lot of crime in London last month. is a minimal portion of the hypothetical article art1 from the Data Journalism Example. All other components of art1 (i.e., the incidence map, chart, and photograph) are excluded from this scenario so we can focus on access, not modeling.

Obtaining document D

In this scenario, the document D can be obtained from the web at one or more locations. The same document D can also be obtained as an email attachment (e.g., in the email sent to public-prov-wg@w3.org). Copying from a USB drive is a third way to obtain the document D.

Variety of forms

To emphasize the fact that the text of document D (i.e., <html><body><p>There was a lot of crime in London last month.</p></body></html) can take a variety of forms, an image on github and an email's image attachment are available.

Starting with the basics, and adding provenance

Document D is as simple as we could make it. Then we set them up on the web and in email. They can also be on your hard drive. So what do we have to add to enable access to provenance for these four files (html, html, png, png)?