ODRL Deontic Semantics

ODRL semantically anchors its vocabulary in the three fundamental deontic operators:

• Permission: An action is allowed. The absence of a prohibition does not imply permission.
• Prohibition: An action is forbidden. This is a strong modal constraint that must not be violated.
• Duty: An action is obligatory. A duty is triggered by the exercise of a permission or the fulfillment of a constraint, creating a normative consequence. This explicit separation avoids the ambiguity of simple allow/deny access control lists.

Deontic rules in ODRL are not absolute; they are scoped by Constraints that define the precise context of applicability. These constraints act as logical refinements on the left-hand side of the normative rule:

• Temporal Constraints: Define the interval during which a permission is valid or a duty must be fulfilled (e.g., odrl:dateTime).
• Spatial Constraints: Limit usage to specific geographic jurisdictions or locations.
• State Constraints: Trigger duties based on system or asset states (e.g., odrl:status). This allows for the modeling of complex, conditional norms rather than static rules.

ODRL uniquely models Duty not just as a standalone obligation, but as a consequence of exercising a permission. This implements the semantics of a conditional obligation:

• Compensation Duty: If you play a song (permission), you must pay a royalty (duty).
• Attribution Duty: If you distribute a document (permission), you must credit the author (duty).
• Post-Usage Duty: If you access data (permission), you must delete the local copy within 30 days (duty). This mechanism is critical for encoding the complex value exchanges in digital contracts.

ODRL defines a default precedence logic to resolve normative conflicts between policies originating from different parties or at different levels of specificity:

• Lex Specialis: A more specific permission or prohibition overrides a more general one.
• Directive Priority: Policies can be assigned an explicit odrl:priority value to resolve conflicts deterministically.
• Prohibition Precedence: In the absence of explicit priority, prohibitions typically override permissions to ensure a conservative, fail-safe compliance posture. This provides a predictable algorithmic basis for resolving contradictory rules in a multi-stakeholder environment.

ODRL assigns specific functional roles to parties, which are critical for interpreting the direction of a deontic operator:

• Assigner: The entity that issues the rule and holds the authority to grant the permission or impose the duty.
• Assignee: The entity to whom the rule is directed and who is bound by the obligation or prohibition.
• Target: The digital asset that is the object of the rule. This tripartite structure (Assigner, Assignee, Target) provides the necessary semantic scaffolding to answer 'who owes what to whom' in a machine-readable way.

ODRL is an abstract information model. Its deontic semantics are made computationally rigorous through formal Profiles that bind the model to specific serializations and validation logics:

• ODRL SHACL Profile: Uses Shapes Constraint Language to validate RDF graphs against deontic rules, detecting violations in knowledge bases.
• ODRL XML Schema: Provides a syntactic validation layer for XML-encoded policies.
• Deontic Event Calculus Mapping: Formalizes the lifecycle of an ODRL duty (activated, fulfilled, violated, expired) as state transitions in a temporal logic, enabling automated compliance monitoring.