- From: Joseph Reagle <reagle@w3.org>
- Date: Wed, 10 Apr 2002 14:34:51 -0400
- To: "Blair Dillaway" <blaird@microsoft.com>, <xml-encryption@w3.org>
[resulting
http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/
$Revision: 1.176 $ o
]
On Wednesday 10 April 2002 13:08, Blair Dillaway wrote:
> In the latest XML Enc schema, the definition below generates an
> ambiguous content type error on validation . I'm not certain about the
> best way to fix this, but believe we should fix it. Any suggestions?
... the only way to check for these is to create an instance which might
flush out all such ambigous content. I've filled out the enc-example.xml to
excercise as much of the schema as possible, and tweaked the schema to the
following to fix your problem. Please confirm these work for you:
http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/#sec-Schema
<element name="AgreementMethod" type="xenc:AgreementMethodType"/>
<complexType name="AgreementMethodType" mixed="true">
<sequence>
<element name="KA-Nonce" minOccurs="0" type="base64Binary"/>
<!-- <element ref="ds:DigestMethod" minOccurs="0"/> -->
<any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
<element name="OriginatorKeyInfo" minOccurs="0"
type="ds:KeyInfoType"/>
<element name="RecipientKeyInfo" minOccurs="0"
type="ds:KeyInfoType"/>
</sequence>
<attribute name="Algorithm" type="anyURI" use="required"/>
</complexType>
--
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 Wednesday, 10 April 2002 14:34:53 UTC