OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-raws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [regrep-raws] FYI: WSDL, RAWS, and UDDI


The tModel looks good. A slightly modified version is follows:

<tModel tModelKey="uuid:---some unique key---">
    <name>ebXML Registry SOAP interface</name>
    <description lang="en">Represents the WSDL specification for the SOAP
interface to the OASIS ebXML Registry V2.0</description>
      <description lang="en">
Provides the URL to the WSDL specification for the SOAP interface to the OASIS
ebXML Registry V2.0

      <keyedReference tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4"
                keyName="uddi: A WSDL specification"

The changes are mostly to the name/description etc.

BTW I recall that you had said that you had registered the tModel(s) in a UBR
Could you please refresh my memory on exactly which artifacts were registered
(w/keys) and exactly which UBR
node it was registered with (test/production/V1/V2?).

Thanks in advance for the information.

"Munter, Joel D" wrote:

> I have been designing and constructing a tModel in UDDI based on the (RAWS)
> WSDL files posted on Oasis-Open.org.  I wanted to take some time to
> communicate to you a recommended (UDDI Best Practice) way to model this.
> The Oasis ebXML Registry TC has posted two WSDL files:
> The first is intended to be abstract and NOT bound to any particular
> transport
> http://www.oasis-open.org/committees/regrep/documents/2.0/services/Registry.
> wsdl
> The second is intended to be concrete and IS specific to a particular
> transport
> http://www.oasis-open.org/committees/regrep/documents/2.0/services/RegistryS
> OAPBinding.wsdl
> In UDDI, I have defined a link (it is called <overviewURL/>) within the
> tModel referencing the Oasis ebXML Registry TC WSDL file, named
> RegistrySOAPBinding.wsdl.  You should note that within this file is an
> import processing instruction that effectively pulls in the abstract
> definition Registry/WSDL file.
> <!--Import the definition of the abstract OASIS ebXML Registry services-->
> <import namespace="urn:oasis:names:tc:ebxml-regrep:services:wsdl:2.0"
> location="http://www.oasis-open.org/committees/regrep/documents/2.0/services
> /Registry.wsdl"/>
> This allows the abstract file to be "re-used" with any other "concrete"
> binding.
> The UDDI V1/V2 compliant tModel can then be modeled as shown below.
> <tModel tModelKey="uuid:---some unique key---">
>     <name>ebXML:RegistryServices</name>
>     <description lang="en">ebXML: Registry as Web Service</description>
>     <overviewDoc>
>       <description lang="en">ebXML: Reg/Rep Service (RAWS)</description>
>       <overviewURL>
> http://www.oasis-open.org/committees/regrep/documents/2.0/services/RegistryS
> OAPBinding.wsdl
>       </overviewURL>
>     </overviewDoc>
>     <categoryBag>
>       <keyedReference tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4"
>                 keyName="uddi: A specification"
>                 keyValue="wsdlSpecification"/>
> </tModel>
> Thanks,
> Joel Munter
> Distributed Systems, Intel Labs
> joel.d.munter@intel.com
> (480) 552-3076
> (602) 790-0924 (cell)
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC