- From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Date: Mon, 22 Aug 2011 22:04:21 +0100
- To: public-prov-wg@w3.org
Hi Paul, This issue was closed, pending review. Are you satisfied with the changes? Can we close it? Alternatively, you can reopen it, or create a more specific issue. Thanks, Luc PS See note on this issue's page On 23/07/11 15:21, Provenance Working Group Issue Tracker wrote: > 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 Monday, 22 August 2011 21:04:52 UTC