Wednesday, 31 August 2011
- Re: PROV-WG Telecon Agenda 01 Sep 2011
- PROV-WG Telecon Agenda 01 Sep 2011
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
Tuesday, 30 August 2011
Monday, 29 August 2011
Saturday, 27 August 2011
- Re: formal semantics strawman
- Re: formal semantics strawman
- Re: PROV-ISSUE-76 (xml-examples): Shouldn't we have proper examples in XML and not RDF/XML [Accessing and Querying Provenance]
- Re: [Spam:***** SpamScore] Re: formal semantics strawman
- RE: [Spam:***** SpamScore] Re: formal semantics strawman
Friday, 26 August 2011
- Re: PROV-ISSUE-84 (namespace-for-properties): What should namespace for properties be? [Formal Model]
- Re: formal semantics strawman
- Re: PROV-ISSUE-75 (provenance-service-and-provenance-uri): What do we do when we get both provenance service and provenance-uri? [Accessing and Querying Provenance]
- Re: PROV-ISSUE-76 (xml-examples): Shouldn't we have proper examples in XML and not RDF/XML [Accessing and Querying Provenance]
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance]
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-76 (xml-examples): Shouldn't we have proper examples in XML and not RDF/XML [Accessing and Querying Provenance]
- Re: PROV-ISSUE-75 (provenance-service-and-provenance-uri): What do we do when we get both provenance service and provenance-uri? [Accessing and Querying Provenance]
- Re: PROV-ISSUE-55 (are-provenance-uris-needed): Are provenance URIs really needed [Accessing and Querying Provenance]
- PROV-ISSUE-84 (namespace-for-properties): What should namespace for properties be? [Formal Model]
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance]
Thursday, 25 August 2011
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance]
- Re: PROV-ISSUE-76 (xml-examples): Shouldn't we have proper examples in XML and not RDF/XML [Accessing and Querying Provenance]
- Re: PROV-ISSUE-75 (provenance-service-and-provenance-uri): What do we do when we get both provenance service and provenance-uri? [Accessing and Querying Provenance]
- Re: PROV-ISSUE-55 (are-provenance-uris-needed): Are provenance URIs really needed [Accessing and Querying Provenance]
- Re: Provenance requirements for RDF named graphs
- Re: formal semantics strawman
- Provenance requirements for RDF named graphs
- Re: cross-referencing constraints in conceptual model and formal model
- formal semantics strawman
- Re: cross-referencing constraints in conceptual model and formal model
- Provenance model document is over-complicated and hard to understand
- Re: [PAQ] rel="me"
- Re: playing with pil ontology
- ISSUE-83: Express inverse relationships in Provenance Model as well as ontology
- Re: PROV-ISSUE-40 (recommended-roles): Roles should not be SHOULD and not MUST [Conceptual Model]
- Re: [PAQ] rel="me"
- Re: [PAQ] rel="me"
- Re: playing with pil ontology
- Re: PROV-ISSUE-80 (about-provenance-template): Query about provenance template [Accessing and Querying Provenance]
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- Re: updates to PAQ doc for discussion
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: cross-referencing constraints in conceptual model and formal model
- Re: playing with pil ontology
- Re: PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance]
- Re: cross-referencing constraints in conceptual model and formal model
- Re: PROV-ISSUE-75 (provenance-service-and-provenance-uri): What do we do when we get both provenance service and provenance-uri? [Accessing and Querying Provenance]
- Provenance context URIs for RDF data (was: PAQ document update, target renamed as context)
- Re: PROV-WG Telecon Agenda 25 August 2011
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- Re: PROV-ISSUE-76 (xml-examples): Shouldn't we have proper examples in XML and not RDF/XML [Accessing and Querying Provenance]
- Re: PAQ document update, target renamed as context
- Re: PROV-ISSUE-55 (are-provenance-uris-needed): Are provenance URIs really needed [Accessing and Querying Provenance]
- views, complements and invariants (was: updates to PAQ doc for discussion)
- Re: PAQ document update, target renamed as context
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: playing with pil ontology
- Re: PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
- PROV-ISSUE-82 (pidm-event): Should we introduce a notion of event in the data model? [Conceptual Model]
- Re: PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
Wednesday, 24 August 2011
- Re: [PAQ] rel="me"
- PROV-ISSUE-81 (identity-clash-scope): In a given scope, are entities with same identifier but different attributes legal? [Conceptual Model]
- [PAQ] rel="me"
- Re: PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
- RE: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- Weekly Connection Task Force Call - each Monday
- Re: PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
- Re: playing with pil ontology
- PROV-WG Telecon Agenda 25 August 2011
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- Re: playing with pil ontology
Tuesday, 23 August 2011
- Re: playing with pil ontology
- Re: playing with pil ontology
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- PROV-ISSUE-80 (about-provenance-template): Query about provenance template [Accessing and Querying Provenance]
- PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance]
- Re: updates to PAQ doc for discussion
- Re: closing issues for the Model Document
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- Guidelines for the Connection Task Force Report
- Re: PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
Monday, 22 August 2011
- PROV-ISSUE-78 (contexts-and-provenance-uris): multiple contexts and provenance-uris [Accessing and Querying Provenance]
- PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance]
- PROV-ISSUE-76 (xml-examples): Shouldn't we have proper examples in XML and not RDF/XML [Accessing and Querying Provenance]
- PROV-ISSUE-75 (provenance-service-and-provenance-uri): What do we do when we get both provenance service and provenance-uri? [Accessing and Querying Provenance]
- Re: PROV-ISSUE-55 (are-provenance-uris-needed): Are provenance URIs really needed [Accessing and Querying Provenance]
- Re: PROV-ISSUE-55 (are-provenance-uris-needed): Are provenance URIs really needed [Accessing and Querying Provenance]
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- closing issues for the Model Document
- RE: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- Re: PROV-ISSUE-62 (about-prov-language): about provenance language [Conceptual Model]
- Re: PROV-ISSUE-62 (about-prov-language): about provenance language [Conceptual Model]
- Re: PROV-ISSUE-61 (is-revision-necessary): is revision necessary? [Conceptual Model]
- Re: PROV-ISSUE-60: comments on bob [Conceptual Model]
- Re: PROV-ISSUE-59 (generation-definition): on generation [Conceptual Model]
- Re: PROV-ISSUE-58 (time-iso8601): is reference to iso8601 appropriate? [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-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Re: PROV-ISSUE-48 (Provenance Concept: Revision): Revision should be a class and not a property [Conceptual Model]
- Re: PROV-ISSUE-45: isDerivedFrom and IVPof are transitive. [Conceptual Model]
- Re: PROV-ISSUE-41 (distinct-roles): Distinct roles should be SHOULD and not MUST [Conceptual Model]
- Re: PROV-ISSUE-40 (recommended-roles): Roles should not be SHOULD and not MUST [Conceptual Model]
- Re: PROV-ISSUE-39 (generation-identifiable-activity): Generation should be defined as an identifable activity [Conceptual Model]
- Re: PROV-ISSUE-35: Section 4: How one would know that two BOBs are characterizations of the same entity? [Conceptual Model]
- Re: PROV-ISSUE-33: Section 3.1 and Section 3.2: example of IVPof [Conceptual Model]
- Re: PROV-ISSUE-32: Bob definition [Conceptual Model]
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- RE: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- RE: updates to PAQ doc for discussion
- Re: cross-referencing constraints in conceptual model and formal model
- RE: updates to PAQ doc for discussion
- Re: cross-referencing constraints in conceptual model and formal model
- Re: cross-referencing constraints in conceptual model and formal model
- Re: PAQ document update, target renamed as context
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: updates to PAQ doc for discussion
- Re: PROV-ISSUE-69 (Process Execution): Process execution occurs over a "continuous time interval"? [Conceptual Model]
Sunday, 21 August 2011
- Re: PAQ document update, target renamed as context
- Re: PAQ document update, target renamed as context
- Re: playing with pil ontology
Saturday, 20 August 2011
- RE: updates to PAQ doc for discussion
- Re: PAQ document update, target renamed as context
- Re: updates to PAQ doc for discussion
Friday, 19 August 2011
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: PAQ document update, target renamed as context
- Re: PAQ document update, target renamed as context
- Re: PAQ document update, target renamed as context
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: playing with pil ontology
Thursday, 18 August 2011
- CIDOC-CRM Ontology
- test message please ignore
- Re: PAQ document update, target renamed as context
- Re: [PAQ] editorial issues
- Re: PAQ document update, target renamed as context
- cross-referencing constraints in conceptual model and formal model
- RE: Telecon Agenda Aug 18, 2011
- Regrets ...
- regrets for telecon 8/18, 8/25, and stakeholder questionnaire status update
- RE: PAQ document update, target renamed as context
Wednesday, 17 August 2011
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: playing with pil ontology
- PAQ document update, target renamed as context
- Possible regrets (was: Telecon Agenda Aug 18, 2011)
- Re: playing with pil ontology
- Re: Updated stakeholders survey on wiki, need to compile list of communities to inform when survey goes live
Tuesday, 16 August 2011
- RE: playing with pil ontology
- Updated stakeholders survey on wiki, need to compile list of communities to inform when survey goes live
- Re: playing with pil ontology
- Re: playing with pil ontology
- RE: updates to PAQ doc for discussion
- Telecon Agenda Aug 18, 2011
- RE: playing with pil ontology
- Re: playing with pil ontology
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
Monday, 15 August 2011
- Re: playing with pil ontology
- Re: playing with pil ontology
- Re: updates to PAQ doc for discussion
- RE: playing with pil ontology
- Re: playing with pil ontology
- Re: playing with pil ontology
- RE: updates to PAQ doc for discussion
- Re: [paq] using anchor or different links
- RE: playing with pil ontology
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- RE: [paq] using anchor or different links
- RE: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- Re: playing with pil ontology
- Re: Connection Task Force Conference Call
- Re: [paq] using anchor or different links
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
- RE: playing with pil ontology
Sunday, 14 August 2011
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
Friday, 12 August 2011
- Re: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- Re: Dates for second F2F
- Re: playing with pil ontology
- Re: [paq] using anchor or different links
- Re: updates to PAQ doc for discussion
- Re: playing with pil ontology
Thursday, 11 August 2011
- RE: [paq] using anchor or different links
- RE: updates to PAQ doc for discussion
- Re: playing with pil ontology
- [paq] using anchor or different links
- Re: updates to PAQ doc for discussion
- playing with pil ontology
- Minutes of Aug. 11 2011 Telecon
- PROV-ISSUE-74: Consider renaming target-uri as context-uri to be consistent with RFC 5988 [Accessing and Querying Provenance]
- PROV-ISSUE-73: Use "anchor" context URI instead of introducing a "target" relationship in HTTP [Accessing and Querying Provenance]
- Re: PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- PROV-ISSUE-72 (DGarijo): Uses should be renamed as used [Formal Model]
- RE: updates to PAQ doc for discussion
- RE: updates to PAQ doc for discussion
- Re: updates to PAQ doc for discussion
Wednesday, 10 August 2011
- updates to PAQ doc for discussion
- Telecon Agenda Aug 11, 2011
- Re: defining shortcuts and extensions
- defining shortcuts and extensions
- Re: call for new question ideas for the 2nd implementation stakeholder questionnaire
Tuesday, 9 August 2011
- Re: Connection Task Force Conference Call
- Re: Connection Task Force Conference Call
- Connection Task Force Conference Call
- Re: naming the standard
- Re: naming the standard
- Re: defining shortcuts and extensions
- Re: defining shortcuts and extensions
- Discussion focus for the next two weeks
- defining shortcuts and extensions
- Re: naming the standard
- Re: naming the standard
Monday, 8 August 2011
- call for new question ideas for the 2nd implementation stakeholder questionnaire
- name of standards - responses
- naming the standard
Sunday, 7 August 2011
Saturday, 6 August 2011
- PROV-ISSUE-71 (Conceptual Model draft): Section 3.2 of Conceptual Model draft (Content and Editing) [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): What is a PE? (was) Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
Friday, 5 August 2011
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-69 (Process Execution): Process execution occurs over a "continuous time interval"? [Conceptual Model]
- Re: PROV-ISSUE-43 (derivation-time): Deriviation should have associated time [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-69 (Process Execution): Process execution occurs over a "continuous time interval"? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- provenance model document
- Meeting minutes 2011-08-04
- Re: PROV-ISSUE-69 (Process Execution): Process execution occurs over a "continuous time interval"? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- PAQ: revised section on querying
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-44 (shortcuts): Introduce widely used provenance concepts as shortcuts in the model [Conceptual Model]
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- RE: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
Thursday, 4 August 2011
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-26 (uses and generates questions): How can one figure out the provenance of a given entity?
- Re: PROV-ISSUE-44 (shortcuts): Introduce widely used provenance concepts as shortcuts in the model [Conceptual Model]
- Re: Dates for second F2F
- Dates for second F2F
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: PROV-ISSUE-62 (about-prov-language): about provenance language [Conceptual Model]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- PAQ: further revision of simple HTTP interface for discovery (ISSUE 53)
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- scribe required for teleconference
- Re: PROV-ISSUE-62 (about-prov-language): about provenance language [Conceptual Model]
- Re: [PAQ] editorial issues
- PROV-ISSUE-70 (provenance-term): PAQ document uses inconsistent terminology for "provenance"
- PAQ closing issues
- Re: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Re: PROV-ISSUE-68 (http-link-domain): Domain of HTTP links with rel=provenance [Accessing and Querying Provenance]
- Re: [PAQ] editorial issues
- Re: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Re: PROV-ISSUE-60: comments on bob [Conceptual Model]
- Re: PROV-ISSUE-53 (sparql-query-is-overkill): can't we have a lighter method to retrieve provenance-uri, given a document uri? [Accessing and Querying Provenance]
- Re: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-46 (where-is-D-in-provenance): Where do I find document D in provenance [Accessing and Querying Provenance]
- Re: PROV-ISSUE-65 (domain-specific-info): How is domain specific data combined with the generic model [Conceptual Model]
- Re: PROV-ISSUE-64 (definition-use): definition of use [Conceptual Model]
- Re: PROV-ISSUE-62 (about-prov-language): about provenance language [Conceptual Model]
- PROV-ISSUE-69 (Process Execution): Process execution occurs over a "continuous time interval"? [Conceptual Model]
Wednesday, 3 August 2011
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: Straw Poll - Naming the Provenance Standard
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
Tuesday, 2 August 2011
- RE: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Prov WG Telecon Agenda 04 August 2011
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- RE: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- RE: PROV-ISSUE-56 (derivation-definition-does-not-imply-transitivity): Derivation as defined is not transitive [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-57 (comment-on-ivp-of): comment on ivp of
- Straw Poll - Naming the Provenance Standard
- Minutes from July 28, 2011 Telecon
- Re: PROV-ISSUE-46 (where-is-D-in-provenance): Where do I find document D in provenance [Accessing and Querying Provenance]
- Re: PROV-ISSUE-51 (asserter-def): Asserter needs to be defined with respect to a provenance container/account [Conceptual Model]
- Re: relation <--> property
- PROV-ISSUE-68 (http-link-domain): Domain of HTTP links with rel=provenance [Accessing and Querying Provenance]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
Monday, 1 August 2011
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- [PAQ] editorial issues
- Re: PROV-ISSUE-53 (sparql-query-is-overkill): can't we have a lighter method to retrieve provenance-uri, given a document uri? [Accessing and Querying Provenance]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- RE: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- RE: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- RE: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- Re: vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-67 (single-execution): Why is there a difference in what is represented by one vs multiple executions? [Conceptual Model]
- Re: PROV-ISSUE-66 (is-execution-a-bob): Why is process execution not defined as a characterised entity? [Conceptual Model]
- vote on replacement for BOB (deadline: Wednesday 03 Aug 8am GMT)