XML

Document or fragment context

Records whether the input stands alone or requires enclosing namespace, entity or structural context.

1. Is the input a complete XML document or a fragment, and what establishes its boundaries? boundary
2. What XML version and character encoding apply, and do the declaration, byte evidence and transport metadata agree? measurement

Syntax assessment evidence

Records the parser outcome, configuration and locations of structural or character errors.

1. Does the input satisfy the applicable XML well-formedness rules, including nesting, attribute uniqueness and reference syntax? measurement
2. Which parser, configuration and input extent support that assessment, and did processing reach the end? provenance

Expanded name identity

Records expanded names and the context needed to interpret prefixes in markup or vocabulary-defined values.

1. What are the expanded names of relevant elements and attributes, accounting for the fact that a default namespace does not apply to unprefixed attribute names? definition
2. Which attribute or text values represent qualified names under the vocabulary's rules, and which in-scope bindings interpret them? boundary

Content and whitespace significance

Identifies where text, child order and whitespace must survive processing.

1. Which elements contain mixed text and child elements, and what ordering must an extraction or edit preserve? measurement
2. What evidence from xml:space, constraints or vocabulary rules permits whitespace to be preserved, normalised or removed? action

Governing DTD or schema

Records the selected constraint language, resource version and basis for selection.

1. Which DTD, XML Schema, RELAX NG schema or other constraint set governs this use, and how was its authority established? provenance
2. Are DOCTYPE identifiers or schema-location hints accepted, overridden or ignored by the consuming system? action

Qualified conformance result

Associates diagnostics and processing effects with a specific constraint set and run.

1. What validation result and diagnostics were obtained against the identified constraint versions? measurement
2. Which defaults, normalisations or type annotations did processing contribute to the representation available to the agent? provenance
3. Which vocabulary meanings or business rules remain unchecked even if validation succeeds? boundary

External resource dependency map

Separates parser dependencies from optional inclusion, validation and transformation resources.

1. Which external DTDs or entities are referenced, and which additional resources would enabled schema validation, XInclude or transformation stages request? measurement
2. What base URI, applicable xml:base values, resolver rules or catalog mappings determine the effective resource locations? provenance
3. Which resources may be accessed, and what result is required when a dependency is unavailable or refused? action

Bounded parser execution

Records configured controls and distinguishes limit-triggered termination from a proven syntax failure.

1. Are DOCTYPE processing, external entity resolution and entity expansion enabled for this operation? action
2. What limits apply to nesting depth, expanded content size, input size and processing time, and were any reached? measurement

Namespace-aware operation contract

Specifies selection context, transformation dependencies and required postconditions.

1. What query or transformation language version, context node and namespace bindings identify the intended nodes? definition
2. Which content may be changed, and what well-formedness, validation and vocabulary-specific checks must pass afterward? action

Round-trip preservation contract

Records whether lexical choices, comments, processing instructions and signed content constrain output.

1. Must a round trip preserve exact bytes, prefixes, CDATA boundaries, entity spelling, comments or processing instructions, or only specified tree properties? boundary
2. If comparison or signature verification uses canonicalisation, which algorithm, options and selected content govern the result? definition
3. Which serialisation or formatting changes are permitted, and how will the required equivalence be checked? action

Kinds and varieties

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these kinds and varieties hold for the sense of XML this model covers, and on what evidence? provenance

Identifiers and schemes

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these identifiers and schemes hold for the sense of XML this model covers, and on what evidence? provenance

Standards and regulation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these standards and regulation hold for the sense of XML this model covers, and on what evidence? provenance

Real-world use

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these real-world use hold for the sense of XML this model covers, and on what evidence? provenance

Typical measurements

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these typical measurements hold for the sense of XML this model covers, and on what evidence? provenance

Failure modes and hazards

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these failure modes and hazards hold for the sense of XML this model covers, and on what evidence? provenance

Regional variation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these regional variation hold for the sense of XML this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these neighbouring kinds and how to tell them apart hold for the sense of XML this model covers, and on what evidence? provenance