public-prov-wg@w3.org from January 2013 by subject

Call for Participation: BigPROV @EDBT 2013: Workshop on Managing and Querying Provenance Data at Scale

Constraints in Prolog

examples with blank nodes in prov-o html document

Fwd: prov-o rec confusion

Fwd: Re: prov-aq review for release as working draft (ISSUE-613)

Implementation reports

ISSUE-595: Prov-xml subtyping needs to be marked in the document

Little PROV-O questions

meeting the exit criteria

Multiple XML schema files for a common target namespace (PROV-ISSUE-608)

problem viewing editor's draft (https in hg)

PROV comments from Clark&Parsia

PROV Dictionary

prov-aq review for release as working draft (ISSUE-613)

PROV-AQ: How to indicate SPARQL endpoint for provenance (ISSUE 609)

prov-constraints in sparql

PROV-DICTIONARY internal review for first public working draft (ISSUE-614)

PROV-ISSUE-553: QNames are too restrictive as identifiers [XML Serialization]

PROV-ISSUE-591: delegation PROV-O example missing activity reference [Primer]

PROV-ISSUE-611 (clarkparsia): Stardog implementation

PROV-ISSUE-612 (constraints-in-owl-public): Encoding of Constraints in OWL [Ontology]

PROV-ISSUE-613 (prov-aq-draft-review): Review paq for release as last call working draft [Accessing and Querying Provenance]

PROV-ISSUE-614: PROV-DICTIONARY internal review for first public working draft [PROV-DICTIONARY]

PROV-ISSUE-615: Provide explanation to constraint 47(3) [prov-dm-constraints]

PROV-ISSUE-616 (quoted-in-primer): Confusing use of wasQuotedFrom in primer [Primer]

PROV-ISSUE-617: Why are some prov-constraint inferences in prov-o, but not others? [Ontology]

PROV-ISSUE-618 (pingback-in-prov-aq): Should pingback be described in PROV-AQ? [Accessing and Querying Provenance]

PROV-ISSUE-619 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance]

PROV-ISSUE-620 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance]

PROV-ISSUE-621 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance]

PROV-ISSUE-622 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance]

PROV-ISSUE-623: outdated definition of prov:wasDerivedFrom [Ontology]

prov-o encoding of constraints ISSUE-612

PROV-O modeling of Unix' PID?

PROV-O's cross reference index

prov-wg - Telcon Agenda Jan. 24, 2013

prov-wg 2013-01-17 teleconference minutes

prov-wg Handling comments during CR

prov-wg Telcon Agenda January 10, 2012

prov-wg Telcon Agenda January 3, 2012

prov-wg teleconference agenda

PROV-WG teleconference agenda 2013.01.17

prov-wg: Minutes Jan. 10, 2012 Telcon

prov-wg: Telcon Minutes Jan. 24 2013

Prov-XML test cases

Provenance Working Group Teleconference Minutes of 03 January 2013

question about hadRole in example for qualifiedInfluence

question on constraint 47 (3) - wasAssociatedWith-ordering

Responses to CR public comments

scribe for first 2013 teleconference

scribe is required, thanks

scribe required, please

Typos in PROV-O examples

Update on implementations of prov

Updates to PROV-AQ

Where to put public comment response

{Disarmed} Re: prov-aq review for release as working draft (ISSUE-613)

Last message date: Thursday, 31 January 2013 23:06:05 UTC