Re: Cleaning Up the Namespaces

Your wrote:
> a problem I'm experiencing is when I try to validate our WSDL example
> (wsdl-eg.xml) against our augmented wsdl schema
> (wsdl-p3p-extension.xsd) -- because we've added my:Privacy as a child
> of wsdl:definitions -- XSV gives me an error about 'wsdl12-ext.xsd'?

Looks like XSV doesn't know how to handle redirects appropriately:
[[
> HEAD http://www.w3.org/2003/06/wsdl
HTTP/1.1 301 Moved Permanently
Date: Mon, 30 Jun 2003 13:40:13 GMT
Server: Apache/1.3.27 (Unix) PHP/4.2.3
WWW-Authenticate: Basic realm="W3CACL"
Location: http://www.w3.org/2003/06/wsdl/
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 301 Moved Permanently
Date: Mon, 30 Jun 2003 13:40:13 GMT
Server: Apache/1.3.27 (Unix) PHP/4.2.3
WWW-Authenticate: Basic realm="W3CACL"
Location: http://www.w3.org/2003/06/wsdl/wsdl12.xsd
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Date: Mon, 30 Jun 2003 13:40:13 GMT
Server: Apache/1.3.27 (Unix) PHP/4.2.3
WWW-Authenticate: Basic realm="W3CACL"
P3P: policyref="http://www.w3.org/2001/05/P3P/p3p.xml"
Cache-Control: max-age=21600
Expires: Mon, 30 Jun 2003 19:40:13 GMT
Last-Modified: Fri, 06 Jun 2003 20:27:49 GMT
ETag: "3ee0f945"
Accept-Ranges: bytes
Content-Length: 15083
Content-Type: application/xml; qs=0.9
]]

The effective location of the WSDL XML Schema is
http://www.w3.org/2003/06/wsdl/wsdl12.xsd, and not
http://www.w3.org/2003/06/wsdl. Therefore, the include statement in
wsdl12.xsd should be resolved against
http://www.w3.org/2003/06/wsdl/wsdl12.xsd.

I note that the old version of Xerces that I'm using is also subject to
this problem. Didn't try with a latest one.

Not sure if the WSDL 1.2 specification should reference the effective
location of the XML Schema instead of the namespace...

Philippe

Received on Monday, 30 June 2003 09:47:16 UTC