- From: Joseph M. Reagle Jr. <reagle@w3.org>
- Date: Thu, 19 Apr 2001 15:27:32 -0400
- To: "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
Forwarded Text ---- >W3C is pleased to announce the publication of a revised >XML-Signature Syntax and Processing Candidate Recommendation. > > XML-Signature Syntax and Processing > 19 April 2001 > http://www.w3.org/TR/2001/CR-xmldsig-core-20010419/ > Editors > Donald Eastlake <dee3@torque.pothole.com> > Joseph Reagle <reagle@w3.org> > David Solo <dsolo@alum.mit.edu> > Authors > Mark Bartel <mbartel@JetForm.com> > John Boyer <jboyer@PureEdge.com> > Barb Fox <bfox@Exchange.Microsoft.com> > Brian LaMacchia <bal@microsoft.com> > Ed Simon <ed.simon@entrust.com> > >Abstract > >This document specifies XML digital signature processing rules and >syntax. XML Signatures provide integrity, message authentication, and/or >signer authentication services for data of any type, whether located >within the XML that includes the signature or elsewhere. > >Status of this document > > This specification from the IETF/W3C XML Signature Working Group > (W3C Activity Statement) is a second Candidate Recommendation of > the W3C. This version contains many bug-fixes, clarifications, > and improvements for DTD/schema extensibility and re-use. It > reflects resolution of recent (and past) issues and the Schema > Proposed Recommendation. As warned in the previous Candidate > Recommendation, the minimal canonicalization algorithm has been > removed because the Working Group could find no implementation. > This specification is considered to be very stable. The W3C > Namespace Policy requires that if a change in the namespace > makes previously valid or compliant instances and > implementations invalid, the namespace must also change. > Since the clarifications do not substantively affect valid > instance syntax or implemented features, the namespace has > not been changed. > > The duration of this Candidate Recommendation will last one month > 19 May 2001 to ensure we have not introduced any new errors and so > as to coincide with the close of a four week IETF last call. > Subsequently, and assuming no substantive issues are raised, this > version will be proposed as a Proposed Recommendation and Draft > Standard. Note, this specification already has significant > implementation experience as demonstrated by its > Interoperability Report. __ Joseph Reagle Jr. http://www.w3.org/People/Reagle/ W3C Policy Analyst mailto:reagle@w3.org IETF/W3C XML-Signature Co-Chair http://www.w3.org/Signature W3C XML Encryption Chair http://www.w3.org/Encryption/2001/
Received on Thursday, 19 April 2001 15:27:46 UTC