OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I've been investigating WSDL over the last couple of months, and one
of its problems is that is doesn't mandate a particular type system
(currently XMLSchema is the defacto standard), nor does it include a
method for resolving what type system you'd like to work with. One of
the reoccurring issues is the transition from the old draft version to
the CR version of XML Schema.

I've been thinking that RDDL could be the solution by having a RDDL
document with the different WSDL + Type systems available for a given
SOAP endpoint, and have a WSDL client pick the one it most wants to
work with. However based on what i've seen so far, i'm unsure as to
what the roles should be set to. basically i want to describe the

WSDL + http://www.w3.org/1999/XMLSchema
WSDL + http://www.w3.org/2000/10/XMLSchema
BTW, WSDL has its own namespace of http://schemas.xmlsoap.org/wsdl/

This would help solve some of the transitional issues, whilst at the
same time open up an approach to moving to other schema languages
(XMLSchema seems overly complex for WSDL's needs)

As WSDL is a compound document, can anyone suggest what i should be
using for role attribute ?