Re: Proposal: A Registry Browser GUI tool

[Nicholas Kassem <nick.kassem@eng.sun.com>]

Please see my comments.

Nick

At 08:55 PM 9/13/2000 -0400, David RR Webber wrote:
>Message text written by Farrukh Najmi
> >
>My thought was that the tool would use ebXML TRP Messaging for exactly that
>reason.
>
>Nicholas Kassem wrote:
>
> > Getting back to the original question. I think having a regrep client
>(i.e.
> > tool) would be very nice particularly if it used ebXML TRP. I think this
> > could solve another problem we have, namely that there is talk in some
> > quarters that ebXML TRP is not suitable for B2C. I don't subscribe to
>this
> > notion and it would be very good if we could dispel this myth. Thoughts ?
> >
> > Nick
> ><
>
>OK - I view this somewhat differently.  TRP are using http / MIME based
>interchanges.  I see that RegRep can follow that same approach - but
>quiessentially the interaction model is different here, and therefore
>the envelope structures and dialogues are too.

Interesting - yes clearly we see this differently. How a regrep client 
accesses the regrep service should be no different than any other 
ebXML  Business Process. The regrep client is simply a specialized BP with 
specific QoS (from the underlying MS) requirements. I believe this is what 
was stated in the very early days of ebXML.


>Rik's model of TRP is a FedEx package and a Mailroom delivery.

Not familiar with "Rik's model" do you mean the ebXML TRP MS specifications ?


>RegRep is much more like the MickeyD's driven in.  When you hit
>that window you expect your query to be serviced.  Not that some
>driver will show up the next day with your burger!

I beg to differ. You seem to imply that ebXML TRP has some systemic 
performance limitations precluding its' use in B2C scenarios. I don't 
accept this assertion.