Provenance Incubator Group Teleconference

13 Aug 2010

See also: IRC log


+1.518.326.aaaa, +30281039aabb, +30281039aacc


<trackbot> Date: 13 August 2010

<jcheney> http://www.w3.org/2005/Incubator/prov/wiki/User_Requirements#Disease_Outbreak_Scenario

James will talk abt his ideas on the Disease Outbreak scenario that he has worked out until now

<jcheney> http://www.w3.org/2005/Incubator/prov/wiki/Analysis_of_Disease_Outbreak_Scenario

imagine having a richer provenance infrastructure layer to handle with this problem.

not sure if we can associate this with the other scenarios

for instance the cases in the presence of dynamic data -- might be illustrated by other scenarios but might be more complex in this one.

Tim: how does james see the form of information and how can this interact with structured data

James: info starts as unstructured, but eventually people are interested in asking structured complex queries
... this observation comes from people in Bioinformatics. from a usability point of view, figuring out a schema is not trivial as data grows in different ways.
... the provenance infrastructure should be agnostic from the structure below
... the important parts of the scenario can be found at : http://www.w3.org/2005/Incubator/prov/wiki/User_Requirements#Disease_Outbreak_Scenario and http://www.w3.org/2005/Incubator/prov/wiki/Analysis_of_Disease_Outbreak_Scenario
... on the public policy side-- there is work that automatically record decision making
... in the UK it is required to produce reports for cost benefit analysis (e.g., what the impact on X is on Y)
... triangular structure in the scenario (users who are trying to understand, reuse, the data and decision makers)
... the point is that there are multiple levels of abstraction for the specification of provenance -- different ways of saying / expressing provenance information)


Daniel: no substantial progress, 46 untagged papers & relevant papers for the scenario

untagged papers should be tagged in the following weeks. & progress of tagging of relevant papers for the disease outbreak scenario

& we should tag the relevant papers to provenance with the #provenance tag

(this is not done)

James: better to think of the scenario and then tag relevant papers instead of going through the list and tag

+1 from me

Daniel: before uploading entries make sure that the entry does not exist

<timlebo_rpi> http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Dimensions

<DGarijo> that url is what I used too ;)

<timlebo_rpi> http://www.w3.org/2005/Incubator/prov/wiki/Requirements

<jcheney> http://www.w3.org/2005/Incubator/prov/wiki/User_Requirements#Requirements_for_Provenance_on_the_Web_2

trackbot, end telcon

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/08/13 15:36:40 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: Irini
Inferring Scribes: Irini

WARNING: No "Topic:" lines found.

Default Present: +1.518.326.aaaa, +30281039aabb, +30281039aacc
Present: +1.518.326.aaaa +30281039aabb +30281039aacc

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 13 Aug 2010
Guessing minutes URL: http://www.w3.org/2010/08/13-prov-xg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]