version role
- CURIE:
gmeow:versionRole - IRI: https://blackcatinformatics.ca/gmeow/versionRole
- Category: property
- Defined by:
gmeow:slices/versions - Box roles: RBox role (What is this?)
The role or status classification this membership asserts for the member within the set — canonical, variant, latest, stable, LTS, deprecated, yanked, draft, published, revised, collected, withdrawn. NON-FUNCTIONAL: an entity may hold multiple roles from different authorities simultaneously (standpoint-indexed coexistence per Principle 9), and a role may change over time via new memberships rather than overwrite.
Structure
Property shape: object property; gmeow:VersionMembership -> gmeow:VersionRole
Practical Pattern
Use gmeow:versionRole from gmeow:VersionMembership to gmeow:VersionRole 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.
Release Channels
- Source:
slices/core/versions/examples/release-channels.ttl - Examples catalog: open in catalog#example-slices-core-versions-examples-release-channels
# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: versioning as an authority-scoped claim (Principle 10). A
# gmeow:VersionMembership is a reified Observation: it asserts that an entity
# (gmeow:versionMember) belongs to a gmeow:VersionSet with a gmeow:versionRole
# (canonical / stable / LTS / deprecated / yanked …) and a gmeow:versionScale
# (the size of the change), AS CLAIMED BY an authority (gmeow:membershipAuthority
# / gmeow:vantage). Membership is never overwritten: when a release's role
# changes (stable → deprecated), close the old membership's interval or mint a
# fresh one (P10). Here one release is canonical in the stable channel and, later,
# deprecated — both memberships coexist.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex: <https://blackcatinformatics.ca/gmeow/examples/versions/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# --- The membership claim: 1.0.0 is the canonical, major release in the stable
# channel, as asserted by the maintainer.
ex:canonicalMembership a gmeow:VersionMembership ;
gmeow:versionMember ex:release100 ;
gmeow:versionSet ex:stableChannel ;
gmeow:versionRole gmeow:roleCanonical ;
gmeow:versionScale gmeow:scaleMajor ;
gmeow:membershipAuthority ex:maintainer ;
gmeow:vantage ex:maintainer ;
gmeow:membershipInterval ex:canonicalPeriod .
Common Companion Terms
gmeow:VersionMembership, gmeow:VersionRole
Usage Advice
Use when
- Use to record the role or status a membership asserts for its member — latest, stable, deprecated, yanked, and so on — as a standpoint-scoped value rather than an essential type.
Avoid when
- Avoid forcing a single global role per artifact: competing authority roles coexist (Principle 9), so leave it non-functional and mint a new membership when the role changes rather than overwrite.
How to use
- Reference a seeded
gmeow:VersionRoleindividual; carry differing authority opinions as separate memberships and bound a role in time withgmeow:membershipInterval.