prov-wg teleconference minutes 2012-09-27
Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
- Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
- Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
batch 3 (18 issues): proposed responses to public comments (deadline Wednesday Oct 3rd)
Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
- Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
- Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
PROV-ISSUE-565 (rdfa-check): Do the suggested way of pointing to provenance work in rdfa [Accessing and Querying Provenance]
scribe required for today, thanks
Editorial error in the primer
PROV-ISSUE-564 (primer-version-copy): Primer Section 2.9 Versions and copies [Primer]
PROV-ISSUE-563 (primer-alternates-figure): Primer Section 3.9 Alternates [Primer]
PROV-ISSUE-562 (primer-specialization-inheritance): Primer Section 2.9 specialization [Primer]
PROV-ISSUE-561 (primer-figure-sync): Primer Section 2 figure [Primer]
Re: PROV-ISSUE-519: Data Model Figure 8 [prov-dm]
Re: PROV-ISSUE-521: Data Model Section 5.3.3 [prov-dm]
PROV-ISSUE-560: type overlap question [prov-dm-constraints]
Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
- Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
- Re: Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
prov-dm normative sections (ISSUE-495)
PROV-WG Telecon Agenda 27 September 2012
Re: PROV-ISSUE-520: Data Model Section 5.3.1 [prov-dm]
PROV-ISSUE-559: For delegation, two agents need to have some overlap in their lifetime. [prov-dm-constraints]
Re: ACTION-650: Review what provenance WG is doing with an eye to application to privacy issues
prov-o ISSUE-349
update on issue-479
Re: PROV-ISSUE-530: Data Model Section 5.7.2 (Table 6) [prov-dm]
prov-wg Telcon Minutes Sept. 20, 2012
WORKS workshop: Submission deadline extended to the 28th of September
[CFP] BigPROV @EDBT 2013: Workshop on Managing and Querying Provenance Data at Scale
proposed responses to public comments (deadline: Wednesday 09/26)
- RE: proposed responses to public comments (deadline: Wednesday 09/26)
- Re: proposed responses to public comments (deadline: Wednesday 09/26)
Fwd: ACTION-650: Review what provenance WG is doing with an eye to application to privacy issues
Re: PROV-ISSUE-461: provo cross reference inadequate in printed form [PROV-O HTML]
PROV-XML Call on monday (please RSVP)
Re: PROV-ISSUE-442 (prov-o-html-term-coverage): Identify prov.owl terms that can be omitted in prov.html [PROV-O HTML]
Re: PROV-ISSUE-382 (jzhao): Qualification patters in prov-o section 3.3 [PROV-O HTML]
FYI - Fwd: Comments on TF-Graphs/Minimal-dataset-semantics
prov-wg Telcon Agenda September 20, 2012
- Re: prov-wg Telcon Agenda September 20, 2012
- Re: prov-wg Telcon Agenda September 20, 2012
- Re: prov-wg Telcon Agenda September 20, 2012
- Re: prov-wg Telcon Agenda September 20, 2012
PROV-ISSUE-558: Introducing commonAttributes allows role/value on objects which dm does not allow for [XML Serialization]
PROV-ISSUE-557: why collectionMemberOf instead of hadMember? [XML Serialization]
- Re: PROV-ISSUE-557: why collectionMemberOf instead of hadMember? [XML Serialization]
- Re: PROV-ISSUE-557: why collectionMemberOf instead of hadMember? [XML Serialization]
XML Schema Updates
Re: PROV-ISSUE-554 (time-qualification): public comment: should qualfied and unqualified versions the same [prov-dm-constraints]
PROV-ISSUE-556 (time-qualification): public comment: should qualfied and unqualified versions the same [prov-dm-constraints]
PROV-ISSUE-555 (time-qualification): public comment: should qualfied and unqualified versions the same [prov-dm-constraints]
PROV-ISSUE-554 (time-qualification): public comment: should qualfied and unqualified versions the same [prov-dm-constraints]
prov-wg: Minutes of September 13, 2012 Telcon
PROV SW page and FAQ
response to public comments (deadline: Tuesday Sep 18)
- Re: response to public comments (deadline: Tuesday Sep 18)
- Re: response to public comments (deadline: Tuesday Sep 18)
On creating/editing W3C Notes
PROV-ISSUE-553: QNames are too restrictive as identifiers [XML Serialization]
PROV-ISSUE-552 (subclass-prov-o): Check subclass definitions in prov-o [Ontology]
implementation report - requiring an upload of a provenance trace?
Re: PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
prov-wg Telcon Agenda September 13, 2012
- Re: prov-wg Telcon Agenda September 13, 2012
- Re: prov-wg Telcon Agenda September 13, 2012
- Re: prov-wg Telcon Agenda September 13, 2012
- Re: prov-wg Telcon Agenda September 13, 2012
- Re: prov-wg Telcon Agenda September 13, 2012
- Re: prov-wg Telcon Agenda September 13, 2012
PROV-ISSUE-551: Flatten XML Schema removing records and/or dependencies? [XML Serialization]
Constraints Last Call published
skeleton of the implementation report
Re: PROV-ISSUE-479: cite TriG for examples [Ontology]
- Re: PROV-ISSUE-479: cite TriG for examples [Ontology]
- Re: PROV-ISSUE-479: cite TriG for examples [Ontology]
- Re: PROV-ISSUE-479: cite TriG for examples [Ontology]
PROV-ISSUE-550: Bundles have required records, why not optional? [XML Serialization]
PROV-ISSUE-549: XML Schema Bundle vs. NamedBundle [XML Serialization]
PROV-ISSUE-548: XSD MentionOf, change terms to match PROV-DM [XML Serialization]
PROV-ISSUE-547: prov:records requires a specific order of elements [XML Serialization]
prov-o call today
Sesame's AliBaba uses PROV-O for auditing
PROV-ISSUE-546: Notation Section 3.7.4 [prov-n]
PROV-ISSUE-545: Notation Section 3.7.2 [prov-n]
PROV-ISSUE-544: Notation Section 3.7 [prov-n]
PROV-ISSUE-543: Notation Section 3.5 [prov-n]
PROV-ISSUE-542: Notation Section 3.1.4 [prov-n]
PROV-ISSUE-541: Notation Section 3.1.3 [prov-n]
PROV-ISSUE-540: Notation Section 3, structure of documentation [prov-n]
PROV-ISSUE-539: Notation Section 3, EBNF format [prov-n]
PROV-ISSUE-538: Notation Section 2.4, example 2 [prov-n]
PROV-ISSUE-537: Notation Section 2.4 [prov-n]
PROV-ISSUE-536: Notation Section 2.3 [prov-n]
PROV-ISSUE-535: Notation Section 2.2 [prov-n]
PROV-ISSUE-534: Notation Section 2.1 [prov-n]
PROV-ISSUE-533: Notation, of attributes [prov-n]
PROV-ISSUE-532: Data Model Section 5.7.2.3 [prov-dm]
PROV-ISSUE-531: Data Model Section 5.7.2.2 [prov-dm]
PROV-ISSUE-530: Data Model Section 5.7.2 (Table 6) [prov-dm]
- Re: PROV-ISSUE-530: Data Model Section 5.7.2 (Table 6) [prov-dm]
- Re: PROV-ISSUE-530: Data Model Section 5.7.2 (Table 6) [prov-dm]
PROV-ISSUE-529: Data Model Section 5.6.1 [prov-dm]
PROV-ISSUE-528: Data Model Section 5.5.3 [prov-dm]
PROV-ISSUE-527: Data Model Section 5.5.3 [prov-dm]
PROV-ISSUE-526: Data Model Section 5.5.2 [prov-dm]
- Re: PROV-ISSUE-526: Data Model Section 5.5.2 [prov-dm]
- Re: PROV-ISSUE-526: Data Model Section 5.5.2 [prov-dm]
PROV-ISSUE-525: Data Model Section 5.5.1 [prov-dm]
PROV-ISSUE-524: Data Model Section 5.4.1 [prov-dm]
PROV-ISSUE-523: Data Model Section 5.3.5 [prov-dm]
PROV-ISSUE-522: Data Model Section 5.3.4 [prov-dm]
PROV-ISSUE-521: Data Model Section 5.3.3 [prov-dm]
PROV-ISSUE-520: Data Model Section 5.3.1 [prov-dm]
PROV-ISSUE-519: Data Model Figure 8 [prov-dm]
PROV-ISSUE-518: Data Model Section 5.2.4 [prov-dm]
- Primary Source again (Re: PROV-ISSUE-518: Data Model Section 5.2.4 ) [prov-dm]
PROV-ISSUE-517: Data Model Sections 5.2.2 and 5.2.3 [prov-dm]
PROV-ISSUE-516: Data Model Section 5.2.1 [prov-dm]
PROV-ISSUE-515: Data Model Section 5.1.8 [prov-dm]
- Re: PROV-ISSUE-515: Data Model Section 5.1.8 [prov-dm]
- Re: PROV-ISSUE-515: Data Model Section 5.1.8 [prov-dm]
PROV-ISSUE-514: Data Model Section 5.1.7 [prov-dm]
PROV-ISSUE-513: Data Model Section 5.1.6 [prov-dm]
PROV-ISSUE-512: Data Model Section 5.1.5 (Example 21) [prov-dm]
PROV-ISSUE-511: Data Model Section 5.1.4 [prov-dm]
PROV-ISSUE-510: Data Model Section 5.1.3 [prov-dm]
PROV-ISSUE-509: Data Model Figure 5 [prov-dm]
PROV-ISSUE-508: Data Model Table 5 [prov-dm]
PROV-ISSUE-507: Data Model Tables 4 and 5 [prov-dm]
- Re: PROV-ISSUE-507: Data Model Tables 4 and 5 [prov-dm]
- Re: PROV-ISSUE-507: Data Model Tables 4 and 5 [prov-dm]
PROV-ISSUE-506: Data Model Section 4.1 [prov-dm]
PROV-ISSUE-505: Data Model Section 3 [prov-dm]
PROV-ISSUE-504: Data Model Section 2.2.2 [prov-dm]
PROV-ISSUE-503: Data Model Section 2.2.1.2 [prov-dm]
PROV-ISSUE-502: Data Model Section 2.1.2 [prov-dm]
PROV-ISSUE-501: Data Model Section 2.1.1, example [prov-dm]
- Re: PROV-ISSUE-501: Data Model Section 2.1.1, example [prov-dm]
- Re: PROV-ISSUE-501: Data Model Section 2.1.1, example [prov-dm]
- Re: PROV-ISSUE-501: Data Model Section 2.1.1, example [prov-dm]
PROV-ISSUE-500: Data Model Section 2.1.1, hierarchies [prov-dm]
PROV-ISSUE-499: Data Model Section 2.1.1, semantics [prov-dm]
PROV-ISSUE-498: Data Model Table 2 [prov-dm]
PROV-ISSUE-497: prov-dm: Data Model Figure 1 [prov-dm]
- Re: PROV-ISSUE-497: prov-dm: Data Model Figure 1 [prov-dm]
- Re: PROV-ISSUE-497: prov-dm: Data Model Figure 1 [prov-dm]
- Re: PROV-ISSUE-497: prov-dm: Data Model Figure 1 [prov-dm]
PROV-ISSUE-496: ivan's feedback on prov-n LC [prov-n]
PROV-ISSUE-495: ivan's feedback on prov-dm LC [prov-dm]
Re: PROV-ISSUE-463 (freimuth): comments from robert freimuth [prov-dm]
PROV-ISSUE-494: Make prov:ref a required attribute for Ref complexTypes
F2F4 Sign-up and Details
prov-wg meeting minutes 2012-09-06
updates to implementation questionnaire
today's call: scribe required
RE: bibtex for prov documents?
Re: PROV-ISSUE-482: [external question] bundle IDs on insertion, context [prov-dm]
Re: PROV-ISSUE-214 (prov-sem-event-activities): PROV-SEM: Linking events to activities [Formal Semantics]
Re: PROV-ISSUE-212 (three-vs-two-levels): Shold we distinguish between things, entities and entity records in the semantics or just have entities and entity records [Formal Semantics]
PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
- Re: PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
- Re: PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
- Re: PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
- Re: PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
- Re: PROV-ISSUE-493: prov:type has type Value; valid values too general, include number, datetime, boolean, etc. [prov-dm]
PROV-ISSUE-492: typo in example [prov-dm]
Re: PROV-ISSUE-482: [external question] bundle IDs on insertion, context [prov-dm]
- Re: PROV-ISSUE-482: [external question] bundle IDs on insertion, context [prov-dm]
- Re: PROV-ISSUE-482: [external question] bundle IDs on insertion, context [prov-dm]
Re: PROV-ISSUE-449: Better definition of prov:value [prov-dm]
Re: PROV-ISSUE-450: DM tables "incomplete" (specifically: activity ending activity) [prov-dm]
PROV-ISSUE-491: [external] feedback on prov:agent explanation. [PROV-O HTML]
Re: PROV-ISSUE-447: subactivity relation [prov-dm]
- RE: PROV-ISSUE-447: subactivity relation [prov-dm]
- Re: PROV-ISSUE-447: subactivity relation [prov-dm]
- Re: PROV-ISSUE-447: subactivity relation [prov-dm]
Re: PROV-ISSUE-396: Rename "wasRevisionOf" to "revisedFrom"? [prov-dm]
Re: PROV-ISSUE-435: "specialized entity" in specialization definition [prov-dm]
Re: PROV-ISSUE-409 (prov-dm-review-LC): feedback on PROV-DM document (for last call release) [prov-dm]
Re: PROV-ISSUE-395: Rename hadOriginalSource to "originatedFrom"? [prov-dm]
Re: ISSUE-385: hasProvenanceIn: finding a solution
Re: PROV-ISSUE-391 (jzhao): Reflecting Membership in the Collection Component [prov-dm]
Re: [owl changed] Re: PROV-ISSUE-384 (prov-role-in-attribution): prov:role in attribution or not? [prov-dm]
Re: PROV-ISSUE-383 (how-to-handle-subtypes): How to handle subtypes in PROV-DM [prov-dm]
Re: PROV-ISSUE-376 (rename-responsibility): Renaming Responsibility (to Behalf?) [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-337 (agent-and-entity): agent should not be a subclass of entity [prov-dm]
Re: PROV-ISSUE-288 (TLebo): ProvRDF issues for Usage [mapping prov-dm <-> prov-o]
Re: PROV-ISSUE-459 (prov-constraints-lc-review): PROV-CONSTRAINTS review [prov-dm-constraints]
PROV-WG Telecon Agenda 06 September 2012
Re: PROV-ISSUE-465 (avoid-infinite-inferences): Avoid infinite loops in inferences [prov-dm-constraints]
Re: PROV-ISSUE-471 (wrong-wasAttributedTo-constraints): wasAttributedTo constraints not sensical [prov-dm-constraints]
- Re: PROV-ISSUE-471 (wrong-wasAttributedTo-constraints): wasAttributedTo constraints not sensical [prov-dm-constraints]
- Re: PROV-ISSUE-471 (wrong-wasAttributedTo-constraints): wasAttributedTo constraints not sensical [prov-dm-constraints]