This specification defines several XML processor profiles, each of which fully determines a data model for any given XML document. It is intended as a resource for other specifications, which can by a single normative reference establish precisely what input processing they require.
This is a public
This draft adds two further profiles, and sets out invariants in terms of document properties which will or will not be guaranteed to be the same for the same document when processed by processors conform to the same or different profiles. Comments on the utility of these additions are particularly welcome.
The Working Group invites review of this draft, which is likely to be
followed soon by a Last Call Working Draft.
Please send comments on this draft to the public mailing list
As this specification is intended for use by other specifications which themselves define one or more XML languages, the Working Group particularly welcomes input for other Working Groups who are responsible for such specifications.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the
The XML specification
This specification addresses this issue by defining several XML processor profiles, each of which fully determines a data model for any given XML document. It is intended as a resource for other specifications, which can by a single normative reference establish precisely what input processing they require.
The profiles defined here are appropriate for processing both XML 1.0
The term
All of the profiles describe the steps necessary
to construct a data model from a
The minimum approach to the construction of a data model requires the following:
Processing of the document as
Maintenance of the
The basic approach to the construction of a data model requires the following:
Processing of the document as
Maintenance of the
Identification of all xml:id attributes as IDs as
required by
The modest approach to the construction of a data model requires the following:
Processing of the document as
Maintenance of the
Identification of all xml:id attributes as IDs as
required by
The recommended approach to the construction of a data model requires the following:
Processing of the document as
Maintenance of the
Identification of all xml:id attributes as IDs as
required by
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
The following
Processes its input as required by point (1) above;
Recognizes and preserves the ID type of all xml:id attributes in
conformance with
Data models constructed in conformance with one of the profiles defined above will be guaranteed to share certain properties. The following sub-sections describe this in terms of invariants with respect to the information available in the data model.
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
[document element], [base URI], [character encoding scheme], [standalone], [version], [all declarations processed]
[namespace name], [local name], [prefix], [children], [attributes], [namespace attributes], [in-scope namespaces], [base URI], [parent]
[namespace name], [local name], [prefix], [normalized value], [specified], [attribute type], [references], [owner element]
[target], [content], [base URI], [notation], [parent]
[name],
[system identifier],
[public identifier],
[declaration base URI],
[parent]—standalone="yes"
[character code], [parent]
[content], [parent]
[prefix], [namespace name]
Whether the remaining information is present
[children], [notations], [unparsed entities]
[element content whitespace]
When two data models are constructed in conformance with the
two
[attribute type],
[references]—xml:id attributes
And all the differences listed in the next two sections.
Entirely, in that where a basic processor reports an Unexpanded Entity Reference, richer ones will report the entity expansion, which may be or include entire elements.
Entirely, for the same reason, or, just with respect to [normalized value], [specified], [attribute type] and [references] where a basic processor has not processed the relevant declaration, but a richer one has.
Entirely, in the opposite sense to the Element case above
Entirely, per the Element case above
And all the differences listed in the next section.
Entirely, in that where a modest processor reports an
xinclude Element, a recommend Processor will report the result of
XInclude processing, which may be or
include entire elements.
Entirely, for the same reason
The profiles defined here, particularly the application/xslt+xml or text/css might define a profile specifying appropriate <?xml-stylesheet type="[their media type]" . . .?> processing in addition to the processing required by
Conformance is a matter for any specification which references this one
to mandate, expressed in terms such as "Conforming implementations