Re: Typos in schema definition

>> I found two typos in [1].
>
>Sorry for the tardy reply!

Sorry for the tardy reply, too.

>> 1. With the following, the OAEPParams element cannot be a child of the
>> EncryptionMethod element because of namespace="##other" of <any>.
>>
>>   <complexType name='EncryptionMethodType' mixed='true'>
>>     <sequence>
>>       <element name='KeySize' minOccurs='0'
>>                type='xenc:KeySizeType'/>
>>       <any namespace='##other' minOccurs='0'
>>                                maxOccurs='unbounded'/>
>>     </sequence>
>>     <attribute name='Algorithm' type='anyURI' use='required'/>
>>   </complexType>
>
>Ok, changed to ##any.

If "##other" is changed to "##any", the schema becomes ambiguous because
the KeySize element matches both <element> and <any>.  It should be changed
in another way.

>> 2. With the following, either the DataReference or KeyReference element
>> can be a child of the ReferenceList element.  minOccurs="0" and
maxOccurs
>> ="unbounded" would be attributes of <choice>.
>>
>>   <element name='ReferenceList'>
>>     <complexType>
>>       <choice>
>>         <element name='DataReference' type='xenc:ReferenceType'
>>          minOccurs='0' maxOccurs='unbounded'/>
>>         <element name='KeyReference' type='xenc:ReferenceType'
>>          minOccurs='0' maxOccurs='unbounded'/>
>>       </choice>
>>     </complexType>
>>   </element>
>
>So you wish to preclude a key found in an  EncryptedKey from being used to
>encrypt data *and* other keys? I presume so, and I've adopted your
>structure below [1], but I guess we should make the minOccurs='1'? (No
>sense having an empty ReferenceList?)

Sorry for confusing you.  I don't wish to preclude such a key use and don't
see any problem if a key is used to encrypt both data and other keys.

Thanks,
Takeshi IMAMURA
Tokyo Research Laboratory
IBM Research
imamu@jp.ibm.com

Received on Friday, 22 March 2002 14:11:09 UTC