Re: Inline schemas with no target namespace

Ram,

Just the immediate childen of the wsdl:types element need a namespace. 
Within those you can include or import a no-namespace schema.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



"Ramkumar Menon" <ramkumar.menon@gmail.com> 
Sent by: www-ws-desc-request@w3.org
05/19/2006 05:50 PM

To
www-ws-desc@w3.org
cc

Subject
Inline schemas with no target namespace







Hi All,

Would appreciate yor thoughts on the following.

Section 3.1.2.1 of the Core Langage spec says
"WSDL 2.0 modifies the XML Schema definition of the xs:schema element
information item to make this attribute information item required".

There is a scenario where I have an existing XSD that I am intending
to re-use while designing the WSDL. The XSD has no target namespace,
and has a bunch of elements and attributes defined within it. What it
also does is to import a couple of XSDs that have a non-null target
namespace. the wsdl intends to define the message parts to point to
one of the nodes defined in the imported XSDs within the nonamespace
XSD. The nodes that had been directly defined in the no-namespace XSD
are not used by the WSDL, but are consumed by other applications.
In this case, do yo think that it would be "really" invalid to inline
such an XSD into the WSDL ? I was wondering that atleast
theoretically, this should be possible. The question is - "Do we need
to make some statements around this in the spec" ?


regards,
Menon.

-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor