1 # Common Lisp Topic Maps — Slice 4
3 A working ANSI Common Lisp reader for CTM identity/default-name syntax and
4 unary/binary Associations, with same-map merging of Topics, Names, Associations
5 and Roles in a bounded TMDM model. HyperDoc remains a possible future client
6 and is neither the codebase nor a dependency. Slice 4 adds a pure, independent
7 CXTM canonicalizer for this model. Templates and cross-document merging remain
8 outside the implementation.
10 Systems: `topic-maps` (the retained foundation), `topic-maps/tests`,
11 `topic-maps/tmdm`, `topic-maps/ctm`, `topic-maps/ctm/tests` and
12 `topic-maps/ctm/merging-tests` and `topic-maps/ctm/association-tests`, plus `topic-maps/cxtm` and
13 `topic-maps/cxtm/tests`.
14 The core reader/model uses ANSI Common Lisp; the foundation/tooling uses
15 ASDF/UIOP and Python's standard library. No Quicklisp packages are required.
17 Start with [Reading Canonical Topic Maps](docs/reading-canonical-topic-maps.md)
18 for the CXTM API, normative clauses, base-locator policy and actual byte comparisons.
19 [Reading the First CTM Associations](docs/reading-first-ctm-associations.md)
20 for actual Association/Role items, late Topic merges and current subset boundaries.
21 [Reading Topic Identity and Merging](docs/reading-topic-merging.md)
22 for the current API, reference replacement, identifier tails and exact subset
23 boundaries. See [Reading the First Five CTM Documents](docs/reading-first-five-ctm-documents.md)
24 for original sources, actual objects, normative clauses, baseline evidence and
25 copy-pasteable DESCRIBE forms. [API and boundaries](docs/slice-1-api-and-boundaries.md)
26 document the accepted Slice 1 baseline; the Slice 2 document supersedes its
27 statements about absent identity tails, merging and immutable Name references.
28 The Slice 3 document supersedes historical statements about absent Associations/Roles.
30 The pinned suite targets the **CTM draft dated 2010-03-31**. Passing it alone
31 does not establish full ISO/IEC 13250-6:2010 conformity.
35 In a new Common Lisp process, with this checkout selected:
39 (asdf:initialize-source-registry
40 '(:source-registry :ignore-inherited-configuration))
41 (asdf:load-asd #p"/Users/rgb/workspace/topic-maps/topic-maps.asd")
42 (asdf:load-system "topic-maps/ctm")
43 (asdf:load-system "topic-maps")
44 (defparameter *corpus* (topic-maps.test-foundation:discover-corpus))
45 (topic-maps.test-foundation:summarize-corpus *corpus*)
46 (topic-maps.test-foundation:select-cases *corpus* :category :invalid)
47 (topic-maps.test-foundation:select-cases *corpus* :id "ctm/in/simple.ctm")
48 (asdf:test-system "topic-maps/tests")
49 (asdf:test-system "topic-maps/ctm/tests")
50 (asdf:test-system "topic-maps/ctm/merging-tests")
51 (asdf:test-system "topic-maps/ctm/association-tests")
52 (asdf:test-system "topic-maps/cxtm/tests")
53 (topic-maps.test-foundation:write-validation-report
54 *corpus* #p"/tmp/topic-maps-inventory.json")
57 Change only the checkout pathname when using another machine. The case's
58 Document IRI remains independent of that pathname. Records are inspectable
59 Common Lisp structures, with actual source/baseline pathnames and explicit
60 contracts, results, statuses, diagnostics and reviewed clauses.
62 ## Offline verification
65 # SBCL must already be installed. No network is used by this command.
66 TOPIC_MAPS_REPORT=/tmp/topic-maps-validation.json ./scripts/test.sh
69 Set `SBCL=/absolute/path/to/sbcl` if needed. The launcher starts a new process,
70 ignores system/user initialization, clears inherited ASDF source configuration
71 and writes FASLs outside the repository. It runs byte-integrity fixtures,
72 Common Lisp infrastructure checks and an independent JSON-schema/content check
73 when a report pathname is supplied. `nix develop path:.` supplies a minimal,
74 pinned SBCL/Python/Git environment; initial environment provisioning may need
75 network access, while test execution after provisioning does not.
77 The complete upstream corpus is already vendored, unchanged. If absent in a
78 source distribution, acquire it once:
81 python3 scripts/corpus.py acquire
82 python3 scripts/corpus.py verify
85 Acquisition uses the exact commit and archive digest in
86 [corpus-lock.json](references/corpus-lock.json), refuses to merge over existing
87 contents and verifies every file. Verification is offline. Valid CTM inputs
88 are selected only under `ctm/in`, invalid ones only under `ctm/invalid`, and
89 CXTM baselines only under `ctm/baseline`. Auxiliary files are reported separately.
91 ## Current validation and historical foundation
93 The complete pinned corpus remains unchanged: 231 valid CTM inputs, 42 invalid
94 inputs, 231 CXTM baselines and 22 CTM auxiliary files. Twenty-four selected semantic
95 cases now also pass actual CXTM byte comparisons. These 24 `:CXTM-EQUAL`
96 contracts are PASS, alongside `ctm/invalid/prefix-undefined.ctm` under its specific
97 CTM rejection contract. The remaining 248 imported contracts are NOT-RUN. Unsupported constructs and I/O errors
98 cannot count as that required rejection.
100 The full launcher runs the retained 54 foundation checks, two Python integrity
101 fixtures, 123 retained identity checks, 646 merge checks, 657 Association checks,
102 imported-report validation and selected baseline
103 property evidence, 445 CXTM checks and 16,294 independent Unicode NFC oracle
104 comparisons. The oracle needs Python UCD 15.0 or 15.1 (tables use UCD 15.1.0).
105 A report path also produces `<path>.semantics.json` with
106 separate model observations, plus `<path>.merging.json`, `<path>.associations.json`
107 and `<path>.cxtm.json` (complete actual/expected XML and byte counts).
108 The merge checks include 128 graph/order variants with an independent reachability
109 oracle. Reports are deterministic across the tested SBCL versions and checkout
110 relocation. See [Slice 4 validation](docs/slice-4-validation.md) for current evidence.
111 [Slice 3 validation](docs/slice-3-validation.md),
112 [imported contracts](reports/slice-1/validation.json) and
113 [semantic observations](reports/slice-1/semantics.json).
115 [Slice 0 inventory](docs/inventory.md), [architecture](docs/architecture.md),
116 [coverage](docs/coverage.md) and [validation](docs/validation.md) remain historical
117 foundation records. Their original report/logs are preserved. Their statements
118 about absent reader/model systems describe Slice 0, not the current branch.
119 Slice 1 is built from `9c83db34eb1ba8091b004433f088056717dbaa7e` on
120 `codex/ctm-slice-1`. Slice 2 starts from the accepted Slice 1a commit
121 `fb60afd548d679d83fd8ec76bc5ff384c1e23e5f` on `codex/ctm-slice-2`.
122 Slice 4 starts from `35648c4dcc71e8dc6448b64abcacb438e53d64a2` on
124 Slice 3 starts from accepted `66664dbff6275d60dab1bc6a232fa70f7b916b8c` on
125 `codex/ctm-slice-3`. Await review before continuing to the next slice.