[regrep] Solving Real Enduser Problems (Was Re: [regrep] Booz Allen Hamilton paper online)

[<duane@yellowdragonsoft.com>]

We have been working on XML witchcraft and found it is superior to all
other standards

:-)

On 10/21/2003, "Chiusano Joseph" <chiusano_joseph@bah.com> wrote:

>Revisiting a 6-month-old e-mail that David Webber sent back in April...
>
>Are we any closer now to David's vision than we were back then?
>
>Kind Regards,
>Joe
>
>David RR Webber - XML ebusiness wrote:
>>
>> Teams,
>>
>> Applying some rather brutal marketplace observations here - customers
>> could not careless either way - to them - its just a webpage thru a portal
>> to information.
>>
>> They could not careless if it is ebXML, UDDI, FAX group 4, XML-witchcraft
>> or similar.
>>
>> So the sooner we realize that the bigger challenge is getting ANY real
>> marketplace implementations on a large scale that solve REAL enduser
>> problems - and I'm talking about widespread use of classifications and
>> ability to traverse and discover information - rather than limited
>> experiments -
>> and user communities proactively working with registries to dynamically
>> grow uses - the sooner we collectively together move this whole
>> elephant forward - then that is the measure that I'm looking for.
>>
>> Frankly - its long overdue time - to stop thinking about separate items
>> of technology here - that customers can just turn away from as yet
>> another example of marketplace confusion - should I buy the
>> light-grey one or the dark-gray one?
>>
>> It's one boat - and we're all in it - so we'd better start figuring out
>> which directions to row in, and row collaboratively.
>>
>> We're hardly a good example of what we are preaching, eh?
>>
>> I think the engine should be in the front; no, it should be in the
>> back;  no it has to go in the middle;  will someone please define
>> an engine?  Are we building a car, a boat or an aircraft?
>>
>> If we could agree on key functionality that endusers need from
>> registries - the top 5 list - then combine resources to show
>> how to deliver those for the top 5 business use cases, using
>> combined OASIS Registry technologies - then we might
>> ctually surprise ourselves, no?
>>
>> DW.
>> ==========================================================
>> Message text written by "Patil, Sanjaykumar"
>> >
>> I think the article implicitly acknowledges your observation, as the very
>> first item under the "Interoperability Between Registries" in the article
>> is titled :- "Using UDDI to find ebXML Registry/Repository".
>>
>> In addition, the article is also bringing forth the "possibility" (aptly
>> under  a section - "Additional Possibilities") that an ebXML registry can
>> be used for discovering a UDDI Registry. I do not think it is very
>> confusing to think of this possibility. Imagine a scenario where there are
>> just so many publicly maintained and ubiquitous UDDI Registries out there
>> that an organization may have to depend upon its internal ebXML Registry
>> for browsing the many and possibly picking one amongst them. On the other
>> hand, I think the reasons are clear about why the organization may be using
>> ebXML Registry for its internal usage.
>>
>> <)