Re: [ws-brsp] Proposed resolution for: Fw: Multiple inline schema's with the same targetNamespace doesn't work properly

[Doug Davis <dug@us.ibm.com>]

this looks fine to me.

thanks
-Doug
________________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.

Jacques Durand ---09/26/2012 05:09:53 PM---After a bit of investigation on the code of previous tools, here would be a proposed response to Ger

From: Jacques Durand <JDurand@us.fujitsu.com>
To: Doug Davis/Raleigh/IBM@IBMUS, "ws-brsp@lists.oasis-open.org" <ws-brsp@lists.oasis-open.org>,
Date: 09/26/2012 05:09 PM
Subject: [ws-brsp] Proposed resolution for: Fw: Multiple inline schema's with the same targetNamespace doesn't work properly
Sent by: <ws-brsp@lists.oasis-open.org>

---

After a bit of investigation on the code of previous tools, here would be a proposed response to Gerwin, to be approved by TC:

1)      Are multiple inline XSD Schema's with the same targetNamespace allowed? Are there any references available?

WS-BRSP: yes according to WSDL1.0 specification. The profiles do not restrict this at all.

2) Can you confirm that the problem reported above is a bug in the Analyzer? If this is true, we can still claim to be Basic Profile compliant.
WS-BRSP: yes, a bug: the current Analyzer should not fault that – it goes beyond what the test assertions require. When validating against one of these schema types, it appears that only the first type that matches the namespace is considered in the current code. Because of this, it is advised to redo the tests after successively permuting circularly all these same-namespace types, to make sure that the failure disappears when the type is at a place where the Analyzer can catch it.
 

3) If this is a bug, can it be fixed?
WS-BRSP: yes – but we can’t commit to a fixing date yet, as we are in transition regarding the management of source code and builds. At the next meeting early November latest, we should be able to commit to a date. We may need to rely on the collaboration of the user in order to verify the fix. We can also provide guidance as exactly what change needs be done if/when the source code becomes available to end-users.
 
Let me know if any comment / modification needs be done on this.
 
Thanks
-jacques

From: ws-brsp@lists.oasis-open.org [mailto:ws-brsp@lists.oasis-open.org] On Behalf Of Doug Davis
Sent: Wednesday, September 05, 2012 1:08 PM
To: ws-brsp@lists.oasis-open.org
Subject: [ws-brsp] Fw: Multiple inline schema's with the same targetNamespace doesn't work properly
 

Forwarding to the new group so that we don't forget that we owe Gerwin an official response. 
-Doug 


---------- Forwarded message ----------
From: Gerwin Jansen <gjansen@cordys.com>
Date: Mon, Jun 4, 2012 at 10:55 AM
Subject: Multiple inline schema's with the same targetNamespace doesn't work properly
To: Scott McGrath <scott.mcgrath@oasis-open.org>


Hi WS-I members,

I created a WSDL with multiple inline schema's with the same targetNamespace. WSDL 1.1 is not very clear regarding this, but this is corrected in WSDL 2.0, which explicitly allows this: 
A WSDL 2.0 document may define multiple inline schemas in its types element. The two or more schemas may have the same target namespace provided that they do not define the same elements or types. It is an error to define the same element or type more than once, even if the definitions are identical. 

This gives me the impression that WSDL 1.1 was also intended to allow this, although not explicitly stated. 
Basic Profile Version 1.1 doesn't seem to restrict WSDL 1.1 in any way regarding multiple schema's with the same targetNamespace. 
This is also confirmed by the fact that the Analyzer tool allows me to refer to different inline XSD Schema's with the same targetNamespace from a Message Part element. 
But when it comes to a reference from one inline XSD Schema to another XSD Schema, it is failing saying: 
Error: src-resolve: Cannot resolve the name 'same:addressElement' to a(n) 'element declaration' component. 

I included the required Analyzer config file, WSDL file, console output and report in the attached zip file. 

Given this scenario, I have the following questions: 
1) Are multiple inline XSD Schema's with the same targetNamespace allowed? Are there any references available? 
2) Can you confirm that the problem reported above is a bug in the Analyzer? If this is true, we can still claim to be Basic Profile compliant. 
3) If this is a bug, can it be fixed? 

Kind regards, 
Gerwin

Gerwin Jansen
Software Engineer
gjansen@cordys.com
www.cordys.com
T +31 341 375685 • M +31 6 13746668 

 

 CORDYS – My Business Platform