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

[Arvola Chan <arvola@tibco.com>]

Chris:

Thanks for your clarification. The schema at
http://schemas.xmlsoap.org/soap/envelope/ does indicate that it is intended
for SOAP 1.1.

<!--
 Schema for the SOAP/1.1 envelope

     This schema has been produced using W3C's SOAP Version 1.2 schema
     found at:

     http://www.w3.org/2001/06/soap-envelope

     Copyright 2001 Martin Gudgin, Developmentor.

     Changes made are the following:
     - reverted namespace to http://schemas.xmlsoap.org/soap/envelope/
     - reverted mustUnderstand to only allow 0 and 1 as lexical values
...
-->

When I modified msg-header-2_0.xsd to use
http://schemas.xmlsoap.org/soap/envelope/ as the schema location, I did not
encounter any error from my schema editor. It does not make use of the
anyAttribute construct within an attributeGroup. On the other hand, it does
make use of the ds:annotation construct which may be problematical for some
parsers.

My edited version of msg-header-2_0.xsd is attached.

Regards,
-Arvola

-----Original Message-----
From: Christopher Ferris <chris.ferris@sun.com>
To: Arvola Chan <arvola@tibco.com>
Cc: Rich Salz <rsalz@zolera.com>; Doug Bunting <dougb62@yahoo.com>;
ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
Date: Wednesday, February 13, 2002 9:06 AM
Subject: Re:
[ebxml-msg]Issue73:http://schemas.xmlsoap.org/soap/envelopenamespace


>Arvola,
>
>Please see below.
>
>Cheers,
>
>Chris
>
>Arvola Chan wrote:
>
>> Chris:
>>
>> Shouldn't we change from
>>
>>     xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>> to
>>     xmlns:soap="http://schemas.xmlsoap.org/soap/encoding/"
>
>
>No, the encoding is a separate schema upon which we don't rely.
>
>
>>
>> and from
>>
>>     <import namespace="http://schemas.xmlsoap.org/soap/envelope/"
>>
schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/envelo
>> pe.xsd"/>
>> to
>>     <import namespace="http://schemas.xmlsoap.org/soap/encoding/"
>> schemaLocation="http://schemas.xmlsoap.org/soap/encoding/>
>
>
>Nope, same reasoning. Rich was just siting the wrong URI
>(encoding and envelope are both SOAP1.1 schemas). encoding in 1.1
>is for SOAP RPC.
>
>
>>
>> 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
>> Extensibility):
>>
>> 'anyAttribute' unsupported in attributeGroup, because of the following
>> construct in http://schemas.xmlsoap.org/soap/encoding/:
>>
>>   <xs:attributeGroup name="commonAttributes" >
>>     <xs:annotation>
>>    <xs:documentation>
>>      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:documentation>
>>  </xs:annotation>
>>     <xs:attribute name="id" type="xs:ID" />
>>     <xs:attribute name="href" type="xs:anyURI" />
>>     <xs:anyAttribute namespace="##other" processContents="lax" />
>>   </xs:attributeGroup>
>>
>> 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.
>>
>> Thanks,
>> -Arvola
>>
>>
>>
>>
>> -----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:
>> [ebxml-msg]Issue73:http://schemas.xmlsoap.org/soap/envelopenamespace
>>
>>
>>
>>>Rich,
>>>
>>>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.
>>>
>>>Chris
>>>
>>>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.
>>>>
>>>>
>>>>
>>>
>>
>>
>
>

msg-header-2_0b.xsd