W3C

- DRAFT -

Provenance Incubator Group Teleconference

14 May 2010

Agenda

See also: IRC log

Attendees

Present
Yolanda, jcheney, +49.302.093.aabb, Ivan, olaf, Yogesh, michaelp, +1.619.524.aacc, jun, paolo, SamCoppens, dgarijo, +1.518.608.aadd
Regrets
Chair
Yolanda Gil
Scribe
SamCoppens

Contents


<trackbot> Date: 14 May 2010

<olaf> http://www.slideshare.net/olafhartig/brief-introduction-to-the-provenance-vocabulary-for-w3c-provxg

<scribe> Scribe: SamCoppens

<JIm> Zakim ??P18 is JIm

Olaf: Provenance voabulary meant for publishing provenance of Linked Data
... vocabulary must be understandable
... no granlularity is predefined
... aother vocabularies are used for a more detailed description along the linked data principle
... Provenance vocabulary contains links to related vocabularies
... aim is to integrate provenance data in the web of data
... development of metadata components automatically generate provenance data
... provenance data in addition of the published linked data
... Future work: allignment of provenance vocabularies
... Future work: extra modules for aspects not covered yet by the provenance vocabulary
... Future work: extra publication tools

<JIm> Can you discuss slide 11...

<ssahoo> Provenir ontology slides: http://knoesis.wright.edu/library/download/ProvenirOntology_satyasahoo.pdf

Jun: mappings allow to query different provenance vocabularies
... concern: the vocabulary is not meant to describe everything

yolanda: How is the linked data community is thinking in terms of provenance, what are the requirements, ...

Olaf: Not many usecases untill now, general understanding: publish and then see how it is used
... The provenance vocab delivers the means for this
... next step is see how this provenance information can be used

Jun: also used for evaluation of the published data

Yolanda: How much of the provenance data is being consumated?

<JIm> +q

Olaf: they can use provenance descriptions and a more detailed description can be delivered by e.g. OPM
... At least some of the provenance data, e.g. Dublin Core, is being used and a little more complicated model can help with this

<paolo> http://knoesis.wright.edu/library/download/ProvenirOntology_satyasahoo.pdf

Satya: Provenir Ontology

Upper ontology used for creating domain ontologies

Satya: e.g. Trident ontology, Janus Ontology, Parasite Experiment Ontology
... This allows interoperability between the domain ontologies
... Query operators support provenance queries
... query engine supports query operators
... support for rdfs entailments
... -->reasoning!
... support for the full provenance cycle
... capture the provenance of the rdf statements (slide 12)
... From which source are the rdf triples derived from
... derives_from gives all the provenance information (slide 13)

Yolanda: provenance of published articles, but we haven't dealt with the complexity of the process
... how to deal with the granularity?

Satya: provenir does not deal with the complexity
... provenance can be domain specific, e.g. the description of the processes involved

Why no relationship: generated_by_process

?

Satya: you can create specialised properties for this

Next topic: the mappings

<olaf> http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings

Satya: creation of set of mappings between the provenance vocabularies
... approach: used the terms of the OPM model as a starting point
... other provenance terms from other vocabularies are mapped to this

Olaf: this is only a first step
... second step: which properties doesn't fit to OPM
... Third step: to which term can these be mapped then

Michael: some elements are not provenance focused
... these mappings can be very useful

<michaelp> Other null-mappings will be provenance-focussed elements that are not part of OPM

Satya: Every Thursday on 11 am Boston

<Jose_> -Jose_

rssagent, draft minutes

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/05/14 16:07:38 $

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)

Found Scribe: SamCoppens
Inferring ScribeNick: SamCoppens

WARNING: No "Topic:" lines found.

Default Present: Yolanda, jcheney, +49.302.093.aabb, Ivan, olaf, Yogesh, michaelp, +1.619.524.aacc, jun, paolo, SamCoppens, dgarijo, +1.518.608.aadd
Present: Yolanda jcheney +49.302.093.aabb Ivan olaf Yogesh michaelp +1.619.524.aacc jun paolo SamCoppens dgarijo +1.518.608.aadd
Agenda: http://lists.w3.org/Archives/Public/public-xg-prov/2010May/0005.html
Found Date: 14 May 2010
Guessing minutes URL: http://www.w3.org/2010/05/14-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]