Re: Registry of Registries: RE: Comments on ebXML-V_0.7

[Duane Nickull <duane@xmlglobal.com>]

Hello John:

I agree.  EbXML should define the methodology for the deployment of the
Reg of Registries.  

Goxml.com is not an organization,  it is a product.  As such,  it can be
deployed by ???? to act as a Registry of Registries.  To my company, it
means one product sale - not a company maker or breaker.  We would not
want to operate it though.  The business model of who operates it may be
something to leave up to the Steering Committee.

"They mandate, we implement"  ;-)

Duane

"Petit, John" wrote:
> 
> That is good that Goxml.com can do this, but leaving this last lynch pin to
> global search to the private sector seems like ebXML would be stopping just
> short of much greater utility. A registry of registries seems to be part of
> the global e-commerce framework that ebXML is mandated to specify. This
> still means that organizations like Goxml will have to implement them and be
> able to exploit opportunities there, but a general registry of registries
> mechanism should still be described/specified at some level by ebXML. I
> would go even further to say that a trusted, neutral party should run the
> registry of registries, and that organizations like Goxml would access the
> data and value add.
> 
> -----Original Message-----
> From: Duane Nickull [mailto:duane@xmlglobal.com]
> Sent: Tuesday, July 25, 2000 11:05 PM
> To: srh@us.ibm.com
> Cc: Nieman, Scott; 'Petit, John'; ebXML-arch List
> Subject: Re: Registry of Registries: RE: Comments on ebXML-V_0.7
> 
> The concept of a Repository and registry Search Engine (a registry of
> registries) is
> not new.  We discussed this in our first draft (a registry must be able to
> conduct
> indexing of distributed repositories.
> 
> Goxml.com can do this.  All we have to do is expose the XML to the acceptor
> mechanism.   If you are interested in working on this concept,  I can
> arrange for an
> SDK from v 2.0 when its available.
> 
> Cheers
> 
> Duane
> *****************************************************************************
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized.
> 
> If you are not the intended recipient, any disclosure, copying, distribution
> or any action taken or omitted to be taken in reliance on it, is prohibited
> and may be unlawful. When addressed to our clients any opinions or advice
> contained in this email are subject to the terms and conditions expressed in
> the governing KPMG client engagement letter.
> *****************************************************************************