I think what you will see is an emergence of semi-private registries that will check their constituents (industry-specific, country-specific, etc.) The other option is to follow the DNS growth pattern, ie. here come the lawsuits.
The standards for naming are already there - you guys should be familiar with the UN/SPSC and like efforts. The problem is in trying to deal with the taxonomy data on a large level - it gets progressively harder the more data you have. And there are companies working on that problem!
On the whole I would agree - things are a bit immature for now, but as the big players try to get useful products out, the bugs will get ironed out.
This is after all why they are adopting UDDI over ebXML.
Consider a DNS registry. This isn't all that different. It is a considerably more complex, because it can describe a number of different services (see the notion of records in DNS though).
If you do make it a global registry, the concept of yellow/white pages makes sense: these are essentially just different queries against the database. You surely have used the White/Yellow Pages in your house?
As a developing standard, of course there is no RFC for this yet. It is still being hammered out - look at the specs!
Lastly, the argument regarding MS is somewhat empty... MS can't drive standards adoption on a B2B level - that's not their space. The only chance they have in driving these is by making them into community efforts. If MS is willing to spend money to do something good, why not take it???
As a side note, if you think this is a complex spec you should look at UDDI's superset: ebXML
If you have done anything with e-commerce tools today you should know what a bloody mess it the whole area is. No one can afford to deal with partners electronically, because it takes so much IT effort to get them up and running.
If UDDI catches on, adherence will become mandatory. If that isn't good news to the legions of the unemployed tech workers, I don't know what is. Imagine if every one of those mom-and-pop shops suddenly realizes that their biggest customer will walk away unless they adopt this UDDI/ebXML thing...
Anotherwords, you people should be reading up on this and gaining some expertise pronto. Help spread the word.
Slashdot Mirror
The standards for naming are already there - you guys should be familiar with the UN/SPSC and like efforts. The problem is in trying to deal with the taxonomy data on a large level - it gets progressively harder the more data you have. And there are companies working on that problem!
On the whole I would agree - things are a bit immature for now, but as the big players try to get useful products out, the bugs will get ironed out.
This is after all why they are adopting UDDI over ebXML.
Needless to say this is also a considerably cheaper solution...
Consider a DNS registry. This isn't all that different. It is a considerably more complex, because it can describe a number of different services (see the notion of records in DNS though).
If you do make it a global registry, the concept of yellow/white pages makes sense: these are essentially just different queries against the database. You surely have used the White/Yellow Pages in your house?
As a developing standard, of course there is no RFC for this yet. It is still being hammered out - look at the specs!
Lastly, the argument regarding MS is somewhat empty... MS can't drive standards adoption on a B2B level - that's not their space. The only chance they have in driving these is by making them into community efforts. If MS is willing to spend money to do something good, why not take it???
As a side note, if you think this is a complex spec you should look at UDDI's superset: ebXML
If UDDI catches on, adherence will become mandatory. If that isn't good news to the legions of the unemployed tech workers, I don't know what is. Imagine if every one of those mom-and-pop shops suddenly realizes that their biggest customer will walk away unless they adopt this UDDI/ebXML thing...
Anotherwords, you people should be reading up on this and gaining some expertise pronto. Help spread the word.