Re: PROV-ISSUE-40 (recommended-roles): Roles should not be SHOULD and not MUST [Conceptual Model]

supposedly there are replies to this but I the W3C DB doesn't have them and I don't have the emails either. Anyways:

I am not sure MUST-> SHOULD solves the problem, because it does not give any useful guideline regarding the semantics of a relation 
without a role.

I would be happier to see  /default/ roles be defined for these relation, which can be overriden.


-Paolo


>
> PROV-ISSUE-40 (recommended-roles): Roles should not be SHOULD and not MUST [Conceptual Model]
>
> http://www.w3.org/2011/prov/track/issues/40
>
> Raised by: Paul Groth
> On product: Conceptual Model
>
> Currently, roles are required for Generation, Use, and isControlledby.
>
> Specifically the following sentence is given:
>
> "Use, Generation, and Control assertions must contain a role."
>
> It is not clear why roles must always be there. In some cases, I may not want to assert the role that something played with respect to a process.
>
> Suggested resolution is to replace MUST with SHOULD.