Re: PROV-ISSUE-134: Non-Human Agent vs. Human Agent [Data Model]
Re: PROV-ISSUE-130 (YolandaGil): Definition and examples of "agent" should be clarified in Provenance Data Model (PROV-DM) Draft [Data Model]
Re: PROV-ISSUE-129 (YolandaGil): Definitions of "Activity"/"Event"/"ProcessExecution" should be more crisp and differentiable in Provenance Data Model (PROV-DM) Draft [Data Model]
Re: PROV-ISSUE-127: Constraint id= participation (PROV DM and PROV ontology) [Data Model]
Re: PROV-ISSUE-113: wasScheduledAfter is transitive [Conceptual Model]
Re: ISSUE-23: Create definition of involve to replace Use
Re: PROV-ISSUE-94 (pe-attributes): are process executions characterized in the same way as entities? [Conceptual Model]
Re: PROV-ISSUE-91 (what-to-define-for-location): what should we define under the heading 'location' [Conceptual Model]
Re: PROV-ISSUE-82 (pidm-event): Should we introduce a notion of event in the data model? [Conceptual Model]
Re: PROV-ISSUE-81 (identity-clash-scope): In a given scope, are entities with same identifier but different attributes legal? [Conceptual Model]
Re: PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
Re: PROV-ISSUE-69 (Process Execution): Process execution occurs over a "continuous time interval"? [Conceptual Model]
Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
Re: PROV-ISSUE-51 (asserter-def): Asserter needs to be defined with respect to a provenance container/account [Conceptual Model]
Re: PROV-ISSUE-51 (asserter-def): Asserter needs to be defined with respect to a provenance container/account [Conceptual Model]
Re: PROV-ISSUE-50 (Ordering of Process): Defintion for Ordering of Process [Conceptual Model]
Re: PROV-ISSUE-49 (Participation): Suggested definition for Participation [Conceptual Model]
Re: PROV-ISSUE-41 (distinct-roles): Distinct roles should be SHOULD and not MUST [Conceptual Model]
Re: PROV-ISSUE-48 (Provenance Concept: Revision): Revision should be a class and not a property [Conceptual Model]
PROV-WG Telecon Agenda 01 Dec 2011
PROV-O telcon (Nov 28)
Plan to progress PROV-AQ to FPWD
CFP: Eighth International Conference on Data Integration in the Life Sciences (DILS 2012)
PROV-O comments
Re: PROV-ISSUE-163 (TLebo): What does provenance information describe? [Accessing and Querying Provenance]
PROV-ISSUE-175 (TLebo): 4.3 Provenance service discovery [Accessing and Querying Provenance]
PROV-ISSUE-174 (TLebo): Replace http://example.info with http://example.{com,org} [Accessing and Querying Provenance]
PROV-ISSUE-173 (TLebo): representations versus formats [Accessing and Querying Provenance]
PROV-ISSUE-172 (TLebo): purpose of prov:hasAnchor [Accessing and Querying Provenance]
PROV-ISSUE-171 (TLebo): HTTP in RDF [Accessing and Querying Provenance]
PROV-ISSUE-170 (TLebo): Resources are "represented", not "presented" [Accessing and Querying Provenance]
PROV-ISSUE-169 (TLebo): Motivating provenance services in PAQ [Accessing and Querying Provenance]
PROV-ISSUE-168 (TLebo): HTTP POSTing a provenance URI to an originating source [Accessing and Querying Provenance]
rel links in HTTP and HTML
PROV-ISSUE-167 (TLebo): What is a "normal web resource"? [Accessing and Querying Provenance]
PROV-ISSUE-166 (TLebo): Sufficient _what_?
PROV-ISSUE-165 (TLebo): Enforcing non-contradictory provenance. [Accessing and Querying Provenance]
PROV-ISSUE-164 (TLebo): pre-determined versus determined [Accessing and Querying Provenance]
PROV-ISSUE-163 (TLebo): What does provenance information describe? [Accessing and Querying Provenance]
PROV-ISSUE-162 (TLebo): Entities can only be web resources? [Accessing and Querying Provenance]
PROV-WG: Telecon Agenda Nov 23, 2012
PROV-ISSUE-161 (TLebo): Quotation: quoting agent should be done with Accounts [Data Model]
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]
- 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]
PROV-ISSUE-160 (TLebo): Redundant terminology in new wasDerivedFrom classification scheme [Data Model]
PROV-ISSUE-159 (Tlebo): note on how PROV-O inteprets DM's "type" and "subtype" [Ontology]
PROV-ISSUE-158 (TLebo): Cite temporal ordering constraint [Data Model]
PROV-ISSUE-157 (TLebo): wasInformedBy's non-transitivity
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]
PROV-ISSUE-155 (prov-o-pre-fpwd): general comments on prov-o document [Formal Semantics]
Ontology telcon
SPARQL endpoint discovery - two suggestions
PROV-ISSUE-154 (RDF-provenance-service-uri): Include provenance-service-uri for RDF resources [Accessing and Querying Provenance]
Comments on PAQ
PROV-ISSUE-153 (complementarity): Complementarity description differs from model definition [Primer]
PROV-ISSUE-152 (QualifiedInvolvement): will the QualifiedInvolvement approach work for other relations? [Ontology]
PAQ tidying notes
PROV-DM derivation concerns arising from my primer review
- Re: PROV-DM derivation concerns arising from my primer review
- Re: PROV-DM derivation concerns arising from my primer review
- Re: PROV-DM derivation concerns arising from my primer review
- Re: PROV-DM derivation concerns arising from my primer review
PROV-ISSUE-151 (TLebo): Rename wasQuoteOf to wasQuotedFrom [Data Model]
CFP: 4th International Provenance and Annotation Workshop (IPAW'2012)
Quotation example
PROV-WG Telecon Agenda 17 Nov 2011
Review of PROV-O for FPWD vote
Updates on issues raised for PROV-O
Primer first draft for review
- Re: Primer first draft for review
- Re: Primer first draft for review
- Re: Primer first draft for review
- Re: Primer first draft for review
Re: PROV-ISSUE-135 (collection-names): Collection relations have confusing names [Data Model]
prov-o terms
PROV-ISSUE-150: question on formal semantics of role in wasGeneratedBy relation [Formal Semantics]
PROV-WG: Minutes from Nov 10, 2011 Telecon
PROV-WG Reminder: Review PAQ before FPWD vote
- Re: PROV-WG Reminder: Review PAQ before FPWD vote
- Re: PROV-WG Reminder: Review PAQ before FPWD vote
- Re: PROV-WG Reminder: Review PAQ before FPWD vote
- Re: PROV-WG Reminder: Review PAQ before FPWD vote
- Re: PROV-WG Reminder: Review PAQ before FPWD vote
PROV-O telcon
PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
- Re: PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
- Re: PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
- Re: PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
- Re: PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
- Re: PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
- Re: PROV-ISSUE-149 (revision-asserter): Why does revision record include an asserter? [Data Model]
Semantics
A proposal for modeling agents
- RE: A proposal for modeling agents
- Re: A proposal for modeling agents
- Re: A proposal for modeling agents
- Re: A proposal for modeling agents
Leveraging OBE for PROV-O Accounts
PROV-ISSUE-148 (WasScheduledAfter): wasScheduledAfter definition is difficult to understand
PROV-WG scribe needed
PAQ updates
PROV-WG: Telecon Agenda Nov. 10 2011
Reminder: Please fill out F2F Poll
Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
- Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
- Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
New URL for PROV-O ontology
mercurial repository heads
Primer new plan
Re: PROV-ISSUE-126: Section 5.3.3.2 "Process Execution Independent Derivation Expression." [Data Model]
Re: feedback on Qualified Involvements wiki page
Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
Fwd: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
prov-dm qualifier: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm qualifier: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm qualifier: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm qualifier: a proposal to vote on (deadline Wednesday midnight GMT)
Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
- Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]
Re: PROV-ISSUE-125: derivation-attributes constraint (PROV-DM and PROV-O) [Data Model]
- Re: PROV-ISSUE-125: derivation-attributes constraint (PROV-DM and PROV-O) [Data Model]
- Re: PROV-ISSUE-125: derivation-attributes constraint (PROV-DM and PROV-O) [Data Model]
Re: PROV-ISSUE-124: Constraints on Used Relation (PROV-DM and PROV-OM) [Conceptual Model]
Re: PROV-ISSUE-100 (Entity definition): Section 5.2.1 Entity [Conceptual Model]
Re: PROV-ISSUE-122: Constraint on wasGeneratedBy (PROV-DM and PROV-OM) [Conceptual Model]
Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model]
- Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual 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]
- Re: PROV-ISSUE-101 (Conceptual Model): Section 5.2.2 ProcessExecution (conceptual model document review) [Conceptual Model]
- Re: PROV-ISSUE-101 (Conceptual Model): Section 5.2.2 ProcessExecution (conceptual model document review) [Conceptual Model]
prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm derivation: three proposals to vote on (deadline Wednesday midnight GMT)
Qualified Involvements proposal
PROV-O telcon
F2F2 dates and locations poll: deadline Nov 16th
PROV-ISSUE-146 (Tlebo): wasAttributeTo [Data Model]
PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
- Re: PROV-ISSUE-145 (Tlebo): qualified identifiers may not work well with named graphs [Data Model]
PROV-ISSUE-144 (Tlebo): how is "reserved attribute 'type'" related to rdf:type? [Data Model]
- Re: PROV-ISSUE-144 (Tlebo): how is "reserved attribute 'type'" related to rdf:type? [Data Model]
- Re: PROV-ISSUE-144 (Tlebo): how is "reserved attribute 'type'" related to rdf:type? [Data Model]
PROV-ISSUE-143 (Tlebo): Qualifiers - why does order matter? [Data Model]
- Re: PROV-ISSUE-143 (Tlebo): Qualifiers - why does order matter? [Data Model]
- Re: PROV-ISSUE-143 (Tlebo): Qualifiers - why does order matter? [Data Model]
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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
- 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]
Meeting minutes 2011-11-03
Re: Blog Post: 5 Simple Provenance Statements
PROV-DM - editorial nit
PROV-ISSUE-141 (agent-attributes): Is there a way to associate attributes (e.g. a name) with an agent in ASN? [Data Model]
PROV-ISSUE-140 (entity-qualifier-syntax): ASN uses different syntax for entity attributes and qualifiers
Thoughts in the prov primer
Re: prov-o example relations
Regrets
Re: prov-dm attributes: two proposals to vote on (deadline Wednesday midnight GMT)
Re: prov-dm expression: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm expression: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm expression: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm expression: a proposal to vote on (deadline Wednesday midnight GMT)
- RE: prov-dm expression: a proposal to vote on (deadline Wednesday midnight GMT)
- Re: prov-dm expression: a proposal to vote on (deadline Wednesday midnight GMT)