I'm ok as long as the technology does not change including current
terminology.
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
Martin W Sachs/Watson/IBM@IBMUS on 10/24/2000 05:13:48 PM
To: Scott Hinkelman/Austin/IBM@IBMUS
cc: Krishna Sankar <[email protected]>, [email protected],
Ebxml-Tp <[email protected]>, [email protected], Nick
Kassem <[email protected]>, Sigmund Handelman/Watson/IBM@IBMUS
Subject: RE: TPA Formation Track in POC
The version 0.0 document will be in the TP team's private page by the end
of the week, clothed its beautiful new ebXML cover, if I don't have too
many interruptions.
My suggestion was based on the presumed desirability of referencing an
ebXML document rather than an IBM document but if everyone is content to
leave it as is, so am I.
FYI, the ebXML-ized spec is
Collaboration-Protocol Profile and Agreement Specification
Version 0.0
*************************************************************************************
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
*************************************************************************************
Scott Hinkelman/Austin/IBM@IBMUS on 10/24/2000 11:06:26 AM
To: Krishna Sankar <[email protected]>
cc: Martin W Sachs/Watson/IBM <[email protected]>,
[email protected], Ebxml-Tp <[email protected]>,
[email protected], Nick Kassem <[email protected]>,
Sigmund Handelman/Watson/IBM@IBMUS
Subject: RE: TPA Formation Track in POC
I would consider this type of change artificial at this point given Nov 6.
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
Krishna Sankar <[email protected]> on 10/23/2000 08:40:54 PM
To: Martin W Sachs/Watson/IBM@IBMUS, [email protected]
cc: Ebxml-Tp <[email protected]>, [email protected], Nick
Kassem <[email protected]>, Scott Hinkelman/Austin/IBM@IBMUS,
Sigmund Handelman/Watson/IBM@IBMUS
Subject: RE: TPA Formation Track in POC
Marty/Mark,
There are a few places in the POC document where TPA and PP are
mentioned.
There are a few xml documents where we need the "tpa_1_0_6.dtd". Either we
change all references to the new ones (whatever they are) or keep the old
ones. The diagrams and the write-ups as well as the dtds should reflect the
same vocabulary.
I suggest we keep the old ones (TPA,PP et al) unless we have the
version
0.0 documents including the DTD. We want a consistent terminology across
all
our documents.
Cheers
-----Original Message-----
From: Martin W Sachs/Watson/IBM [mailto:[email protected]]
Sent: Monday, October 23, 2000 12:08 PM
To: [email protected]
Cc: Ebxml-Tp; [email protected]; Nick Kassem; Scott
Hinkelman/Austin/IBM; Sigmund Handelman/Watson/IBM
Subject: Re: TPA Formation Track in POC
This writeup looks good and is in reasonable accord with the current TP
team thinking and terminology. I have the following suggestions:
The TP team has agreed to adopted the tpaML proposal as version 0.0 of
its specification. We will have version 0.0 (with an ebXML cover and a
new title) for the Tokyo meeting. Therefore, I suggest replacing all
reference to tpaML 1.0.6 by "ebXML Trading-Partner Specification, ver.
0.0".
In the figure, I suggest replacing PP by CPP in all boxes, to match the
terminology in the writeup and that used by the TP team.
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
****************************************************************************
*********
Mark Hale <[email protected]> on 10/23/2000 12:52:27 PM
Please respond to [email protected]
To: Ebxml-Tp <[email protected]>, [email protected]
cc: Nick Kassem <[email protected]>
Subject: TPA Formation Track in POC
In the POC, we have been working to finalize the tracks that will be
demonstrated and met for a F2F this past week. There will be three Tracks
in the POC:
Track 1: TPA Formation
Track 2: Retail Industry Use Case
Track 3: Automotive Industry Use Case
I've re-written the TPA Formation track to be consistent with terminology
found in the other working groups. I ask you to please review the attached
document and make comments. Please keep in mind that the POC does not
write
specifications but, rather, implements them. We tried our best to assemble
a baseline that represented the workings of BP/TP that ties into the other
two tracks. We hope to see the scenario expanded in Vancouver.
Please post comments to [email protected].
Thanks,
Mark
________________________________________________________________________
Mark A. Hale 650-940-4155 tel
Standards Architect 650-230-4065 fax
Ajuba Solutions [email protected]
2593 Coast Avenue http://www.ajubasolutions.com
Mountain View, CA 94043
