has permission

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

Relates a rights statement to a permission it grants (an odrl:permission rule).

Structure

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

Practical Pattern

Use gmeow:hasPermission from gmeow:RightsStatement to gmeow:Permission 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

# --- Promoted form: the deontic rules the flat edge cannot carry.
ex:rights a gmeow:RightsStatement ;
    gmeow:statementAbout ex:dataset ;
    gmeow:hasPermission  ex:permReproduce ;
    gmeow:hasProhibition ex:prohCommercial .

Common Companion Terms

gmeow:RightsStatement, gmeow:Permission

Projects To

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

External Equivalences

Equivalent or closely aligned targets: cc, ma, odrl, schema

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:hasPermission`	equivalence	`-`	skos:relatedMatch	cc:permits	`gmeow-rights.sssom.tsv`; `gmeow:eqRights041`; confidence 0.6
`gmeow:hasPermission`	equivalence	`-`	skos:relatedMatch	ma:hasPermissions	`gmeow-rights.sssom.tsv`; `gmeow:eqRights201`; confidence 0.55
`gmeow:hasPermission`	equivalence	`-`	skos:closeMatch	odrl:permission	`gmeow-rights.sssom.tsv`; `gmeow:eqRights006`; confidence 0.85
`gmeow:hasPermission`	equivalence	`-`	skos:relatedMatch	schema:hasDigitalDocumentPermission	`gmeow-rights.sssom.tsv`; `gmeow:eqRights187`; confidence 0.5

Projection Coverage

Source	Kind	Profile	Predicate/Relation	Target	Evidence
`gmeow:hasPermission`	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:hasPermission`	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:hasPermission`	projection	`odrl`	projects to / <=	odrl:Permission, odrl:action, odrl:assignee, odrl:permission, odrl:target, rdf:type	`gmeow:mapOdrlPermission`

Usage Advice

Use when

Use to attach a gmeow:Permission rule — an action the assignee is allowed to exercise — to a gmeow:RightsStatement (the odrl:permission link).

Avoid when

Avoid for a forbidden action (use gmeow:hasProhibition) or an obligation (use gmeow:hasDuty); a permission's own required duties ride gmeow:hasDuty on the permission, not here.

How to use

Mint one gmeow:Permission per allowed action, give it a gmeow:ruleAction, and link it with gmeow:hasPermission; add gmeow:hasDuty on the permission for conditions like attribution or share-alike.

Examples

ex:photoRights gmeow:hasPermission ex:mayReproduce.

Published Alignment Graph

Alignments

Relation	Target
`closeMatch`	`odrl:permission`
`relatedMatch`	`cc:permits`
`relatedMatch`	`ma:hasPermissions`
`relatedMatch`	`schema:hasDigitalDocumentPermission`