OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re:[ebxml-msg]Issue73:http://schemas.xmlsoap.org/soap/envelopenamespace


Shouldn't we change from


and from

    <import namespace="http://schemas.xmlsoap.org/soap/envelope/"
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"

Unfortunately, when I make the above change to the schema, I got back the
following error from my schema editor (Turbo XML 2.2.1 from TIBCO

'anyAttribute' unsupported in attributeGroup, because of the following
construct in http://schemas.xmlsoap.org/soap/encoding/:

  <xs:attributeGroup name="commonAttributes" >
     Attributes common to all elements that function as accessors or
        represent independent (multi-ref) values.  The href attribute is
        intended to be used in a manner like CONREF.  That is, the element
        content should be empty iff the href attribute appears
    <xs:attribute name="id" type="xs:ID" />
    <xs:attribute name="href" type="xs:anyURI" />
    <xs:anyAttribute namespace="##other" processContents="lax" />

Can folks working on interop tests verify if
http://schemas.xmlsoap.org/soap/encoding/ can be understood by their
parsers? In fact, I have heard from David previously that some parsers don't
even support the xs:annotation construct.

I have sent an urgent support request to find out why Turbo XML is not
supporting this construct.


-----Original Message-----
From: Christopher Ferris <chris.ferris@sun.com>
To: Rich Salz <rsalz@zolera.com>
Cc: Arvola Chan <arvola@tibco.com>; Doug Bunting <dougb62@yahoo.com>;
ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
Date: Wednesday, February 13, 2002 6:42 AM
Subject: Re:

>Thanks, I didn't catch that note. I woul therefore recommend that
>we a) remove the envelope.xsd from our document tree and b) update
>the message-header.xsd to reflect the schemaLocation of the
>envelope namespace as the value of that namespace.
>Rich Salz wrote:
>> Chris,
>> In fact, Gudge updated the schemas at xmlsoap.org, so using
>> http://schemas.xmlsoap.org/soap/encoding/
>> will get you SOAP 1.1 but compliant with XML Schema REC.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC