Atomic Constraint

• CURIE: gmeow:AtomicConstraint
• IRI: https://blackcatinformatics.ca/gmeow/AtomicConstraint
• Category: class
• Defined by: gmeow:slices/rights
• Box roles: TBox role (What is this?)

A single ODRL constraint comparison: a gmeow:leftOperand (the dimension tested), a gmeow:constraintOperator (the comparison), and a gmeow:rightOperand (the value). E.g. leftOperand dateTime, operator lteq, rightOperand 2030-01-01 — 'valid until 2030'.

Structure

Subclass of: gmeow:Constraint

Practical Pattern

Use gmeow:AtomicConstraint as a specialized kind of gmeow:Constraint. Add statement metadata or a standpoint when the assertion needs provenance, confidence, or vantage.

Common Companion Terms

gmeow:Constraint

Usage Advice

Use when

• Use for a single rule-condition comparison — a dimension, an operator, and a value (dateTime ≤ 2030, spatial = EU, count ≤ 5) — the leaf of the ODRL constraint algebra.

Avoid when

• Avoid for a boolean combination of several conditions (use gmeow:LogicalConstraint) and avoid splitting one comparison across triples; an atomic constraint carries exactly one operand/operator/value triple.

How to use

• Mint one AtomicConstraint, set gmeow:leftOperand and gmeow:constraintOperator to values and gmeow:rightOperand (or gmeow:rightOperandReference for an IRI) to the tested value, and attach it with gmeow:ruleConstraint.

Examples

• ex:until2030 a gmeow:AtomicConstraint; gmeow:leftOperand gmeow:leftOpDateTime; gmeow:constraintOperator gmeow:operatorLteq; gmeow:rightOperand "2030-01-01".