Tag Scheme

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

A namespaced set of tags — a project vocabulary, a personal tag bucket, or a controlled vocabulary. Multi-tenant: many schemes coexist, and a tag may belong to zero or more schemes (gmeow:tagInScheme). The counterpart of skos:ConceptScheme and schema:DefinedTermSet.

Structure

Subclass of: gmeow:InformationObject

Practical Pattern

Use gmeow:TagScheme 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.

Folksonomy

• Source: slices/core/tags/examples/folksonomy.ttl
• Examples catalog: open in catalog#example-slices-core-tags-examples-folksonomy

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: tagging is flat-first, reified on demand ( P4). A bare
# gmeow:hasTag covers "this is tagged X". Tags themselves form a SKOS-style poly-
# hierarchy (gmeow:broaderTag / gmeow:narrowerTag / gmeow:relatedTag) inside a
# gmeow:TagScheme. When the PROVENANCE of a tagging matters — who applied it, in
# which scheme — it is promoted to a reified gmeow:Tagging relator binding tagger
# × tagged × tag × scheme, so a contested or machine-applied tag is auditable.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/tags/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .

# --- A scheme and a small tag hierarchy within it.
ex:scheme a gmeow:TagScheme ; rdfs:label "Research topic keywords"@en .

Named Profile Membership

• Source: slices/core/profiles/examples/named-profile-membership.ttl
• Examples catalog: open in catalog#example-slices-core-profiles-examples-named-profile-membership

@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/profiles/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos:  <http://www.w3.org/2004/02/skos/core#> .



# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example — the Profile meta-pattern in use: a closed descriptor schema
# over an open value vocabulary, and an instance that claims conformance to it.
#
# A consumer declares a self-describing facet for a TAGGING (the reified
# tagger × tagged × tag × scheme relator) WITHOUT minting per-tag subclasses.
# It mints one gmeow:Profile that names (a) the class it applies to (the existing
# gmeow:Tagging), (b) the descriptor properties that constitute the facet, and
# (c) the open value vocabulary those descriptors draw from (the existing
# gmeow:Tag, whose members are individuals, never subclasses — P9). Extension
# happens by adding Tag INDIVIDUALS — each referenced as the value of the
# gmeow:taggingTag descriptor — never by altering the closed descriptor set. A
# concrete Tagging points at the Profile with gmeow:hasProfile, so a consumer
# holding only the data can dereference the Profile and learn the complete
# schema — the self-description that makes "extensible by construction" a
# structure, not a slogan. The example mints no classes of its own (it reuses
# gmeow:Tagging / gmeow:Tag / gmeow:TagScheme), and asserts no Expression-typed
# value, so no P11 frame is required.

# --- The OPEN value vocabulary in use: gmeow:Tag individuals, referenced below
#     as the value of the gmeow:taggingTag descriptor. New tags are added HERE,
#     as data — the descriptor schema above is never touched.
ex:scheme a gmeow:TagScheme ; rdfs:label "Research topic keywords"@en .
ex:tagML a gmeow:Tag ;
    rdfs:label "machine-learning"@en ;
    gmeow:tagInScheme ex:scheme .

Common Companion Terms

gmeow:InformationObject

Projects To

External Equivalences

Equivalent or closely aligned targets: schema, skos

Linkages

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

Term Equivalences

Projection Coverage

Usage Advice

Use when

• Use to bucket tags into a namespace — a personal tag set, a project vocabulary, or a curated controlled vocabulary — so folksonomy and controlled-vocabulary tags can coexist under distinct scheme identities.

Avoid when

• Avoid forcing a tag into exactly one scheme (membership is many-valued via gmeow:tagInScheme) and avoid using a scheme to assert hierarchy — broader/narrower relations live on the tags themselves.

How to use

• Mint the scheme as an individual and link tags to it with gmeow:tagInScheme; a tag may be cross-listed in several schemes, and a Tagging act may name the scheme it was performed under via gmeow:taggingScheme.

Examples

• ex:projectVocab a gmeow:TagScheme; rdfs:label "Project vocabulary"@en.