Re: Seeking lURNed advice on UDDI

[Iain W Fergusson <fergusson_iain@jpmorgan.com>]

Eric,

You wrote :
>My conjecture is that the uniqueness is defined by an
>URN parser for the UDDI registry software. The URN parsing
>is not going to be done at a HTTP transport level so IE and
>Netscape is not going to help you......

IMO each of the UDDI Operators ( IBM, Microsoft and Ariba ) will simply check
that the value of the xmlns attribute is "urn:uddi-org:api" and reject the
message if it is anything else.

There is a required generic="1.0" attribute on each of the UDDI calls, which is
how UDDI servers will differentiate between different versions of the UDDI
protocol in future. This means that xmlns="urn:uddi-org:api" need never be
changed to carry version information, so the URN should never need microparsed.

> On page 60-65, there is a further definition of tModel
> name uddi-org:type and additional types other than api.

I'm not sure what you mean by "additional types other than api".

The uddi-org:types tModel is a taxonomy that can be used to categorize other
tModels.
"api" is not a type in that taxonomy.

If you look at p.62, there are definitions of 2 tModels, uddi-org:inquiry and
uddi-org:publication.
These tModels represent the 2 parts of the UDDI API.
Both accept SOAP messages which use the "urn:uddi-org:api" namespace, but there
is nothing in UDDI to tell you that.
If you want to record that sort of detailed interface information, you need to
use WSDL rather than UDDI.

Hope this helps,

Regards,

Iain Fergusson
JP Morgan European Technology Centre





echiu@imservice.com on 26/04/2001 05:37:02

To:   tbray@textuality.com, xml-dev@lists.xml.org
cc:   paulclinger@yahoo.com (bcc: Iain W Fergusson)
Subject:  Re: Seeking lURNed advice on UDDI




[cc: Paul Kulchenko since he is extending his work on SOAP::Lite to support
UDDI,
and may have an implemented solution for the URN parser.]

Tim,

Your timing is excellent - I was spending most
of the day poring over this UDDI document to figure out
what's defined and how it works.

On page 10, there is a definition of xmlns:
"This special attribute is a required metadata element for all
messages....It is used to designate a URN value that is reserved for all
references to
the UDDI schema...required to be urn:uddi-org:api"

On page 60-65, there is a further definition of tModel
name uddi-org:type and additional types other than api.

My conjecture is that the uniqueness is defined by an
URN parser for the UDDI registry software. The URN parsing
is not going to be done at a HTTP transport level so IE and
Netscape is not going to help you......

Paul might have some insight into this as he is working
on an implementation in this area.

For more info on URN, there is the RFC (attached) and
this URL on naming and addresses
http://www.w3.org/Addressing/

Good luck, and share with me the knowledge if you
figure it how to implement the spec....

Eric Chiu
----- Original Message -----
From: Tim Bray <tbray@textuality.com>
To: <xml-dev@lists.xml.org>
Sent: Wednesday, April 25, 2001 7:13 PM
Subject: Seeking lURNed advice on UDDI


> I'm beginning to think that UDDI might be real useful.
>
> If you check out the spec-ware (PDF, grrrrrrrrrr) at
>
>   http://www.uddi.org/pubs/ProgrammersAPI-V1-1.pdf
>
> it turns out that the UDDI tagset is in a namespace whose
> name is "urn:uddi-org:api".  This makes me uncomfortable, but
> maybe that's just because I don't understand URNs.  First off,
> how unique is that?  It doesn't *look* very unique to a URN
> virgin.
>
> Second, does this mean that you can't use RDDL or even an
> ordinary web page to allow the eager-to-learn to discover
> some things about the namespace?   Or are have URN resolvers
> been quietly been springing up while I wasn't looking?
> (Neither IE nor Mozilla do anything useful for me with this
> particular URI).  -Tim
>
>
> ------------------------------------------------------------------
> The xml-dev list is sponsored by XML.org, an initiative of OASIS
> <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: xml-dev-request@lists.xml.org
>

Text - character set unknown