Service query in XRID

["Dave McAlpin" <Dave.McAlpin@epok.net>]

I don't really understand how a service offering of $r*a/QUERY would be
helpful. At that point, all you have left is a MIME type in the Type
element to say that what you really mean is UDDI (or whatever). Seems
like the Service element is where you'd want to say the service offering
was UDDI.

Dave

> -----Original Message-----
> From: Wachob, Gabe [mailto:gwachob@visa.com]
> Sent: Friday, June 04, 2004 9:59 AM
> To: Fen Labalme; Dave McAlpin
> Cc: xri@lists.oasis-open.org
> Subject: RE: [xri] Possible changes to XRI 1.0
> 


<snip>


> > Service query -
> >
> > We might want to define a service, perhaps $r*a/QUERY, at
> > which address
> > lies a discovery service (UDDI or something else) that can be
queried
> > and which would return the broker's available services.  Has
> > this been
> > considered and if so, would this be the proper way to implement it?
> 
> This is entirely reasonable, though I'm still not seeing the need for
it.
> I would think it would be specified as an additional XRI local access
> service (ie in addition to X2R). In fact, we could even define UDDI
access
> itself (with some means of processing the XRI into UDDI fields) as a
local
> access service.
> 
> This would NOT require rev'ing the core spec as the core spec
explicitly
> says that new local access services can be defined outside the core
spec.
> 
> 	-Gabe
>