W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2002

Re: Typos in schema definition

From: Joseph Reagle <reagle@w3.org>
Date: Mon, 1 Apr 2002 17:48:11 -0500
Message-Id: <200204012248.RAA28044@tux.w3.org>
To: "Takeshi Imamura" <IMAMU@jp.ibm.com>
Cc: xml-encryption@w3.org, Kohsuke KAWAGUCHI <kohsuke.kawaguchi@eng.sun.com>, xmlschema-dev@w3.org
On Monday 01 April 2002 05:28, Takeshi Imamura wrote:
> >I haven't tested this or included it in the spec yet.
> >
> > <complexType name='EncryptionMethodType' mixed='true'>
> >   <sequence>
> >     <element name='KeySize' minOccurs='0' type='xenc:KeySizeType'/>
> >     <choice>
> >       <sequence>
> >         <element ref='ds:DigestMethod' minOccurs='0'/> 
> >         <element name='OAEPparams' minOccurs='0' type='base64Binary'/>
> >       </sequence>
> >       <any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
> >     </choice>
> >   </sequence>
> >   <attribute name='Algorithm' type='anyURI' use='required'/>
> ></complexType>

Actually, I later tested this with Sun's MSV but it didn't complain [1]. 
Howevever, once I read your email I did test it with XSV (I only wish I 
could get it to work under Linux!) and it did complain of a 
non-deterministic content model, so I'm not sure if MSV supports that 
constraint...? 

[1] java -jar /usr/local/msv/msv.jar xenc-schema.xsd enc-example.xml
start parsing a grammar.
validating enc-example.xml
the document is valid.

> This still seems ambiguous because a ds:DigestMethod element can match
> both <element ref="ds:DigestMethod"> and <any namespace="##other">. 

That surprises me. ds:DigestMethod (by itself) can only match the second 
choice: ##other. If there's a ds:DigestMethod and a OAEPparams then it only 
matches the first choice. Right? Regardless, since your understanding and 
XSV's agree, I'd moved to what you propose below:

> 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-Schema
Received on Monday, 1 April 2002 17:48:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:30 GMT