suggested resolution ISSUE-507

Dear Robert

Thank you for your comment. Below is the suggested resolution. Please
let us know if you are fine with it. You can find any suggested
changes in the latest editor's draft at
http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html

Thanks,
Paul

ISSUE-507 (Inverse Relations)

"PROV-O gives the unqualified inverse of wasAssociatedWith as
prov:wasAssociateFor, but that association isn't included in these
tables. Please verify all docs in the PROV spec are internally
consistent and complete, so that someone that reads only the data
model spec is not missing information found in the ontology spec."

Original email:
http://lists.w3.org/Archives/Public/public-prov-wg/2012Sep/0097.html

Tracker: http://www.w3.org/2011/prov/track/issues/507

Group Response
- In line with relational design, PROV-DM, as a conceptual model,
defines relations without defining their inverses.

- PROV-O does not define inverse relations normatively. Instead,
prov-o suggests (by means of annotations) names that may be used for
inverse properties.

- Hence, PROV-O and PROV-DM are aligned since they do not provide
normative definitions of inverses.

- This issue was debated at length by the Working Group. A key concern
regarding normative definitions of inverse is the proliferation of
terms.

- A PROV extension may adopt the suggested names for their specific purpose.

References:
- Issue on inverse: http://www.w3.org/2011/prov/track/issues/83
- Group resolution to add annotation for inverses:
http://www.w3.org/2011/prov/wiki/PIL_OWL_Ontology_Meeting_20

Changes to the document: none.

-- 
--
Dr. Paul Groth (p.t.groth@vu.nl)
http://www.few.vu.nl/~pgroth/
Assistant Professor
- Knowledge Representation & Reasoning Group |
  Artificial Intelligence Section | Department of Computer Science
- The Network Institute
VU University Amsterdam

Received on Thursday, 27 September 2012 19:36:30 UTC