[Odrl-version2] Core Model ["Poznan Edition"] - Draft Specification
Steven Rowat
steven_rowat at sunshine.net
Fri Jan 16 16:02:33 EST 2009
Greetings,
Congratulations, and the new green/yellow/pink format makes analyzing
the changes very easy.
The new conflict structure seems like a good step; my hunch is that in
actual use a further level of refinement for particularly difficult
conflicts might be necessary, but I doubt if that can be written in at
this point.
About inheritance, and with reference to diagram/example 4.9, I'd
personally prefer if inherited actions were also listed in the Child,
so that it would be easy to look in one place and see that the Rights
Expression (i.e., in the Child) allows one to 'display' and to
'print', rather than having to look and see 'inherit' and then look
back into the Parent. However, that would entail making an exception
for Actions, which is probably not a good idea (ie., show the
inheritance for them, but not for other parts of the Expression).
On the other hand, how many parts of the Expression are actually
inherited? In the example (4.9) it appears that only the Asset, which
is explicitly declared in the Child (via 'inherit'), and the
Permission to print, which is not explicitly declared. So perhaps it
would, in fact, be more consistent to declare both of them explicitly?
And last, and least, I'm sure you'll use a spell-checker before
posting a final form on the web (there are several typos) - but one
that might be good to change right away (which puzzled me for a couple
of seconds as to what word it was) is 'adequalte' in section 5; i.e.:
'are expected to be developed that adequalte document these changes'.
Overall, seems much smoother and simpler. Nice work.
Steven Rowat
More information about the Odrl-version2_odrl.net
mailing list