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

PROV-ISSUE-41 (distinct-roles): Distinct roles should be SHOULD and not MUST [Conceptual Model]

From: Provenance Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Sat, 23 Jul 2011 14:21:08 +0000
To: public-prov-wg@w3.org
Message-Id: <E1Qkd4m-00073S-EC@stu.w3.org>

PROV-ISSUE-41 (distinct-roles): Distinct roles should be SHOULD and not MUST [Conceptual Model]

http://www.w3.org/2011/prov/track/issues/41

Raised by: Paul Groth
On product: Conceptual Model

Currently, use has the following definition with respect to roles:

"A reference to a given BOB may appear in multiple use assertions that refer to a given process execution, but each of those use assertions must have a distinct role."

A process execution could conceivably read the same file twice. Thus, the file would play the same role twice with respect to a process execution. It's not clear why this constraint is an absolute or the impact of making it a non-hard requirement.

 Although, I can see why it would be recommended practice in order to ensure disambiguation of roles. 

Suggested resolution, change the sentence to as follows:

"A reference to a given BOB may appear in multiple use assertions that refer to a given process execution, but each of those use assertions should have a distinct role."
Received on Saturday, 23 July 2011 14:21:09 GMT

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