Decide the ODRL profile IRI after the DPROD/dprod move (DPROD/dprod vs DPROD/contracts vs umbrella) #210

Background

The DPROD vocabulary moved from the bare https://www.omg.org/spec/DPROD/ to https://www.omg.org/spec/DPROD/dprod/ (#204 / #205). That leaves the ODRL profile IRI — currently still the bare https://www.omg.org/spec/DPROD/ — needing a decision.

The profile IRI appears as:

• the prof:Profile subject in dprod-contracts/dprod-contracts-prof.ttl
• the SHACL sh:hasValue enforcement + messages in dprod-contracts/dprod-contracts-shapes.ttl ("DPROD policies must declare odrl:profile <…>")
• every odrl:profile <…/DPROD/> in the examples and docs

This is split out of #207 / #209 because it is a modeling decision, not a mechanical rename. #209 now carries only the uncontroversial fixes (the dprod sh:namespace correctness bug and header comments).

Options

1. https://www.omg.org/spec/DPROD/dprod/ — the profile and the core owl:Ontology become one multi-typed resource ("the DPROD ontology is the profile that policies declare"). Simple, one canonical IRI.
2. https://www.omg.org/spec/DPROD/contracts/ — align the profile with the contracts ontology it actually profiles (the prof:hasArtifact targets already live under …/contracts/). Keeps profile ≠ ontology.
3. Keep bare https://www.omg.org/spec/DPROD/ — treat it as the umbrella spec IRI; the vocabulary (/dprod/), shapes (/shapes/), and contracts (/contracts/) hang under it.
4. Something else.

Considerations

• Every policy that declares odrl:profile and the SHACL sh:hasValue must agree on whichever value is chosen.
• Backward compatibility: option 1/2 change the value every existing DPROD policy declares.
• Whether the ODRL profile is conceptually the same thing as the OWL ontology.

No code change until this is decided; the implementation is a one-line regex once a target is chosen.