OASIS ebXML Messaging Services TC

 View Only

Re: [ebxml-msg] envelope.xsd

  • 1.  Re: [ebxml-msg] envelope.xsd

    Posted 03-05-2002 19:37
    Arvola,
    
    My comments were against 2.0 I think, not 2.0c. However, I think
    that we are in agreement. I am suggesting that the spec make no mention
    whatsoever of our snapshot of the SOAP envelope schema.
    
    I would therefore recommend that lines 619-624 be deleted, leaving:
    
    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 any schema document(s) that should be used to
                           ^^^^^^^^^^^^^^^^^^^^^^
    validate
    the document. Failure to 627
    include the schemaLocation attribute could prevent XML schema validation of
    received messages. 628
    
    and then delete the remainder of the section. No example is necessary
    IMO, we leave that to the developer to work out how to use 
    xsi:schemaLocation.
    
    Cheers,
    
    Chris
    
    Arvola Chan wrote:
    
    > 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
    > 
    >