1 Purpose
This document defines the machine-readable objects, validation rules, and access boundaries for Standards Content Model and Schema within the defined Good Taste Awards standards system.
2 Scope
This document applies to the requirements, decisions, records, controls, and outputs expressly identified under Standards Content Model and Schema. Award scope and exclusions are defined by GTA-STD-100; this document shall not create an additional award dimension. Operational prerequisites identified here affect assessment validity and never constitute product certification.
3 Authority and interpretation
The Data and Publication Custodian owns GTA-DATA-001; the Standards Authority approves it. formal verbs, defined terms, stable requirement identities, policy constants, and generated representations shall be interpreted under GTA-GOV-002, GTA-GOV-005, and the defined registers.
3.1 Registered relationships
| Relationship | Direction | Related document |
|---|---|---|
machine_representation_of | outbound | GTA-GOV-002 |
renders_content_model_of | inbound | GTA-PUB-002 |
governed_by | outbound | GTA-GOV-001 |
4 Requirements
GTA-DATA-001-R001 — Document object
The Data and Publication Custodian shall define identifier, title, version, status, type, language, visibility, owner, authority, and content.
GTA-DATA-001-R002 — Clause object
The Data and Publication Custodian shall define stable anchor, heading, level, formal force, text, parent, and order.
GTA-DATA-001-R003 — Definition object
The Data and Publication Custodian shall define preferred term, meaning, prohibited aliases, owner, and references.
GTA-DATA-001-R004 — Requirement object
The Data and Publication Custodian shall define actor, action, condition, exception, evidence, consequence, and verification.
GTA-DATA-001-R005 — Relationship object
The Data and Publication Custodian shall define source, target, relation type, direction, scope, and validity.
GTA-DATA-001-R006 — Table object
The Data and Publication Custodian shall define caption, columns, rows, header relationships, and responsive rendering.
GTA-DATA-001-R007 — Note and example
The Data and Publication Custodian shall distinguish informative explanation from formal requirement.
GTA-DATA-001-R008 — Asset object
The Data and Publication Custodian shall define identity, alternative text, format, integrity, and use.
GTA-DATA-001-R009 — Navigation object
The Data and Publication Custodian shall define hierarchy, sequence, collection, breadcrumb, and related-content links.
GTA-DATA-001-R010 — Schema validation
The Data and Publication Custodian shall enforce types, required properties, registered authority fields, English authority, and stable identity.
GTA-DATA-001-R011 — Serialization
The Data and Publication Custodian shall support Markdown source, structured representation, reader output, and export without semantic loss.
GTA-DATA-001-R012 — Version relationships
The Data and Publication Custodian shall represent replaces, supersedes, amends, implements, depends on, and cites relationships.
5 Defined content-object model
The source document, machine representation, and reader representation shall preserve the same document identity and formal meaning. Structured objects may add retrieval, integrity, accessibility, or navigation data; they shall not paraphrase a requirement, convert an informative statement into a requirement, or remove a condition attached to a requirement.
| Object class | Stable identity | Required semantic content | confirmed representation |
|---|---|---|---|
| Document | standards document number and semantic version | title, state, authority, language, family, type, visibility, source route, active route, fixed-version route, content integrity value | registered Markdown source and validated document object |
| Clause | document number plus stable anchor | heading, hierarchy level, clause class, formal force, accountable actor where applicable, body, order, and content integrity value | clause object embedded in its document object |
| Requirement | immutable requirement identifier | actor, formal action, defined subject, applicable condition, qualification or exception, required evidence, verification route, and consequence of nonconformity | requirement-class clause and traceability entry |
| Definition | immutable term identifier | preferred English term, defined meaning, owner, status, and applicable reference | defined terminology resource |
| Relationship | source, relationship type, and target | direction, scope, derivation state, and valid endpoint identities | document relationship collection and system relationship resource |
| Table | parent clause identity plus ordinal position | ordered headers, ordered rows, cell text, header relationship, and source Markdown | structured table object with preserved source table in the parent clause |
| Note or example | parent clause identity plus ordinal position | informative label, content, scope, and parent relationship | informative child content; never a requirement object |
| Asset | parent identity plus asset identity | media type, alternative text, integrity value, use, and access class | separately addressable asset referenced from a clause |
| Navigation | target identity and relation | hierarchy, sequence, collection, breadcrumb, and related-content destination | generated navigation data derived from the defined register and relationship resource |
6 Document-object contract
| Property | Cardinality | Defined rule |
|---|---|---|
schema_version | exactly one | identifies the machine contract applied to the object |
id | exactly one | equals the registered standards document number |
title | exactly one | equals the registered authoritative English title |
version | exactly one | uses a three-part semantic version and identifies the fixed representation |
status | exactly one | is active, superseded, or withdrawn |
authoritative_language | exactly one | is en |
family, document_type, formal_status | one each | identify classification without changing the force of individual clauses |
visibility | exactly one | controls the confirmed distribution; a public projection also declares its source visibility |
owner, approval_authority | one each | use registered defined roles |
source_path | exactly one | identifies the registered authoritative source file |
canonical_path | exactly one | identifies the mutable active-version route |
fixed_version_path | exactly one | identifies the immutable version-specific route |
summary | exactly one | provides retrieval context and has no independent formal force |
content_hash | exactly one | is calculated from the complete authoritative source representation |
representation_hash | exactly one | is calculated from the structured object after any confirmed projection and protects that exact representation |
clauses | one or more | preserves source order and contains every defined heading and body block |
relationships | zero or more | contains every effective registered relationship incident to the document |
7 Clause- and requirement-object contract
| Property | Clause rule | Requirement rule |
|---|---|---|
id | document number plus stable anchor | same as clause rule |
anchor | unique within the document and stable for the represented heading | equals the lowercase requirement identifier for an identified requirement |
level | preserves heading hierarchy | preserves requirement heading hierarchy |
heading | preserves authoritative English heading | begins with the immutable requirement identifier |
clause_type | is section | is requirement |
requirement_id | null unless the clause is a requirement | equals the registered requirement identifier |
section_number | records the controlling top-level section where present | may be null where identity is carried by the requirement identifier |
formal_force | is derived from defined formal language | records requirement, prohibition, recommendation, permission, or informative force without altering the text |
actor | may be null | records the defined role expressed in the requirement |
body_markdown | preserves the complete source block | preserves the complete identified requirement block |
tables | contains each parsed table in source order | same as clause rule |
content_hash | is calculated from the complete clause block | same as clause rule |
Each parsed table shall carry a stable table identifier, its ordinal position within the clause, a caption derived from the parent heading unless an explicit caption is present, an ordered header array, and rectangular ordered row arrays. A merged, malformed, or non-rectangular source table shall fail the build rather than be silently normalized.
8 Serialization and semantic equivalence
The registered Markdown file is the authoritative textual source. A generated object is conforming only when its metadata, clause order, headings, identified requirements, tables, relationships, and integrity values can be regenerated deterministically from that source and the defined registries.
An active-route object and its matching fixed-version object shall be byte-equivalent within the same release. A public projection shall retain the source document number and version, identify its public-projection status, and include only content confirmed by the registered projection rule. Removal of restricted content shall not leave a misleading heading, broken cross-reference, or statement whose meaning depends on omitted content.
Schema validation is necessary but not sufficient. Release control shall also verify register agreement, source integrity, unique anchors, requirement sequence, relationship validity, public-field exclusion, fixed-version immutability, and reconstruction of every published clause from its source document.
9 Conformity and records
Conformity with Standards Content Model and Schema requires evidence comprising the schema result, object identity, relationship check, permission event, and reconstruction test. The record for each applicable GTA-DATA-001 requirement shall permit reconstruction without relying on an unrecorded explanation.
Evidence created under GTA-DATA-001 shall use stable identifiers, immutable event sequence numbers, and machine event timestamps. A correction shall be append-only. A nonconformity shall place the affected object in a non-releasable state until its consequence and confirmed disposition are recorded. Role combination remains subject to the mandatory separation rules.