Re: FYI: Registry Services spec posted

[Martin W Sachs/Watson/IBM <mwsachs@us.ibm.com>]

Farrukh,

Sorry - I made a typo in pointing out a typo:

Line 365 and line 366:  This xml fragment says "RequestAcceptanceResponse"
on both lines.  The text says "RequestAcceptedResponse".

Regards,
Marty

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



Farrukh Najmi <Farrukh.Najmi@east.sun.com> on 09/08/2000 07:53:51 PM

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:   ebxml-tp@lists.ebxml.org, ebxml-transport@lists.ebxml.org, ebxml
      repository <ebxml-regrep@lists.ebxml.org>
Subject:  Re: FYI: Registry Services spec posted



Marty,

Thanks for your encouraging words and comments on this very early spec.

See my comments inline:

--

Regards,
Farrukh

Martin W Sachs/Watson/IBM wrote:

> Resending - tripped over the request filter (again.)
>
> Farrukh,
>
> Please note:  I am not currently subxcribed to the RegRep lixt. I suggest
> that you post this email to RegRep.

Done

>
>
> Please advise if you expect sufficient TPA discussion on RegRep so that I
> should subxcribe.  If possible, however, TPA discussion should be
directed
> to the TP list (as you have done in this case).

IMO, we in regrep would benefit from your keeping track of our progress to
keep things
aligned with TP. Note that the main focus for November is Doc management
and TPA
management. So yes, I would suggest you subscribe to regreg and help us
stay aligned.

I can post reference each new spec version to TP if you think it is
appropriate, but then
you could
not participate in the discussions. Your call.

>
>
> This spec looks very good.   I do have some comments:
>
> 1.2  Related ebXML Specifications
>
> Line 157:  The name "tpaML" at this time is the name for the IBM TPA
> proposal.  Chances are that the name of the ebXML TPA deliverable will
> probably be different.  I suggest that at this time, line 157 say "b)
> Trading-Partner Specification" and that the term "TPA" or "TPA
> specification" be used throughout in place of "tpaML".

Done in v0.5

>
>
> 3  Registration Process
>
> Line 246ff:  This is an excellent example of the use of tpaML.
>
> 3.1.1  UML Class Diagram
>
> Line 274, list item 4:  If this is intended to describe Scott Hinkelman's
> current TPA UML model, it is not correct.  The type argument designates
> whether the action is normal (obeys sequencing rules) or permitted to be
> issued while other requests are outstanding.
> RequestName defines the name of the action. RequestMessage defines the
> message type (i.e. schema name). I note that the action definitions in
the
> Registrar and Registrant service interface sections are correct.

I did not yet have a chance to see Scott's UML model so any resemblance is
accidental.
Will align better in the future if it makes sense.

>
>
> 3.2.3.3  Exception Responses Defined for Request
>
> Line 328:  The message type should be RequestErrorResponse.

Thanks for catching. Pitfall of cut and paste. Fixed

>
>
> 3.2.5  Registrar Service Interface in tpaML
>
> It should be noted that this XML fragment is tentative since the exact
> grammar of the ebXML TPA has not yet been defined.

Add footnote disclaimer with suggested text.

>
>
> 3.2.6  Registrant Service Interface in tpaML

>
>
> It should be noted that this XML fragment is tentative since the exact
> grammar of the ebXML TPA has not yet been defined.

Ditto

>
>
> Line 357:  Please change "Registrar" to "Registrant"

Again good eye. This could be quite confusing to the reader

>
>
> Line 365:  The text says RequestAcceptedResponse, not ...Accepted...
> Line 366:  The text says RequestAcceptedResponse, not ...Accepted...

Marty, I did not understand above comment. I dont see a problem. Please
clarify.

>
>
> 5  TPA Management Service Specification
>
> This is a good beginning.  It should be probably noted that this section
> will have to be revisited after the TP specification has been created.

Added note to that effect (minus the good begining part :-) ).

>
>
> Regards,
> Marty
>
>
*************************************************************************************

>
> Martin W. Sachs
> IBM T. J. Watson Research Center
> P. O. B. 704
> Yorktown Hts, NY 10598
> 914-784-7287;  IBM tie line 863-7287
> Notes address:  Martin W Sachs/Watson/IBM
> Internet address:  mwsachs @ us.ibm.com
>
*************************************************************************************

>
> Farrukh Najmi <Farrukh.Najmi@east.sun.com> on 09/07/2000 04:48:57 PM
>
> To:   "ebxml-tp@lists.ebxml.org" <ebxml-tp@lists.ebxml.org>
> cc:
> Subject:  FYI: Registry Services spec posted
>
> You can find it at the following URL:
>
>     http://lists.ebxml.org/archives/ebxml-regrep/200009/msg00006.html
>
> I would be very interested in your comments (on the regrep list)
> regarding the document in general,
> and TPA Manager functionality in particular.
>
> BTW, I took the liberty to list Marty and David as contributors because
> they provided me with a better
> understanding of requirements for regrep from a TP perspective. If I
> have misrepresented
> their thoughts, it is accidental and I will be glad to correct such
> mistakes.
>
> --
>
> Regards,
> Farrukh Najmi