Versioning policy for the Compliance Report Model

While reusing the Compliance Report Model, I noticed three versioning points that may be worth making explicit before wider adoption.

1. Version-specific IRI

The ontology declares owl:versionInfo "0.9.0", but no owl:versionIRI is currently provided, and:

https://w3id.org/force/compliance-report/0.9.0

does not resolve.

Proposal: configure resolvable version-specific W3ID IRIs, and add owl:versionIRI once those redirects exist. The stable report: namespace should remain unchanged for vocabulary terms.

2. Compatibility policy

It would be useful to document how compatibility is determined between releases, e.g.:

• PATCH: editorial/non-semantic changes
• MINOR: backward-compatible additions
• MAJOR: breaking semantic changes

Where appropriate, OWL versioning properties such as owl:priorVersion, owl:backwardCompatibleWith, and owl:incompatibleWith could make these relationships explicit.

Existing term IRIs should remain stable and should not be silently repurposed.

3. ODRL dependency

The model currently references the general ODRL namespace and the live formal-semantics draft. It would be useful to state explicitly which ODRL version a release targets (currently ODRL 2.2) and, where relevant, reference a dated/versioned formal-semantics snapshot .rather than a changing editor's draft. That would let consumers tell whether a given release still applies when a future ODRL version relaesers.

Start by inspecting the model metadata containing owl:versionInfo, the W3ID redirect configuration, and the current ODRL references. Confirm the intended ODRL 2.2 target and versioning policy; done means version-specific IRIs resolve, compatibility rules are documented, stable term IRIs remain unchanged, and the dependency reference is versioned or dated.