[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-msg] envelope.xsd
Chris:
Your line numbers are a bit off. Which version of the spec are you referring
to? Here is the relevant portion in the 2_0c spec:
2.3.2 xsi:schemaLocation attribute 618
The SOAP namespace: 619
http://schemas.xmlsoap.org/soap/envelope/ 620
resolves to a W3C XML Schema specification. The ebXML OASIS ebXML Messaging
TC has provided 621
an equivalent version of the SOAP schema conforming to the W3C
Recommendation version of the XML 622
Schema specification [XMLSchema]. 623
http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd 624
All ebXML MSH implementations are strongly RECOMMENDED to include the
XMLSchema-instance 625
namespace qualified schemaLocation attribute in the SOAP Envelope element to
indicate to validating 626
parsers a location of the schema document that should be used to validate
the document. Failure to 627
include the schemaLocation attribute could prevent XML schema validation of
received messages. 628
For example: 629
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 630
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 631
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ 632
http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"> 633
In addition, ebXML SOAP Header and Body extension element content may be
similarly qualified so as 634
to identify the location where validating parsers can find the schema
document containing the ebXML 635
namespace qualified SOAP extension element definitions. The ebXML SOAP
extension element schema 636
has been defined using the W3C Recommendation version of the XML Schema
specification 637
[XMLSchema] (see Appendix A). The XMLSchema-instance namespace qualified
schemaLocation 638
attribute should include a mapping of the ebXML SOAP Envelope extensions
namespace to its schema 639
document in the same element that declares the ebXML SOAP Envelope
extensions namespace. 640
Your suggested changes do not seem directly applicable to the 2_0c spec.
Also, it may still be puzzling to uninitiated readers why we have introduced
our own snapshot of envelope.xsd without the deleted information. If we make
changes to the spec at this point, I would have preferred that we do it
properly by specifying http://schemas.xmlsoap.org/soap/envelope/ as the
schema location. If we want to leave the spec as is, then I recommend
replacing the contents of
http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd.
Regards,
-Arvola
-----Original Message-----
From: Christopher Ferris [mailto:chris.ferris@sun.com]
Sent: Tuesday, March 05, 2002 1:43 PM
To: Christopher Ferris
Cc: Arvola Chan; David Fischer; Ian. C. Jones (E-mail); ebXML Msg
Subject: Re: [ebxml-msg] envelope.xsd
oops, I meant to include the email in which I made
a proposal to address the schemaLocation section.
Since it isn't archived, here is the relevant fragment
from the email I sent to David, Ian, Arvola and Doug:
-------------------------------------------------------------------
*** w/r/t section 2.3.2, I think that its removal in whole is uncalled
for. I would propose
the following alternative approach:
1 - delete lines 620-639
2 - modify line 640 as follows:
In addition, ebXML SOAP Header and Body extension element content must
may be similarly qualified so as to identify the location where
validating parsers can find the schema document containing the ebXML
namespace qualified SOAP extension element definitions.
3 - modify example at line 651 as follows:
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd" >
-------------------------------------------------------------------
Cheers,
Chris
Christopher Ferris wrote:
> Arvola,
>
> And I countered with a proposal that I think addressed the
> issue without actually removing the schemaLocation section[1].
>
> The point is (from my perspective) that we don't want to
> preclude use of schemaLocation (for any purpose) but that
> we don't necessarily want to encourage its use for the
> SOAP envelope.xsd since we really don't own this.
>
> We previously had an issue w/r/t the version of XSD that
> was used to create the schema document at the namespace
> URI, but we no longer have an issue so why are we continuing
> to recommend this practice.
>
> I would suggest that if anything, we say that the schemaLocation
> is:
>
> xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
> http://schemas.xmlsoap.org/soap/envelope/"
>
> If we replace what is at:
>
> http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd
>
>
> with what is at:
>
> http://schemas.xmlsoap.org/soap/envelope/
>
> I'm okay with that too, but we still don't want to advertise this
> in the spec IMO.
>
> Cheers,
>
> Chris
>
> Arvola Chan wrote:
>
>> Chris:
>>
>> Both Doug and members of the interop team objected to the removal of
>> section
>> 2.3.2 on the xsi:schemaLocation attribute.
>>
>> Here is an excerpt from the 2_0c spec:
>>
>> 2.3.2 xsi:schemaLocation attribute
>> The SOAP namespace: http://schemas.xmlsoap.org/soap/envelope/ resolves
>> to a
>> W3C XML schema specification. The ebXML OASIS ebXML Messaging TC has
>> provided an equivalent version of the SOAP schema conforming to the W3C
>> Recommendation version of the XML Schema specification [XMLSchema].
>>
>> http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd
>>
>> All ebXML MSH implementations are strongly RECOMMENDED to include the
>> XMLSchema-instance
>> namespace qualified schemaLocation attribute in the SOAP Envelope
>> element to
>> indicate to validating parsers a location of the schema document that
>> should
>> be used to validate the document. Failure to include the schemaLocation
>> attribute could prevent XML schema validation of received messages. For
>> example:
>>
>> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
>> http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd">
>>
>> -Arvola
>>
>> -----Original Message-----
>> From: Christopher Ferris [mailto:chris.ferris@sun.com]
>> Sent: Tuesday, March 05, 2002 12:35 PM
>> To: Arvola Chan
>> Cc: David Fischer; Ian. C. Jones (E-mail); ebXML Msg
>> Subject: Re: [ebxml-msg] envelope.xsd
>>
>>
>> I thought that we had agreed that we should be referencing
>> http://schemas.xmlsoap.org/soap/envelope/ directly?
>>
>> Chris
>>
>> Arvola Chan wrote:
>>
>>
>>> David:
>>>
>>> Since the spec still recommends the use of
>>>
>>> http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd
>>>
>>> as the schema location for the SOAP Envelope, do we want to replace the
>>> content of
>>>
>>> http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd
>>>
>>> with the content of
>>>
>>> http://schemas.xmlsoap.org/soap/envelope/ so that we are using the
>>>
>> official
>>
>>> SOAP 1.1 schema rather than our own crafted version?
>>>
>>> -Arvola
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ----------------------------------------------------------------
>>> To subscribe or unsubscribe from this elist use the subscription
>>> manager: <http://lists.oasis-open.org/ob/adm.pl>
>>>
>>
>>
>>
>
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC