- From: Joseph Reagle <reagle@w3.org>
- Date: Fri, 5 Apr 2002 13:50:04 -0500
- To: "Takeshi Imamura" <IMAMU@jp.ibm.com>
- Cc: xml-encryption@w3.org, Kohsuke KAWAGUCHI <kohsuke.kawaguchi@eng.sun.com>, xmlschema-dev@w3.org
I thought about this and I no longer hold my original concern that the change would invalidate existing instances (and whether this necessitated a change of namespace). Given that the original instances were invalid, our change hasn't broken any instance that used to work. <smile/> On Monday 01 April 2002 17:48, Joseph Reagle wrote: > > So it would be easier to define this as you say or as follows: > > > > <complexType name='EncryptionMethodType' mixed='true'> > > <sequence> > > <element name='KeySize' minOccurs='0' type='xenc:KeySizeType'/> > > <element name='OAEPparams' minOccurs='0' type='base64Binary'/> > > <any namespace='##other' minOccurs='0' maxOccurs='unbounded'/> > > </sequence> > > <attribute name='Algorithm' type='anyURI' use='required'/> > > </complexType> > > The only change that is required was that in the examples I precede the > ds:DigestMethod with OAEPparams. However, now that the old ordering is > now invalid, this will require us to change our namespace. > > http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/Overview.html#sec-Sc >hema -- 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 Friday, 5 April 2002 13:50:09 UTC