Re: PROV-ISSUE-364 (collection-constraints-bugs): Collection constraint has wrong syntax for memberOf [prov-dm-constraints]
ISSUE-385: hasProvenanceIn: finding a solution
Definition of role
PROV-ISSUE-386: 3.2 missing terms in turtle examples
Dublin Core - PROV Mapping, Call for Feedback (until June 5th)
Re: revised prov-dm document (ISSUE-331)
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-29 (mutual-iVP-of): can two bobs be mutually "IVP of" each other [Conceptual Model]
PROV-WG Telecon Agenda 31 May 2012
Fwd: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- RE: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- RE: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- RE: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
- Re: PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]
reminder: prov-o telecon today
prov-wg: Telecon Minutes May 24, 2012
Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
- Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
IPAW 2012: hotel rates expire tomorrow!
PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
delegation definition
- Re: delegation definition
- Re: delegation definition
- Re: delegation definition
- Re: delegation definition
- Re: delegation definition
- Re: delegation definition
respec: misbalanced appendices
Re: PROV-ISSUE-288 (TLebo): ProvRDF issues for Usage [mapping prov-dm <-> prov-o]
Re: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
- Re: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
- Re: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
- Re: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
- Re: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
PROV-ISSUE-382 (jzhao): Qualification patters in prov-o section 3.3 [PROV-O HTML]
PROV-ISSUE-381 (jzhao): Feedback and refactoring suggestion to prov-o section 3.2 [PROV-O HTML]
Call for Participation: IPAW 2012
prov-wg: Telecon Agenda May 25, 2012
PROV-ISSUE-380 (start-hadActivity): Missing hadActivity reference on Start [PROV-O HTML]
PROV-ISSUE-379 (jzhao): Update provo html section 3.1 [PROV-O HTML]
- Re: PROV-ISSUE-379 (jzhao): Update provo html section 3.1 [PROV-O HTML]
- Re: PROV-ISSUE-379 (jzhao): Update provo html section 3.1 [PROV-O HTML]
[owl changed] justified: wasAttributedTo subpropertyOf tracedTo
Re: PROV-ISSUE-315 (dgarijo): Mapping of subclass relationships [mapping prov-dm <-> prov-o]
Re: PROV-ISSUE-346 (distinguish-constraints): types of constraints unclear [prov-dm-constraints]
Re: PROV-ISSUE-345 (delineate-constraints): style hinders readability: constraints not separated clearly enough [prov-dm-constraints]
Re: PROV-ISSUE-343 (account-objections): Objections regarding Account [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-221 (constraint-was-associated-with): What are the constraints for wasAssociatedWith and actedOnBehalfOf? [prov-dm]
prov-o meeting today - reminder
Proposal on PROV-DM reorganization
- Re: Proposal on PROV-DM reorganization
- Re: Proposal on PROV-DM reorganization
- Re: Proposal on PROV-DM reorganization
Re: PROV-ISSUE-350 (xref-with-unions): cross references with union domains fail [PROV-O HTML]
- Re: PROV-ISSUE-350 (xref-with-unions): cross references with union domains fail [PROV-O HTML]
- Re: PROV-ISSUE-350 (xref-with-unions): cross references with union domains fail [PROV-O HTML]
prov-wg meeting minutes 2012-05-17
PROV-ISSUE-378 (clarifyHadActivity): clarify hadActivity [Ontology]
- Re: PROV-ISSUE-378 (clarifyHadActivity): clarify hadActivity [Ontology]
prov-o team agenda items for next week
today's call: scribe required, please
generation by two distinct activities?
PROV-ISSUE-377 (rl-plus-plus-justify): All RL "violations" justified appendix [PROV-O HTML]
Re: PROV-ISSUE-253: misc issues with the ontology [mapping prov-dm <-> prov-o]
Re: PROV-ISSUE-213 (prov-sem-events): Alignment of events in PROV-DM vs PROV-SEM [Formal Semantics]
Re: PROV-ISSUE-283 (TLebo): Account, Note, Plan and Location subclasses of Entity? [mapping prov-dm <-> prov-o]
Re: http://www.w3.org/2011/prov/track/products/9 Issues
PROV-ISSUE-376 (rename-responsibility): Renaming Responsibility (to Behalf?) [prov-dm]
Re: PROV-ISSUE-350 (xref-with-unions): cross references with union domains fail [PROV-O HTML]
PROV-ISSUE-375 (owl-property-links): link to OWL property types in PROV-O [Ontology]
Re: PROV-ISSUE-205 (optional-activity-in-generation-record): optional activity in generation record [prov-dm]
Re: PROV-ISSUE-369 (drop-startByActivity): Should we drop wasStartedByActivity? [prov-dm]
Re: PROV-ISSUE-295 (TLebo): hasAnnotation [ a prov:Note ] [prov-dm]
Re: PROV-ISSUE-340 (start-by-activity-is-comm): Start by Activity is Communication; drop it. [prov-dm]
Re: PROV-ISSUE-260 (TLebo): In Note section: cite prov:Provenance as better practice to annotate assertions. [prov-dm]
Re: PROV-ISSUE-257 (TLebo): rename "Account"/"Bundle"/"AccountEntity" to "Provenance" [prov-dm]
Re: PROV-ISSUE-88 (Provenance-container): Provenance container seems an unnecessary concept
Re: PROV-ISSUE-223 (definition-of-entity): What is the definition of entity [prov-dm]
PROV-WG Telecon Agenda 17 May 2012
Re: PROV-ISSUE-354 (all-or-nothing-for-optional-arguments): Adopt an all-or-nothing approach to optional positional arguments [prov-n]
Re: PROV-ISSUE-353 (optional-id-syntactic-marker): Introduce a syntactic marker for when optional id is expressed [prov-n]
PROV-ISSUE-374 (member-membership-indirection): indirection for Dictionary members [Ontology]
prov:value versus KeyValuePair
- Re: prov:value versus KeyValuePair
InstantaneousEvent disjointness
[owl changed] hadQuoter hadQuoted and wasApprovedBy
[owl changed] InstantaneousEvent disjoints
Re: PROV-ISSUE-281 (TLebo): prov-o namspaces are not dereferencable [Ontology]
- Re: PROV-ISSUE-281 (TLebo): prov-o namspaces are not dereferencable [Ontology]
- Re: PROV-ISSUE-281 (TLebo): prov-o namspaces are not dereferencable [Ontology]
prov-o telecon today
Proposal for restructuring PROV-DM into core+extensions
- Re: Proposal for restructuring PROV-DM into core+extensions
- Re: Proposal for restructuring PROV-DM into core+extensions
provenance of provenance
- Re: provenance of provenance
- Re: provenance of provenance
- Re: provenance of provenance
- Re: provenance of provenance
- Re: provenance of provenance
- Re: provenance of provenance
prov-wg meeting minutes 2012-05-10
[owl changed] invalidatedAtTime and generatedAtTime now functional
Review and next steps on PROV-CONSTRAINTS
- Re: Review and next steps on PROV-CONSTRAINTS
- Re: Review and next steps on PROV-CONSTRAINTS
- Re: Review and next steps on PROV-CONSTRAINTS
Fwd: Re: A proposal for reorganizing PROV materials
PROV-WG Telecon Agenda 10 May 2012
Re: A proposal for reorganizing PROV materials (was: Complexity/simplicty redux)
prov-dm: outstanding issues to close
PROV-ISSUE-362 (altOf-www): alternateOf is to handle levels of specificity, not the wild wild west of WWW URI selection [prov-dm]
specialization/alternate in 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-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-357 (author-in-quotation): author in definition of quotation [prov-dm]
prov-wg: Telcon Minutes May 3, 2012
new signatures for derivation relations
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-89 (what-entity-attributes): How do we find the attributes of an entity? [Formal Model]
Mini-mini comment on prov-dm
PROV-ISSUE-373: trim qualified from "3.2 expanded" [PROV-O HTML]
prov-o telecon today
PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- [owl changed] Re: PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] Re: PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
- Re: [owl changed] Re: PROV-ISSUE-372 (qualified-property-chains): ( prov:qualifedUsage prov:entity ) rdfs:subPropertyOf prov:used
Question on permitted datatypes
Another prov-o comment/question
Minor editorial comment on Prov-o
Complexity/simplicty redux
proposal separating collections
Fwd: provenance working group draft specs - ready for review
announcement email for prov specs
- Re: announcement email for prov specs
- Re: announcement email for prov specs
- Re: announcement email for prov specs
Revised PROV-AQ
scribe for today?
Re: PROV-ISSUE-365 (membership-as-insertion-too-limitting): Collection constraint membership-as-insertion too limitting [prov-dm-constraints]
Re: PROV-ISSUE-340 (start-by-activity-is-comm): Start by Activity is Communication; drop it. [prov-dm]
Re: PROV-ISSUE-352 (rename-WasQuotedFrom): A better name for wasQuotedFrom [prov-dm]
Re: PROV-ISSUE-204 (end-of-entity): What marks the end of an entity? [prov-dm]
Re: PROV-ISSUE-311 (clarify-optionals): Clarify optional arguments in DM [prov-dm]
Re: Difference between wasInformedBy and wasStartedByActivity
- Re: Difference between wasInformedBy and wasStartedByActivity
- Re: Difference between wasInformedBy and wasStartedByActivity
[provo] Re: Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Re: Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
- Re: [provo] Difference between wasInformedBy and wasStartedByActivity (ttl examples)
Re: PROV-ISSUE-368 (no-responsibility-in-derivation): No responsibility in derivation [prov-dm]
Re: PROV-ISSUE-268 (two-level-ontology): Two Level Ontology? [Ontology]
Re: PROV-ISSUE-338: explain prov:agent vs. prov:hadPlan naming convention [PROV-O HTML]
Re: 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: [owl changed] ISSUE-83: Express inverse relationships in Provenance Model as well as ontology
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]
Re: PROV-ISSUE-351 (membership-complete): memberOf complete attribute missing [prov-dm]
Re: PROV-ISSUE-369 (drop-startByActivity): Should we drop wasStartedByActivity? [prov-dm]
prov-wg: Telcon Agenda May 3, 2012
Re: PROV-ISSUE-267 (TLebo): annotate all subproperty axioms to justify them [Ontology]
PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
- Re: PROV-ISSUE-371 (junzhao): timestamped provo.owl [PROV-O HTML]
Re: PROV-ISSUE-368 (no-responsibility-in-derivation): No responsibility in derivation [prov-dm]
Re: PROV-ISSUE-369 (drop-startByActivity): Should we drop wasStartedByActivity? [prov-dm]
- Re: PROV-ISSUE-369 (drop-startByActivity): Should we drop wasStartedByActivity? [prov-dm]
- Re: PROV-ISSUE-369 (drop-startByActivity): Should we drop wasStartedByActivity? [prov-dm]