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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

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

Subject: Re: [ebxml-dev] Distributive Directories ?

Title: RE: [ebxml-dev] Distributive Directories ?
Yes, certainly but it also some great lessons.
Firstly, X.500 was a great idea. Problem was that it just didn't work that well and was enourmously expensive. One needed a computer like a Wang or a Tandem or an IBM to run it. They certainly weren't cheap.
It needed really expensive people to get it working.
They were early pioneering days. I remember that at that time a 2400 baud modem cost around $1000. I remember a company that I worked for paying around $56,000 per annum for a 48k data line between two cities.
Now a 300k DSL line can cost as little as $50 per month.
Then the Computer cost $300,000+. Now the same power costs $900.
So therefore, the commercial environment in which a Distributed Directory could exist now is entirely different than the days of X.400/X.500 that really never were.
As an architecture, I suggest that Distributed Directories suit the needs of Medium/Small enterprises better than centralised directories and that the whole nature of computers is different now.
I'm not suggesting that X.400/X.500 should be resurected, simply that we have a computing environment of the future is one where all the computers will be permenantly connected to each other in much the way that the inventors of X.500 had hoped.
As for commercial success, that's another thing. We first need to see a few commercial releases and watch to see how they go.
Best Regards
David Lyon
Product Manager
----- Original Message -----
Sent: Friday, April 19, 2002 11:23 PM
Subject: RE: [ebxml-dev] Distributive Directories ?

Doesn't the history of X.400/X.500 give us some reason to question the commercial success of Distributed Directories and the administration thereof ?


-----Original Message-----
From: David Lyon [mailto:david.lyon@globaltradedesk.com]
Sent: Friday, April 19, 2002 1:10 AM
To: andrzej@chaeron.com; ebxml-dev@lists.ebxml.org
Subject: [ebxml-dev] Distributive Directories ?


You've raised some really good points.

Now I don't profess to be an expert in UDDI or WSDL but I've always liked
the general philosophy behind ebXML. Generally speaking the idea of a
registry is a good one, it's virtually an extension of the Trading Partner
information that is kept in most of the old EDI software programs.

Has anybody ever considered a Distributive Directory ?

This is now possible and viable with broadband and offers advantages for
small business over a centralised registry.

The philosophy behind a Distributive Directory is that a company joins an
Exchange and when they do their details are broadcast (name, address,
net-address) to everybody on the exchange.

The details of the new company are stored in the database of all the
companies that are connected.

The result is that within a city or region, everybody can have the contact
details of everybody else and their pricelist/catalog.

One could connect an entire city so that everybody could share everybody
elses information.

With broadband transmission speeds, a 2gig/hertz processor and a 70 gig hard
drive, this seems to be readily achievable. That btw, is the hardware that
the local Plumber can afford.

Surely this sort of technology is on the verge of becoming a reality. There
are some among us who have seen it in operation.

Comments ?

----- Original Message -----
From: "Andrzej Jan Taramina" <andrzej@chaeron.com>
To: <ebxml-dev@lists.ebxml.org>
Sent: Friday, April 19, 2002 2:10 PM
Subject: Re: [ebxml-dev] RE: [EDI-L] Article on ebXML Core Components

> > > Will the registry/repository concept for ebXML eventually merge with
> > > counterpart defined for UDDI/Web Services ?
> There are some fundamental issues that might prevent this as well as the
> ones.
> UDDI is a registry only...no repository, where as ebXML has both.  That
could (and
> may need to be) rectified by the UDDI spec (imagine 10,000 WSDL
> pointed to by a UDDI rep.....how would you manage the storage of all these
in a large
> corporation in a doable fashion?  Put them on different web servers all
over the
> company?  Not likely......some form of centralized repository will
eventually be
> needed to complement UDDI).
> The big issue is that UDDI has been designed to be a "global" public
> (though that does not preclude private implementations), with support for
> and distribution of nodes (meaning that the distributed system appears as
a single
> global registry).  Whereas ebXML RegRep has been designed as a
> registry, to target a specific group of parties with a common interest (a
supply chain,
> industry vertical, etc.) and no provision has been made for
> Those are big chasms to cross in trying to merge the two together.
> philosophical roots.
> Best practice seems to suggest that you use ebXML RegRep for community
> and use UDDI more globally which in turn has a "pointer" to the specific
> ...Andrzej
> Chaeron Corporation
> http://www.chaeron.com
> ----------------------------------------------------------------
> The ebxml-dev list is sponsored by OASIS.
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.ebxml.org/ob/adm.pl>

The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC