Version Set

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

A first-class information object representing a version family or release lineage — the set of all concrete artifacts that are versions of a common stable entity. A VersionSet is an InformationObject (a kind of Entity) so it can carry identifiers, provenance, and authority links. Examples: the lineage of a software project, the edition chain of a book, the variant family of an email thread, the DOI concept record.

Structure

Subclass of: gmeow:InformationObject

Practical Pattern

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

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#> .

ex:stableChannel a gmeow:VersionSet ; rdfs:label "Stable release channel"@en .

Common Companion Terms

gmeow:InformationObject

External Equivalences

Equivalent or closely aligned targets: doap

Linkages

Generated from the canonical mapping DSL. SSSOM files are the generated public interchange form for term equivalences.

Term Equivalences

Usage Advice

Use when

• Use to name the stable concept-level lineage that concrete versions belong to — the family any individual release, edition, or snapshot is a version of — so memberships can hang off it rather than off a privileged 'latest'.

Avoid when

• Avoid for a single concrete artifact (that is the gmeow:versionMember entity) and avoid collapsing the lineage into one of its versions; the set is the concept, the members are the versions (concept-vs-version distinction).

How to use

• Mint one VersionSet per lineage, carry its identifiers and authority links here, and relate each concrete version to it through a gmeow:VersionMembership rather than by direct typing.

Examples

• ex:gmeowLineage a gmeow:VersionSet.