Skip to main content
This page specifies how a license revision’s scope is rendered as an ODRL 2.2 policy in JSON-LD, the TLP profile terms the rendering uses, and what the rendering does and does not mean.

Status of a rendering

TLP-ODRL-1. A license server MAY publish an ODRL rendering of a license revision. A rendering MUST be generated from the revision’s scope, MUST carry the revision’s object IRI as its uid and its terms_digest as tlp:termsDigest, and MUST mark every duty that renders a recorded term with "tlp:enforcement": "recorded". When a rendering and the signed terms disagree, the signed terms govern. TLP-ODRL-2. A party MUST NOT treat the result of evaluating an ODRL rendering as a TLP decision. Whether a use may proceed is decided only by a check (Decision semantics).

The TLP profile

A rendering declares the profile https://docs.reflections.ai/standard/interop/odrl and uses the prefix tlp: for https://docs.reflections.ai/standard/interop/odrl#. The profile adds these terms to the ODRL 2.2 vocabulary: Purposes and channels are named the same way, as tlp:purpose_advertising and tlp:channel_social. Each IRI names one field’s value, so audio the modality and audio the channel stay distinct.

Example (informative)

Ridgeline’s license K7Q4M2 from Maya Okafor: image depiction of her studio likeness for advertising, on social media and the web, in the United States and Canada, from 1 October 2026 to 31 March 2027. Reframing, background extension, lighting, text overlay and objects are allowed; the other seven adjustments are not. Outputs carry a brand disclosure, and training is prohibited.

Mapping

TLP-ODRL-3. A rendering MUST map each scope field it renders as this table specifies, and MUST leave out fields the table marks as not rendered. Obligations that a decision carries map to duties in the same way:

Use vocabulary

The TLP values the profile’s IRIs name.

Licenses

License revisions, scope and signed terms.