The 44 controls / TS32
TS32 · Structured data
Stable @id values connect the same entities without creating duplicates.
Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.
Control rule version : 0.1.0-draft.19
Reading guide: start with applicability and required evidence, then read expectations together with their limitations. Understand C, NC, NT and NA outcomes · Prepare a dossier
Expectations and evidence
- Required inputs (protocol identifiers)
- structured-data, intent
- When it applies
- Graphs using entity identifiers.
- How to check
- Build the graph and identify unnamed nodes, variable identifiers and duplicates.
- Expectation
- The same entities retain identifiers across the corpus; graph references resolve and duplicates are assessed, without requiring all types named in the legacy grid.
- Evidence to retain
- Archived graph, inventory of present entities and identifiers, assessed references and duplicates.
- Non-applicability
- No relevant graph with identifiers.
- Limitations
- Schema.org defines a vocabulary; interpretation depends on the consumer.
- Outcome clarification
- C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
- Reference scope
- Technical reference; the TSEP acceptance rule remains an editorial proposal.
Atomic rules
This control is documented in the protocol. This version does not yet attach executable atomic rules to it.