]> dreyeck.freedombox.rocks Git - topic-maps.git/blob - docs/coverage.md
Implement CTM isa and ako with atomic core subject protection
[topic-maps.git] / docs / coverage.md
1 # Coverage and standards traceability
2
3 Three independent questions are recorded separately: specification coverage,
4 corpus evidence and Common Lisp implementation. **CTM parsing/deserialization
5 is implemented for none of these features in Slice 0.** Corpus files provide
6 expected contracts; they are not executed and none is PASS.
7
8 Normative reference: [ISO/IEC 13250-6:2010, consulted CTM text](https://www.isotopicmaps.org/ctm/ctm.html).
9 TMDM semantics refer to the [2006 edition](https://www.isotopicmaps.org/sam/sam-model/2006-06-18/).
10 The corpus targets the **CTM draft dated 2010-03-31**; passing it alone cannot
11 establish full published-edition conformity. Revisions are pinned in inventory.
12
13 ## Reviewed Slice 1 subjects
14
15 Paths in this table are relative to `vendor/cxtm/ctm`; every listed file exists
16 and its contents were inspected. Clause associations were checked against the
17 consulted normative text and are recorded on the corresponding case records.
18 They identify applicable clauses, not exhaustive coverage of those clauses.
19
20 | Feature specified by CTM | Evidence in corpus | Verified normative clauses | Implemented in CL? |
21 | --- | --- | --- | --- |
22 | Local Topic Identifiers | `in/simple.ctm` | [3.3.6](https://www.isotopicmaps.org/ctm/ctm.html#sec-topic-identity), 3.8, 3.2 | No |
23 | Subject Identifiers | `in/subject-identifier.ctm`, `in/topic-subject-identifier.ctm` | 3.3.6; 3.8 or 3.9 respectively | No |
24 | Subject Locators | `in/subject-locator.ctm`, `in/topic-subject-locator.ctm` | 3.3.6; 3.8 or 3.9 respectively | No |
25 | Item Identifiers | `in/item-identifier.ctm`, `in/topic-item-identifier.ctm` | 3.3.6; 3.8 or 3.9 respectively | No |
26 | Simple Topic Names | `in/name.ctm`, `in/name2.ctm` | [3.11](https://www.isotopicmaps.org/ctm/ctm.html#sec-name), 3.8 | No |
27 | Prefix resolution | `in/prefix-duplicate.ctm`, `in/prefix-multiline.ctm`, `invalid/prefix-undefined.ctm` | [3.3.4](https://www.isotopicmaps.org/ctm/ctm.html#sec-creating-iris-from-qnames), [3.16.1](https://www.isotopicmaps.org/ctm/ctm.html#dir-prefix); multiline also 3.3.1 | No |
28 | Document IRI handling | `in/simple.ctm`, `in/subject-identifier-relative.ctm`, `in/subject-locator-relative.ctm`, `in/item-identifier-relative.ctm` | 3.2, [3.3.3](https://www.isotopicmaps.org/ctm/ctm.html#sec-creating-iris), 3.3.6 | No |
29
30 The foundation assigns explicit fixture Document IRIs; that metadata operation
31 is not an implementation of CTM's resolution/deserialization rules.
32
33 ## Other represented features
34
35 Representative inputs were inspected to establish that the corpus includes
36 these constructs. The specification defines them in the indicated sections;
37 individual edge-case mappings and draft/final alignment still require review.
38 These cases keep empty clause lists until that review is done.
39
40 | Corpus feature | Representative input | Relevant section / mapping review | Implemented? |
41 | --- | --- | --- | --- |
42 | Associations and role notation | `in/association-binary.ctm` | [3.13](https://www.isotopicmaps.org/ctm/ctm.html#sec-assoc); detailed case mapping pending | No |
43 | Occurrences | `in/occurrence-string.ctm` | [3.10](https://www.isotopicmaps.org/ctm/ctm.html#sec-occurrence); detailed mapping pending | No |
44 | Variants | `in/variant.ctm` | [3.12](https://www.isotopicmaps.org/ctm/ctm.html#sec-variant); detailed mapping pending | No |
45 | Templates | `in/template-simple.ctm` | [3.14](https://www.isotopicmaps.org/ctm/ctm.html#sec-template), 3.15; detailed mapping pending | No |
46 | Include and mergemap resources | `in/include.ctm`, `in/mergemap.ctm` and their `.sub` files | 3.16.2–3; detailed mapping pending | No |
47 | Wildcards | `in/wildcard.ctm` | 3.3.8; detailed mapping pending | No |
48 | Encoding | `in/encoding-8859-5.ctm` | 3.6 and 3.2; detailed mapping pending | No |
49
50 Additional filename families cover scope, reification, type-instance/subtype
51 shortcuts, numeric/date values, escapes and nested topics. Their clause/case
52 correspondence is explicitly **unreviewed** in this slice. Nothing infers a
53 coverage claim from the prefix of a filename alone.
54
55 ## Known gaps and what Slice 1 needs
56
57 The original `MISSING.txt` is retained; its historical notes overlap some later
58 additions (see inventory). A comprehensive boundary-value matrix, all invalid
59 paths, cross-construct interactions and the 2010 draft/final audit are pending.
60 A canonical baseline proves neither its own correctness nor exhaustive coverage.
61 No canonicalizer, lexer, parser, model or deserializer exists in this project.
62
63 Slice 1 needs an actual reader and the minimal semantic support warranted by
64 its chosen cases. It must address local identifiers, the three explicit identity
65 forms, simple names, prefix binding and explicit Document-IRI resolution.
66 Semantic baselines must not be replaced by success flags or mocked model data.
67 If only a reader exists initially, canonical comparison remains NOT-RUN or
68 UNSUPPORTED as appropriate until a warranted comparison path exists.
69
70 ## First five proposed semantic cases
71
72 1. **`ctm/in/simple.ctm`** — a single local identifier. Establishes a Topic and
73 its Document-IRI-relative item identity without adding names or relations.
74 2. **`ctm/in/subject-identifier.ctm`** — a Topic referenced directly by a
75 Subject Identifier; distinguishes subject identification from local item identity.
76 3. **`ctm/in/subject-locator.ctm`** — the explicit Subject Locator form; keeps
77 that property distinct from a Subject Identifier.
78 4. **`ctm/in/item-identifier.ctm`** — the explicit Item Identifier form; completes
79 the three identity forms without extra topic-tail syntax.
80 5. **`ctm/in/name.ctm`** — a simple name and its canonical representation,
81 extending the first local Topic case with one descriptive assertion.
82
83 Each has a matching original CXTM baseline. They form a small semantic set
84 rather than merely accepted strings. Next come `prefix-multiline.ctm`,
85 `prefix-duplicate.ctm`, `invalid/prefix-undefined.ctm` and the three relative
86 identifier cases. These proposed selections do not change their NOT-RUN status.
87
88 **Ready for Slice 1: Yes.** The reproducible test foundation is available for
89 review. Slice 1 is not started automatically.