more on the FW: Draft RegRep and TRP transport harmonization

[Rik Drummond <rvd2@worldnet.att.net>]

rr needs synch services as noted below from trp.  best regards, rik

-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@east.sun.com]
Sent: Monday, September 18, 2000 11:58 PM
To: Rik Drummond
Subject: Re: Draft RegRep and TRP transport harmonization



Rik,

You are right that #2 is more relevant to TRP since all Registry Services
(RS)
are accessed over ebXML TRP

So RS is your customer.

Please note that the one important issue TRP needs to keep in mind is that
there
are some TRP interactions
between RS clients and RS that need to be synchronous in nature. I assume
this
is not a problem and may
just be an attribute of the Request specification in the TPA.

--
Regards,
Farrukh

Rik Drummond wrote:

> thanks for the update. I assume the #2 spec is the one we in trp want to
> read? if so let me know the url or just send it to me and i will get it
out
> to the group...
> rik
>
> -----Original Message-----
> From: Farrukh Najmi [mailto:Farrukh.Najmi@east.sun.com]
> Sent: Monday, September 18, 2000 11:34 PM
> To: Rik Drummond
> Subject: Re: Draft RegRep and TRP transport harmonization
>
> Rik,
>
> FWIW, RR has two specs:
>
> 1. Repository Information Model Specification v0.1 (released today)
> 2. Registry Services Specification v0.5 (will be released tomorrow
>
> For the immediate future (tokyo POC) these are the only documents that are
> both
> sanctioned
> by the RR team and relevant to any other WG.
>
>
> I look forward to seeing you at the Dallas f2f.
>
> --
> Regards,
> Farrukh
>
> Rik Drummond wrote:
>
> > ok we will wait for an official document from RegRep.... Thanks, Rik
> >
> > -----Original Message-----
> > From: Farrukh Najmi [mailto:Farrukh.Najmi@east.sun.com]
> > Sent: Monday, September 18, 2000 10:45 PM
> > To: David RR Webber
> > Cc: ebxml transport
> > Subject: Re: Draft RegRep and TRP transport harmonization
> >
> > Please ignore this posting and attached document. It is not sanctioned
by
> > the regrep
> > team. I apologize for the FUD this posting is creating. I am frustrated
as
> > hell and
> > have raised this issue to the right people.
> >
> > --
> > Regards,
> > Farrukh
> >
> > David RR Webber wrote:
> >
> > > Attached is the first draft of interface spec's for RegRep
> > > using WebDav DASL -
> > >
> > > WARNING - this has NOT been reviewed
> > > in detail by RegRep yet.
> > >
> > > You will need to review the DASL spec's at
> > >
> > > http://www.webdav.org  to understand the full fucntionality
> > >
> > > here - as I have assumed this knowledge.
> > >
> > > Also - I have NOT focused at all in harmonization with
> > > TRP - that's why I have the draft!
> > >
> > > First I just focused on solving the RegRep issues - and
> > > that is a pile of work still - especially on the Add side;
> > > Query is relatively clear.
> > >
> > > So - I'm looking for positive input here to augment
> > > the RegRep functional with better and more rich
> > > transport details.
> > >
> > > Please supply XML based examples whereever
> > > possible.
> > >
> > > Thanks, DW.
> > >
> >
>   ------------------------------------------------------------------------
> > >                                  Name: RegRep-Primitives-V021.PDF
> > >    RegRep-Primitives-V021.PDF    Type: Portable Document Format
> > (application/pdf)
> > >                              Encoding: base64



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