Cleaning Up the Namespaces (Was: Comments on "[P3P]: Beyond HTTP")

Patrick, I finally got around to adding the references (through some clumsy 
XSLT hackery [1] <smile/>) and I also tried to clean up the use of our 
identifiers and Namespaces[2]. However, it's just as likely I broke 
something, so let me know if I have.

Hugo, 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'?

>Schema resources involved
>Attempt to load a schema document from 
>/home/reagle/data/2web/WWW/P3P/2003/p3p-beyond-http/wsdl-p3p-extension.xsd 
>(source: command line) for no namespace, succeeded

>Attempt to load a schema document from http://www.w3.org/2003/06/wsdl 
>(source: import) for http://www.w3.org/2003/06/wsdl, succeeded

>Attempt to load a schema document from 
>http://www.w3.org/2003/06/wsdl12-ext.xsd (source: include) for 
>http://www.w3.org/2003/06/wsdl, failed: couldn't open *************


[1] http://lists.w3.org/Archives/Public/spec-prod/2003AprJun/0017.html
[2] http://www.w3.org/2003/03/rdf-in-xml.html
     $Revision: 1.21 $ on $Date: 2003/06/10 18:57:29 $
|   Namespaces and Identifiers
|
|    Throughout this document the following namespaces and
|    identifiers are used.
|
|    http://registry.example.com/2003/ns1
|           The namespace of the example order form for the
|           registry.
|
|    http://www.w3.org/P3P/2003/p3p-beyond-http/
|           The namespace of the p3p:Privacy element that is used
|           in SOAP headers.
|
|    http://registry.example.com/wsdl/register
|           The targetNamespace for the registry's WSDL
|
|    http://registry.example.com/P3P/PolicyReferences.xml
|           The location of the registy's P3P policy

Received on Wednesday, 18 June 2003 17:07:19 UTC