Doug:
David,
Cliff, and I had a conference call yesterday. The version for envelope.xsd on
the TC web site we arrived at has the following contents:
<?xml version="1.0" encoding="UTF-8"
?>
- <schema targetNamespace="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/">
<include schemaLocation="http://schemas.xmlsoap.org/soap/envelope/" />
</schema>
It
looks very much like your suggestion:
<?xml version="1.0" encoding="UTF-8"?>
<!--
This is a redirector schema to the normative SOAP v1.1
schema-->
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://schemas.xmlsoap.org/soap/envelope/"
version="1.0">
<import
namespace="http://schemas.xmlsoap.org/soap/envelope/"
schemaLocation="http://schemas.xmlsoap.org/soap/envelope/"
/>
</schema>
The
main difference is that the include construct rather than the import construct
is used. This is appropriate since the namespace in question is the target
namespace instead of a foreign namespace.
Cliff
has tested it to verify that this redirector works with his
software.
On the
web page, we now have two files with identical contents: msg-header-2_0.xsd and
msg-header-2_0c.xsd. Each contains the following
declaration:
- <schema targetNamespace="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:tns="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" elementFormDefault="qualified"
attributeFormDefault="qualified" version="2.0c">
Please note that version
attribute is set to "2.0c". The intent is if we find any problem with this
version, we can create a 2.0d version and replace the contents of
msg-header-2_0.xsd with the contents of the revised version.
Regards,
-Arvola
-----Original Message-----
From: Doug Bunting
[mailto:]
Sent: Thursday, March 14, 2002 12:34
PM
To: David Fischer
Cc: ebXML
Subject: Re:
[ebxml-msg] envelope.xsd
David,
Sorry for my delayed response on this thread.
As we've discussed, the http://schemas.xmlsoap.org/soap/envelope/
namespace identifier resolves to a usable XSD instance. The relevant
import statement should look much like the optional schemaLocation attribute
in ebXML Message instances. This is a relatively minor update to what
Arvola presented.
On Arvola's request which was buried far below:
Doug/Chris/Arvola, would you look at the Errata item I put on
the previous message and edit as necessary to accomplish what is indicated
here?I didn't have anything to add on the Errata page
itself. I took this one step further and looked at the envelope.xsd
redirector you proposed earlier. It looks like it'll work but remains
more complicated than necessary. I've attached something I've edited but
haven't been able to test. (Testing issues were what held up this
email. I've now given up.) If Arvola could confirm this also
works, I'd prefer we use this more direct redirect form.
thanx,
doug
David Fischer wrote:
Looks OK to me -- except for the url
http://schemas.xmlsoap.org/soap/envelope.xsd
which doesn't resolve to anything.
David.
