Rule
- CURIE:
gmeow:Rule - IRI: https://blackcatinformatics.ca/gmeow/Rule
- Category: class
- Defined by:
gmeow:slices/rights - Box roles: TBox role (What is this?)
The abstract base of a deontic rule in a rights statement — it binds a regulated gmeow:RightsAction to an optional target asset and assignee. Specialised by gmeow:Permission, gmeow:Prohibition and gmeow:Duty (the ODRL rule trio).
Structure
Subclass of: gmeow:Norm, gufo:Relator
Practical Pattern
Use gmeow:Rule as a specialized kind of gmeow:Norm, gufo:Relator. Add statement metadata or a standpoint when the assertion needs provenance, confidence, or vantage.
Common Companion Terms
External Equivalences
Equivalent or closely aligned targets: odrl
Linkages
Generated from the canonical mapping DSL. SSSOM files are the generated public interchange form for term equivalences.
Term Equivalences
| Source | Kind | Profile | Predicate/Relation | Target | Evidence |
|---|---|---|---|---|---|
gmeow:Rule |
equivalence | - |
skos:closeMatch | odrl:Rule | gmeow-rights.sssom.tsv; gmeow:eqRights010; confidence 0.8 |
Usage Advice
Use when
- Use as the abstract base only when reasoning over any deontic rule regardless of polarity; for a concrete rule mint the specific kind —
gmeow:Permission,gmeow:Prohibition, orgmeow:Duty.
Avoid when
- Avoid typing an instance as a bare
gmeow:Rule(the three concrete kinds are pairwise disjoint and always apply) and avoid encoding the regulated action as a rule subclass — the action is an opengmeow:RightsActionvalue.
How to use
- Type a rule as
Permission/Prohibition/Duty, give it exactly onegmeow:ruleAction, and addgmeow:ruleTarget,gmeow:ruleAssignee, andgmeow:ruleConstraintas needed; the baseRuleaxiom guarantees every rule names an action.
Examples
- ex:rule a
gmeow:Permission;gmeow:ruleActiongmeow:actionUse.