W3C home > Mailing lists > Public > public-xmlsec@w3.org > November 2011

CfC: Transition XML Security 2.0 documents to CR

From: <Frederick.Hirsch@nokia.com>
Date: Wed, 30 Nov 2011 21:13:14 +0000
To: <public-xmlsec@w3.org>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <DEB90DDB-04DF-4D48-91C1-E6A60C4DFF02@nokia.com>
This is a Call for Consensus (CfC) to advance the following three  2.0 documents to CR:

a) Canonical XML Version 2.0, http://www.w3.org/2008/xmlsec/Drafts/c14n-20/


  *   Including change in progress to reference the 2.0 Test Cases document as noted in http://lists.w3.org/Archives/Public/public-xmlsec/2011Nov/0021.html


  *   Last Call Comments tracker: https://www.w3.org/2006/02/lc-comments-tracker/42458/WD-xml-c14n2-20110421/doc/

b) XML Signature Syntax and Processing Version 2.0, http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-20/


  *   Last Call Comments tracker: https://www.w3.org/2006/02/lc-comments-tracker/42458/WD-xmldsig-core2-20110421/doc/

c) XML Signature Streaming Profile of XPath 1.0, http://www.w3.org/2008/xmlsec/Drafts/xmldsig-xpath/


  *   Last Call Comments tracker: https://www.w3.org/2006/02/lc-comments-tracker/42458/WD-xmldsig-xpath-20110421/doc/

--
According to the W3C process, CR signifies the document is stable and ready for implementation. Requirements to enter CR include a WG decision (in this case based on this CfC), a summary of changes including substantive changes, changes to requirements, evidence of wide review, and formally addressing issues raised in Last Call (see http://www.w3.org/2005/10/Process-20051014/tr.html#transition-reqs )

The Last Call Comments tracker links for the documents indicate all the comments received and that they have been resolved to the satisfaction of commenters. These comments also indicate review outside this group.

Changes since Last Call are as follows:

Canonical XML 2.0:

  *   ACTION-799 - clarify whitespace definition as XML definition, provide warning re using other libraries like Java
  *   ACTION-800 - update for 1-1 prefix to uri mapping
  *   Add reference to XML for whitespace

XML Signature 2.0:

  *   add reference to best practices to introduction, to resolve LC-2507
  *   adopt change from Marcos to Best Practices reference in intro
  *   change SHOULD for KeyInfoReference instead of RetrievalMethod per ACTION-816 (Substantive)
  *   Add to first paragraph in 7, KeyInfo Element additional text on scope.; changes to finish addressing LC-2506, http://www.w3.org/2006/02/lc-comments-tracker/42458/WD-xmldsig-core2-20110421/2506?cid=2506
  *
  *   update to not disallow transform in RetrievalMethod, make consistent with 1.1 (Substantive)
  *
  *   ACTION-810  changes for LC-4288, clarify context for XPath evaluation
  *
  *   ACTION-809  changes for LC-2487, correct attribute name in examples
  *
  *   Added a new term in Appendix A - XML Namespace URI
  *
  *   ACTION-830, refinements to XML terminology used in document wording

XML Signature Streaming Profile of XPath 1.0:

  *   no changes since Last Call

No changes in requirements driving this work have been noted. No formal objections have been noted.

As with XML Security 1.1 we will move to CR while noting the ECC IPR issue in the status section of XML Signature 2.0.

Please indicate support or disagreement with progressing these documents to CR by responding on the public list, before 9 November 2011. No response will be interpreted as agreement with moving to CR

Assuming agreement, we will proceed with the CR transition request during December and publish in January.

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Chair XML Security WG

For tracker, this should complete ACTION-858
Received on Wednesday, 30 November 2011 21:13:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 November 2011 21:13:53 GMT