Date Model spec: slight modifications

As this community is getting closer to ODRL 2.1 we at IPTC went over the
wording in the current Date Model draft document 

http://www.w3.org/community/odrl/work/2-0-core-model-constraint-draft-change
s/

and propose some slight modifications:

 

* 2.1 Policy / undefined attribute / ". known profile ."

We assume there is no intention for an ODRL Profile Registry making a
profile a known one.

 

We think this language should point at the profiles defined by the profile
attribute of a policy instance - then they are known to this policy.

 

* 2.3.1 Role: The function attribute MUST take one of the following values:
assigner or assignee

This is wrong. A policy as a whole should have an assigner and an assignee
but for other purposes other functions could be selected.

 

** 2.5 Duty - "... a requirement that MAY be fulfilled ."

Duty by Merriam-Webster: "something that you must do because it is morally
right or because the law requires it"

We feel this MAY should be changed into a MUST (also in the definition of
the Action a few lines below that quote.)

 

** 2.6 Prohibition - "... all of them are valid"

This sentence should not be about formal validity but about the requirement
that all prohibitions have to be satisfied.

 

Michael

 

Michael Steidl

Managing Director of the IPTC [mdirector@iptc.org]

International Press Telecommunications Council 
Web:  <http://www.iptc.org/> www.iptc.org - on Twitter
<http://www.twitter.com/IPTC> @IPTC

Business office address: 

25 Southampton Buildings, London WC2A 1AL, United Kingdom

Registered in England, company no 101096