sts 0.6.7 → 0.6.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 53e7ba614487ea4d658f8292c403c6811255a85affd65ef9f98976ccc32aa426
-  data.tar.gz: a750e10d49eddc0664746e85114c7db000638b0a3e3addc4b352d179bb21684b
+  metadata.gz: 55257a4c0bd11d4374ea655ffdef2d2a51c1e2fe8761cabbe450188065b85cb6
+  data.tar.gz: afe4c91a2e1b739eeffee4d044e8ea03b28774d43146aafdbd2d744d7577880a
 SHA512:
-  metadata.gz: a03cfc08c64cec197ee4a7a88a9ec41f46b3e94a80ea916092444be3419ec8c5aff06af3888094937be86cd7bbd2ed97b1663a688c16ba46650c0c61eed3cd60
-  data.tar.gz: 9ff6274690f18e27d2528497ffa5f4d0b5f3304e2636d276af5503b17318d6c86a090f3eeb583c0e889d26104878d8df9baed1b0d81ea227ed8b8be44e30573c
+  metadata.gz: be6961ce1a6581c1fa6d7a51cb80253a99e01d53fabb31cb3d4feff43f8d87f7a2b283b3fbb8aa07ad31a91e4ac0a634e1bbbcbbf5dce733f45ad93bc77fdfc8
+  data.tar.gz: 9c476be12a1c7d51c9552892c2ad0bd677f16677e10587865d5a127ff20cf1be67b9e241a17e90155845ba704b58b404317cd1292bd138ddd00a182b875cb01e

data/.rubocop_todo.yml

@@ -24,6 +24,7 @@ Layout/LineLength:
     - 'lib/sts/tbx_iso_tml/lang_set.rb'
     - 'lib/sts/tbx_iso_tml/term_type.rb'
     - 'spec/elements/new_elements_spec.rb'
+    - 'spec/iso_sts/schema_validation_spec.rb'
     - 'spec/round_trip/reference_docs_spec.rb'
     - 'spec/spec_helper.rb'
 
@@ -73,6 +74,7 @@ RSpec/DescribeClass:
     - 'spec/fn_namespace_spec.rb'
     - 'spec/mathml_version_spec.rb'
     - 'spec/round_trip/reference_docs_spec.rb'
+    - 'spec/iso_sts/schema_validation_spec.rb'
 
 # Offense count: 1
 # This cop supports safe autocorrection (--autocorrect).
@@ -124,3 +126,4 @@ RSpec/SpecFilePathFormat:
     - 'spec/sts_table_spec.rb'
     - 'spec/iso_sts/iso_sts_spec.rb'
     - 'spec/iso_sts/iso_sts_element_spec.rb'
+    - 'spec/iso_sts/schema_validation_spec.rb'

data/CLAUDE.md

@@ -1,58 +1,84 @@
 # CLAUDE.md
 
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+This file provides guidance to Claude Code (claude.ai/code) for working with code in this repository.
 
 ## Build and Test Commands
 
 ```bash
-# Run tests
+# Run all tests + rubocop (default task)
+bundle exec rake
+
+# Run tests only
 bundle exec rspec
 
-# Run tests with specific file
-bundle exec rspec spec/sts_spec.rb
+# Run a specific spec file
+bundle exec rspec spec/iso_sts/iso_sts_element_spec.rb
 
-# Run RuboCop linting
+# Run rubocop
 bundle exec rubocop
 
-# Run both (default task)
-bundle exec rake
+# Auto-fix linting offenses
+bundle exec rubocop -a
 ```
 
 ## Architecture
 
-This is a Ruby gem for parsing NISO STS (National Information Standards Organization - Science and Technical Standards) XML documents. It uses `lutaml-model` for XML serialization/deserialization.
+sts-ruby is a Ruby gem for parsing and serialising NISO STS, ISOSTS, and
+TBX-ISO-TML XML documents. It uses `lutaml-model` for declarative
+serialisation.
 
-### Namespace Structure
+### Namespace structure
 
 ```
 Sts
-├── NisoSts        # NISO STS elements (lib/sts/niso_sts/)
-│   ├── MmlContent # MathML content elements (autoloaded)
-│   └── Xi, Ali   # Module elements
-├── TbxIsoTml     # TBX ISO TML elements (lib/sts/tbx_iso_tml/)
-├── Mathml        # MathML namespace wrapper
-└── Namespaces    # XML namespace definitions
+├── IsoSts         # ISOSTS v1.1 (frozen legacy, 2013 DTD)
+├── NisoSts        # NISO STS (evolving: 1.0, 1.2)
+├── TbxIsoTml      # TBX-ISO-TML (ISO 30042, shared)
+├── Namespaces     # XML namespace class declarations (TbxNamespace)
+├── Profiles       # ISO/IEC document profile validator
+└── VERSION
 ```
 
-### Key Implementation Patterns
+### Architectural principle: namespace independence
+
+ISOSTS and NISO STS are independent schemas that genuinely diverge.
+Each `Sts::<Namespace>::<Class>` is modelled from its own schema source
+(`reference-docs/isosts-v1/xsd/ISOSTS.xsd` for IsoSts,
+`reference-docs/NISO-STS-extended-1-MathML3-XSD/` for NisoSts). NEVER:
+
+- Alias `IsoSts::<X> = NisoSts::<X>` (couples the namespaces)
+- Create a shared `Sts::Base::<X>` that both inherit from
+- Reuse NisoSts types inside IsoSts or vice versa
+
+TBX is shared (used by both IsoSts and NisoSts hosts), so cross-references
+to `TbxIsoTml::*` are permitted — but each TbxIsoTml class must be a
+true TBX-ISO-TML element, not a JATS/NISO STS element misplaced.
+
+See `TODO.roadmap/00-overview.md` for the prioritised roadmap of remaining
+work.
+
+### MathML host binding
+
+ISOSTS imports `ncbi-mathml2/mathml2.xsd` (MathML 2). NISO STS uses
+MathML 3. TBX-ISO-TML is hosted under either. Bind per host:
 
-**Element Classes** (in `lib/sts/niso_sts/`):
-- Inherit from `Lutaml::Model::Serializable`
-- Define attributes and XML mapping in `xml do ... end` block
-- Use `map_element` to map child elements, `map_content` for text content
-- Use `mixed_content` for elements that contain both text and child elements
+- `IsoSts::*` math attributes → `Mml::V2::Math`
+- `TbxIsoTml::*` math attributes → `Mml::V2::Math` (TBX-in-ISOSTS only)
+- `NisoSts::*` math attributes → `Mml::V3::Math`
+
+### Element class pattern
 
-**Example element structure:**
 ```ruby
 module Sts
-  module NisoSts
+  module IsoSts
     class SomeElement < Lutaml::Model::Serializable
       attribute :id, :string
-      attribute :content, :string
-      attribute :child, ::Sts::NisoSts::ChildElement
+      attribute :content, :string, collection: true
+      attribute :child, ::Sts::IsoSts::ChildElement, collection: true
 
       xml do
         element "some-element"
+        ordered                 # preserve child order on serialise
         map_attribute "id", to: :id
         map_content to: :content
         map_element "child", to: :child
@@ -62,11 +88,55 @@ module Sts
 end
 ```
 
-**Autoload Pattern**: Elements are autoloaded via `lib/sts/niso_sts.rb`. When adding new elements, add autoloads in alphabetical order.
+### Autoload convention
+
+`lib/sts.rb` autoloads top-level namespaces. `lib/sts/<namespace>.rb`
+autoloads every class in that namespace, organised by category with
+leading comments and alphabetical order within each group.
+
+External gems are eager-required at the top of `lib/sts.rb`
+(`require "lutaml/model"`, `require "mml"`). Internal code never uses
+`require_relative` or `require` with internal paths — autoload only.
+Enforced by `spec/anti_patterns_spec.rb`.
+
+### Anti-patterns (forbidden; enforced by spec)
+
+`spec/anti_patterns_spec.rb` runs 9 per-file checks on every `lib/` file:
+
+- `method_missing`, `respond_to_missing?` — forbidden (hides interfaces)
+- `Object.const_get` — forbidden (runtime string lookup)
+- `.send(` — forbidden (bypasses access control)
+- `instance_variable_set` / `instance_variable_get` — forbidden (breaks encapsulation)
+- `respond_to?` type-checks — forbidden (use `is_a?` or redesign so the check isn't needed)
+- Hand-rolled serialization methods on `Serializable` subclasses:
+  `to_h`, `to_hash`, `from_h`, `from_hash`, `to_json`, `from_json`,
+  `serialize`, `deserialize`, `to_xml`, `from_xml` — forbidden
+  (use `attribute` + `mapping`; framework-generated serialisation is correct)
+- `require_relative` in lib/ — forbidden (use autoload)
+- `require` with internal library path — forbidden (use autoload;
+  external gems like `lutaml/model` are allowlisted)
+
+### Schema authority
+
+For any new IsoSts element, generate the attribute list from
+`reference-docs/isosts-v1/xsd/ISOSTS.xsd` directly. Don't copy from
+NisoSts — the schemas disagree on most elements. Attribute-list
+specifications ("X models its configured attribute set") are the
+project's defence against drift, since round-tripping alone cannot prove
+schema conformance.
+
+### Spec patterns
 
-**Bold/Italic Elements**: These use `::Sts::TbxIsoTml::Bold` and `::Sts::TbxIsoTml::Italic` types (not `:string`), enabling proper round-tripping of nested markup.
+- **Attribute-set assertions** — `expect(Foo.attributes.keys).to match_array(%i[id content_type ...])`
+- **Child-type assertions** — `expect(Bar.attributes[:foo].type).to eq(Baz)`
+- **Round-trip tests** — `expect(Foo.to_xml(Foo.from_xml(xml))).to be_xml_equivalent_to(xml)`
+- **Schema-validation tests** — `spec/schema_validation_spec.rb` validates
+  IsoSts output against ISOSTS.xsd directly via Nokogiri::XML::Schema
 
-### Reference Data
+### Reference data
 
-- XSD schema: `reference-docs/NISO-STS-extended-1-MathML3-XSD/`
+- ISOSTS XSD: `reference-docs/isosts-v1/xsd/ISOSTS.xsd`
+- NISO STS XSD: `reference-docs/NISO-STS-extended-1-MathML3-XSD/`
+- TBX schema (under ISOSTS): `reference-docs/isosts-v1/xsd/tbx.xsd`
 - Test fixtures: `spec/fixtures/`
+- TODO roadmap: `TODO.roadmap/`

data/README.adoc

@@ -140,23 +140,26 @@ sts.class.name # => "Sts::IsoSts::Standard"
 
 ==== ISOSTS MathML 2
 
-ISOSTS uses MathML 2 (not MathML 3+ like NISO STS). A custom Ruby implementation is provided in `Sts::IsoSts::Mathml2::*`:
+ISOSTS uses MathML 2 (not MathML 3 like NISO STS). All MathML is provided
+by the mml gem, bound per host:
+
+* `IsoSts::*` math attributes → `Mml::V2::Math`
+* `TbxIsoTml::*` math attributes → `Mml::V2::Math` (TBX-in-ISOSTS only)
+* `NisoSts::*` math attributes → `Mml::V3::Math`
 
 [source,ruby]
 ----
-# Access MathML 2 content
 disp_formula = sts.body.sec.first.disp_formula
-math = disp_formula.math  # => Sts::IsoSts::Mathml2::Math
-
-# MathML 2 elements
-math.id          # => "mml_1"
-math.display     # => "block" or "inline"
+math = disp_formula.math  # => Mml::V2::Math
 
-# Serialized as mml:math
-math.to_xml      # => <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" ...>
+# Round-trip preserves mml: prefix
+disp_formula.to_xml       # => <disp-formula><mml:math ...>...</mml:math></disp-formula>
 ----
 
-Available MathML 2 elements: `Math`, `Mrow`, `Mi`, `Mn`, `Mo`, `Mtext`, `Mspace`, `Msub`, `Msup`, `Msubsup`, `Mfrac`, `Msqrt`, `Mroot`, `Mstyle`, `Menclose`, `Mpadded`, `Mphantom`, `Mtable`, `Mtr`, `Mtd`, `Mlabeledtr`, `Mfenced`, `Semantics`, `Annotation`, `AnnotationXml`
+MathML 2 and 3 share the same XML namespace (`http://www.w3.org/1998/Math/MathML`),
+so `Mml::Namespace` (the mml gem's top-level namespace class) is used
+directly in both `IsoSts::Standard#namespace_scope` and
+`NisoSts::Standard#namespace_scope`.
 
 ==== ISOSTS TBX Terminology
 
@@ -191,6 +194,42 @@ sts = Sts::NisoSts::Standard.from_xml(xml_with_tbx)
 sts = Sts::IsoSts::Standard.from_xml(xml_with_tbx)
 ----
 
+== Architecture principles
+
+=== Namespace independence
+
+`IsoSts`, `NisoSts`, and `TbxIsoTml` are independent schemas that
+genuinely diverge. Each `Sts::<Namespace>::<Class>` is modelled from its
+own schema source — never aliased across namespaces, never sharing base
+classes. The schemas disagree on most elements (e.g., `IsoSts::Fig` has
+`title`/`alternatives` that `NisoSts::Figure` lacks), so sharing types
+would fight the schemas and violate the Open/Closed principle.
+
+=== Anti-pattern enforcement
+
+`spec/anti_patterns_spec.rb` runs 9 per-file checks across `lib/` to
+forbid: `method_missing`, `respond_to_missing?`, `Object.const_get`,
+`.send(`, `instance_variable_set`/`get`, `respond_to?` type-checks,
+hand-rolled serialization methods on `Serializable` subclasses
+(`to_h`, `to_xml`, `from_xml`, etc.), `require_relative`, and
+internal `require`. See `CLAUDE.md` for the rationale.
+
+=== Schema validation
+
+`spec/schema_validation_spec.rb` validates IsoSts output against the
+canonical `reference-docs/isosts-v1/xsd/ISOSTS.xsd` via
+`Nokogiri::XML::Schema`. Round-tripping alone cannot prove schema
+conformance (a model that invents or drops an attribute still
+round-trips symmetrically); the XSD is the only authoritative check.
+
+=== Autoload convention
+
+`lib/sts.rb` autoloads top-level namespaces. Each namespace's
+`lib/sts/<namespace>.rb` autoloads every class in alphabetical order
+within category groups. External gems (`lutaml/model`, `mml`) are
+eager-required at the top of `lib/sts.rb`; internal code uses autoload
+only — no `require_relative`, no `require "sts/..."`.
+
 == Credits
 
 This gem is developed, maintained and funded by

data/TODO.roadmap/00-overview.md

@@ -23,32 +23,37 @@ noted.
 
 | Track | Subject | Items |
 |---|---|---|
-| A | lutaml-model upstream fixes (file BUGREPORTs, propose patches) | 01, 02 |
-| B | Issue #40 namespace coupling completion | 03, 04 |
-| C | Architectural improvements (DRY, versioning, audit) | 05, 06, 07, 08 |
+| A | lutaml-model upstream analysis (filed as robustness suggestions) | 02 |
+| B | Issue #40 namespace coupling completion | 01 (done), 03 (done), 04 |
+| C | Architectural improvements (DRY, versioning, audit) | 05, 07, 08 |
 | D | Quality, specs, and coverage | 09, 10, 11 |
 
 ## Priority order
 
 The priority is "highest leverage per unit of risk" first:
 
-1. **B.03** (child-bearing roots): model `IsoSts::License`, `IsoSts::TermHead`,
-   `IsoSts::CustomMetaGroup` — closes 5 of 11 issue #40 refs in one PR. Low
-   risk, schema-correct, no recursion.
-2. **A.01, A.02** (lutaml-model BUGREPORTs): pure documentation, zero risk.
-   Unblocks C.06 (MathmlNamespace deduplication).
-3. **C.07** (TbxIsoTml misclassification audit): documents a deferred audit
+1. **B.01** (MathmlNamespace deduplication): DONE 2026-07-27. sts-ruby had
+   two Ruby classes for one XML namespace; deleted one, use `Mml::Namespace`
+   directly. Originally misdiagnosed as a lutaml-model bug — see
+   `01-mathml-namespace-deduplication.md` for the lesson.
+2. **B.03** (child-bearing roots): DONE 2026-07-27. Modelled License,
+   TermHead, CustomMetaGroup closures. Closed 5 of 11 issue #40 refs.
+3. **A.02** (lutaml-model ElementBuilder dispatch): filed as
+   `BUGREPORT.element-builder-dispatch-on-value-class.md` in lutaml-model.
+   Pure documentation; zero risk. **Reframed as a robustness suggestion,
+   not a bug** — sts-ruby's responsibility to use correct types was the
+   actual fix (PR #47 deleted duplicate Fn classes).
+4. **C.07** (TbxIsoTml misclassification audit): documents a deferred audit
    (Xref, TableWrap, etc.) — pattern is already proven by Fn/FnGroup and
    Math removals.
-4. **C.05** (Content MathML unification): 148 parallel classes in
+5. **C.05** (Content MathML unification): 148 parallel classes in
    `lib/sts/niso_sts/mml_content/` — same DRY argument as Presentation
    MathML unification (commit 9e977a5).
-5. **B.04** (recursive roots): the heavy lift. Each root pulls a ~78-element
+6. **B.04** (recursive roots): the heavy lift. Each root pulls a ~78-element
    mutually-recursive core. Requires per-element planning. Most architecturally
    significant.
-6. **C.08** (register versioning): lets ISOSTS v1.1, NISO STS 1.0, NISO STS 1.2
+7. **C.08** (register versioning): lets ISOSTS v1.1, NISO STS 1.0, NISO STS 1.2
    coexist without class-name clashes.
-7. **C.06** (MathmlNamespace deduplication): blocked on A.01.
 8. **D.09, D.10, D.11** (quality, coverage, docs): ongoing.
 
 ## Architectural principles (enforced on all new work)

data/TODO.roadmap/01-mathml-namespace-deduplication.md

@@ -0,0 +1,62 @@
+# 01: MathmlNamespace deduplication (DONE)
+
+**Status**: complete (2026-07-27).
+**Originally tracked as**: `01-lutaml-model-namespace-scope-uri-matching.md`
+(misdiagnosed as a lutaml-model bug) and `06-mathml-namespace-deduplication.md`
+(blocked on the misdiagnosed upstream fix). Merged and completed here.
+
+## Original misdiagnosis
+
+When sts-ruby unified Presentation MathML on the mml gem (commit 9e977a5),
+the `mml:` prefix was dropped on serialization unless both
+`Sts::Namespaces::MathmlNamespace` AND `Mml::Namespace` were listed in
+`IsoSts::Standard#namespace_scope` / `NisoSts::Standard#namespace_scope`.
+
+The initial diagnosis (filed as `BUGREPORT.namespace-scope-uri-matching.md`
+in lutaml-model) blamed `namespace_scope` for matching by class identity
+instead of URI. The proposed fix was to change lutaml-model's matching
+semantics.
+
+## Actual root cause
+
+**sts-ruby had two Ruby classes for one XML namespace.** A namespace IS
+its URI (per Namespaces in XML 1.0). `Sts::Namespaces::MathmlNamespace`
+and `Mml::Namespace` both declared:
+
+```ruby
+uri "http://www.w3.org/1998/Math/MathML"
+prefix_default "mml"
+```
+
+They were the same namespace. The duplication was the smell; the
+"workaround" of listing both was actually papering over the duplication.
+
+The BUGREPORT was retracted. The fix is purely sts-ruby's responsibility.
+
+## Fix shipped (2026-07-27)
+
+- Deleted `Sts::Namespaces::MathmlNamespace` from `lib/sts/namespaces.rb`.
+- Replaced `::Sts::Namespaces::MathmlNamespace` with `::Mml::Namespace` in:
+  - `lib/sts/iso_sts/standard.rb`
+  - `lib/sts/niso_sts/standard.rb`
+  - `lib/sts/niso_sts/mml_content.rb` (the Content MathML module — still
+    scheduled for unification per TODO.roadmap/05)
+- Added 4 regression specs asserting `MathmlNamespace` is undefined and
+  `Mml::Namespace` is used directly.
+
+## Verification
+
+- 5153 examples, 0 failures.
+- TBX fixture round-trip preserves `<mml:math>` prefix.
+- NISO STS fixture round-trip preserves `<mml:math>` prefix.
+- `grep -rn "MathmlNamespace" lib/` returns nothing.
+
+## Lesson
+
+When you see a "framework limitation" that requires you to declare
+something twice, the more likely explanation is that you have two
+definitions of the same thing. Namespaces in particular are URI-identified;
+two classes for one URI is a DRY violation, not a framework bug.
+
+Memory updated: `mml-gem-integration-failure` no longer describes the
+`namespace_scope` duplication as a "known smell" — it's resolved.

data/lib/sts/iso_sts/standard.rb

@@ -15,7 +15,7 @@ module Sts
         element "standard"
         ordered
         namespace_scope [
-          ::Sts::Namespaces::MathmlNamespace,
+          ::Mml::Namespace,
           ::Mml::Namespace,
           ::Sts::Namespaces::TbxNamespace,
           ::Lutaml::Xml::W3c::XlinkNamespace,

data/lib/sts/namespaces.rb

@@ -2,11 +2,6 @@
 
 module Sts
   module Namespaces
-    class MathmlNamespace < Lutaml::Xml::Namespace
-      uri "http://www.w3.org/1998/Math/MathML"
-      prefix_default "mml"
-    end
-
     class TbxNamespace < Lutaml::Xml::Namespace
       uri "urn:iso:std:iso:30042:ed-1"
       uri_aliases "urn:iso:std:iso:30042:ed-2"

data/lib/sts/niso_sts/mml_content.rb

@@ -7,7 +7,7 @@ module Sts
       # Content MathML elements share the MathML namespace
       class Object < Lutaml::Model::Serializable
         xml do
-          namespace ::Sts::Namespaces::MathmlNamespace
+          namespace ::Mml::Namespace
         end
       end
 

data/lib/sts/niso_sts/standard.rb

@@ -17,7 +17,7 @@ module Sts
         element "standard"
         ordered
         namespace_scope [
-          ::Sts::Namespaces::MathmlNamespace,
+          ::Mml::Namespace,
           ::Mml::Namespace,
           ::Sts::Namespaces::TbxNamespace,
           ::Lutaml::Xml::W3c::XlinkNamespace,

data/lib/sts/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Sts
-  VERSION = "0.6.7"
+  VERSION = "0.6.9"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sts
 version: !ruby/object:Gem::Version
-  version: 0.6.7
+  version: 0.6.9
 platform: ruby
 authors:
 - Ribose
@@ -107,12 +107,11 @@ files:
 - TODO.finalize/10-audit-other-duplicates.md
 - TODO.finalize/11-strengthen-anti-patterns-spec.md
 - TODO.roadmap/00-overview.md
-- TODO.roadmap/01-lutaml-model-namespace-scope-uri-matching.md
+- TODO.roadmap/01-mathml-namespace-deduplication.md
 - TODO.roadmap/02-lutaml-model-element-builder-dispatch.md
 - TODO.roadmap/03-issue-40-child-bearing-roots.md
 - TODO.roadmap/04-issue-40-recursive-roots.md
 - TODO.roadmap/05-content-mathml-unification.md
-- TODO.roadmap/06-mathml-namespace-deduplication.md
 - TODO.roadmap/07-tbxisotml-misclassification-audit.md
 - TODO.roadmap/08-register-versioning.md
 - TODO.roadmap/09-test-coverage-gaps.md

data/TODO.roadmap/01-lutaml-model-namespace-scope-uri-matching.md

@@ -1,111 +0,0 @@
-# A.01: lutaml-model `namespace_scope` URI-based matching
-
-**Status**: BUGREPORT drafted; sts-ruby fix blocked on upstream.
-**Repo**: `lutaml/lutaml-model`
-**Estimated effort**: small (lutaml-model: ~20 lines + spec; sts-ruby: ~5 lines once landed)
-
-## Problem
-
-`namespace_scope` in `Lutaml::Model::Serializable.xml do … end` currently
-matches namespace classes by **identity** (`==`), not by URI. Two classes
-that declare the same URI/prefix are treated as different namespaces, so a
-parent that lists one cannot satisfy a child that declares the other.
-
-## Real-world symptom in sts-ruby
-
-`Sts::Namespaces::MathmlNamespace` (lib/sts/namespaces.rb) and
-`Mml::Namespace` (the mml gem's top-level namespace class) both encode:
-
-```ruby
-uri "http://www.w3.org/1998/Math/MathML"
-prefix_default "mml"
-```
-
-They are different classes (different `object_id`s). When `Mml::V3::Math` is
-nested inside `Sts::NisoSts::Standard`, the parent's `namespace_scope` lists
-`MathmlNamespace`. The child declares `Mml::Namespace`. Identity comparison
-fails, the `mml:` prefix is dropped on serialization.
-
-The current workaround — listing both classes in `namespace_scope`:
-
-```ruby
-namespace_scope [
-  ::Sts::Namespaces::MathmlNamespace,
-  ::Mml::Namespace,
-  ::Sts::Namespaces::TbxNamespace,
-  ::Lutaml::Xml::W3c::XlinkNamespace,
-]
-```
-
-— is a DRY violation. It documents the lutaml-model limitation rather than
-fixing it. See `lib/sts/iso_sts/standard.rb:18-19` and
-`lib/sts/niso_sts/standard.rb:20-21`.
-
-## Proposed lutaml-model fix
-
-In `Lutaml::Xml::NamespaceScope` (or wherever the membership check lives),
-compare by URI instead of (or in addition to) class identity. The public
-API doesn't change; only the matching semantics do.
-
-```ruby
-# pseudocode
-def includes?(namespace_class)
-  namespaces.any? do |declared|
-    declared.uri == namespace_class.uri
-  end
-end
-```
-
-## Files
-
-- `BUGREPORT.namespace-scope-uri-matching.md` in
-  `~/src/lutaml/lutaml-model/` (this track files it)
-- lutaml-model spec: `spec/lutaml/xml/namespace_scope_spec.rb` — assert that
-  two classes with the same URI are equivalent for `namespace_scope`
-- sts-ruby: remove the duplicated `MathmlNamespace` entry from
-  `IsoSts::Standard` and `NisoSts::Standard` once the upstream fix lands
-
-## Verification
-
-- Reproduction case (currently failing in 0.8.18):
-
-  ```ruby
-  class A < Lutaml::Model::Serializable
-    xml do
-      namespace SomeNs   # uri "urn:test", prefix "t"
-      element "a"
-    end
-  end
-  class B < Lutaml::Model::Serializable
-    xml do
-      namespace OtherNs  # also uri "urn:test", prefix "t" — different class
-      element "b"
-    end
-  end
-  class Parent < Lutaml::Model::Serializable
-    attribute :child, B
-    xml do
-      namespace_scope [SomeNs]
-      map_element "child", to: :child
-    end
-  end
-  # Currently: child's prefix is dropped on serialize.
-  # After fix: child's prefix is preserved (URIs match).
-  ```
-
-## Why not fix in sts-ruby today
-
-Cannot: the duplication is the only way to make `Mml::V3::Math` and
-`Mml::V2::Math` serialize with the `mml:` prefix inside STS Standard
-elements. Removing `MathmlNamespace` without the upstream fix would
-silently drop the prefix on every IsoSts/NisoSts document with MathML
-content.
-
-Track C.06 (MathmlNamespace deduplication) is the sts-ruby cleanup; it
-blocks on this track.
-
-## How to apply
-
-1. File BUGREPORT in `~/src/lutaml/lutaml-model/BUGREPORT.namespace-scope-uri-matching.md`.
-2. Optionally open PR upstream with the fix sketch above.
-3. After upstream lands and sts-ruby bumps its lutaml-model dep, do C.06.

data/TODO.roadmap/06-mathml-namespace-deduplication.md

@@ -1,59 +0,0 @@
-# C.06: MathmlNamespace deduplication
-
-**Status**: blocked on A.01 (lutaml-model namespace_scope URI matching).
-**Estimated effort**: trivial (delete one class, two `namespace_scope`
-entries).
-
-## Problem
-
-`Sts::Namespaces::MathmlNamespace` (lib/sts/namespaces.rb:5-8) and
-`Mml::Namespace` (mml gem's top-level namespace class) both encode:
-
-```ruby
-uri "http://www.w3.org/1998/Math/MathML"
-prefix_default "mml"
-```
-
-Two classes, same URI/prefix. The current `namespace_scope` workaround on
-`IsoSts::Standard` and `NisoSts::Standard` lists both:
-
-```ruby
-namespace_scope [
-  ::Sts::Namespaces::MathmlNamespace,
-  ::Mml::Namespace,
-  ::Sts::Namespaces::TbxNamespace,
-  ::Lutaml::Xml::W3c::XlinkNamespace,
-]
-```
-
-This is the documented smell noted in memory `mml-gem-integration-failure`
-("namespace_scope duplication is a known smell"). It exists because
-lutaml-model's `namespace_scope` matches by class identity, not by URI.
-
-## Plan
-
-Once A.01 lands upstream and sts-ruby has bumped its lutaml-model dep:
-
-1. Delete `Sts::Namespaces::MathmlNamespace` from `lib/sts/namespaces.rb`.
-2. Replace both `namespace_scope` entries with `::Mml::Namespace` only.
-3. Audit any other references to `MathmlNamespace` (likely only
-   `lib/sts/niso_sts/mml_content.rb:10` — but that whole module is
-   being deleted by C.05).
-
-## Verification
-
-- `grep -rn "MathmlNamespace" lib/` returns nothing
-- TBX round-trip fixtures still preserve `<mml:math>` prefix
-- NISO STS fixtures still preserve `<mml:math>` prefix
-- IsoSts fixtures (V2) still preserve `<mml:math>` prefix
-
-## How to apply
-
-- Coordinate with A.01 — file the BUGREPORT first, then either propose the
-  upstream fix or wait for it
-- When the upstream fix is in a released lutaml-model version, bump
-  sts.gemspec and ship this cleanup as a follow-up PR
-
-See also: TODO.sts-refactor/03-namespace-coupling.md "MathML wrapper"
-discussion (now historical — the wrapper itself was deleted in 9e977a5,
-but the namespace duplication remains).