IETF W3C  
Canonical XML Implementation and Interoperability Report

Editors(s):
John Boyer <[email protected]>
Joseph Reagle, <[email protected]>
Previous versions
...

This document describes the interoperability requirements over a features, operations, and requirements specified by the Canonical XML specification of the IETF/W3C XML Signature WG as required by the charter. The minimum exit criteria for this implementation period is defined by the IETF RFC2026 Draft Standard semantic:

4.1.2 Draft Standard A specification from which at least two independent and interoperable implementations from different code bases have been developed, and for which sufficient successful operational experience has been obtained... For the purposes of this section, "interoperable" means to be functionally equivalent or interchangeable components of the system or process in which they are used.

Implementations must operate over the following list of (mostly) MANDATORY operations of the October 11 specification as captured in the October 11 examples. There is already signficant implementation experience and we expect to satisfy the exit criteria (2 implementations) within two weeks of reaching Candidate Rec. However, this period may be extended so as to increase our confidence by increasing the number of compliant implementations and/or expanding the test cases.

The following information is the best assesment of the Editors/Chairs for the given dated specification and does not necessarily represent the latest state of any given implementation over this or later specifications.  The following key applies: "Y"(implemented), " Y{1,2,*}"(interoperable with others in that Y{1,2,*} set), "N"(not implemented), ""(unkown).

Features (yellow designates interoperable examples exchanged) Key Word Done360 Baltimore IAIK IBM Apache Phaos XMLSec NEC Datapower
Octet stream input MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
withComments SHOULD  

Y1

 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Document Subsets (c14n portion of a document) MUST   Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
  • Node-set input (achieve subsetting via Xpath like node-set input)
 SHOULD   Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Processor Requrements (yellow designates interoperable examples exchanged) Key Word Done360 Baltimore IAIK IBM Apache Phaos XMLSec NEC Datapower
Use processors that support UTF-8 and UTF-16 and that translate to the UCS character domain MUST   Y1 Y1 Y   Y1 Y1 Y1 Y1
implementations MUST report an operation failure on documents containing relative namespace URIs. MUST   Y1 Y1 Y1   Y1 Y1 Y1 Y1
implementations MUST NOT be implemented with an XML parser that converts relative URIs to absolute URIs. MUST   Y1 Y1 Y1   Y1 Y1 Y1 Y1
Examples (yellow designates interoperable examples exchanged) Key Word Done360 Baltimore IAIK IBM Apache Phaos XMLSec NEC Datapower
PIs, Comments, and Outside of Document Element MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Whitespace in Document Content MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Start and End Tags MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Character Modifications and Character References MUST ~ Y Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Entity References MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
UTF-8 Encoding MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Document Subsets MUST Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1 Y1
Joseph Reagle <[email protected]>

Last revised by Reagle $Date: 2003/05/06 17:45:49 $

=======