W3C home > Mailing lists > Public > xml-encryption@w3.org > April 2002

RE: Schema validation problem

From: Blair Dillaway <blaird@microsoft.com>
Date: Wed, 10 Apr 2002 14:27:19 -0700
Message-ID: <AA19CFCE90F52E4B942B27D42349637902CDCF98@red-msg-01.redmond.corp.microsoft.com>
To: <reagle@w3.org>, <xml-encryption@w3.org>

Thanks for the quick response.  This solves the problem I was running


-----Original Message-----
From: Joseph Reagle [mailto:reagle@w3.org] 
Sent: Wednesday, April 10, 2002 11:35 AM
To: Blair Dillaway; xml-encryption@w3.org
Subject: Re: Schema validation problem

[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
excercise as much of the schema as possible, and tweaked the schema to
following to fix your problem. Please confirm these work for you:

    <element name="AgreementMethod" type="xenc:AgreementMethodType"/>
    <complexType name="AgreementMethodType" mixed="true">
        <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" 
        <element name="RecipientKeyInfo" minOccurs="0" 
      <attribute name="Algorithm" type="anyURI" use="required"/>


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 17:27:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:03 UTC