1 # Common Lisp Topic Maps — Slice 2
3 A working ANSI Common Lisp reader for the first CTM identity/default-name
4 subset, with same-map Topic/Name merging in a minimal TMDM model. HyperDoc
5 remains a possible future client and is neither the codebase nor a dependency. There is no CXTM
6 canonicalizer, association/template implementation or cross-document merge engine.
8 Systems: `topic-maps` (the retained foundation), `topic-maps/tests`,
9 `topic-maps/tmdm`, `topic-maps/ctm`, `topic-maps/ctm/tests` and
10 `topic-maps/ctm/merging-tests`.
11 The core reader/model uses ANSI Common Lisp; the foundation/tooling uses
12 ASDF/UIOP and Python's standard library. No Quicklisp packages are required.
14 Start with [Reading Topic Identity and Merging](docs/reading-topic-merging.md)
15 for the current API, reference replacement, identifier tails and exact subset
16 boundaries. See [Reading the First Five CTM Documents](docs/reading-first-five-ctm-documents.md)
17 for original sources, actual objects, normative clauses, baseline evidence and
18 copy-pasteable DESCRIBE forms. [API and boundaries](docs/slice-1-api-and-boundaries.md)
19 document the accepted Slice 1 baseline; the Slice 2 document supersedes its
20 statements about absent identity tails, merging and immutable Name references.
22 The pinned suite targets the **CTM draft dated 2010-03-31**. Passing it alone
23 does not establish full ISO/IEC 13250-6:2010 conformity.
27 In a new Common Lisp process, with this checkout selected:
31 (asdf:initialize-source-registry
32 '(:source-registry :ignore-inherited-configuration))
33 (asdf:load-asd #p"/Users/rgb/workspace/topic-maps/topic-maps.asd")
34 (asdf:load-system "topic-maps/ctm")
35 (asdf:load-system "topic-maps")
36 (defparameter *corpus* (topic-maps.test-foundation:discover-corpus))
37 (topic-maps.test-foundation:summarize-corpus *corpus*)
38 (topic-maps.test-foundation:select-cases *corpus* :category :invalid)
39 (topic-maps.test-foundation:select-cases *corpus* :id "ctm/in/simple.ctm")
40 (asdf:test-system "topic-maps/tests")
41 (asdf:test-system "topic-maps/ctm/tests")
42 (asdf:test-system "topic-maps/ctm/merging-tests")
43 (topic-maps.test-foundation:write-validation-report
44 *corpus* #p"/tmp/topic-maps-inventory.json")
47 Change only the checkout pathname when using another machine. The case's
48 Document IRI remains independent of that pathname. Records are inspectable
49 Common Lisp structures, with actual source/baseline pathnames and explicit
50 contracts, results, statuses, diagnostics and reviewed clauses.
52 ## Offline verification
55 # SBCL must already be installed. No network is used by this command.
56 TOPIC_MAPS_REPORT=/tmp/topic-maps-validation.json ./scripts/test.sh
59 Set `SBCL=/absolute/path/to/sbcl` if needed. The launcher starts a new process,
60 ignores system/user initialization, clears inherited ASDF source configuration
61 and writes FASLs outside the repository. It runs byte-integrity fixtures,
62 Common Lisp infrastructure checks and an independent JSON-schema/content check
63 when a report pathname is supplied. `nix develop path:.` supplies a minimal,
64 pinned SBCL/Python/Git environment; initial environment provisioning may need
65 network access, while test execution after provisioning does not.
67 The complete upstream corpus is already vendored, unchanged. If absent in a
68 source distribution, acquire it once:
71 python3 scripts/corpus.py acquire
72 python3 scripts/corpus.py verify
75 Acquisition uses the exact commit and archive digest in
76 [corpus-lock.json](references/corpus-lock.json), refuses to merge over existing
77 contents and verifies every file. Verification is offline. Valid CTM inputs
78 are selected only under `ctm/in`, invalid ones only under `ctm/invalid`, and
79 CXTM baselines only under `ctm/baseline`. Auxiliary files are reported separately.
81 ## Current validation and historical foundation
83 The complete pinned corpus remains unchanged: 231 valid CTM inputs, 42 invalid
84 inputs, 231 CXTM baselines and 22 CTM auxiliary files. Sixteen selected semantic
85 cases pass; their imported canonical contracts remain NOT-RUN. Only
86 `ctm/invalid/prefix-undefined.ctm` is PASS under its CTM rejection contract;
87 272 imported contracts remain NOT-RUN. Unsupported constructs and I/O errors
88 cannot count as that required rejection.
90 The full launcher runs the retained 54 foundation checks, two Python integrity
91 fixtures, 123 retained identity checks, 646 merge checks, imported-report validation and selected baseline
92 property evidence. A report path also produces `<path>.semantics.json` with
93 separate model observations, plus `<path>.merging.json` for the new cases.
94 The merge checks include 128 graph/order variants with an independent reachability
95 oracle. Reports are deterministic across the tested SBCL versions and checkout
96 relocation. See [Slice 2 validation](docs/slice-2-validation.md),
97 [imported contracts](reports/slice-1/validation.json) and
98 [semantic observations](reports/slice-1/semantics.json).
100 [Slice 0 inventory](docs/inventory.md), [architecture](docs/architecture.md),
101 [coverage](docs/coverage.md) and [validation](docs/validation.md) remain historical
102 foundation records. Their original report/logs are preserved. Their statements
103 about absent reader/model systems describe Slice 0, not the current branch.
104 Slice 1 is built from `9c83db34eb1ba8091b004433f088056717dbaa7e` on
105 `codex/ctm-slice-1`. Slice 2 starts from the accepted Slice 1a commit
106 `fb60afd548d679d83fd8ec76bc5ff384c1e23e5f` on `codex/ctm-slice-2`.
107 Associations/Roles are not part of this slice; await review before continuing.