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

PROV-ISSUE-391 (jzhao): Reflecting Membership in the Collection Component [prov-dm]

From: Provenance Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Sun, 03 Jun 2012 16:48:45 +0000
Message-Id: <E1SbDyv-0001eC-5L@tibor.w3.org>
To: public-prov-wg@w3.org
PROV-ISSUE-391 (jzhao): Reflecting Membership in the Collection Component [prov-dm]


Raised by: Jun Zhao
On product: prov-dm

The PROV-O team are in the process of reflecting the modeling of Membership in the ontology. By reading deeply into the section 5.6.5 of the DM spec about Membership, I wonder whether we should reflect a bit on the DM modeling on this construct.

It would have been straightforward to use this construct to declare which key-value pair as being a member of a collection. However, the definition of Membership shows that this construct is designed for expressing much more than this:

- The DM doc says that: "The membership relation removes the need for explicit mention of the state of the dictionary prior to each operation, allowing the state of a dictionary to be expressed without having to introduce a prior state." What does this "state of the dictionary" refer to? If we know the collection c1 before the insertion or deletion, and collection c2 after these activities, then we are all OK, right? I wonder whether this statement implies some scenarios that I am not aware of.

- A membership relation, written memberOf(id; c, {(key_1, e_1), ..., (key_n, e_n)}, cplt, attrs), has:
	•	id: an optional identifier identifying the relation;
	•	collection: an identifier (c) for the dictionary whose members are asserted;
	•	key-entity-set: a set of key-entity pairs (key_1, e_1), ..., (key_n, e_n) that are members of the dictionary;
	•	complete: an optional boolean Value (cplt); if true, it indicates that no other member belongs to the dictionary; if false, it indicates that other members belong to the dictionary; if unspecified, other members may belong to the dictionary.
	•	attributes: an optional set (attrs) of attribute-value pairs representing additional information about this relation.

It seems a rather complicated definition. Why do we have to mark a collection as "complete"? What additional attributes are we expecting to provide for a membership relation? This has direct impact on the prov ontology. The distinction between a membership and a collection is not that obvious. Can we live without a Membership class to express provenance of collections?

We would really like to have this issue resolved as soon as possible, in line with our internal release timeline, which is the upcoming Thursday. Help is much appreciated!

[1] http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#component6


Received on Sunday, 3 June 2012 16:48:47 UTC

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