- From: Tom Jordahl <tomj@macromedia.com>
- Date: Wed, 23 Jun 2004 09:51:34 -0400
- To: "'Mark Nottingham'" <mark.nottingham@bea.com>, "'Roberto Chinnici'" <Roberto.Chinnici@Sun.COM>
- Cc: "'www-ws-desc@w3.org'" <www-ws-desc@w3.org>
+1
This was a big pain implementing WSDL 1.1 processing - that everything could
have the same NCName.
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Mark Nottingham
Sent: Monday, June 21, 2004 8:14 PM
To: Roberto Chinnici
Cc: www-ws-desc@w3.org
Subject: Re: Issue 210: component equivalence
On Jun 21, 2004, at 4:58 PM, Roberto Chinnici wrote:
> Given that different top-level components must have different names,
> if you process a valid WSDL document and get some components out of it,
> you can decide whether two top-level components are equivalent just
> by comparing their {name} properties.
Oh, OK. how about:
--8<--
Note that because different top-level components (e.g., interface,
binding and service) are required to have different names, it's
possible to determine whether two of a given type are equivalent by
examining their {name} and {target namespace} properties.
-->8--
Thanks,
--
Mark Nottingham Principal Technologist
Office of the CTO BEA Systems
Received on Wednesday, 23 June 2004 09:52:09 UTC