has duty

CURIE: gmeow:hasDuty
IRI: https://blackcatinformatics.ca/gmeow/hasDuty
Category: property
Defined by: gmeow:slices/rights
Box roles: RBox role (What is this?)

Relates a rights statement (or a permission) to a duty / obligation that must be discharged (an odrl:duty / odrl:obligation rule). The domain is the union of gmeow:RightsStatement and gmeow:Permission, so a permission may carry its own duties without being misclassified as a rights statement.

Structure

Property shape: object property; gmeow:RightsStatement | gmeow:Permission -> gmeow:Duty

Practical Pattern

Use gmeow:hasDuty from gmeow:RightsStatement | gmeow:Permission to gmeow:Duty when the relationship itself belongs in the native GMEOW graph.

Example Snippets

These snippets are generated from canonical slice examples and trimmed to the Turtle blocks where this term appears.

Licensed Dataset

Source: slices/core/rights/examples/licensed-dataset.ttl
Examples catalog: open in catalog#example-slices-core-rights-examples-licensed-dataset

# --- Permission to reproduce, but only if the attribution DUTY is discharged.
ex:permReproduce a gmeow:Permission ;
    gmeow:ruleAction gmeow:actionReproduce ;
    gmeow:hasDuty    ex:dutyAttribute .

Common Companion Terms

gmeow:Duty

Projects To

Profile	External Targets
`cc`	`cc`
`odrl`	`odrl`, `rdf`

External Equivalences

Equivalent or closely aligned targets: cc, 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:hasDuty`	equivalence	`-`	skos:relatedMatch	cc:requires	`gmeow-rights.sssom.tsv`; `gmeow:eqRights042`; confidence 0.6
`gmeow:hasDuty`	equivalence	`-`	skos:relatedMatch	odrl:duty	`gmeow-rights.sssom.tsv`; `gmeow:eqRights009`; confidence 0.7
`gmeow:hasDuty`	equivalence	`-`	skos:closeMatch	odrl:obligation	`gmeow-rights.sssom.tsv`; `gmeow:eqRights008`; confidence 0.8

Projection Coverage

Source	Kind	Profile	Predicate/Relation	Target	Evidence
`gmeow:hasDuty`	projection	`cc`	projects to / <=	cc:Attribution, cc:requires	`gmeow:mapCcRequiresAttribution`; confidence 0.8; lossy: the duty's assignee, constraints and rule identity drop; CC REL carries only the class-level requirement
`gmeow:hasDuty`	projection	`odrl`	projects to / <=	odrl:Duty, odrl:action, odrl:assignee, odrl:duty, odrl:target, rdf:type	`gmeow:mapOdrlPermissionDuty`; lossy: the permission's own odrl:constraint (e.g. temporal validity) does not propagate to the duty — ODRL 2.2 does not inherit a permission's constraints onto its duties, so the duty's constraint scope must be stated separately on the duty rule
`gmeow:hasDuty`	projection	`odrl`	projects to / <=	odrl:Duty, odrl:action, odrl:assignee, odrl:obligation, odrl:target, rdf:type	`gmeow:mapOdrlDuty`

Usage Advice

Use when

Use to attach a gmeow:Duty — an obligation that must be discharged (attribute, share-alike, retain notice) — to a gmeow:RightsStatement or, more often, to the gmeow:Permission it conditions (the odrl:duty / odrl:obligation link).

Avoid when

Avoid for an allowed or forbidden action (use gmeow:hasPermission / gmeow:hasProhibition) and avoid attaching it to a Prohibition; a prohibition's remedy is gmeow:ruleConsequence, not a duty.

How to use

Mint one gmeow:Duty per obligation, give it a gmeow:ruleAction (e.g. gmeow:actionAttribute), and link it with gmeow:hasDuty on the enclosing permission so the obligation travels with the right it conditions.

Examples

ex:mayReproduce gmeow:hasDuty ex:mustAttribute.

Published Alignment Graph

Alignments

Relation	Target
`closeMatch`	`odrl:obligation`
`relatedMatch`	`cc:requires`
`relatedMatch`	`odrl:duty`