Subclass

Thinking about the ODRL Regulatory Compliance Profile [1] and the general aims of ODRL to cover the widest possible use cases for communities, I think an option would be to simply subclass the ODRL entities into the specific requirements for this community.

This keeps up the interoperability role of ODRL, as well as allowing this community to use terms they are more comfortable with.

For example:
  orcp:Resource rdfs:subClassOf odrl:Asset
  orcp:Obligation rdfs:subClassOf odrl:Duty

(I assume that is what the Profile has done for orcp:PredicateConstraint and odrl:Constraint)


Cheers - Renato

[1] https://ai.wu.ac.at/policies/orcp/regulatory-model.html <https://ai.wu.ac.at/policies/orcp/regulatory-model.html>