RE: latest Version; Chap16 Revision 1

Thanks.
Attached is rework 1 of Chapter 16 on TPA. Our TPA F2F meeting resulted in
a more clear across the board understanding of how it fits. We have also
made specific terminology adjustments, and are now formally distinguishing
between the profile function and agreement function.

Concerning the terminology and rest of the document,
"TPA" are now cast as as a larger scope that what ebXML is addressing, so
we only may need to adjust the usage of "TPA" elsewhere to indicate
something of the nature of... the context of support for TPA's in ebXML.

This is incomplete and I will send another before Monday, but given the
urgency of the calendar, here is what it is as of now.

(See attached file:
ebXML_TA_v0.8.72i_Chap16_Hinkelman_PartialRevision1.doc)

Thanks,
Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
[email protected], Fax: 512-838-1074



Brian Eisenberg <[email protected]> on 10/14/2000 01:06:47 AM

To:   "'[email protected] '"
      <[email protected]>
cc:   "'Klaus-Dieter Naujok '" <[email protected]>, "'Bruce Peat '"
      <[email protected]>, "'Jeff Suttor '" <[email protected]>,
      "'Duane Nickull '" <[email protected]>, "'David Webber '"
      <[email protected]>
Subject:  RE: latest Version




To all ebXML TA folks:

After a long week of nearly around the clock work, we have completely
revised the Technical Architecture specification. We worked through all of
the comments from the Quality Review team and have completely reworked the
ENTIRE TA spec. Aside from the Messaging Services section, this version
(0.8.72i) is essentially a new architecture document. That said, given the
extent of change from the previous version, no change log is included.

Here is the plan of action:

1. Please review the specification (TA team only) over the weekend. Please
post all comments to the TA discussion list. Please focus on the content of
the document, not the grammar and formatting.

2. Barring any show-stopping issues, our plan is to do a final revision on
Monday before submitting it to the Quality Review team (by end of day
Monday).

3. If approved by the Quality Review team (5 days after submitting we
should
hear back from them), we will post to the entire ebXML community for a
comment and review period.

4. After collecting comments from the review period leading up to Tokyo, we
(the TA team) will devote most of the Tokyo meeting incorporating comments,
and also having our liaisons work with each of the project teams to get
feedback on each of the respective major sections in the TA spec.

5. Drink lots of sake :-)

Before reviewing the specification, please keep the following in mind:

1. The glossary needs to be harmonized with this latest spec. This means
that the "bold italic" convention for glossary terms has NOT yet been
applied to this version of the TA spec. This task will be completed before
submission to the Quality Review team.

2. If your name is not on the list of participants, please email me at:
[email protected] with your name and company info. We did our best to
include everyone, but may have inadvertently overlooked a few TA team
participants. Please accept our apologies if we did so.

The specification is attached as a zipped Word doc named:
ebXML_TA_v0.8.72i.zip (620 K). If anyone has problems opening the .ZIP
archive, please send email to [email protected] and I will directly
email you a copy of the word file (1.9 MB).

I'd like to personally thank the following people for their hard work
during
the past week: Klaus-Dieter Naujok, David RR Webber, Duane Nickull, Jeff
Sutor, Chris Ferris, Karsten Riemer, and Bruce Peat.

Best Regards,

--Brian

Brian Eisenberg
Standards & Technology Liaison
DataChannel, Inc.

Microsoft Word 4