XML processor profiles

1.1 Terminology

[Definition: The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this specification are to be interpreted as described in [RFC 2119].]

The term base URI is used in this specification as it is defined in [RFC 3986].

2.1 The minimum XML processor profile

The minimum approach to the construction of a data model requires the following:

1. Processing of the document as required of conformant non-validating XML processors without reading any external markup declarations;

2. Maintenance of the base URI of each element in conformance with [XML Base];

2.2 The basic XML processor profile

The basic approach to the construction of a data model requires the following:

1. Processing of the document as required of conformant non-validating XML processors without reading any external markup declarations;

2. Maintenance of the base URI of each element in conformance with [XML Base];

3. Identification of all xml:id attributes as IDs as required by [xml:id Version 1.0]

2.3 The modest XML processor profile

The modest approach to the construction of a data model requires the following:

1. Processing of the document as required of conformant non-validating XML processors while reading all external markup declarations;

2. Maintenance of the base URI of each element in conformance with [XML Base];

3. Identification of all xml:id attributes as IDs as required by [xml:id Version 1.0]

2.4 The recommended XML processor profile

The recommended approach to the construction of a data model requires the following:

1. Processing of the document as required of conformant non-validating XML processors while reading and processing all external markup declarations;

2. Maintenance of the base URI of each element in conformance with [XML Base];

3. Identification of all xml:id attributes as IDs as required by [xml:id Version 1.0]

4. Replacement of all include elements in the XInclude namespace, and namespace, xml:base and xml:lang fixup of the result, as required for conformance to [XML Inclusions (XInclude) Version 1.0 (Second Edition)].

The following [XProc: An XML Pipeline Language] pipeline implements the 2.4 The recommended XML processor profile when executed by a conformant XProc processor which

• Processes its input as required by point (1) above;

• Recognizes and preserves the ID type of all xml:id attributes in conformance with [xml:id Version 1.0].

<p:pipeline xmlns:p="https://www.w3.org/ns/xproc">
  <p:xinclude fixup-xml-base="true" fixup-xml-lang="true"/>
</p:pipeline>

3.1 Data model invariants within a given profile

Any two data models which are both constructed in conformance with the same profile from a given namespace-well-formed XML document will have exactly the same information with repect to the following information items and properties (per [XML Information Set (Second Edition)]):

The Document Information Item

[document element], [base URI], [character encoding scheme], [standalone], [version], [all declarations processed]

Element Information Items

[namespace name], [local name], [prefix], [children], [attributes], [namespace attributes], [in-scope namespaces], [base URI], [parent]

Attribute Information Items

[namespace name], [local name], [prefix], [normalized value], [specified], [attribute type], [references], [owner element]

Processing Instruction Information Items

[target], [content], [base URI], [notation], [parent]

Unexpanded Entity Reference Information Items

[name], [system identifier], [public identifier], [declaration base URI], [parent]—This type of information item will not occur at all if using 2.3 The modest XML processor profile or 2.4 The recommended XML processor profile profiles, or if standalone="yes"

Character Information Items

[character code], [parent]

Comment Information Items

[content], [parent]

Namespace Information Items

[prefix], [namespace name]

3.2 Data model variation between profiles

When two data models are constructed in conformance with the two different profiles from a given namespace-well-formed XML document, the information contained therein will in some cases (depending on the specifics of the document in question) differ with repect to the following information items and properties (per [XML Information Set (Second Edition)]) (leaving aside the items and properties identified as implementation-defined above):