w3c
Is there a need for a custom protocol to be formalised for ODRL?
Is there a need for odrl://url/ to enable consistent interoperability?
Similar to OIDC, a location to understand the services provided:odrl://url/.well-known/odrl-configuration
Providing a consistent way to discover:
- profiles
- taxonomies and ontologies used
My two cents: the policy already describes which profile is being used. Software processing policies do not have such a standard representation, but they should...
This proposal was one level of abstraction above - a consistent end-point to find it all.
To find a profile = I need to know the policy ... To find the policy = I need to know where it is ... To use the policy = I need to know which taxonomies/ontologies to fetch ...