$Revision: 1.1 $ on $Date: 2001/09/28 19:49:07 $ GMT by $Author: reagle $
Copy right ©2001 The Internet Society & W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, docum ent use and softwa re licensing rules apply.
This document specifies two XML Signature transforms for [XML1.0] and [XML-Schema] validation.
This document is an Editors' draft with no standing whatsoever.
This is the first draft of the "XML Validation Transforms
for XML Signature" from theXML Signature
Working Group(Activity
). Comments and implementation experience of this proposal are
solicited.
Publication of this document 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 a W3C Working Draft as anything other than a
"work in progress." A list of current W3C working drafts can be
found athttp://www.w3.org/TR/
.
Please send comments to the editors (<reagle@w3.org>
and cc: the listw3c-ietf-xmldsig@w3.org
Patent disclosures relevant to this specification may be
found on the Working Group'spatent
disclosure page) in conformance with W3C
policy
This document profiles the changes made to an XML document by [XML] and [XML-schema] validation as [XML-DSIG] transforms. The input, output, and processing (via normative references) is specified, along with the syntax and processing of [XML-DSIG] transform parameters.
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 RFC2119 [KEYWORDS]:
"they MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm (e.g., limiting retransmissions)"
No provision is made for an explicit version number in this syntax. If a future version is needed, it will use a different URI. The base URI that MUST be used for identification of these transforms is:
xmlns="http://www.w3.org/2001/09/validate#"
The contributions of the following Working Group members to this specification are gratefully acknowledged:
...
The normative specification of validating XML 1.0 processing is [XML]. Use of this transform indicates the document should be processed by a validating XML processor which, "must read and process the entire DTD and all external parsed entities referenced in the document." [XML]
The XML validation transform has no parameters, the document should be processed according to information available to the document, including document type declarations within the document.
If the input is octets they must be parsed by a validating XML parser. If the input is an XPath node-set, this node-set must be serialized first prior to validation. (However, validating an XPath nodeset is of little use since the node-set will not have a Document Type Declaration associated with it.) Note, while the changes made to an information set by XML validation can affect entities and default attribute content values. Consequently, the presence and order of XML validation may affect the canonical form.
http://www.w3.org/2001/09/validate#schema
The normative specification for XML Schema is [XML-Schema]. Use of the schema
validation transform without any parameters indicates that the
document should be processed according to information within the
resource being transformed. Use of a name space qualified
schema
element, which must be the sole child of the
Transform
, indicates the specified schema should be
used for validation; whether this instantiates other validation
using other schema is determined by the XML Schema processing
model; the ordered application of multiple schema validations may
require multiple Transforms
. No special provision is
made for the identification of a remote stylesheet at a given URI
because it can be communicated via an
xsd:include
or
xsd:import
within the schema
child of
the Transform
.
This transform requires a specified set of "Required Information Set Items and Properties" [XML-schema, Appendix D]. If the input is octets, the octets must be parsed. If the input is an XPath node-set, this node-set may be able to serve as the necessary information set. Note, while the changes made to an information set by schema validation are largely augmentations, and consequently not contained in the XPath data model, schema validation can affect default attribute and element content values. Consequently, the presence and order of schema validation may affect the canonical form.
[Do we have to worry about laxly schema valid? -JR]
...
Joseph M. Reagle Jr., W3C
Massachusetts Institute of Technology
Laboratory for Computer Science
NE43-350, 545 Technology Square
Cambridge, MA 02139
Phone: + 1.617.258.7621
Email: reagle@w3.org