W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2004

RE: Issue 210: component equivalence

From: Tom Jordahl <tomj@macromedia.com>
Date: Wed, 23 Jun 2004 11:28:08 -0400
Message-ID: <CB1FF0A474AEA84EA0206D5B05F6A4CB08982169@S1001EXM02.macromedia.com>
To: "'Sanjiva Weerawarana'" <sanjiva@watson.ibm.com>, Tom Jordahl <tomj@macromedia.com>, "'Mark Nottingham'" <mark.nottingham@bea.com>, "'Roberto Chinnici'" <Roberto.Chinnici@Sun.COM>
Cc: "'www-ws-desc@w3.org'" <www-ws-desc@w3.org>


Doh!

Oh well....  I think we talk about this 2 years ago and I lost that battle.
:-)


--
Tom Jordahl
Macromedia Server Development

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Sanjiva Weerawarana
Sent: Wednesday, June 23, 2004 11:19 AM
To: Tom Jordahl; 'Mark Nottingham'; 'Roberto Chinnici'
Cc: www-ws-desc@w3.org
Subject: Re: Issue 210: component equivalence


That's still true :-( .. Mark's text said "two components of the
same type" .. so its still legit for an interface to be x:foo
and for a binding to be x:foo.

We've inherited that feature from XSD .. good or bad.

Sanjiva.

----- Original Message ----- 
From: "Tom Jordahl" <tomj@macromedia.com>
To: "'Mark Nottingham'" <mark.nottingham@bea.com>; "'Roberto Chinnici'"
<Roberto.Chinnici@Sun.COM>
Cc: <www-ws-desc@w3.org>
Sent: Wednesday, June 23, 2004 7:51 PM
Subject: RE: Issue 210: component equivalence


>
> +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 11:28:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:31 GMT