W3C home > Mailing lists > Public > public-prov-wg@w3.org > October 2011

Serializations, mappings, and equivalence

From: James Cheney <jcheney@inf.ed.ac.uk>
Date: Fri, 21 Oct 2011 08:40:51 -0600
Message-Id: <E3AC8162-DC71-4032-98A4-F761C2D632A9@inf.ed.ac.uk>
To: Provenance Working Group WG <public-prov-wg@w3.org>

>From the minutes and discussion yesterday, it seems that the question I asked yesterday may not have been understood, and later discussion also touched on the point I was trying to make, so I wanted to try again:

1.  The PROV-DM document uses a novel (but Prolog-like) abstract syntax notation (ASN), which can be used to describe instances of PROV.

The PROV-O OWL ontology talks about RDF and gives constraints and facts about RDF instances of PROV, and uses RDF/XML.

However, now I'm not sure what an instance of PROV "is".  Have we agreed that the RDF form is the canonical version?  I believe the charter implies this.   If so, is the ASN to be viewed as yet another compact syntax for RDF, and if so, why not use an existing one?  Furthermore, are two instances of PROV equivalent exactly when their RDF versions are equivalent (modulo OWL reasoning)?  Or do we impose further rules for equivalence?

If we have two different languages, then there is a danger - I think it's clear to *us* how to hand-convert from one representation to another, but it may be far from clear to people learning the model, and be a source of further confusion.  

The charter says, in comments under the deliverables:

"A by-product of this formalization is the mapping of the provenance interchange language to RDF graphs."

That is what I feel is missing - PROV-DM and PROV-O mention this mapping/serialization, but I am concerned that the part of PROV-O that describes this mapping does not give me (or someone unfamiliar with the model) enough information to take an ASN instance and convert it "blindly" to an RDF instance.  This could be something that the formal semantics formalizes - even if it is obvious to us, formally specifying it could be helpful to others for whom the mapping may not be obvious.  

2. Similarly, there is a deliverable D5 on XML serialization:

D5: PIL XML Serialization (W3C Note). This document specifies an XML serialization of PIL.

and the comments say:

"A serialization to XML (D5) will help disseminate the language to communities beyond the Semantic Web community."

I understood this as meaning a direct serialization to XML that would not require use of RDF in places where it's not already common, whereas the discussion yesterday seemed to indicate that people think it would be fine to serialize as RDF/XML - i.e., if we standardize on RDF/XML then D5 is a no-op.  Is this correct?  If so, it seems to defeat the purpose of D5, and makes me wonder why we have an intermediate ASN instead of just using RDF everywhere.

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
Received on Friday, 21 October 2011 14:41:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:51:02 UTC