PROV CR Exit Criteria

The working group intends to submit this document for consideration as a W3C Proposed Recommendation after XXX having met at a minimum the following criteria.

1. PROV-O

• Each feature of PROV-O is demonstrated to be supported by at least two independent implementations.
• For each feature, one interoperability pair will have been demonstrated to exist.

2. PROV-N

• Each feature of PROV-N is demonstrated to be supported by at least two independent implementations.
• For each feature, one interoperability pair will have been demonstrated to exist.

3. PROV-DM

• PROV-O and PROV-N have satisfied their exit criteria

4. PROV-Constraints

• For each of the test cases defined by the working group, at least two independent implementations pass the tests and claim to conform to the document.
• Draft test process: http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html

Notes

What is an interoperability pair?

An interoperability pair consists of an implementation generating a feature and another, independent, implementation consuming that feature.

What constitutes an implementation?

An implementation is one of three things:

• A data set (including web pages) that use PROV for representing provenance information
  • For the purposes of PROV-N, we also consider human readable documents that use the notation to count as an implementation
• A vocabulary or ontology that extends PROV
• A piece of software that consumes or produces PROV

What constitutes demonstration?

Affirmative assertion of implementation evidenced by filling out the implementation questionnaire

What are features?

Those defined in the implementation report. Essentially, for PROV-O and PROV-N, this is each individual concept. For PROV-Constraints, this is each constraint defined in the document.

http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html

Why does PROV-Constraints not test inferences?

• The test cases are designed to test that an implementation must perform some inferences in order for constraints to be handled.

What is the rationale behind PROV-DM's exit criteria?

• PROV-DM is a conceptual model, thus it is realised in the usage of PROV-N and PROV-O.
• While not a formal exit criteria, the working group would like to provide evidence that the conceptual model was also helpful in creating implementations.