sts 0.5.2 → 0.5.4

data/GAPS.guidelines.iso-sts-ed2.1/10-references.md

@@ -0,0 +1,56 @@
+# Section 10: References
+
+## Overview
+Section 10 covers document-internal references (cross-references) and references to other documents. It details `<xref>` usage with various `@ref-type` values, footnotes, URLs, and supplementary material.
+
+## Element Coverage
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<xref>` | Cross-references | `TbxIsoTml::Xref` | Partial | Missing `@custom-type` attribute; content handling limited |
+| `<fn>` | Footnotes | `NisoSts::Fn` / `TbxIsoTml::Fn` | Supported | Has `@id`, `<label>`, `<p>` |
+| `<fn-group>` | Footnote group (legacy IEC) | `NisoSts::FnGroup` | Supported | In `<back>` |
+| `<ext-link>` | External URLs | `NisoSts::ExtLink` | Supported | Has `@ext-link-type`, `@xlink:href` |
+| `<uri>` | URIs in text | `NisoSts::Uri` | Supported | |
+| `<std>` | Standard references in text | `NisoSts::ReferenceStandard` | Partial | Missing `@content-type`, `@std-id` |
+| `<mixed-citation>` | Non-standard document references | `NisoSts::MixedCitation` | Partial | Missing `@id`, `<break>`, `<uri>` children |
+| `<supplementary-material>` | External supplementary files | `NisoSts::SupplementaryMaterial` | Supported | Has `@xlink:href`, content |
+| `<inline-supplementary-material>` | Inline supplementary reference | `NisoSts::InlineSupplementaryMaterial` | Supported | |
+
+## Attribute Gaps
+
+| Attribute | Parent Element | Guidelines Usage | Modeled | Status |
+|-----------|---------------|-----------------|---------|--------|
+| `@ref-type` | `<xref>` | "sec", "table", "fig", "disp-formula", "bibr", "fn", "table-fn", "app", "list", "abbreviation", "custom" | Yes | Supported |
+| `@rid` | `<xref>` | Target element ID | Yes | Supported |
+| `@custom-type` | `<xref>` | "term-entry", "note", "example" (with `@ref-type="custom"`) | No | **Missing** -- critical for term cross-refs |
+| `@id` | `<xref>` | Element identifier (Sec 3.4) | No | Missing |
+| `@ext-link-type` | `<ext-link>` | "uri" for URLs | Yes | Supported |
+| `@xlink:href` | `<ext-link>` | Actual URL | Yes | Supported |
+| `@id` | `<fn>` | Footnote identifier | Yes | Supported |
+| `@id` | `<mixed-citation>` | Element identifier (Sec 3.4) | No | Missing |
+
+## Cross-Reference Type Values (Sec 10.1.1)
+
+| `@ref-type` Value | Usage | Modeled | Notes |
+|-------------------|-------|---------|-------|
+| "abbreviation" | Cross-ref to abbreviations | Supported (string) | |
+| "app" | Cross-ref to annexes | Supported | |
+| "bibr" | Cross-ref to bibliography | Supported | |
+| "custom" | With `@custom-type` for terms, notes, examples | Partial | `@custom-type` not modeled |
+| "disp-formula" | Cross-ref to formulae | Supported | |
+| "fig" | Cross-ref to figures | Supported | |
+| "fn" | Cross-ref to footnotes | Supported | |
+| "sec" | Cross-ref to sections | Supported | |
+| "table" | Cross-ref to tables | Supported | |
+| "table-fn" | Cross-ref to table footnotes | Supported | |
+| "list" | Cross-ref to list items | Supported | |
+
+## Key Gaps
+- [ ] **CRITICAL**: `TbxIsoTml::Xref` missing `@custom-type` attribute -- required for cross-references to terms (`@custom-type="term-entry"`), notes (`@custom-type="note"`), and examples (`@custom-type="example"`) from outside the terminology section (Sec 9.2.6, 10.1.3)
+- [ ] `TbxIsoTml::Xref` missing `@id` attribute -- listed in Sec 3.4 as needing ID
+- [ ] `NisoSts::MixedCitation` missing `@id` attribute -- listed in Sec 3.4 as needing ID
+- [ ] `NisoSts::MixedCitation` missing `<break>` child -- legacy content has line breaks within citations (B.2.21)
+- [ ] `NisoSts::MixedCitation` missing `<uri>` child -- legacy content has URIs inside citations (B.2.21)
+- [ ] `NisoSts::ReferenceStandard` missing `@content-type` attribute -- used for "uri" references
+- [ ] `NisoSts::ReferenceStandard` missing `<std-id>` child -- IEC references use `<std-id>` inside `<std>` (Sec B.2.20)

data/GAPS.guidelines.iso-sts-ed2.1/annex-a-multilingual.md

@@ -0,0 +1,79 @@
+# Annex A: Multilingual Contents, Translations and Adoptions
+
+## Overview
+Annex A covers the structuring and tagging of multilingual documents, translations, and adoptions of IEC/ISO standards. It specifies the `<adoption>` element structure, metadata handling for derived versions, `@xml:lang` usage on block elements, and TBX terminology considerations during translation.
+
+## Element Coverage
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<adoption>` | Container for adopted standard | `NisoSts::Adoption` | Partial | Has `@id`, `@xml:lang`, `<adoption-front>`, `<back>`, nested `<adoption>`, `<standard>`; missing `<processing-meta>` guidance |
+| `<adoption-front>` | Adoption metadata front matter | `NisoSts::AdoptionFront` | Partial | Inherits from `Front`; maps `iso-meta`, `std-meta`, `sec`; missing `<std-doc-meta>` child |
+| `<standard>` | Original standard inside adoption | `NisoSts::Standard` | Partial | Has `@id`, `@xml:lang`, `<front>`, `<body>`, `<back>`; missing `<processing-meta>` child |
+| `<front>` | Standard front matter | `NisoSts::Front` | Partial | Maps `iso-meta`, `std-meta`, `sec`; missing `<std-doc-meta>` child |
+| `<std-doc-meta>` | Metadata valid for entire document | `NisoSts::StdDocMeta` | Modeled (not mapped) | Class exists but not mapped in `Front` or `AdoptionFront` |
+| `<std-meta>` | Metadata for derived version | `NisoSts::MetadataStd` | Partial | Has `@id`, `@std-meta-type`, extensive metadata children; missing `<abstract>`, `<isbn>`, `<counts>`, `<suppl-type/number/version>`, multiple `<permissions>` |
+| `<iso-meta>` | ISO-specific metadata | `NisoSts::MetadataIso` | Partial | Has standard metadata children; guidelines recommend avoiding `<iso-meta>` in favor of `<std-meta>` |
+| `<processing-meta>` | Table model, TBX model, MathML version | Missing | Missing | **Critical gap** -- contains `@tagset`, `@tbx-tagset`, `@mathml-version`; recommended to keep identical between original and adoption |
+
+## Attribute Gaps
+
+| Attribute | Parent Element | Guidelines Usage | Modeled | Status |
+|-----------|---------------|-----------------|---------|--------|
+| `@xml:lang` | `<adoption>` | Language of adopted content | Yes | Supported |
+| `@xml:lang` | `<standard>` | Language of original standard | Yes | Supported |
+| `@xml:lang` | `<sec>` | Language override for multilingual sections | No | **Missing** -- guidelines say `@xml:lang` should be on "most outer block level element" for multilingual documents |
+| `@xml:lang` | `<body>` | Language override for body content | No | Missing |
+| `@xml:lang` | `<back>` | Language override for back matter | No | Missing |
+| `@xml:lang` | `<p>` | Language override for paragraphs | No | Missing |
+| `@xml:lang` | `<list>` | Language override for lists | No | Missing |
+| `@xml:lang` | `<fig>` | Language override for figures | No | Missing |
+| `@xml:lang` | `<fig-group>` | Language override for figure groups | No | Missing |
+| `@xml:lang` | `<term-sec>` | Language override for term sections | No | Missing |
+| `@xml:lang` | `<disp-formula>` | Language override for formulae | No | Missing |
+| `@xml:lang` | `<tbx:langSet>` | Language of terminology set | Yes | Supported -- has `@xml:lang` as `lang` attribute |
+| `@id` | `<adoption>` | Adoption identifier | Yes | Supported |
+| `@id` | `<standard>` | Standard identifier | Yes | Supported |
+
+## TBX Terminology Translation Considerations (A.3.2)
+
+The guidelines identify TBX elements that may require modification during translation:
+
+| Element | Translation Concern | sts-ruby Model | Status |
+|---------|---------------------|---------------|--------|
+| `<tbx:langSet>` | `@xml:lang` adapted to translation language | `TbxIsoTml::LangSet` | Supported -- `@xml:lang` modeled |
+| `<tbx:grammaticalNumber>` | May need adaptation to target language | `TbxIsoTml::GrammaticalNumber` | Supported |
+| `<tbx:geographicalUsage>` | May need to be added for target language | `TbxIsoTml::GeographicalUsage` | Supported |
+| `<tbx:grammaticalGender>` | May need to be added for translation | `TbxIsoTml::GrammaticalGender` | Supported |
+| `<tbx:example>` | May need adaptation for translation users | `TbxIsoTml::Example` | Supported |
+| `<tbx:partOfSpeech>` | Usually identical but may need adaptation | `TbxIsoTml::PartOfSpeech` | Supported |
+| `<tbx:pronunciation>` | May need to be added for translation | `TbxIsoTml::Pronunciation` | Supported |
+| `<tbx:source>` | May need adaptation or removal | `TbxIsoTml::Source` | Partial -- missing `<std>` child |
+| `<label>` | Preserve original numbering in translation | `NisoSts::Label` | Supported |
+| `<tbx:termEntry>` | Preserve entry structure and IDs | `TbxIsoTml::TermEntry` | Supported |
+
+## Metadata Preservation Rules (A.3.1)
+
+| Rule | sts-ruby Support | Notes |
+|------|-----------------|-------|
+| Original metadata preserved in `<standard>` | Yes | `Standard` has `Front` with `iso-meta`/`std-meta` |
+| Adopting org metadata in `<adoption-front>` `<std-meta>` | Partial | `AdoptionFront` maps `std-meta` but missing `<std-doc-meta>` |
+| `<std-doc-meta>` for document-wide metadata | No (class exists, not wired) | `StdDocMeta` class exists but not referenced from `Front` or `AdoptionFront` |
+| `<processing-meta>` kept identical | No | `<processing-meta>` element not modeled at all |
+| Avoid `<iso-meta>`, `<reg-meta>`, `<nat-meta>` | N/A | Guidelines say avoid these; models exist for `iso-meta` only |
+| Preserve original IDs | Yes | Elements have `@id` attributes |
+| Preserve element tags for identical content | Yes | Round-trip fidelity supported by lutaml-model |
+
+## Key Gaps
+
+- [ ] **CRITICAL**: `<processing-meta>` element not modeled -- recommended to keep identical between original standard and adoption; contains `@tagset`, `@tbx-tagset`, `@mathml-version` attributes (Sec A.3.1)
+- [ ] **CRITICAL**: `NisoSts::Front` and `NisoSts::AdoptionFront` missing `<std-doc-meta>` child -- guidelines say `<std-doc-meta>` contains "metadata valid for the entire document" during adoptions (Sec A.3.1)
+- [ ] **CRITICAL**: `NisoSts::AdoptionFront` inherits from `Front` but only maps `iso-meta`, `std-meta`, `sec` -- missing `<std-doc-meta>` mapping needed for adoption metadata layering
+- [ ] **IMPORTANT**: Key block-level elements missing `@xml:lang` attribute -- multilingual documents need `@xml:lang` on `<sec>`, `<body>`, `<back>`, `<p>`, `<list>`, `<fig>`, `<fig-group>`, `<term-sec>`, `<disp-formula>` to mark language-specific content (Sec A.3.1)
+- [ ] `NisoSts::Section` missing `@xml:lang` attribute -- most critical for multilingual documents where "it is sufficient to provide the @xml:lang on the top level `<sec>` element only" (Sec A.3.1)
+- [ ] `NisoSts::Body` missing `@xml:lang` attribute -- needed for language override at body level
+- [ ] `NisoSts::Paragraph` missing `@xml:lang` attribute -- needed for inline language switching
+- [ ] `NisoSts::List` missing `@xml:lang` attribute -- needed for language-specific lists
+- [ ] `NisoSts::Figure` and `NisoSts::FigGroup` missing `@xml:lang` attribute -- needed for multilingual figure captions
+- [ ] `NisoSts::TermSection` missing `@xml:lang` attribute -- needed for terminology in different languages
+- [ ] `NisoSts::DisplayFormula` missing `@xml:lang` attribute -- needed for multilingual formula notes

data/GAPS.guidelines.niso-sts-v1.0/01-introduction-scope.md

@@ -0,0 +1,27 @@
+# Section 1-3: Introduction, Legal Terms, and General Scope
+
+## Overview
+Covers the maintenance, legal terms, scope, coding guidance, tagging differences between ISO and IEC, formatting conventions, and multilingual document handling.
+
+## Element Coverage
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<standard>` | Root element for all NISO STS documents | `NisoSts::Standard`, `IsoSts::Standard` | ✅ Supported | Both NisoSts and IsoSts variants exist |
+| `@xml:lang` | Language attribute on block-level elements | Mapped as `lang` on Standard, various models | ✅ Supported | Used on `<standard>`, `<title-wrap>`, `<abstract>` etc. |
+| `xmlns:mml` | MathML namespace declaration | `Namespaces::MathmlNamespace` | ✅ Supported | Declared via `namespace_scope` on Standard |
+| `xmlns:tbx` | TBX namespace declaration | `Namespaces::TbxNamespace` | ✅ Supported | Declared via `namespace_scope` on Standard |
+| `xmlns:xlink` | XLink namespace declaration | `Namespaces::XlinkNamespace` | ✅ Supported | Declared via `namespace_scope` on Standard |
+
+## Attribute Gaps
+
+| Attribute | Parent Element | Guidelines Usage | Modeled | Status |
+|-----------|---------------|-----------------|---------|--------|
+| `@dtd-version` | `<standard>` | DTD version identifier | ✅ Mapped on both NisoSts::Standard and IsoSts::Standard | OK |
+| `@specific-use` | `<standard>` | Usage at IsoSts | ✅ Mapped on IsoSts::Standard only | OK -- NisoSts does not have it |
+
+## Key Gaps
+
+- [ ] **No `@xml:lang` on `NisoSts::Standard`**: The NisoSts::Standard maps `lang` but it uses `Lutaml::Xml::W3c::XmlLangType` which should correctly handle `xml:lang`. Verify round-trip fidelity.
+- [ ] **`xmlns` namespace attributes not round-tripped as XML attributes**: The `mml`, `tbx`, `xlink` attributes on `NisoSts::Standard` are declared but mapped through `namespace_scope`, not as individual XML attributes. The guidelines example shows `xmlns:mml="..."` etc. directly on `<standard>`. Verify this serializes correctly.
+- No structural gaps in this section -- it is primarily about conventions.

data/GAPS.guidelines.niso-sts-v1.0/02-document-structure.md

@@ -0,0 +1,100 @@
+# Section 4: Document Structure
+
+## Overview
+Covers the overall document structure: root `<standard>` element, front matter (`<front>`), body (`<body>`), back matter (`<back>`), clauses (`<sec>`), annexes (`<app>`), bibliography (`<ref-list>`), index, and footnotes.
+
+## Element Coverage
+
+### Root and Major Structural Elements
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<standard>` | Root element | `NisoSts::Standard`, `IsoSts::Standard` | ✅ Supported | |
+| `<front>` | Front matter container | `NisoSts::Front`, `IsoSts::Front` | ✅ Supported | |
+| `<body>` | Body content | `NisoSts::Body`, `IsoSts::Body` | ✅ Supported | |
+| `<back>` | Back matter | `NisoSts::Back`, `IsoSts::Back` | ✅ Supported | |
+
+### Front Matter (Section 4.2)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<std-meta>` | Standards organization metadata | `NisoSts::MetadataStd` | ✅ Supported | |
+| `<iso-meta>` | ISO-specific metadata (legacy) | `NisoSts::MetadataIso`, `IsoSts::IsoMeta` | ✅ Supported | Both NisoSts and IsoSts variants |
+| `<reg-meta>` | Regional metadata | `NisoSts::RegMeta`, `IsoSts::RegMeta` | ✅ Supported | |
+| `<nat-meta>` | National metadata | `NisoSts::NatMeta`, `IsoSts::NatMeta` | ✅ Supported | |
+| `<std-doc-meta>` | Document-level metadata | `NisoSts::StdDocMeta` | ✅ Supported | NisoSts only; NOT in IsoSts::Front |
+| `<sec>` (foreword) | Foreword section | `NisoSts::Section` with `sec-type="foreword"` | ✅ Supported | |
+| `<sec>` (introduction) | Introduction section | `NisoSts::Section` with `sec-type="intro"` | ✅ Supported | |
+
+### Clauses (Section 4.3)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<sec>` | Clause/subclause | `NisoSts::Section`, `IsoSts::Sec` | ✅ Supported | |
+| `<label>` | Clause number | `NisoSts::Label`, `IsoSts::Label` | ✅ Supported | |
+| `<title>` | Clause title | `NisoSts::Title`, `IsoSts::Title` | ✅ Supported | |
+| `<p>` | Paragraph text | `NisoSts::Paragraph`, `IsoSts::Paragraph` | ✅ Supported | |
+
+### Back Matter (Section 4.4)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<app-group>` | Annex group container | `NisoSts::AppGroup`, `IsoSts::AppGroup` | ✅ Supported | |
+| `<app>` | Individual annex | `NisoSts::App`, `IsoSts::App` | ✅ Supported | |
+| `<annex-type>` | Annex type label (informative/normative) | `NisoSts::App#annex_type` (string), `IsoSts::AnnexType` | ✅ Supported | |
+| `<ref-list>` (bibliography) | Bibliography | `NisoSts::ReferenceList`, `IsoSts::RefList` | ✅ Supported | |
+| `<index>` | Index element | **MISSING** | ❌ Missing | No `Index` class found in NisoSts or IsoSts |
+| `<index-title-group>` | Index title group | **MISSING** | ❌ Missing | |
+| `<index-div>` | Index division | **MISSING** | ❌ Missing | |
+| `<index-entry>` | Index entry | **MISSING** | ❌ Missing | |
+| `<see-entry>` | See-entry in index | **MISSING** | ❌ Missing | `NisoSts::See` exists but for def-list, not index |
+| `<related-object>` | Related object reference | **MISSING** | ❌ Missing | |
+| `<fn-group>` | Footnote group (IEC legacy) | `NisoSts::FnGroup`, `IsoSts::FnGroup` | ✅ Supported | |
+
+## Attribute Gaps
+
+| Attribute | Parent Element | Guidelines Usage | Modeled | Status |
+|-----------|---------------|-----------------|---------|--------|
+| `@sec-type` | `<sec>` | Clause type (foreword/intro/scope/norm-refs/terms) | ✅ Mapped as `type` in NisoSts, `sec_type` in IsoSts | OK |
+| `@content-type` | `<app>` | inform-annex / normative-annex / informative / normative | ✅ Mapped | OK |
+| `@content-type` | `<ref-list>` | "bibl" for bibliography | ✅ Mapped | OK |
+| `@content-type` | `<ref-list>` (nested) | "norm-refs" for normative references | ✅ Mapped | OK |
+| `@id` | `<sec>` | Section identifiers | ✅ Mapped | OK |
+| `@id` | `<app>` | Annex identifiers | ✅ Mapped | OK |
+| `@id` | `<ref-list>` | Bibliography identifiers | ✅ Mapped | OK |
+
+## NisoSts::Front Gaps
+
+| Feature | Guideline Reference | Status | Notes |
+|---------|-------------------|--------|-------|
+| `<std-doc-meta>` in `<front>` | Section 4.2.2 | ❌ Missing from NisoSts::Front | `StdDocMeta` class exists but is NOT mapped in `NisoSts::Front` -- only `iso_meta`, `std_meta`, and `sec` are mapped |
+| `<std-doc-meta>` in IsoSts::Front | Section 4.2.2 | ❌ Missing | Not present in IsoSts::Front either |
+| Multiple `<std-meta>` elements | Section A.3 | ⚠️ Limited | `NisoSts::Front` maps `std_meta` as single (not collection), but guidelines say multiple instances are allowed for national metadata |
+| `<sec>` in front for Foreword/Introduction | Section 4.2.3, 4.2.4 | ✅ Supported | `NisoSts::Front` maps `sec` as collection |
+
+## NisoSts::Section Content Gaps
+
+| Child Element | Guidelines Usage | In NisoSts::Section | In IsoSts::Sec | Notes |
+|--------------|-----------------|---------------------|----------------|-------|
+| `<code>` | Programming code | ❌ Missing | ❌ Missing | No `Code` class exists in sts-ruby |
+| `<supplementary-material>` | Supplementary materials | ❌ Missing from Section | ❌ Missing | Class exists (`NisoSts::SupplementaryMaterial`) but not mapped as child of Section or IsoSts::Sec |
+| `<normative-note>` | Normative notes | ❌ Missing from Section | ❌ Missing | `NisoSts::NormativeNote` class exists but not mapped in Section; only `non-normative-note` is mapped |
+| `<normative-example>` | Normative examples | ❌ Missing from Section | ❌ Missing | `NisoSts::NormativeExample` class exists but not mapped |
+| `<media>` | Media element | ❌ Missing | ❌ Missing | No `Media` class mapped in Section |
+| `<chem-struct>` | Chemical structure | ❌ Missing | ❌ Missing | `ChemStruct` class exists but not mapped in Section |
+
+## Key Gaps
+
+- [ ] **`<index>` element missing entirely**: No `Index`, `IndexDiv`, `IndexEntry`, `IndexTitleGroup`, `SeeEntry`, or `RelatedObject` classes exist. The guidelines show full index coding (Section 4.4.4) with `<index>`, `<index-title-group>`, `<index-div>`, `<index-entry>`, `<see-entry>`, `<related-object>`. These need to be implemented.
+
+- [ ] **`<std-doc-meta>` not mapped in Front**: The `StdDocMeta` class exists but is not wired into either `NisoSts::Front` or `IsoSts::Front`. Per Section 4.2.2, this element captures document-level metadata.
+
+- [ ] **`NisoSts::Front` lacks `<std-doc-meta>` and multiple `<std-meta>` support**: Guidelines allow multiple `<std-meta>` instances for national metadata. Currently only a single `std_meta` is mapped.
+
+- [ ] **`<code>` element not modeled**: Section 5.12 describes `<code>` with attributes `@id`, `@code-type`, `@code-version`, `@executable`, `@language`, `@language-version`, `@platforms`. No `Code` class exists.
+
+- [ ] **`<supplementary-material>` not available as child of `<sec>`**: Used in IEC forewords for interpretation sheets and software supplements (Section on IEC ISH). Class exists but not wired into Section.
+
+- [ ] **`<normative-note>` and `<normative-example>` not in Section**: Classes exist (`NisoSts::NormativeNote`, `NisoSts::NormativeExample`) but are not mapped as children of `<sec>`. Some clause types require normative notes.
+
+- [ ] **`NisoSts::Back` missing `<index>`**: Index should appear after bibliography and before footnote groups in back matter.

data/GAPS.guidelines.niso-sts-v1.0/03-front-matter.md

@@ -0,0 +1,149 @@
+# Section 4.2: Front Matter (Metadata)
+
+## Overview
+Covers the metadata elements within `<front>`: `<std-meta>`, `<iso-meta>`, `<reg-meta>`, `<nat-meta>`, and `<std-doc-meta>`, along with their child elements for titles, identifiers, dates, permissions, and other metadata.
+
+## Element Coverage
+
+### Metadata Container Elements
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<std-meta>` | `NisoSts::MetadataStd` | ✅ Supported | Primary metadata container |
+| `<iso-meta>` | `NisoSts::MetadataIso` | ✅ Supported | Legacy ISO metadata |
+| `<iso-meta>` | `IsoSts::IsoMeta` | ✅ Supported | IsoSts variant |
+| `<reg-meta>` | `NisoSts::RegMeta`, `IsoSts::RegMeta` | ✅ Supported | |
+| `<nat-meta>` | `NisoSts::NatMeta`, `IsoSts::NatMeta` | ✅ Supported | |
+| `<std-doc-meta>` | `NisoSts::StdDocMeta` | ⚠️ Class exists | Not wired into `NisoSts::Front` or `IsoSts::Front` |
+
+### Title Elements
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<title-wrap>` | `NisoSts::TitleWrap` | ✅ Supported | |
+| `@xml:lang` on `<title-wrap>` | `TitleWrap#lang` | ✅ Supported | Uses `XmlLangType` |
+| `<intro>` | `TitleWrap#intro` (string) | ✅ Supported | |
+| `<main>` | `TitleWrap#main` (string) | ✅ Supported | |
+| `<compl>` | `NisoSts::TitleCompl` | ✅ Supported | Inherits from `TitleFull` |
+| `<full>` | `NisoSts::TitleFull` | ✅ Supported | |
+
+### Identification Elements
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<proj-id>` | `NisoSts::ProjId` | ✅ Supported | In MetadataStd |
+| `<std-ident>` | `NisoSts::StandardIdentification` | ✅ Supported | |
+| `<originator>` | `StandardIdentification#originator` | ✅ Supported | |
+| `<doc-type>` | `StandardIdentification#doc_type` | ✅ Supported | |
+| `<doc-number>` | `StandardIdentification#doc_number` | ✅ Supported | |
+| `<part-number>` | `StandardIdentification#part_number` | ✅ Supported | |
+| `<edition>` | `StandardIdentification#edition` | ✅ Supported | |
+| `<version>` | `StandardIdentification#version` | ✅ Supported | |
+| `<doc-ident>` | `NisoSts::DocumentIdentification` | ✅ Supported | ISO legacy only |
+| `<std-id-group>` | `NisoSts::StdIdGroup` | ✅ Supported | |
+| `<std-id>` | `NisoSts::StdId` | ✅ Supported | With `@std-id-link-type`, `@std-id-type` |
+| `<isbn>` | `NisoSts::Isbn` | ✅ In mixed-citation only | Not in MetadataStd |
+| `<suppl-type>` | `NisoSts::SupplType` | ✅ Class exists | |
+| `<suppl-number>` | `NisoSts::SupplNumber` | ✅ Class exists | |
+| `<suppl-version>` | `NisoSts::SupplVersion` | ✅ Class exists | |
+
+### Organization Elements
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<std-org>` | `NisoSts::StdOrg` | ✅ Supported | |
+| `@std-org-type` | `StdOrg#std_org_type` | ✅ Supported | |
+| `@std-org-role` | `StdOrg#std_org_role` | ✅ Supported | |
+| `<std-org-abbrev>` | `NisoSts::StdOrgAbbrev` | ✅ Supported | |
+| `<std-org-name>` | `NisoSts::StdOrgName` | ✅ Supported | |
+| `<std-org-loc>` | `NisoSts::StdOrgLoc` | ✅ Supported | |
+| `<std-org-group>` | `NisoSts::StdOrgGroup` | ✅ Supported | |
+
+### Reference and Date Elements
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<content-language>` | `MetadataStd#content_language` | ✅ Supported | |
+| `<std-ref>` | `NisoSts::StandardRef` | ✅ Supported | With `@type` |
+| `<doc-ref>` | `MetadataStd#doc_ref` | ✅ Supported | |
+| `<release-date>` | `NisoSts::ReleaseDate` | ✅ Supported | With `@date-type`, `@iso-8601-date` |
+| `<release-version>` | `NisoSts::ReleaseVersion` | ✅ Supported | |
+| `<meta-date>` | `NisoSts::MetaDate` | ✅ Supported | With `@type` |
+| `<pub-date>` | `MetadataStd#pub_date` | ✅ Supported | String type |
+| `<comm-ref>` | `MetadataStd#comm_ref` | ✅ Supported | |
+| `<secretariat>` | `MetadataStd#secretariat` | ✅ Supported | |
+| `<ics>` | `MetadataStd#ics` | ✅ Supported | Collection in MetadataStd |
+| `<page-count>` | `NisoSts::PageCount` | ✅ Supported | With `@count` |
+
+### Cross-Reference and Other Metadata
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<std-xref>` | `NisoSts::StdCrossReference` | ✅ Supported | With `@type` |
+| `<self-uri>` | `NisoSts::SelfUri` | ✅ Supported | |
+| `<custom-meta-group>` | `NisoSts::CustomMetaGroup` | ✅ Supported | |
+| `<custom-meta>` | `NisoSts::CustomMeta` | ✅ Supported | |
+| `<meta-name>` | In `CustomMeta` | ✅ Supported | |
+| `<meta-value>` | In `CustomMeta` | ✅ Supported | |
+| `<meta-note>` | `NisoSts::MetaNote` | ✅ Supported | |
+| `<abstract>` | `NisoSts::Abstract` | ✅ Class exists | Not mapped in MetadataStd |
+
+### Permissions (Section 4.2.2)
+
+| Element | sts-ruby Model | Status | Notes |
+|---------|---------------|--------|-------|
+| `<permissions>` | `NisoSts::Permissions` | ✅ Supported | |
+| `<copyright-statement>` | `Permissions#copyright_statement` (string) | ⚠️ Partial | Guidelines show this can contain `<inline-graphic>` and rich text, but modeled as plain string |
+| `<copyright-year>` | `Permissions#copyright_year` (string) | ✅ Supported | |
+| `<copyright-holder>` | `Permissions#copyright_holder` (string) | ⚠️ Partial | Guidelines show multiple `<copyright-holder>` elements allowed |
+| `<license>` | Not in `NisoSts::Permissions` | ❌ Missing | IEC requires `<license>` with `<license-p>` inside permissions |
+| `<license-p>` | Not in `NisoSts::Permissions` | ❌ Missing | License paragraphs |
+| `<license_ref>` | Not in `NisoSts::Permissions` | ❌ Missing | Referenced in IEC metadata example |
+| `<address>` in license | Not in permissions context | ❌ Missing | Guidelines show `<address>` inside `<license-p>` |
+
+## Attribute Gaps
+
+| Attribute | Parent Element | Guidelines Usage | Modeled | Status |
+|-----------|---------------|-----------------|---------|--------|
+| `@std-meta-type` | `<std-meta>` | Metadata type | ✅ Mapped | OK |
+| `@date-type` | `<release-date>` | Date type (published, vote-start, vote-end) | ✅ Mapped | OK |
+| `@type` | `<std-ref>` | "dated" or "undated" | ✅ Mapped | OK |
+| `@count` | `<page-count>` | Page count value | ✅ Mapped | OK |
+| `@type` | `<meta-date>` | Date type (vote-start, vote-end, stability-date) | ✅ Mapped | OK |
+| `@type` | `<std-xref>` | Cross-reference type (revises, etc.) | ✅ Mapped | OK |
+
+## MetadataStd vs MetadataIso Completeness
+
+| Feature | In MetadataStd | In MetadataIso | Notes |
+|---------|---------------|----------------|-------|
+| Multiple `<title-wrap>` | ✅ Collection | ❌ Single only | Guidelines show multi-language title-wraps |
+| Multiple `<std-ref>` | ✅ Collection | ❌ Single only | Both dated and undated refs needed |
+| Multiple `<release-date>` | ✅ Collection | ❌ Single only | Multiple dates (published, vote-start, etc.) |
+| Multiple `<std-org>` | ✅ Collection | ❌ Not present | |
+| Multiple `<ics>` | ✅ Collection | ❌ Single only | Multiple ICS codes common |
+| Multiple `<std-xref>` | ✅ Collection | ❌ Single only | |
+| `<proj-id>` | ✅ Present | ❌ Missing | Project ID needed |
+| `<release-version>` | ✅ Present | ❌ Missing | DIS/FIS/IS stage indicator |
+| `<std-org-group>` | ✅ Present | ❌ Missing | |
+| `<custom-meta-group>` | ✅ Collection | ❌ Single only | |
+| `<meta-note>` | ✅ Collection | ❌ Not present | |
+| `<abstract>` | ❌ Missing | ❌ Missing | Should be in both |
+| Multiple `<permissions>` | ❌ Single only | ❌ Single only | IEC needs multiple permissions blocks |
+
+## Key Gaps
+
+- [ ] **`<license>` missing from `Permissions`**: IEC guidelines (Section 4.2.2) show `<license>` with `<license-p>` children, including `<address>` inside license paragraphs. `NisoSts::License` and `NisoSts::LicenseP` classes exist but are NOT mapped in `Permissions`.
+
+- [ ] **`<copyright-statement>` modeled as plain string**: The IEC example shows `<copyright-statement>` containing `<inline-graphic>` and rich content. It should be a structured model, not a string.
+
+- [ ] **`<copyright-holder>` should be collection**: Guidelines show multiple `<copyright-holder>` elements (Section 4.2.2 ISO example with ANFIA, FIEV, SMMT, VDA, etc.).
+
+- [ ] **`MetadataIso` has limited collections**: `title_wrap`, `std_ref`, `release_date`, `ics`, `std_xref`, `custom_meta_group` are all single instead of collection. ISO legacy documents may have multiple values.
+
+- [ ] **`<abstract>` not mapped in metadata**: The IEC metadata example (Section A.2) shows `<abstract>` inside `<std-meta>`. Neither `MetadataStd` nor `MetadataIso` maps it.
+
+- [ ] **`<counts>` wrapper not modeled**: IEC metadata shows `<counts><page-count count="149"/></counts>`. Currently `page_count` is directly in metadata, missing the `<counts>` wrapper.
+
+- [ ] **`<std-id-group>` inside `<std-ident>` only**: The IEC example shows `<std-id-group>` with `<std-id>` elements having `@originator` attribute. `StdId` does not have `@originator`.
+
+- [ ] **`<comm-ref>` should be richer**: The IEC example shows `<comm-ref id="id_1215">TC 25</comm-ref>` with an `@id` attribute. Currently modeled as plain string.

data/GAPS.guidelines.niso-sts-v1.0/04-body-content.md

@@ -0,0 +1,209 @@
+# Section 5: Body Content
+
+## Overview
+Covers text content elements used within the body: spaces/punctuation, `<label>`, `<title>`, `<p>`, symbols, `<styled-content>`, notes and examples, lists, text alignment (`<array>`), quotations (`<disp-quote>`), graphics, boxed text, code, preformatted text, and editing instructions.
+
+## Element Coverage
+
+### Text Formatting Elements (Section 5.1)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<sup>` | Superscript | `NisoSts::Sup`, `TbxIsoTml::Sup` | ✅ Supported | |
+| `<sub>` | Subscript | `NisoSts::Sub`, `TbxIsoTml::Sub` (not found) | ✅ Partial | Sup exists in TbxIsoTml but Sub may not |
+| `<italic>` | Italic text | `TbxIsoTml::Italic` | ✅ Supported | |
+| `<bold>` | Bold text | `TbxIsoTml::Bold` | ✅ Supported | |
+| `<underline>` | Underlined text | `NisoSts::Underline` | ✅ Supported | |
+| `<sc>` | Small caps | `NisoSts::Sc` | ✅ Supported | |
+| `<strike>` | Strike-through | `NisoSts::Strike` | ✅ Class exists | |
+| `<monospace>` | Monospaced text | `NisoSts::Monospace` | ✅ Supported | |
+| `<roman>` | Roman (plain) override | `NisoSts::Roman` | ✅ Class exists | Used inside table headers |
+| `<overline>` | Overlined text | `NisoSts::Overline` | ✅ Supported | |
+| `<sans-serif>` | Sans-serif text | `NisoSts::SansSerif` | ✅ Class exists | |
+| `<break/>` | Line break | `NisoSts::Break` | ✅ Supported | |
+
+### Labels and Titles (Section 5.2)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<label>` | Numbers/symbols for display elements | `NisoSts::Label` | ✅ Supported | Mixed content with `<sup>` |
+| `<title>` | Designations of elements | `NisoSts::Title`, `IsoSts::Title` | ✅ Supported | |
+
+### Paragraph (Section 5.3)
+
+| Element/Attr | Guidelines Usage | sts-ruby Model | Status | Notes |
+|-------------|-----------------|---------------|--------|-------|
+| `<p>` | General body text | `NisoSts::Paragraph` | ✅ Supported | Mixed content model |
+| `@id` on `<p>` | Paragraph identifier | ✅ Mapped | OK | |
+| `@style-type` on `<p>` | Alignment/formatting | ✅ Mapped | OK | Values: align-left, align-right, align-center, valign-top, etc. |
+| `@content-type` on `<p>` | Content type (e.g. "dimension") | ❌ Not mapped | Missing | Guidelines Section 6.6.5, 8.4 use `@content-type="dimension"` on `<p>` for unit statements |
+| `@specific-use` on `<p>` | Layout instruction (ISO) | ✅ Mapped | OK | |
+
+### Styled Content (Section 5.5)
+
+| Element/Attr | Guidelines Usage | sts-ruby Model | Status | Notes |
+|-------------|-----------------|---------------|--------|-------|
+| `<styled-content>` | Semantic formatting | `NisoSts::StyledContent` | ✅ Supported | |
+| `@style-type` | Addition/deletion/normal | ✅ Mapped | OK | |
+| `@style` | CSS-style font info | ✅ Mapped | OK | |
+| `@specific-use` | IEC insert/delete | ✅ Mapped | OK | |
+
+### Notes and Examples (Section 5.6)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<non-normative-note>` | Notes in text | `NisoSts::NonNormativeNote` | ✅ Supported | With `@id`, `@content-type`, `<label>`, `<p>`, `<list>` |
+| `<non-normative-example>` | Examples in text | `NisoSts::NonNormativeExample` | ✅ Supported | |
+| `<normative-note>` | Normative notes | `NisoSts::NormativeNote` | ✅ Class exists | Not mapped in Section children |
+| `<normative-example>` | Normative examples | `NisoSts::NormativeExample` | ✅ Class exists | Not mapped in Section children |
+| `@content-type="warning"` on note | Warning/caution/important notes | ✅ Mapped | OK | Section 5.6.2 |
+
+### Lists (Section 5.7)
+
+| Element/Attr | Guidelines Usage | sts-ruby Model | Status | Notes |
+|-------------|-----------------|---------------|--------|-------|
+| `<list>` | Lists | `NisoSts::List` | ✅ Supported | |
+| `@list-type` | List type (bullet, dash, alpha-lower, etc.) | ✅ Mapped | OK | |
+| `@content-type` | Content type | ✅ Mapped | OK | |
+| `<list-item>` | List items | `NisoSts::ListItem` | ✅ Supported | |
+| `<label>` in list-item | Bullet/number | ✅ Supported | OK | |
+| `<p>` in list-item | List item text | ✅ Supported | OK | |
+| Nested `<list>` in list-item | Nested lists | ✅ Supported | OK | |
+
+### Text Alignment / Arrays (Section 5.8)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<array>` | Column-aligned text without borders | `NisoSts::SectionArray` | ✅ Supported | |
+| `@id` on `<array>` | Array identifier | ✅ Mapped | OK | |
+
+### Quotations (Section 5.9)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<disp-quote>` | Block quotations | `NisoSts::DispQuote` | ✅ Supported | With `@id`, `@content-type`, `<label>`, `<p>`, `<attrib>` |
+| `<attrib>` | Attribution for quotes | `NisoSts::Attribution` | ✅ Supported | |
+
+### Graphics (Section 5.10)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<graphic>` | Block graphics | `NisoSts::Graphic` | ✅ Supported | With `@xlink:href` |
+| `<inline-graphic>` | Inline graphics | `NisoSts::InlineGraphic` | ✅ Supported | Rich attribute set |
+| `@xlink:href` on `<graphic>` | File reference | ✅ Mapped | OK | |
+| `<object-id>` in `<graphic>` | Object identifiers | ✅ Supported | OK | |
+
+### Boxed Text (Section 5.11)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<boxed-text>` | Boxed/guidance text | `NisoSts::BoxedText` | ✅ Supported | With `@content-type="foreign-source"`, `@position`, `@orientation` |
+| `<caption>` in boxed-text | Box heading | ✅ Supported | OK | |
+
+### Code (Section 5.12)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<code>` | Programming code | ❌ Missing | No `Code` class | Guidelines list attributes: `@id`, `@code-type`, `@code-version`, `@executable`, `@language`, `@language-version`, `@platforms` |
+
+### Preformatted Text (Section 5.13)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<preformat>` | ASCII art, error messages | `NisoSts::Preformat` | ✅ Supported | With `@xml:space`, `@language`, `@preformat-type` |
+
+### Editing Instructions (Section 5.14)
+
+| Element | Guidelines Usage | sts-ruby Model | Status | Notes |
+|---------|-----------------|---------------|--------|-------|
+| `<editing-instruction>` | IEC amendment instructions | `NisoSts::EditingInstruction` | ⚠️ Partial | Has `@id`, `@xml:lang`, `@specific-use`, `<label>` but missing `@content-type` and `<p>` child |
+| `@content-type` on editing-instruction | addition/replacement/deletion/modification | ❌ Not mapped | Missing | Legacy IEC usage |
+| `<p>` in editing-instruction | Instruction text | ❌ Not mapped | Missing | Guidelines show `<p>` children |
+
+## Paragraph Content Gaps
+
+The guidelines show many elements can appear inside `<p>`. Here is what is missing from `NisoSts::Paragraph`:
+
+| Element | In Guidelines `<p>` examples | In Paragraph model | Status |
+|---------|------------------------------|-------------------|--------|
+| `<bold>` | Yes | ✅ Via TbxIsoTml::Bold | OK |
+| `<italic>` | Yes | ✅ Via TbxIsoTml::Italic | OK |
+| `<sup>` | Yes | ✅ | OK |
+| `<sub>` | Yes | ✅ | OK |
+| `<sc>` | Yes | ✅ | OK |
+| `<styled-content>` | Yes | ✅ | OK |
+| `<xref>` | Yes | ✅ | OK |
+| `<std>` | Yes | ✅ | OK |
+| `<ext-link>` | Yes | ✅ | OK |
+| `<uri>` | Yes | ✅ | OK |
+| `<fn>` | Yes | ✅ | OK |
+| `<break>` | Yes | ✅ | OK |
+| `<inline-formula>` | Yes | ✅ | OK |
+| `<inline-graphic>` | Yes | in Paragraph model? | ⚠️ Check -- `<graphic>` is mapped but not `<inline-graphic>` |
+| `<named-content>` | Possible | ❌ Not mapped | `NamedContent` class exists but not in Paragraph |
+| `<strike>` | Possible | ❌ Not mapped | `Strike` class exists but not in Paragraph |
+| `<roman>` | In table headers | ❌ Not mapped | `Roman` class exists but not in Paragraph |
+| `<monospace>` | Yes | ✅ | OK |
+| `<underline>` | Yes | ✅ | OK |
+| `<code>` | Possible in text | ❌ No Code class | Missing |
+| `<email>` | Possible | ❌ Not mapped | `Email` class exists but not in Paragraph |
+| `<target>` | Possible | ❌ Not mapped | Not in Paragraph |
+| `<term>` | In term-display context | ❌ Not mapped | Not in Paragraph |
+
+## NonNormativeNote Content Gaps
+
+| Element | Guidelines Usage | In NonNormativeNote | Status |
+|---------|-----------------|---------------------|--------|
+| `<label>` | NOTE label | ✅ | OK |
+| `<p>` | Note text | ✅ | OK |
+| `<list>` | Notes as lists | ✅ | OK |
+| `<non-normative-note>` | Nested notes | ❌ Not mapped | Guidelines don't show nested but may occur |
+| `<xref>` | Cross-references in notes | ❌ Not mapped | May occur in note text |
+| `<std>` | References in notes | ❌ Not mapped | May occur in note text |
+| `<styled-content>` | Styled text in notes | ❌ Not mapped | May occur |
+| `<fig>` | Figures in notes | ❌ Not mapped | May occur |
+
+## NonNormativeExample Content Gaps
+
+| Element | Guidelines Usage | In NonNormativeExample | Status |
+|---------|-----------------|----------------------|--------|
+| `<label>` | EXAMPLE label | ✅ | OK |
+| `<p>` | Example text | ✅ | OK |
+| `<list>` | Lists in examples | ✅ | OK |
+| `<table-wrap>` | Tables in examples | ✅ | OK |
+| `<non-normative-example>` | Nested examples | ✅ | OK |
+| `<xref>` | Cross-references | ❌ Not mapped | May occur |
+| `<std>` | References | ❌ Not mapped | May occur |
+
+## BoxedText Content Gaps
+
+| Element | Guidelines Usage | In BoxedText | Status |
+|---------|-----------------|-------------|--------|
+| `<caption>` | Box heading | ✅ | OK |
+| `<p>` | Box content | ✅ | OK |
+| `<list>` | Lists in box | ✅ | OK |
+| `<array>` | Column text | ❌ Not mapped | Guidelines list this as valid |
+| `<boxed-text>` | Nested boxed text | ❌ Not mapped | Guidelines list this |
+| `<non-normative-note>` | Notes in box | ❌ Not mapped | Guidelines list this |
+| `<non-normative-example>` | Examples in box | ❌ Not mapped | Guidelines list this |
+| `<disp-formula>` | Formulae in box | ❌ Not mapped | Guidelines list this |
+| `<disp-quote>` | Quotes in box | ❌ Not mapped | Guidelines list this |
+| `<ref-list>` | References in box | ❌ Not mapped | Guidelines list this |
+| `<table-wrap>` | Tables in box | ❌ Not mapped | Guidelines list this |
+| `<fig>` | Figures in box | ❌ Not mapped | Guidelines list this |
+| `<graphic>` | Graphics in box | ❌ Not mapped | Guidelines list this |
+| `<def-list>` | Definition lists | ❌ Not mapped | |
+
+## Key Gaps
+
+- [ ] **`<code>` element completely missing**: Section 5.12 describes this with 7 attributes. No model exists.
+
+- [ ] **`EditingInstruction` incomplete**: Missing `@content-type` attribute (values: addition, replacement, deletion, modification) and `<p>` child element. IEC amendment coding (Section 5.14) relies heavily on this.
+
+- [ ] **`Paragraph` missing `@content-type`**: Used for dimension/unit statements in tables and figures (Section 6.6.5, 8.4).
+
+- [ ] **`BoxedText` severely limited**: Only has `<caption>`, `<label>`, `<p>`, `<preformat>`, `<list>`. Missing: `<array>`, `<boxed-text>`, `<non-normative-note>`, `<non-normative-example>`, `<disp-formula>`, `<disp-quote>`, `<ref-list>`, `<table-wrap>`, `<fig>`, `<graphic>`, `<def-list>` -- all listed as valid children in Section 5.11.
+
+- [ ] **`NonNormativeNote` missing inline elements**: Notes can contain `<xref>`, `<std>`, `<styled-content>`, `<fig>` etc. Currently only supports `<p>`, `<label>`, `<list>`, `<preformat>`, `<boxed-text>`, `<graphic>`, `<array>`.
+
+- [ ] **`Graphic` model is sparse**: Missing `@id`, `@content-type`, `@position`, `@orientation`, `@mimetype`, `@mime-subtype` attributes. Guidelines examples show `<graphic id="fig_1.1">` with sub-figure captions but `Graphic` has no `id` or child `<label>`/`<caption>`.