The ODRL 2.2 Recommendation allows in its Profile Mechanism to define subclasses of Policy of of Rule for a Profile.
But unfortunately the rules or guidelines how to subclass these two classes are vague:
Policy: An ODRL Policy MAY be subclassed to more precisely describe the context of use of the Policy that MAY include additional constraints that ODRL processors MUST understand.
Rule: nothing
This may let makers of a Profile conclude that anything not violating the rules of OWL classes, RDFS Subclasses and of these "outlines" above can be done.
It would be great to give a clearer guidelines in the Best Practices document.
Please have a look at the sections "Defining a subclass of Policy allows:" and "Defining a subclass of Rule allows:" if this covers your understanding of how to define such subclasses.
Currently I'm working on the Profile Best Practices document.
The ODRL 2.2 Recommendation allows in its Profile Mechanism to define subclasses of Policy of of Rule for a Profile. But unfortunately the rules or guidelines how to subclass these two classes are vague:
This may let makers of a Profile conclude that anything not violating the rules of OWL classes, RDFS Subclasses and of these "outlines" above can be done. It would be great to give a clearer guidelines in the Best Practices document.
Please have a look at the sections "Defining a subclass of Policy allows:" and "Defining a subclass of Rule allows:" if this covers your understanding of how to define such subclasses.