Re: How is this supposed to work?

[Farrukh Najmi <Farrukh.Najmi@east.sun.com>]

David, see my comments inline.

David RR Webber wrote:

> <snip>
> At some point we need to raise this as an issue with TRP.
>
> Unlike TRP exchanges that require some business process,
> RegRep Requests are to the large part automated.

The RegRep client-to-servcie interaction are a business process like any other
business process. The process just happens to be defined by ebXML RR instead of
RosettaNet or someone else. They are no more (or less) automated than any other
business process.

> This therefore leaves open the possiblity that inadvertently or
> deliberately someone could exploit this to send junk messages
> endlessly to someone else.  This is a 'feature' of TRP that
> RegRep does not need IMO.

Some one can just as well send junk messages to a party using a non-RegRep
business process. The issues are no different in my mind between 2 parties than
between RR client and RR service.

>
>
> It also highlights the need for us to examine in a transport
> neutral way exactly what functionality we really need for RegRep.
> I'd be much more comfortable with creating such a transport
> requirements base set.  Then allowing people to show how
> TRP fulfils that, and so on.  Time did not permit this for the PoC
> but this should definately be revisited.

I believe in requirements driven developement. This is an RR issue and I
believe there exists at least 3 places where RR requirements have been
articulated (the TA document, the RR Part 1, the informal requirements doc that
I had published.)

>
>
> Thanks, DW.

Thanks.

--
Regards,
Farrukh

begin:vcard 
n:Najmi;Farrukh 
tel;fax:781-442-1610
tel;work:781-442-0703
x-mozilla-html:TRUE
url:www.sun.com
org:Sun Microsystems;Java Software
adr:;;1 Network Drive, MS BUR02-302;Burlington;MA;01803-0902;USA
version:2.1
email;internet:najmi@east.sun.com
fn:Farrukh S. Najmi
end:vcard