RE: Missing WSDL Schema

Indeed. I think namespace owners should get in the habit of putting human
readable docs at the end of the namespace URI with links to the schemas.
This would block toolkits from doing this sort of thing, but still make it
easy and intuitive for users to get access to the required schemas and other
docs. I'm personally a fan of RDDL for this purpose, but then there is
always the danger that toolkits will add RDDL support and then continue to
do the same bad practice of relying upon remote access of schemas for
processing.

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: Friday, July 13, 2001 12:13 AM
> To: Pradyumna_Siddhartha; xmlschema-dev@w3.org
> Subject: RE: Missing WSDL Schema
> 
> 
> See,
> 
> another proof why it's a bad idea to rely on schemas or DTDs 
> being present
> from a remote server...
> 
> > -----Original Message-----
> > From: xmlschema-dev-request@w3.org
> > [mailto:xmlschema-dev-request@w3.org]On Behalf Of 
> Pradyumna_Siddhartha
> > Sent: Friday, July 13, 2001 7:47 AM
> > To: xmlschema-dev@w3.org
> > Subject: Missing WSDL Schema
> >
> >
> > Hi All,
> >
> > 	Does anyone know why the WSDL schemas:
> > 	http://schemas.xmlsoap.org/wsdl
> > 	http://schemas.xmlsoap.org/wsdl/soap
> >
> > 	are apparently missing? I am trying to access a Java-based SOAP
> > service using WSDL and am getting errors while parsing the WSDL file
> > such as:
> >
> > 	Error: URI=null Line=2: Element type "definitions" is not
> > declared.
> > 	Error: URI=null Line=3: Attribute "name" is not declared for
> > element "definitions".
> >
> > 	...and so on. Are the missing files at the bottom of the
> > problem?
> >
> > Thanks and best regards,
> > Sasha
> >
>

Received on Friday, 13 July 2001 19:00:22 UTC