W3C home > Mailing lists > Public > public-prov-wg@w3.org > March 2012

Re: PROV-ISSUE-197: Section 5.4.1 and Section 5.4.2 (PROV-DM as on Dec 5)

From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
Date: Fri, 23 Mar 2012 14:42:31 +0000
Message-ID: <EMEW3|aa34a79517cd11436d609738ac3c3415o2MEgZ08L.Moreau|ecs.soton.ac.uk|4F6C8BD7.6030209@ecs.soton.ac.uk>
To: public-prov-wg@w3.org
Hi Satya,

Further comments, following recent changes.

On 12/07/2011 02:17 AM, Provenance Working Group Issue Tracker wrote:
> PROV-ISSUE-197: Section 5.4.1 and Section 5.4.2 (PROV-DM as on Dec 5)
>
> http://www.w3.org/2011/prov/track/issues/197
>
> Raised by: Satya Sahoo
> On product:
>
> Hi,
> The following are my comments for Section Section 5.4.1 and Section 5.4.2 of the PROV-DM (as on Dec 05):
>
> Section 5.4.1:
> 1. "Given an entity record identifier e, two sets of attribute-values denoted by av1 and av2, two entity records entity(e,av1) and entity(e,av2) occurring in an account are equivalent to the entity record entity(e,av) where av is the set of attribute-value pairs formed by the union of av1 and av2."
>
> Comment: Since entity record identifier and entity identifier are stated to be the same in DM (Section 5.2.1), this constraint should be applicable to entities also. In that case, this constraint should hold across accounts also?
>    
Instead, the constraint is formulated as follows:
http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm-constraints.html#unique-description-in-account

> 2. "Application of identified-entity-in-account results in an entity record containing the attribute-value pairs age=20 and age=30. This results in an inconsistent characterization of a person."
>
> Comment: This is incorrect. The above characterization may be valid at different points in time or events (when the Berlin Wall fell, East and West Germany unified) etc. I don't think this example is needed in DM.
>
>    

We no longer use union of sets of attribute-value pairs. So, i htink 
this issue is superseded.

> 3. "Account records constitute a scope for record identifiers. Since accounts can be nested, scopes can also be nested; thus, the scope of record identifiers should be understood in the context of such nested scopes. When a record with an identifier occurs directly within an account, then its identifier denotes this record in the scope of this account, except in sub-accounts where records with the same identifier occur."
>
> Comment: This issue has been previously raised multiple number of times. The current version of the DM considers identifiers for entity and entity records to be same - hence the above applies to entity identifiers, which violates the Web architecture for globally unique identifiers and strictly monotonic notion of RDF semantics.
>
>    

No more scope, no more nesting of accounts.  So, again, I think this is 
superseded.
> --------------
> Section 5.4.2
> 1. Given the account construct that already has all the functionalities of a record container (with additional information about asserter), why is a separate construct of "record container" needed?
>
>
>    
Container is no longer in prov-dm.
Account exists as a type of entity (accountEntity(name under discussion)).

So, I think the issue is superseded.

In prov-n, the container is where you find namespace declarations. 
Account contains prov-n expressions and has a name.

So, here again, I think the issue is superseded.


Given this, I believe the issue can be closed. Can you confirm this is 
the case?

Regards,
Luc
> Thanks.
>
> Best,
> Satya
>
>
>
>    

-- 
Professor Luc Moreau
Electronics and Computer Science   tel:   +44 23 8059 4487
University of Southampton          fax:   +44 23 8059 2865
Southampton SO17 1BJ               email: l.moreau@ecs.soton.ac.uk
United Kingdom                     http://www.ecs.soton.ac.uk/~lavm
Received on Friday, 23 March 2012 14:43:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 13:06:59 GMT