The W3C Web Services Description Working Group
(http://www.w3.org/2002/ws/desc/) is developing WSDL 1.2.
And, by the way, WSDL 1.1 is not repetitious. It is modular. It describes an
abstract service (<portType>), it maps that abstract service to concrete
protocols (<binding>), and it defines a specific service implementation that
implements specific bindings of an abstract service (<service>). The
<portType> and <binding> elements are reusable resources and are usually
defined in separate files. The <service> definition pertains to a single
service implementation. Different service providers can implement the same
service type. The new WSDL to UDDI mapping describes how to register
<portType> and <binding> definitions as separate tModels, and it allows
users to search for services that implement a standard <portType> and
support a desired <binding>.
Anne
----- Original Message -----
From: "David RR Webber - XML ebusiness" <>
To: "Chiusano Joseph" <>
Cc: "Duane Nickull" <>;
<>; "Anne Thomas Manes" <>
Sent: Wednesday, July 02, 2003 12:29 PM
Subject: Re: [regrep] UDDI as the registry for ebXML components: Typo?
> Joe,
>
> +1
>
> This is the way to go IMHO too. What's more we could have a
> joint task-force between UDDI and ebXML registry teams to
> deliver this. WSDL already provides us with a significant piece
> of this - and of course we've already got the WSDL definitions
> for these started. Maybe just that first step would be very
> helpful - providing a combined WSDL definition file....
>
> Thanks, DW.
>
> p.s. BTW - who designed WSDL? Its very hard to get an
> elegant looking WSDL file - maybe we can provide some
> feedback on this - there's a highlevel of redundancy in the
> WSDL syntax repetition of everything! WSDL V2.0 anyone?!?
> ======================================================
> Message text written by "Chiusano Joseph"
> > A programming language-agnostic mechanism
> for accessing registries (call it "GRI" or "Global Registry Interface").
> This way, one could send a query to a registry for a Web service
> description and not know or care whether the query is processed by a
> UDDI Registry, or an ebXML Registry (or a vendor product that is not
> UDDI- or ebXML-compliant but conforms to GRI).<
>
