Register

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

A social or expressive register — the formality, intimacy, or audience-posture of an expression act (the register/persona design). The OPEN umbrella vocabulary that name registers specialize and that persona expression (norms slice) reuses: the same agent, the same norms, expressed formally in public and intimately in private. Registers are first-class value individuals with their own IRIs, labels, and definitions — never a subclass tree, never a 'primary' (Principle 9). Lives in the names core slice because register-of-address was already core here and the dependency direction (extensions reference core, never the reverse) requires the umbrella below its consumers.

Structure

Subclass of: gufo:QualityValue

Practical Pattern

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

Usage Advice

Use when

• Use as the open umbrella value vocabulary for social/expressive register when a register spans naming AND persona expression — extend it (or its gmeow:NameRegister specialization) with a new individual when a formality or audience-posture is not yet seeded.

Avoid when

• Avoid building a register subclass tree (registers are co-equal value individuals) and avoid a name-only register where the persona-expression sense is meant — reach for the gmeow:NameRegister specialization for name address.

How to use

• Mint each register as an individual under gmeow:Register (or gmeow:NameRegister for name address), give it rdfs:label and skos:definition, and reference it from a usage; never declare one register primary.

Examples

• ex:address gmeow:usageRegister gmeow:registerIntimate.