{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.tr.xml","code":"thing-q2115","url":"https://ver.cy/models/thing/q2115/","name":"XML","alternateNames":["TEI/XML","Cursor on Target"],"kind":"thing","status":"published","version":"0.1.0-research.1","language":"en","classifiers":{"family":"Thing Registry","category":"Information and virtual systems","entryKind":"thing","plane":"INF","domain":["INF.MED"],"industry":[],"navPath":"","tags":[],"facets":{}},"whatItIs":"XML (Extensible Markup Language) is a W3C-standardized, SGML-derived metalanguage that serializes hierarchical documents and data as Unicode text under a single well-formedness grammar of nested tagged elements, attributes, character data and optional validity constraints (DTD or schema).","purpose":"Enable an AI agent to recognise XML representations, assess their structural and interpretive state, and decide which inspection, validation, transformation or exchange operations are justified.","scope":{"in":["XML document or fragment boundaries, declared version, encoding and well-formedness","Elements, attributes, ordered content, text and namespace-qualified names","DOCTYPE declarations, entity references and external resource dependencies","Validation against identified DTDs or schemas and the limits of that validation","Parsing, querying, transformation, serialisation and XML-specific preservation requirements","Processing restrictions needed to handle untrusted or dependency-bearing XML"],"out":["Business meaning and operational rules of XML vocabularies such as invoice or scientific data formats","The complete models of XML Schema, XPath, XSLT and other associated languages","Parser software installation, implementation internals and service operations","Transport protocols, storage systems and access-control infrastructure","HTML parsing and recovery rules for documents processed as HTML","General cryptographic signature and identity models"],"boundaries":[]},"distinguishingFeatures":["Check whether the representation satisfies XML well-formedness rules, including case-sensitive names, properly nested elements and quoted attribute values; visual resemblance to markup is insufficient.","Distinguish a complete XML document, which has one document element, from a fragment containing multiple elements or text that requires a processing context.","Determine whether content is processed with XML or HTML parsing rules; an HTML-like vocabulary or an XHTML namespace alone does not establish the processing mode.","Check whether identity and order depend on expanded element names, attributes and mixed text content, rather than treating the representation as interchangeable with a JSON object.","Distinguish XML well-formedness from conformance to an identified DTD or schema; successful parsing alone does not establish vocabulary validity."],"structure":{"bundles":[{"id":"syntax-and-document-boundary","name":"Syntax and document boundary","description":"Records what constitutes the XML input and whether its characters form an admissible document or fragment.","layers":[{"id":"input-boundary-and-decoding","name":"Input boundary and decoding","description":"Identifies the input extent, representation form and evidence used to decode it.","findings":[{"id":"document-or-fragment-context","name":"Document or fragment context","description":"Records whether the input stands alone or requires enclosing namespace, entity or structural context.","questions":[{"text":"Is the input a complete XML document or a fragment, and what establishes its boundaries?","id":"document-or-fragment-context-q01","kind":"boundary"},{"text":"What XML version and character encoding apply, and do the declaration, byte evidence and transport metadata agree?","id":"document-or-fragment-context-q02","kind":"measurement"}]}]},{"id":"well-formedness","name":"Well-formedness","description":"Separates successful XML syntax assessment from incomplete processing and vocabulary validation.","findings":[{"id":"syntax-assessment-evidence","name":"Syntax assessment evidence","description":"Records the parser outcome, configuration and locations of structural or character errors.","questions":[{"text":"Does the input satisfy the applicable XML well-formedness rules, including nesting, attribute uniqueness and reference syntax?","id":"syntax-assessment-evidence-q01","kind":"measurement"},{"text":"Which parser, configuration and input extent support that assessment, and did processing reach the end?","id":"syntax-assessment-evidence-q02","kind":"provenance"}]}]}]},{"id":"names-and-content-structure","name":"Names and content structure","description":"Captures XML name identity and the ordered combination of markup and character content.","layers":[{"id":"namespace-bindings","name":"Namespace bindings","description":"Distinguishes local names, namespace names and scoped prefix aliases.","findings":[{"id":"expanded-name-identity","name":"Expanded name identity","description":"Records expanded names and the context needed to interpret prefixes in markup or vocabulary-defined values.","questions":[{"text":"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?","id":"expanded-name-identity-q01","kind":"definition"},{"text":"Which attribute or text values represent qualified names under the vocabulary's rules, and which in-scope bindings interpret them?","id":"expanded-name-identity-q02","kind":"boundary"}]}]},{"id":"ordered-and-mixed-content","name":"Ordered and mixed content","description":"Records element nesting, attributes and text in the order needed for faithful interpretation.","findings":[{"id":"content-and-whitespace-significance","name":"Content and whitespace significance","description":"Identifies where text, child order and whitespace must survive processing.","questions":[{"text":"Which elements contain mixed text and child elements, and what ordering must an extraction or edit preserve?","id":"content-and-whitespace-significance-q01","kind":"measurement"},{"text":"What evidence from xml:space, constraints or vocabulary rules permits whitespace to be preserved, normalised or removed?","id":"content-and-whitespace-significance-q02","kind":"action"}]}]}]},{"id":"constraints-and-vocabulary-contract","name":"Constraints and vocabulary contract","description":"Connects the XML representation to identified structural constraints and vocabulary interpretation.","layers":[{"id":"constraint-authority","name":"Constraint authority","description":"Identifies the governing constraint resources and distinguishes authority from document-supplied hints.","findings":[{"id":"governing-dtd-or-schema","name":"Governing DTD or schema","description":"Records the selected constraint language, resource version and basis for selection.","questions":[{"text":"Which DTD, XML Schema, RELAX NG schema or other constraint set governs this use, and how was its authority established?","id":"governing-dtd-or-schema-q01","kind":"provenance"},{"text":"Are DOCTYPE identifiers or schema-location hints accepted, overridden or ignored by the consuming system?","id":"governing-dtd-or-schema-q02","kind":"action"}]}]},{"id":"validation-and-interpretation","name":"Validation and interpretation","description":"Records validation results and the boundary between checked structure and application meaning.","findings":[{"id":"qualified-conformance-result","name":"Qualified conformance result","description":"Associates diagnostics and processing effects with a specific constraint set and run.","questions":[{"text":"What validation result and diagnostics were obtained against the identified constraint versions?","id":"qualified-conformance-result-q01","kind":"measurement"},{"text":"Which defaults, normalisations or type annotations did processing contribute to the representation available to the agent?","id":"qualified-conformance-result-q02","kind":"provenance"},{"text":"Which vocabulary meanings or business rules remain unchecked even if validation succeeds?","id":"qualified-conformance-result-q03","kind":"boundary"}]}]}]},{"id":"dependencies-and-processing-limits","name":"Dependencies and processing limits","description":"Records XML resource resolution, expansion behaviour and limits on parser work.","layers":[{"id":"resource-resolution","name":"Resource resolution","description":"Identifies resources that particular processing stages may request and how their locations are resolved.","findings":[{"id":"external-resource-dependency-map","name":"External resource dependency map","description":"Separates parser dependencies from optional inclusion, validation and transformation resources.","questions":[{"text":"Which external DTDs or entities are referenced, and which additional resources would enabled schema validation, XInclude or transformation stages request?","id":"external-resource-dependency-map-q01","kind":"measurement"},{"text":"What base URI, applicable xml:base values, resolver rules or catalog mappings determine the effective resource locations?","id":"external-resource-dependency-map-q02","kind":"provenance"},{"text":"Which resources may be accessed, and what result is required when a dependency is unavailable or refused?","id":"external-resource-dependency-map-q03","kind":"action"}]}]},{"id":"expansion-and-resource-budgets","name":"Expansion and resource budgets","description":"Captures entity handling and processing budgets needed to assess whether an operation can complete acceptably.","findings":[{"id":"bounded-parser-execution","name":"Bounded parser execution","description":"Records configured controls and distinguishes limit-triggered termination from a proven syntax failure.","questions":[{"text":"Are DOCTYPE processing, external entity resolution and entity expansion enabled for this operation?","id":"bounded-parser-execution-q01","kind":"action"},{"text":"What limits apply to nesting depth, expanded content size, input size and processing time, and were any reached?","id":"bounded-parser-execution-q02","kind":"measurement"}]}]}]},{"id":"operations-and-preservation","name":"Operations and preservation","description":"Defines how XML may be selected, changed and serialised while retaining the properties required by its use.","layers":[{"id":"selection-and-transformation","name":"Selection and transformation","description":"Records the context and assumptions under which XML queries and edits target the intended content.","findings":[{"id":"namespace-aware-operation-contract","name":"Namespace-aware operation contract","description":"Specifies selection context, transformation dependencies and required postconditions.","questions":[{"text":"What query or transformation language version, context node and namespace bindings identify the intended nodes?","id":"namespace-aware-operation-contract-q01","kind":"definition"},{"text":"Which content may be changed, and what well-formedness, validation and vocabulary-specific checks must pass afterward?","id":"namespace-aware-operation-contract-q02","kind":"action"}]}]},{"id":"serialisation-and-equivalence","name":"Serialisation and equivalence","description":"Distinguishes exact representation preservation from tree-level or application-defined equivalence.","findings":[{"id":"round-trip-preservation-contract","name":"Round-trip preservation contract","description":"Records whether lexical choices, comments, processing instructions and signed content constrain output.","questions":[{"text":"Must a round trip preserve exact bytes, prefixes, CDATA boundaries, entity spelling, comments or processing instructions, or only specified tree properties?","id":"round-trip-preservation-contract-q01","kind":"boundary"},{"text":"If comparison or signature verification uses canonicalisation, which algorithm, options and selected content govern the result?","id":"round-trip-preservation-contract-q02","kind":"definition"},{"text":"Which serialisation or formatting changes are permitted, and how will the required equivalence be checked?","id":"round-trip-preservation-contract-q03","kind":"action"}]}]}]},{"id":"evidence-and-external-alignment","name":"Evidence and external alignment","description":"What the world already says about this thing, gathered so the model can be checked against it.","layers":[{"id":"reported-evidence","name":"Reported evidence","description":"Findings from the breadth pass, kept separate from the structural claims.","findings":[{"id":"evidence-kinds","name":"Kinds and varieties","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these kinds and varieties hold for the sense of XML this model covers, and on what evidence?","id":"evidence-kinds-q01","kind":"provenance"}]},{"id":"evidence-identifiers","name":"Identifiers and schemes","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these identifiers and schemes hold for the sense of XML this model covers, and on what evidence?","id":"evidence-identifiers-q01","kind":"provenance"}]},{"id":"evidence-standards-and-regulation","name":"Standards and regulation","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these standards and regulation hold for the sense of XML this model covers, and on what evidence?","id":"evidence-standards-and-regulation-q01","kind":"provenance"}]},{"id":"evidence-real-world-use","name":"Real-world use","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these real-world use hold for the sense of XML this model covers, and on what evidence?","id":"evidence-real-world-use-q01","kind":"provenance"}]},{"id":"evidence-measurements","name":"Typical measurements","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these typical measurements hold for the sense of XML this model covers, and on what evidence?","id":"evidence-measurements-q01","kind":"provenance"}]},{"id":"evidence-failure-modes-and-hazards","name":"Failure modes and hazards","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these failure modes and hazards hold for the sense of XML this model covers, and on what evidence?","id":"evidence-failure-modes-and-hazards-q01","kind":"provenance"}]},{"id":"evidence-regional-variation","name":"Regional variation","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these regional variation hold for the sense of XML this model covers, and on what evidence?","id":"evidence-regional-variation-q01","kind":"provenance"}]},{"id":"evidence-neighbours","name":"Neighbouring kinds and how to tell them apart","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these neighbouring kinds and how to tell them apart hold for the sense of XML this model covers, and on what evidence?","id":"evidence-neighbours-q01","kind":"provenance"}]}]}]}]},"agentConduct":{"may":["Parse, validate and generate XML documents it is authorized to handle.","Check documents against a declared schema and report well-formedness errors.","Convert XML to other formats while preserving its content and encoding."],"mustNot":["Parse untrusted XML with external entity resolution enabled where it can expose files or systems.","Silently drop or alter elements, attributes or namespaces during conversion.","Present a malformed document as valid.","Overwrite shared configuration or data files in XML without a backup."],"requiresHuman":["Changing XML schemas or configuration files that other systems depend on."]},"ethics":{"considerations":["XML carries records such as contracts, health and government data; silent corruption harms the people in them.","Open, documented formats keep data accessible to everyone over time."],"affectedParties":["Users of the data","Developers and integrators","People described in records"]},"owners":{"steward":"Nobody owns the format; the web standards consortium maintains the specification.","roles":[],"masterSystems":[]},"relations":[{"target":"Q37045","type":"parent","note":"registry parent class"}],"interaction":{"identity":{"applicability":"required","items":["Vercy registry: vr.tr.xml","Wikidata: Q2115 (https://www.wikidata.org/wiki/Q2115)"]},"properties":{"applicability":"not-applicable","items":["Representation boundary: complete document | fragment | unresolved","XML version: 1.0 | 1.1 | unresolved, with declared and effective values distinguished","Encoding evidence: relationships among byte encoding, byte-order mark, XML declaration and transport metadata","Well-formedness assessment: not assessed | well-formed | not well-formed | assessment incomplete","Namespace identity: prefix bindings and expanded names expressed as namespace name plus local name","Content form: empty | text-only | element-only | mixed, recorded per element","Validation assessment: not assessed | valid | invalid | indeterminate, relative to an identified constraint set and processor configuration","External dependencies: referenced DTDs, entities, schemas and processing resources, with resolution status","Maximum element depth: nested element levels, with the document element counted as level 1","Preservation requirement: exact bytes | specified lexical features | specified tree properties | vocabulary-defined meaning"]},"recognition":{"applicability":"optional","items":["Text with nested tags in angle brackets, opened and closed in matching pairs.","Files often beginning with an XML declaration naming the version and encoding."]},"capabilities":{"applicability":"required","items":["Parse a document or context-qualified fragment and report XML errors with locations.","Inspect ordered content and select nodes using explicit namespace bindings.","Validate against an identified, authorised DTD or schema and record diagnostics.","Resolve or refuse external dependencies under an explicit processing policy.","Transform or serialise XML while checking declared preservation requirements.","Compare versions using byte, lexical, tree or vocabulary-aware criteria chosen for the task."]},"hazards":{"applicability":"required","items":["Unsafe parsers can be exploited through external entities or entity expansion.","Encoding mismatches corrupt characters and break data exchange."]},"interfaces":{"applicability":"required","items":["Extensible Markup Language (XML) 1.0, World Wide Web Consortium."]},"context":{"applicability":"required","items":["XML is used to represent structured documents and data for storage, exchange, and automated processing.","It is encountered in configuration files, document formats, publishing workflows, and messages exchanged between software systems.","Schemas and related validation mechanisms let participants check whether a document follows an agreed structure."]}},"sources":[{"title":"Extensible Markup Language (XML) 1.0 (Fifth Edition)","url":"https://www.w3.org/TR/xml/","note":"Normative grammar of well-formedness, DTDs, encodings, entities and the XML 1.0 document type"},{"title":"Extensible Markup Language (XML) 1.1 (Second Edition)","url":"https://www.w3.org/TR/xml11/","note":"The 1.1 edition, including additional name characters and NEL, and why it is a separate kind"},{"title":"Namespaces in XML 1.0 (Third Edition)","url":"https://www.w3.org/TR/xml-names/","note":"Qualified names, xmlns declarations, and namespaced versus non-namespaced XML"},{"title":"XML Media Types (RFC 7303)","url":"https://www.rfc-editor.org/rfc/rfc7303","note":"IANA media types application/xml and text/xml, charset handling, and fragment identifiers"},{"title":"Wikidata item Q2115: XML","url":"https://www.wikidata.org/wiki/Q2115","note":"identity and sense of the item"},{"title":"Wikipedia: XML","url":"https://en.wikipedia.org/wiki/XML","note":"general description of the item"}],"openQuestions":["Does the registry intend XML to cover the format, individual XML artifacts and fragments together, or should artifact instances link to a separately registered document model?","Which XML and Namespaces in XML editions must the catalogue support, including any requirement for XML 1.1?","Which processing features and constraint languages are required in the intended agent environment, and which remain optional extensions?","What default resource-resolution and processing-limit policy applies when XML arrives without a declared processing contract?","Which neighbouring registered models own vocabulary semantics, XML canonicalisation and XML signatures, and how should this model link to them?"],"resources":{"spec":"/models/things/publications/thing-q2115/spec.json"},"provenance":{"origin":"thing registry research (pass 2)","builtFrom":["models/things/publications/thing-q2115/spec.json"],"providers":["Codex","Grok"],"researchStatus":"unreviewed","generatedAt":"2026-09-07T10:28:29Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_gate":"Published through the thing publication gate 1.0 on 2026-10-07T10:10:28+00:00: completeness 1.00; sense: Wikidata description; 5 live sources; review by codex: pass","interaction.properties":"Plane INF: no invented physical properties."},"score":1.0}}