prov-o meeting agenda
Re: [prov-html] PROV-ISSUE-308 (prov-o-w3c-style): PROV-O HTML much conform to W3C Style [PROV-O HTML]
Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
- Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
- Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
- Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
- Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
- Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
- Re: PROV-ISSUE-370 (tracedTo-inference-only): Should tracedTo be moved to prov-constraints and be defined as a binary relation that can be inferred [prov-dm]
PROV-ISSUE-369 (drop-startByActivity): Should we drop wasStartedByActivity? [prov-dm]
Re: PROV-ISSUE-368 (no-responsibility-in-derivation): No responsibility in derivation [prov-dm]
PROV-ISSUE-368 (no-responsibility-in-derivation): No responsibility in derivation [prov-dm]
Special issue on Geoscience Data Provenance
Re: Fwd: Going for simplicity (was: actions related to collections)
Problem accessing PROV-O documentation
Going for simplicity (was: actions related to collections)
Re: PROV-ISSUE-128 (Location-Example): Location example uses a filesystem and not a geographical location [Ontology]
Call for participation: SWPM 2012: The Third International Workshop on the role of Semantic Web in Provenance Management
prov-wg meeting minutes 2012-04-26
conforming prov-o to W3C style guidelines
Changes applied to PROV-AQ in response to reviews
tracker down?
[owl changed]
PROV-ISSUE-367 (hadActivity-domain-and-comments-unclear): prov:hadActivity domain and usage unclear [Ontology]
- Re: PROV-ISSUE-367 (hadActivity-domain-and-comments-unclear): prov:hadActivity domain and usage unclear [Ontology]
PROV-ISSUE-366: Approving agent in a qualified wasRevisionOf [Ontology]
- Re: PROV-ISSUE-366: Approving agent in a qualified wasRevisionOf [Ontology]
- Re: PROV-ISSUE-366: Approving agent in a qualified wasRevisionOf [Ontology]
- Re: PROV-ISSUE-366: Approving agent in a qualified wasRevisionOf [Ontology]
Re: PROV-ISSUE-136 (collection-functional): Collection not stated as functional [Data Model]
Re: PROV-ISSUE-137 (collection-isolation): Collection assertions does not guarantee isolation [Data Model]
PROV-ISSUE-365 (membership-as-insertion-too-limitting): Collection constraint membership-as-insertion too limitting [prov-dm-constraints]
PROV-ISSUE-364 (collection-constraints-bugs): Collection constraint has wrong syntax for memberOf [prov-dm-constraints]
PROV-WG Telecon Agenda 26 Apr 2012
Review prov-aq document
prov-o team telecon Monday 23 April 2012
PROV-ISSUE-363 (prov-value-pun): prov:value punned on KeyValuePair and Entity's literal value [Ontology]
Review Prov-AQ document
PROV-ISSUE-362 (altOf-www): alternateOf is to handle levels of specificity, not the wild wild west of WWW URI selection [prov-dm]
Review prov-aq
PROV-ISSUE-361 (definition target-uri): no relationship between resource and provenance information in definition of target-uri [Accessing and Querying Provenance]
PROV-ISSUE-360 (SPARQL example for 5.1.3): SPARQL example for obtaining provenance information directly [Accessing and Querying Provenance]
PROV-ISSUE-359 (provenance query service URI): Avoid the term "provenance query service URI" [Accessing and Querying Provenance]
PROV-ISSUE-358 (web resource): Avoid using the term "Web resource" in PAQ [Accessing and Querying Provenance]
Fwd: Please help: prov-o examples
Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
- Re: PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
prov-wg Telecon minutes April 19, 2012
PROV-ISSUE-357 (author-in-quotation): author in definition of quotation [prov-dm]
Re: PROV-ISSUE-205 (optional-activity-in-generation-record): optional activity in generation record [prov-dm]
Re: PROV-ISSUE-204 (end-of-entity): What marks the end of an entity? [prov-dm]
invalidation is in prov-dm
PROV-ISSUE-356 (replace-hadquoter): Replace hadQuoter by reusing wasAttributedTo [mapping prov-dm <-> prov-o]
- Re: PROV-ISSUE-356 (replace-hadquoter): Replace hadQuoter by reusing wasAttributedTo [mapping prov-dm <-> prov-o]
PROV-ISSUE-355 (convenient-notation-for-qualified-names): introduce a convenience notation for qualified names [prov-n]
PROV-ISSUE-354 (all-or-nothing-for-optional-arguments): Adopt an all-or-nothing approach to optional positional arguments [prov-n]
PROV-ISSUE-353 (optional-id-syntactic-marker): Introduce a syntactic marker for when optional id is expressed [prov-n]
Primer revised for release
PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
- Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
Re: PROV-ISSUE-332 (review-prov-n-wd5): issue to collect feedback on prov-n wd5 [prov-n]
PROV-ISSUE-351 (membership-complete): memberOf complete attribute missing [prov-dm]
prov-o html - for voting tomorrow
prov-wg F2F4 in Lyon?
prov-wg: Telcon Agenda April 19, 2012
Collections: issue-136 and issue-137
Re: PROV-ISSUE-207 (start and end records): start and end records [prov-dm]
presentation at LDOW
revised prov-dm-constraints
entity invalidation
responsibility and association
Re: PROV-ISSUE-133 (YolandaGil): Producing and delivering resources as part of provenance in Provenance Data Model (PROV-DM) Draft [Data Model]
Re: PROV-ISSUE-132 (YolandaGil): Improve the examples to make them more intuitive and of broader appeal in Provenance Data Model (PROV-DM) Draft [Data Model]
Re: PROV-ISSUE-148 (WasScheduledAfter): wasScheduledAfter definition is difficult to understand
Re: PROV-ISSUE-182 (TLebo): stronger name for "wasAssociatedWith" [prov-dm]
Re: PROV-ISSUE-206 (agent-asserted-not-inferred): agents should not be inferred, and wasAssociatedWith should also work with entities [prov-dm]
Re: PROV-ISSUE-219 (prov:label): label attribute is required in PROV [prov-dm]
Re: PROV-ISSUE-238 (TLebo): order relation sections to suit a natural traversal of the Relation table [prov-dm]
Re: PROV-ISSUE-249 (two-derivations): Why do we have 3 derivations? [prov-dm]
revised prov-dm document (ISSUE-331)
Re: PROV-ISSUE-123 (hadParticipant-subprops): prov:used and prov:wasControlledby should be subproperties of prov:hadParticipant
css help - prov-o html
Re: PROV-ISSUE-314 (TLEBO): inconsistent comment location in PROV-O HTML cross referencing [PROV-O HTML]
PROV-ISSUE-350 (xref-with-unions): cross references with union domains fail [PROV-O HTML]
ACTION-70
Re: [provo-html] PROV-ISSUE-119 (vanilla-rdf): How does vanilla RDF work with PROV Ontology [Formal Model]
Re: PROV-ISSUE-312 (TLEBO): acknowledge developers of tools used to create PROV-O HTML [PROV-O HTML]
- Re: PROV-ISSUE-312 (TLEBO): acknowledge developers of tools used to create PROV-O HTML [PROV-O HTML]
prov-o meeting today
Re: PROV-ISSUE-250 (TLebo): respond to Eric's comments [Ontology]
Re: PROV-ISSUE-128 (Location-Example): Location example uses a filesystem and not a geographical location [Ontology]
Re: PROV-ISSUE-117 (general-comments-on-formal-model-document): General Comments On Ontology Document [Formal Model]
Re: [provo-html] PROV-ISSUE-119 (vanilla-rdf): How does vanilla RDF work with PROV Ontology [Formal Model]
Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
- Re: PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology]
warning: hg merging
Fwd: prov:specializationOf
Please help: prov-o examples
PROV-ISSUE-349 (prov-o-html-egs): examples for each term in cross-reference section [PROV-O HTML]
[owl changed]
PROV-ISSUE-348 (prov-o-propery-name-conventions): maintain property naming conventions [Ontology]
PROV-ISSUE-347 (review-provo-luc): feedback from Luc on prov-o WD [prov-n]
- Re: PROV-ISSUE-347 (review-provo-luc): feedback from Luc on prov-o WD [prov-n]
prov-wg meeting minutes 2012-04-12
actions related to collections
- Re: actions related to collections
Fwd: PROV-O: Review Sam Coppens
PROV-ISSUE-346 (distinguish-constraints): types of constraints unclear [prov-dm-constraints]
PROV-ISSUE-345 (delineate-constraints): style hinders readability: constraints not separated clearly enough [prov-dm-constraints]
PROV-ISSUE-344 (jzhao): Missing definitions of terms in section 4
PROV-ISSUE-343 (account-objections): Objections regarding Account [prov-dm-constraints]
PROV-WG Telecon Agenda 12 Apr 2012
PROV-ISSUE-342 (location-of-usage): prov:location is an optional attribute of entity and activity - others okay? [prov-dm]
- Re: PROV-ISSUE-342 (location-of-usage): prov:location is an optional attribute of entity and activity - others okay? [prov-dm]
PROV-ISSUE-341 (revision-approver): revision approver - why? [prov-dm]
PROV-ISSUE-340 (start-by-activity-is-comm): Start by Activity is Communication; drop it. [prov-dm]
- Re: PROV-ISSUE-340 (start-by-activity-is-comm): Start by Activity is Communication; drop it. [prov-dm]
Re: PROV-ISSUE-332 (review-prov-n-wd5): issue to collect feedback on prov-n wd5 [prov-n]
- Re: PROV-ISSUE-332 (review-prov-n-wd5): issue to collect feedback on prov-n wd5 [prov-n]
- Re: PROV-ISSUE-332 (review-prov-n-wd5): issue to collect feedback on prov-n wd5 [prov-n]
Re: PROV-ISSUE-333 (review-prov-dm-constraints-wd5): issue to collect feedback on prov-dm-constraints wd5 [prov-dm-constraints]
- Re: PROV-ISSUE-333 (review-prov-dm-constraints-wd5): issue to collect feedback on prov-dm-constraints wd5 [prov-dm-constraints]
- Re: PROV-ISSUE-333 (review-prov-dm-constraints-wd5): issue to collect feedback on prov-dm-constraints wd5 [prov-dm-constraints]
Re: PROV-ISSUE-331 (review-dm-wd5): issue to collect feedback on prov-dm wd5 [prov-dm]
- Re: PROV-ISSUE-331 (review-dm-wd5): issue to collect feedback on prov-dm wd5 [prov-dm]
[owl changed]
Different senses of specialization
- Re: Different senses of specialization
- Re: Different senses of specialization
- Re: Different senses of specialization
Today's prov-o team telecon
PROV-ISSUE-339 (dgarijo): Domain of "activity" property [Ontology]
PROV-ISSUE-338: explain prov:agent vs. prov:hadPlan naming convention [PROV-O HTML]
Re: PROV-ISSUE-248 (string-as-entity): How to model strings? [Formal Semantics]
Re: PROV-ISSUE-226 (dgarijo): domain of the qualifiedDelegation property? [Ontology]
TAG discussion may be relevant to PROV-CONSTRAINTS
PROV-ISSUE-333 - feedback on PROV-CONSTRAINTS
Re: ISSUE-83: Express inverse relationships in Provenance Model as well as ontology
Re: PROV-ISSUE-277 (TLebo): Supporting property chains [Ontology]
Re: PROV-ISSUE-317 (dgarijo): the domain of hadRole includes Derivation [Ontology]
Re: PROV-ISSUE-318 (dgarijo): Collections missing [Ontology]
Re: PROV-ISSUE-319 (dgarijo): Domain of hasAnnotation [Ontology]
Re: PROV-ISSUE-320 (dgarijo): Change the name of prov:Quotation
Review of PROV-O - ISSUE-336
PROV-ISSUE-331: feedback on PROV-Dm WD5
- Re: PROV-ISSUE-331: feedback on PROV-Dm WD5
- Re: PROV-ISSUE-331: feedback on PROV-Dm WD5
- Re: PROV-ISSUE-331: feedback on PROV-Dm WD5
- Re: PROV-ISSUE-331: feedback on PROV-Dm WD5
- Re: PROV-ISSUE-331: feedback on PROV-Dm WD5
prov-wg: Minutes of the 05 April 2012 Telecon
addressing issues in prov-aq
prov-aq issues resolved
New PROV-AQ editor's draft available
RE: PROV-ISSUE-332 (review-prov-n-wd5): issue to collect feedback on prov-n wd5 [prov-n]
PROV-O issues pending review
prov-wg: note on sending reviews and comments on them
prov-wg: Telecon Agenda April 4, 2012
Re: PROV-ISSUE-223 (definition-of-entity): What is the definition of entity [prov-dm]
PROV-ISSUE-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
- RE: PROV-ISSUE-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
- Re: PROV-ISSUE-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
- Re: PROV-ISSUE-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
- Re: PROV-ISSUE-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
- Re: PROV-ISSUE-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
Re: PROV-ISSUE-223 (definition-of-entity): What is the definition of entity [prov-dm]
Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- RE: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
release of prov-dm, prov-dm-constraints, and prov-n for review
- Re: PROV-ISSUE-331 release of prov-dm for review
- Re: release of prov-dm, prov-dm-constraints, and prov-n for review
- Re: release of prov-dm, prov-dm-constraints, and prov-n for review
PROV-O ready for internal WG review - due 9 April.
- Re: PROV-O ready for internal WG review - due 9 April.
- Re: PROV-O ready for internal WG review - due 9 April.
- Re: PROV-O ready for internal WG review - due 9 April.
- Re: PROV-O ready for internal WG review - due 9 April.
- Re: PROV-O ready for internal WG review - due 9 April.
PROV-ISSUE-336 (provo-2WD-feedback): Incorporate WG feedback into PROV-O 2WD [Ontology]
- RE: PROV-ISSUE-336 (provo-2WD-feedback): Incorporate WG feedback into PROV-O 2WD [Ontology]
- RE: PROV-ISSUE-336 (provo-2WD-feedback): Incorporate WG feedback into PROV-O 2WD [Ontology]
Re: PROV-ISSUE-224 (unified-prov-namespace): Can we use a single namespace for the PROV family of specs? [prov-dm]
Re: PROV-ISSUE-242 (TLebo): generated twice? [prov-dm]
PROV-ISSUE-335 (provo-html-code-style): use <code> and <a href="#Entity> consistently. [PROV-O HTML]
PROV-ISSUE-334 (define-qualification-pattern): Qualification Pattern was used, used in bold font in its first occurrence, but never defined. [PROV-O HTML]
Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
- Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
prov-o telecon 12 noon ET / 4pm GMT
is specializationOf transitive or not?
- Re: is specializationOf transitive or not?
- RE: is specializationOf transitive or not?
- Re: is specializationOf transitive or not?
Re: Best practice for specialization
Primer WD2 ready for review
- Re: Primer WD2 ready for review
- Re: Primer WD2 ready for review
- Re: Primer WD2 ready for review
- Re: Primer WD2 ready for review
Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
- Re: PROV-ISSUE-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]