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

[Peter Kacandes <Peter.Kacandes@EBay.Sun.COM>]

In the eCo sense, that was the whole purpose of the Network layer and the design 
of the network layer was such that the mechanism used at the network layer to 
organize the markets in that network were equally applicable to a network of 
networks. Anybody who wanted to could then take it upon themselves to organize 
the network according to whatever principle they wanted. If the wanted to try 
and index all of the networks in their network, then they could. We always 
figured that that would be the role that the search engine folks would play.

I was certainly expecting that a corrollary in ebXML would exist vis-a-vis the 
registry of registries. Same concept, but I don't think there has to be one 
central one that has them all. That to me seems antithetical to 'Net principles. 
Somebody might want to be a registry of business registries, and somebody else 
might want to be a registry of non-profit registries etc., etc. Of course, 
you've got to figure that somebody will want to try to be the registries of as 
many registries as they can.

regards

pk

ps apologies for not being particularly active lately, but I've been told that 
my actual day to day job has to take precedence.

>Date: Wed, 26 Jul 2000 15:37:48 -0400
>From: "Petit, John" <jpetit@kpmg.com>
>Subject: RE: Registry of Registries: RE: Comments on ebXML-V_0.7
>To: "'Duane Nickull'" <duane@xmlglobal.com>
>Cc: srh@us.ibm.com, "Nieman, Scott" <Scott.Nieman@NorstanConsulting.com>, 
ebXML-arch List <ebxml-architecture@lists.ebxml.org>
>MIME-version: 1.0
>List-Owner: <mailto:ebxml-architecture-help@lists.ebxml.org>
>List-Post: <mailto:ebxml-architecture@lists.ebxml.org>
>List-Subscribe:  
<mailto:ebxml-architecture-request@lists.ebxml.org?body=subscribe>
>List-Unsubscribe:  
<mailto:ebxml-architecture-request@lists.ebxml.org?body=unsubscribe>
>List-Archive: <http://lists.ebxml.org/archives/ebxml-architecture>
>List-Help: <http://lists.ebxml.org/doc/email-manage.html>, 
<mailto:ebxml-architecture-request@lists.ebxml.org?body=help>
>
>Operations aside, the question is whether we should address the registry of
>registries in one of the working groups, and whether Arch should touch upon
>it. As this seems fundamental, I would think the sooner this gets decided
>upon the better.
>
>Also, back to your original Arch doc excerpt that "a registry must be able
>to conduct indexing of distributed repositories." This is only dealing with
>a single registry for a give set of repositories. The ebXML world will have
>many, many registries and associated repositories. The registry of
>registries allows for search across the entire set of ebXML repositories,
>giving cohesion and unification to the ebXML framework for e-commerce. This
>was not addressed in the Arch doc. Do you think that it should be? 
>
>-----Original Message-----
>From: Duane Nickull [mailto:duane@xmlglobal.com]
>Sent: Wednesday, July 26, 2000 11:32 AM
>To: Petit, John
>Cc: srh@us.ibm.com; Nieman, Scott; ebXML-arch List
>Subject: Re: Registry of Registries: RE: Comments on ebXML-V_0.7
>
>
>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.
>>
>****************************************************************************
>*
>*****************************************************************************
>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.         
>*****************************************************************************

Peter Kacandes

Application Planning, Architecture & Strategy	phone number: 	X36529
WWOPS IT/Supply Chain Management		email:	peter.kacandes@ebay