lutaml-xsd 1.2.119 → 1.2.120

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 979411b03fc47a999cbae7439637760622d830b441e53b2385f25e61693deb50
-  data.tar.gz: 0d09ae665a0c4932b94dafd18dcf10cf6f13a11762423aa08caa37a6b6d545eb
+  metadata.gz: 4b59d03aedecdb821438f92cc47219b9c2646abbcd15c8d670516d3666a4ff6c
+  data.tar.gz: fa3dd93b5c71b7252d5d803d5f2d458183b2ec55865de56772bf09f08134f680
 SHA512:
-  metadata.gz: d209c20c956edf6f13312484a9b6534e48511f8544417cee88e2553f87da701c40592c5b912e37ec6047f0ab1170f0c0c2676db750e9c61e1a91a066915a633e
-  data.tar.gz: f601737d13efb40cc2d55763de3426bc7b579fb55c91b061f3e1efaa9f88946b6990c7e214461765c9502525d5937a3cd54ad9f85a259dc176bbe4e0437f6cd0
+  metadata.gz: 0eb9db41c3d88183864b85e74c5101977a25a2cde204d032eb3832e0e2b9a082af032059438a79e7a9ee3cd23ec6ebf912ef5f28f14d50c0255763bc02bbd738
+  data.tar.gz: 66c83250de849b695fdb0f4f650240ccc5b896c938862558ce0c6749521dff6f7dae170ead45c91f663621787ebb2b2a1af5bc613c2adbedd1b098459a792afa

data/TODO.conformance.md

@@ -795,6 +795,30 @@ tuple keys, node-set field violations and absent-field rows handled, cross-eleme
   engine-accepting verdicts (already the 1.1 reading). Phase 3
   (assertions/CTA/openContent/override, moxml#460-dependent)
   remains designed, not built.
+- JSON-SCHEMA-EXPORT ROUND (2026-11-14, #133, release pending):
+  the interop item's three parts land — (1) the SPA export action:
+  GET /api/json-schema in ServeCommand (every package schema as its
+  draft-2020-12 document via JsonSchemaExporter) and the
+  "Export JSON Schema" button in the playground toolbar
+  (downloads the bundle); (2) OUR half of the cross-repo golden
+  spec: spec/fixtures/json_schema_golden/t_person.json pins the
+  exporter's output byte-for-byte (a diff is a contract break —
+  lutaml-jsonschema consumes this shape); (3) the docs cross-link
+  (docs/JSON_SCHEMA.adoc "Consumers" + "Serving"). Endpoint
+  verified live (200, draft-2020-12). lutaml-jsonschema's
+  mirror-image spec stays their side (the issue's "say the word"
+  is the owner's call).
+- RIDE-0610 NOTE (2026-11-14): moxml 0.6.10 + leptris 1.9.420.2
+  (the perf-bound release) probed green on the battery and the
+  FULL measure is CONFORMANCE-NEUTRAL: 4669/4696 identical to the
+  1.2.119 ledger (the diff's two "regressions" vs the older
+  comparator are the registered harness-order corrections, not
+  train movement). ADOPTED. moxml#460 is CLOSED but
+  the engine's assertion EVALUATION is not shipped: the facade
+  compiles 1.1 syntax (vc:minVersion + xs:assert) yet accepts
+  assertion-violating instances silently (probe: sum(a) > 0 with
+  a=-5 → no findings); the finding is posted on #460 with the
+  repro — phase 3 stays engine-gated until evaluation lands.
 - SERVE-PLAYGROUND ROUND (2026-11-14, release pending): the
   comprehension pillar's killer feature lands — `lutaml-xsd serve
   PACKAGE.lxr` serves the built SPA plus a JSON validation API.

data/docs/JSON_SCHEMA.adoc

@@ -40,3 +40,22 @@ File.write("schema.json", json)
 
 The exporter targets documentation, tooling interop, and contract
 publication; it is not a validation-equivalence layer.
+
+## Consumers
+
+lutaml-jsonschema consumes this contract: its model is lossless over
+2020-12 (`map_unmapped`), so exporter output — including keys it does
+not model — round-trips verbatim, and the 492-example suite there
+exercises exporter-shaped documents end-to-end. The golden file at
+`spec/fixtures/json_schema_golden/t_person.json` (pinned by the
+exporter spec) is the contract's byte-level anchor on this side; a
+diff there is a contract break. Losses above are prose here and the
+extension-preservation note on the lutaml-jsonschema side — the two
+documents describe the same boundary from each direction.
+
+## Serving
+
+`lutaml-xsd serve PACKAGE.lxr` exposes the export at
+`GET /api/json-schema` — every schema in the package as its
+draft-2020-12 document — and the SPA playground carries an "Export
+JSON Schema" action that downloads it.