Reminder: Review of responses to PROV-CONSTRAINTS public comments
PROV WG Telecon 2012.11.01
RE: PROV-ISSUE-410 (prov-primer-review): Feedback on Primer document [Primer]
Re: Provenance Example for TriG Spec
Re: PROV-ISSUE-475: Request to drop "mention" and related elements [prov-dm]
Updates to PROV-XML Note draft.
RE: Comments on the Prov Primer
prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
- Re: prov-wg: Vote on Exit Criteria
Review of PROV-CONSTRAINTS issues (ISSUE-576, ISSUE-580, ISSUE-577, ISSUE-578, ISSUE-581)
prov-wg draft agenda F2F4
confirmation on changes to prov-n
prov-wg Minutes of the October 25, 2012 Telcon
Re: typo "addiition" in prov-o 3.1 editor's draft
Review of PROV-CONSTRAINTS issues (ISSUE-582, ISSUE-579, ISSUE-585, ISSUE-583)
Re: PROV-ISSUE-556 (time-qualification): public comment: should qualfied and unqualified versions the same [prov-dm-constraints]
further responses and closed issues in prov-dm
Re: PROV-ISSUE-556 (time-qualification): public comment: should qualfied and unqualified versions the same [prov-dm-constraints]
Re: PROV-ISSUE-560: type overlap question [prov-dm-constraints]
Re: PROV-ISSUE-559: For delegation, two agents need to have some overlap in their lifetime. [prov-dm-constraints]
Review of PROV_CONSTRAINTS issues (ISSUE-582, ISSUE-586, ISSUE-587, ISSUE-588)
Re: PROV-ISSUE-490 (prov-constraints-lc-editorial): PROV-CONSTRAINTS pre-Last Call editorial issues [prov-dm-constraints]
PROV-ISSUE-588 (strictly-precedes-irreflexive): It is never specified explicitly that "strictly-precedes" is irreflexive [prov-dm-constraints]
PROV-ISSUE-587 (rdf-analogies): Concerns about analogies to RDF blank nodes/semantics [prov-dm-constraints]
PROV-ISSUE-586 (toplevel-bundle-description): The description of 'toplevel bundle' as 'set of statements not appearing in a named bundle' is unclear [prov-dm-constraints]
PROV-ISSUE-585 (applying-satisfying-constraints): Suggestion to avoid discussing how to 'apply' constraints; clarify what it means to 'satisfy' constraints [prov-dm-constraints]
PROV-ISSUE-584 (merging): The nonstandard/procedurally defined 'merging' operation on terms [prov-dm-constraints]
PROV-ISSUE-583 (equivalent-instances-in-bundles): Questions concerning what it means for applications to treat equivalent instances 'in the same way', particularly in bundles. [prov-dm-constraints]
PROV-ISSUE-582 (document-instance): 'of their respective documents.' should be '... of their respective instances.' [prov-dm-constraints]
PROV-ISSUE-581 (avoid-specifying-algorithm): Suggestion to avoid wording that 'almost requires' using normalization to implement constraints [prov-dm-constraints]
PROV-ISSUE-580 (drop-syntactic-sugar-definitions): Suggestion to drop definitions in section 4.1 since they are not needed if the semantics is defined more abstractly [prov-dm-constraints]
PROV-ISSUE-579 (declarative-fol-specification): Suggestion to replace procedural specification with (equivalent, but shorter and less prescriptive) declarative theory in First-Order Logic [prov-dm-constraints]
PROV-ISSUE-578 (equivalence): Use of "equivalent" incompatible with common uses of the term in logic/mathematics [prov-dm-constraints]
PROV-ISSUE-577 (valid-vs-consistent): Terminology: valid vs. consistent [prov-dm-constraints]
Syntax checking Turtle examples (ACTION-117)
Fwd: activity delegation (ISSUE-522)
Re: acknowledging PROV responses (ISSUE-516)
on specialization/alternate/membership (ISSUE-525)
- Re: on specialization/alternate/membership (ISSUE-525)
- Re: on specialization/alternate/membership (ISSUE-525)
- Re: on specialization/alternate/membership (ISSUE-525)
closing some prov-dm issues
prov-wg: Telcon Agenda October 25, 2012
prov-wg: Minutes of the October 18, 2012 Telecon
- Re: prov-wg: Minutes of the October 18, 2012 Telecon
- Re: prov-wg: Minutes of the October 18, 2012 Telecon
last call for comments on exit criteria
PROV-ISSUE-576: logical definition and comments on prov-constratins [prov-dm-constraints]
- Re: PROV-ISSUE-576: logical definition and comments on prov-constratins [prov-dm-constraints]
- Re: PROV-ISSUE-576: logical definition and comments on prov-constratins [prov-dm-constraints]
Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
- Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
- Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
- Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
- Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
- Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
- Re: PROV-ISSUE-472 (Feedback_IH): Review of the DC-NOTE by Ivan Herman [Mapping PROV-O to Dublin Core]
Re: proposed responses to public comments (deadline Wednesday 24th, midnight GMT)
Re: PROV-ISSUE-402 (Feedback_SM): Feedback on the feedback from Simon Miles [Mapping PROV-O to Dublin Core]
proposed responses to public comments (deadline Wednesday 24th, midnight GMT)
ISSUE-475: Request to drop "mention" and related elements
Re: PROV-ISSUE-495: ivan's feedback on prov-dm LC [prov-dm]
Re: PROV-ISSUE-463 (freimuth): comments from robert freimuth [prov-dm]
Re: PROV-ISSUE-498: Data Model Table 2 [prov-dm]
Re: PROV-ISSUE-462 (entity-definition-precision): Definition o entity may be too liberal [prov-dm]
- Re: PROV-ISSUE-462 (entity-definition-precision): Definition o entity may be too liberal [prov-dm]
- Re: PROV-ISSUE-462 (entity-definition-precision): Definition o entity may be too liberal [prov-dm]
- Re: PROV-ISSUE-462 (entity-definition-precision): Definition o entity may be too liberal [prov-dm]
- Re: PROV-ISSUE-462 (entity-definition-precision): Definition o entity may be too liberal [prov-dm]
- Re: PROV-ISSUE-462 (entity-definition-precision): Definition o entity may be too liberal [prov-dm]
PROV-ISSUE-575: identifier field [prov-dm-constraints]
Revised Exit Criteria - final comments
pairs of implementations?
Re: PROV-ISSUE-446: prov:involvee not documented in PROV-O [PROV-O HTML]
[PROV-O] Proposed OWL change: Dealing with Issue 568 (hadRole)
- Re: [PROV-O] Proposed OWL change: Dealing with Issue 568 (hadRole)
- Re: [PROV-O] Proposed OWL change: Dealing with Issue 568 (hadRole)
- Re: [PROV-O] Proposed OWL change: Dealing with Issue 568 (hadRole)
scribe needed
RDF WG responses
Fwd: clock change reminder; 28-Oct to 4-Nov
PROV-WG telcon minutes
2nd CFP: BigPROV @EDBT 2013 and ProvBench: Managing and Querying Provenance Data at Scale
Test cases for PROV-CONSTRAINTS
prov-n issues under review
prov-dm issues under review
prov-wg Telcon Agenda Oct. 18, 2012
- Re: prov-wg Telcon Agenda Oct. 18, 2012
- Re: prov-wg Telcon Agenda Oct. 18, 2012
- Re: prov-wg Telcon Agenda Oct. 18, 2012
reminder about prov exit criteria
Re: PROV-ISSUE-499: Data Model Section 2.1.1, semantics [prov-dm]
Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
Re: PROV-ISSUE-499: Data Model Section 2.1.1, semantics [prov-dm]
PROV-ISSUE-574 (primer-figure): Update primer overview figure [Primer]
Re: PROV-ISSUE-496: ivan's feedback on prov-n LC [prov-n]
- Compliance with PROV-N (related to PROV-ISSUE-496: ivan's feedback on prov-n LC [prov-n])
- Re: PROV-ISSUE-496: ivan's feedback on prov-n LC [prov-n]
- Re: PROV-ISSUE-496: ivan's feedback on prov-n LC [prov-n]
Re: PROV-ISSUE-477 (rename toplevel-bundle): rename toplevel-bundle to dataset [prov-n]
prov-n proposed responses to comments (deadline Thursday 12noon GMT)
Re: PROV-ISSUE-544: Notation Section 3.7 [prov-n]
PROV-ISSUE-573 (mime-type): mime type registration feedback [prov-n]
- Re: PROV-ISSUE-573 (mime-type): mime type registration feedback [prov-n]
- Re: PROV-ISSUE-573 (mime-type): mime type registration feedback [prov-n]
Re: PROV-ISSUE-539: Notation Section 3, EBNF format [prov-n]
Re: PROV-ISSUE-540: Notation Section 3, structure of documentation [prov-n]
Re: PROV-ISSUE-533: Notation, of attributes [prov-n]
Re: PROV-ISSUE-538: Notation Section 2.4, example 2 [prov-n]
Re: PROV-ISSUE-536: Notation Section 2.3 [prov-n]
Re: PROV-ISSUE-534: Notation Section 2.1 [prov-n]
Re: PROV-ISSUE-535: Notation Section 2.2 [prov-n]
Re: PROV-ISSUE-537: Notation Section 2.4 [prov-n]
Re: PROV-ISSUE-545: Notation Section 3.7.2 [prov-n]
Re: PROV-ISSUE-546: Notation Section 3.7.4 [prov-n]
Re: PROV-ISSUE-543: Notation Section 3.5 [prov-n]
Re: PROV-ISSUE-541: Notation Section 3.1.3 [prov-n]
Fwd: New public IRC server refuses passwords
prov-n issues closed
proposed responses to public comments (deadline: Wednesday 10/17)
Admin for the F2F: please make sure you register
Re: PROV-ISSUE-572: What constraints should we have on ordering of elements within the main complexTypes? [XML Serialization]
alternate of and sambas
scribe required for today, thanks!
Revised exit criteria
PROV-ISSUE-572: What constraints should we have on ordering of elements within the main complexTypes? [XML Serialization]
Dealing with mutable resources (PROV-O in Callimachus) - ISSUE-569
- RE: Dealing with mutable resources (PROV-O in Callimachus) - ISSUE-569
- Re: Dealing with mutable resources (PROV-O in Callimachus) - ISSUE-569
- Re: Dealing with mutable resources (PROV-O in Callimachus) - ISSUE-569
- Re: Dealing with mutable resources (PROV-O in Callimachus) - ISSUE-569
- Re: Dealing with mutable resources (PROV-O in Callimachus) - ISSUE-569
PROV-ISSUE-570 (changing resources): How do we deal with resources that change? [prov-dm]
PROV-ISSUE-571 (changing resources): How do we deal with resources that change? [prov-dm]
PROV-ISSUE-569 (changing resources): How do we deal with resources that change? [prov-dm]
Presentation on Prov yesterday
Provenance specs: have we lost sight of the goal?
- Re: Provenance specs: have we lost sight of the goal?
- Re: Provenance specs: have we lost sight of the goal?
- Re: Provenance specs: have we lost sight of the goal?
- Re: Provenance specs: have we lost sight of the goal?
PROV-WG Telecon Agenda 10 October 2012
- Re: PROV-WG Telecon Agenda 10 October 2012
- Re: PROV-WG Telecon Agenda 10 October 2012
- Re: PROV-WG Telecon Agenda 10 October 2012
- Re: PROV-WG Telecon Agenda 10 October 2012
prov-wg Telcon Minutes October 4, 2012
RE: PROV-ISSUE-563 (primer-alternates-figure): Primer Section 3.9 Alternates [Primer]
Re: PROV-ISSUE-482: [external question] bundle IDs on insertion, context [prov-dm]
Re: prov-dm normative sections (ISSUE-495)
feedback sought on ISSUE-529, ISSUE-524, ISSUE5-519, ISSUE-523
- RE: feedback sought on ISSUE-529, ISSUE-524, ISSUE5-519, ISSUE-523
- Re: feedback sought on ISSUE-529, ISSUE-524, ISSUE5-519, ISSUE-523
proposed responses to public comments (deadline: Wednesday 10/10)
- RE: proposed responses to public comments (deadline: Wednesday 10/10)
- Re: proposed responses to public comments (deadline: Wednesday 10/10)
- Re: proposed responses to public comments (deadline: Wednesday 10/10)
PROV-ISSUE-568 (hadRole-domain): domain of prov:hadRole [Ontology]
- Re: PROV-ISSUE-568 (hadRole-domain): domain of prov:hadRole [Ontology]
- Re: PROV-ISSUE-568 (hadRole-domain): domain of prov:hadRole [Ontology]
Re: PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]
RE: PROV-ISSUE-515: Data Model Section 5.1.8 [prov-dm]
RE: PROV-ISSUE-530: Data Model Section 5.7.2 (Table 6) [prov-dm]
Re: PROV-ISSUE-520: Data Model Section 5.3.1 [prov-dm]
- RE: PROV-ISSUE-520: Data Model Section 5.3.1 [prov-dm]
- Re: PROV-ISSUE-520: Data Model Section 5.3.1 [prov-dm]
RE: PROV-ISSUE-520: Data Model Section 5.3.1 [prov-dm]
RE: PROV-ISSUE-521: Data Model Section 5.3.3 [prov-dm]
prov-wg - Telcon Agenda October 3, 2012
Re: PROV-ISSUE-522: Data Model Section 5.3.4 [prov-dm]
Re: PROV-ISSUE-513: Data Model Section 5.1.6 [prov-dm]
Re: PROV-ISSUE-516: Data Model Section 5.2.1 [prov-dm]
- Re: PROV-ISSUE-516: Data Model Section 5.2.1 [prov-dm]
- Re: PROV-ISSUE-516: Data Model Section 5.2.1 [prov-dm]
- Re: PROV-ISSUE-516: Data Model Section 5.2.1 [prov-dm]
Re: batch 3 (18 issues): proposed responses to public comments (deadline Wednesday Oct 3rd)
UML and upper case labels
subactivity resolutions
ISSUE-520 response
PROV-ISSUE-567 (Link-to-inverse-prop-missing): The link ti the inverse property file is missing in the ontology [PROV-O HTML]
PROV-ISSUE-566 (fix-images): HTML images still have references to the bundles as named greaphs [PROV-O HTML]
Re: PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]
- Re: PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]
- Re: PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]
- Re: PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]
- Re: PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]