Re: Can multiple inline schemas have same targetNamespace?

Thank you.  The group's resolution is satisfactory (But it sure took a 
long time)  =)

Jeehong Min
Software Engineer - Web Services Solutions
Parasoft Corporation          email: jeehongm@parasoft.com
101 E. Huntington Ave.        voice: (626) 256-3680
Monrovia, CA.  91016          fax  : (626) 256-6884 

"We Make Software Work"



Jonathan Marsh wrote:

> Thank you for your comment - we tracked this as a Last Call comment 
> LC60 [1].  The Working Group agreed to add clarification that two 
> inlined schemas from the same targetNS are OK, and to note that we 
> rely on schema processors to sort out a coherent set of schema 
> components.  You can view the resolution in context at [2].  If we 
> don't hear otherwise within two weeks, we will assume this satisfies 
> your concern.
>
>  
>
> [1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC60
>
> [2] http://www.w3.org/TR/2005/WD-wsdl20-20050510/#inlining-xsd
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] 
> *On Behalf Of *Jeehong Min
> *Sent:* Monday, September 27, 2004 12:48 PM
> *To:* www-ws-desc@w3.org
> *Subject:* Can multiple inline schemas have same targetNamespace?
>
>  
>
> I would appreciate it if you could address the following issue that I 
> have seen in WSDLs of 2 customers in the past month.
>
>  
>
> One vendor's SOAP stack is creating WSDLs with multiple inline schemas 
> that have the same namespace.
>
>  
>
> Here's an example:
>
> <wsdl:definition>
> <wsdl:types>
> <xs:schema targetNamespace="a">
> types and elements
> </xs:schema>
> <xs:schema targetNamespace="a">
> different types and elements
> </xs:schema>
> <xs:schema targetNamespace="b">
> whatever
> </xs:schema>
> </wsdl:types>
> ...
> <wsdl:definition>
>
>  
>
> It's not clear to me whether the above is legal or not (two schemas 
> with the same targetNamespace="a").  Should XML parsers for WSDL be 
> smart enough to handle the above?  Or should parsers report errors? 
>
>
> --
> Jeehong Min
> Software Engineer
> SOAPtest Development
> Parasoft Corporation
>
>  
>
> "We Make Software Work"
>