PROV-O telecon summary
PROV-WG Minutes: Dec 22, 2012
prov-wg scribe today
PROV-ISSUE-207 (start and end records): start and end records [prov-dm]
PROV-ISSUE-206 (agent-asserted-not-inferred): agents should not be inferred, and wasAssociatedWith should also work with entities [prov-dm]
PROV-ISSUE-205 (optional-activity-in-generation-record): optional activity in generation record [prov-dm]
PROV-ISSUE-204 (end-of-entity): What marks the end of an entity? [prov-dm]
PROV-DM structural constraints
Re: PROV-ISSUE-150: question on formal semantics of role in wasGeneratedBy relation [Formal Semantics]
Re: PROV-ISSUE-150: question on formal semantics of role in wasGeneratedBy relation [Formal Semantics]
Re: PROV-ISSUE-121: Constraint on PE (PROV-DM and PROV-OM) [Conceptual Model]
Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
Plan for Prov-aq going forward
PROV-WG: Telecon Agenda Dec 22, 2011
Formal semantics draft
PROV-WG: Minutes of Dec 8, 2011 Telcon
prov-wg meeting minutes 2011-12-15
prov-dm WD2 is out
PROV-ISSUE-203: Proposal to amend definition and usage of Plan in PROV-DM [prov-dm]
- Re: PROV-ISSUE-203: Proposal to amend definition and usage of Plan in PROV-DM [prov-dm]
- Re: PROV-ISSUE-203: Proposal to amend definition and usage of Plan in PROV-DM [prov-dm]
- Re: PROV-ISSUE-203: Proposal to amend definition and usage of Plan in PROV-DM [prov-dm]
Re: viewOf / complementOf discussion in 201-12-15 telecon (correction)
viewOf / complementOf discussion in 201-12-15 telecon
- Re: viewOf / complementOf discussion in 201-12-15 telecon
- Re: viewOf / complementOf discussion in 201-12-15 telecon
complementOf -> viewOf: proposed text
scribe required for today's call ... thank you!
provenance working group issues (more around process but some technical
Fwd: Contributions and Supersedes
prov-dm: new interpretation section
prov-dm: draft for the new 'hadPlan' relation
PROV-WG Telecon Agenda 15 Dec 2011
Revised primer for public release
- Re: Revised primer for public release
- Re: Revised primer for public release
- Re: Revised primer for public release
Prov-o fpwd
Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- Re: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- Re: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- Re: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- RE: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- Re: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- Re: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
- Re: Proposals to vote on related to 'event': deadline Dec 14th midnight GMT
PROV-ISSUE-202 (PROV-AQ-coverage-summary): PROV-AQ give brief map of contents in introduction [Accessing and Querying Provenance]
Re: ISSUE-23: Create definition of involve to replace Use
Apologies - telecon 8 Dec
Re: PROV-ISSUE-182 (TLebo): stronger name for "wasAssociatedWith" [prov-dm]
Detailed fedback on PROV-DM document
Re: PROV-ISSUE-151 (TLebo): Rename wasQuoteOf to wasQuotedFrom [Data Model]
Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model]
Re: PROV-ISSUE-101 (Conceptual Model): Section 5.2.2 ProcessExecution (conceptual model document review) [Conceptual Model]
prov-dm - when are constructs too domain specific?
- Re: prov-dm - when are constructs too domain specific?
- Re: prov-dm - when are constructs too domain specific?
PROV-WG: Telecon Agenda
PROV-ISSUE-201: Section 8 (PROV-DM as on Dec 5) [prov-dm]
- Re: PROV-ISSUE-201: Section 8 (PROV-DM as on Dec 5) [prov-dm]
- Re: PROV-ISSUE-201: Section 8 (PROV-DM as on Dec 5) [prov-dm]
PROV-ISSUE-200: Section 6.3 (PROV-DM as on Dec 5) [prov-dm]
PROV-ISSUE-199: Section 6.2 (PROV-DM as on Dec 5) [prov-dm]
PROV-ISSUE-198: Section 6.1 (PROV-DM as on Dec 5) [prov-dm]
PROV-ISSUE-197: Section 5.4.1 and Section 5.4.2 (PROV-DM as on Dec 5)
PROV-ISSUE-196: Section 5.3.4 (PROV-DM as on Dec 5)
PROV-ISSUE-195: Section 5.3.3.3 (PROV-DM as on Dec 5)
PROV-ISSUE-194: Section 5.3.3.1 and Section 5.3.3.2 (PROV-DM as on Nov 28)
PROV-ISSUE-193: Section 5.3.2.2 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-192: Section 5.3.2.1 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-191: Section 5.3.1.2 (PROV-DM as on Nov 28) [prov-dm]
- Re: PROV-ISSUE-191: Section 5.3.1.2 (PROV-DM as on Nov 28) [prov-dm]
- Re: PROV-ISSUE-191: Section 5.3.1.2 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-190: Section 5.3.1.1 (PROV-DM as on Nov 28) [prov-dm]
- Re: PROV-ISSUE-190: Section 5.3.1.1 (PROV-DM as on Nov 28) [prov-dm]
- Re: PROV-ISSUE-190: Section 5.3.1.1 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-189: Section 5.2.4 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-188: Section 5.2.3 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-187: Section 5.2.2 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-186: Section 5.2.1 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-185: Section 3 (PROV-DM as on Nov 28) [prov-dm]
PROV-ISSUE-184: Section 2.1.2 (PROV-DM version as on Nov 28th) [prov-dm]
- Re: PROV-ISSUE-184: Section 2.1.2 (PROV-DM version as on Nov 28th) [prov-dm]
- Re: PROV-ISSUE-184: Section 2.1.2 (PROV-DM version as on Nov 28th) [prov-dm]
- Re: PROV-ISSUE-184: Section 2.1.2 (PROV-DM version as on Nov 28th) [prov-dm]
Re: PROV-ISSUE-49 (Participation): Suggested definition for Participation [Conceptual Model]
Meeting minutes 2011-12-01
Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
- Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
- Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
- Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
- Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
- Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
- Re: PROV-ISSUE-183 (prov-dm-identifiers): identifiers in prov-dm [prov-dm]
PROV-O call
Re: PROV-DM derivation concerns arising from my primer review
Re: PROV-ISSUE-155 (prov-o-pre-fpwd): general comments on prov-o document [Formal Semantics]
Re: PROV-ISSUE-158 (TLebo): Cite temporal ordering constraint [Data Model]
PROV-ISSUE-182 (TLebo): stronger name for "wasAssociatedWith" [prov-dm]
Re: PROV-ISSUE-143 (Tlebo): Qualifiers - why does order matter? [Data Model]
Re: PROV-ISSUE-126: Section 5.3.3.2 "Process Execution Independent Derivation Expression." [Data Model]
Re: PROV-ISSUE-48 (Provenance Concept: Revision): Revision should be a class and not a property [Conceptual Model]
Re: PROV-ISSUE-168 (TLebo): HTTP POSTing a provenance URI to an originating source [Accessing and Querying Provenance]
Re: PROV-ISSUE-124: Constraints on Used Relation (PROV-DM and PROV-OM) [Conceptual Model]
Re: PROV-ISSUE-166 (TLebo): Sufficient _what_?
Re: PROV-ISSUE-175 (TLebo): 4.3 Provenance service discovery [Accessing and Querying Provenance]
Re: Primer first draft for review
Re: PROV-ISSUE-164 (TLebo): pre-determined versus determined [Accessing and Querying Provenance]
Re: PROV-ISSUE-162 (TLebo): Entities can only be web resources? [Accessing and Querying Provenance]
Re: PROV-ISSUE-172 (TLebo): purpose of prov:hasAnchor [Accessing and Querying Provenance]
Re: PROV-ISSUE-167 (TLebo): What is a "normal web resource"? [Accessing and Querying Provenance]
Re: A proposal for modeling agents
Re: PROV-ISSUE-157 (TLebo): wasInformedBy's non-transitivity
Re: PROV-ISSUE-155 (prov-o-pre-fpwd): general comments on prov-o document [Formal Semantics]
Re: SPARQL endpoint discovery - two suggestions
Re: Comments on PAQ
PROV-ISSUE-181 (TLebo): include reference to SPARQL service description [Accessing and Querying Provenance]
Re: PROV-ISSUE-154 (RDF-provenance-service-uri): Include provenance-service-uri for RDF resources [Accessing and Querying Provenance]
Re: PROV-ISSUE-152 (QualifiedInvolvement): will the QualifiedInvolvement approach work for other relations? [Ontology]
PROV-ISSUE-180 (TLebo): defaults to prov:steps="n" causes issue in PROV-O [prov-dm]
- Re: PROV-ISSUE-180 (TLebo): defaults to prov:steps="n" causes issue in PROV-O [prov-dm]
- Re: PROV-ISSUE-180 (TLebo): defaults to prov:steps="n" causes issue in PROV-O [prov-dm]
Re: PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model]
- Re: PROV-ISSUE-156 (TLebo): information flow ordering record - no temporal constraints? [Data Model]
Re: PROV-O comments
PROV-ISSUE-179 (TLebo): defaults to prov:steps="n" causes issue in PROV-O [prov-dm]
PROV-ISSUE-178 (TLebo): wasStartedBy constraint between started and generated entity [prov-dm]
PROV-ISSUE-177 (TLebo): wasStartedBy's name is overloaded? [prov-dm]
PROV-ISSUE-176 (TLebo): wasInformedBy's non-transitivity example is confusing [prov-dm]
PROV-WG: F2F2 logistics information
Complementarity
PROV-WG: Christmas Break
Re: Examoples in primer
scribe for today
Re: PROV-ISSUE-153 (complementarity): Complementarity description differs from model definition [Primer]
- Re: PROV-ISSUE-153 (complementarity): Complementarity description differs from model definition [Primer]
- Re: PROV-ISSUE-153 (complementarity): Complementarity description differs from model definition [Primer]
- Re: PROV-ISSUE-153 (complementarity): Complementarity description differs from model definition [Primer]
Renaming of ProcessExecution to Activity
PROV-WG Minutes Nov 24, 2011 Telecon
Re: Plan to progress PROV-AQ to FPWD
Closing issues on PROV-AQ
PAQ working draft document renamed to PROV-AQ
Prov-wg: ignore that last email...
Tech Team Telecon: Agenda
Re: PROV-ISSUE-142 (Tlebo): Can roles only be Literals? [Data Model]
- Re: PROV-ISSUE-142 (Tlebo): Can roles only be Literals? [Data Model]
- Re: PROV-ISSUE-142 (Tlebo): Can roles only be Literals? [Data Model]