ebxml-tp message


OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: Re: FW: requirements


Sorry, forgot to post my response to the list.

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
*************************************************************************************
---------------------- Forwarded by Martin W Sachs/Watson/IBM on 09/05/2000
12:12 PM ---------------------------

Martin W Sachs
09/05/2000 09:47 AM

To:   rachelf@ix.netcom.com
cc:
From: Martin W Sachs/Watson/IBM@IBMUS
Subject:  Re: FW: requirements  (Document link: Martin W. Sachs)

Rachel,

Thanks for your comment.  I am sure it will be fodder for discussion in the
TP team.

I must point out, however, that the cat got out of the bag when IBM made an
earlier version of the tpaML proposal publicly available.  We have already
had comments from lawyers,both positive and the kind you are referring to.
A couple of months ago two members of legalXML visited IBM research after
seeing the tpaML specification and were interested in the possibilities of
including this kind of function in what they are doing.

We definitely want to avoid the kind of contentiousness you are talking
about and can certainly change the name to protect ourselves.  We can also
ensure that we don't stray into the non-IT terms and conditions. However,
the lawyers are smart enough to recognize that a piece of paper or xml file
that documents what two parties have to define in common to communicate is
in fact an agreement.  I do think that ignoring existing contract
specifications such as IEEE 828 will only come back to haunt us.

You can run but you can't hide. :-)

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
*************************************************************************************



Rachel Foerster <rachelf@ix.netcom.com> on 09/04/2000 01:04:33 PM

Please respond to rachelf@ix.netcom.com

To:   "ebXML Trading Partner Agreement (E-mail)" <ebxml-tp@lists.ebxml.org>
cc:
Subject:  FW: requirements



Just a very quick comment about the proposed requirements. I am concerned
where it seems to stray into the area of establishing "legal" agreements
between two trading parties. In the past in a traditional EDI process,
whenever "legal" agreements regarding the electronic exchange of
information
entered into the picture, the lawyers/legal departments got involved. In
many cases, this served to "kill" the electronic relationship rather than
enhance or facilitate establishing it.

Furthermore, even though it might be informative to look at the 838 and
other transactions/messages, I remember when the 838 was being developed at
X12. It was an extremely contentious, controversial, and conflict-ridden
effort that took years for the 838 to finally make it through the full
approval process. And now, the U.S. government, which was the driver behind
the 838 is discontinuing its use. Reference info inserted below. I would
not
like to see this effort with ebXML get caught up in this type of quagmire.
Furthermore, since the focus for the ebXML TPA is now global, there are all
kinds of other "legal" issues from other governments, countries, etc. that
could cause the effort to never make it out of the gate.

Therefore, I would propose that the initial TPA requirements and ultimately
the tpa spec be very basic, simple and without any overt/covert legal
implications. Get something out of the gate, approved and in use and then
build on it as additional requirements, which can be generalized to a
global
community, are identified.

Rachel

> -----------------------------------------------------------------
> Meeting Minutes
>
> JECPO
> Central Contractor Registration VAN Meeting
> 23 June 2000
>
> The JECPO's CCR Van Town Hall Meeting met in Ft. Belvoir, Virginia on 23
> June 2000.  CAPT John Mauthe chaired the meeting.
>
> Summary of Discussions - Version 2.1, 4030, & the Future
>
> Ms. Hall discussed the introduction of CCR version 2.1 data elements to
be
> added to CCR.  These new elements necessitate upgrading the 838 from 4010
to
> 4030.  The CCR program anticipates that it will implement the upgrade to
> 4030 during the beginning of August, 2000 (stop accepting 4010 838's on 4
> Aug 00 and begin accepting 4030 838's on 7 Aug 00).  The 4030 upgrade
will
> also correct many of the inconsistency issues between the 838 and the CCR
> web page.  Testing will be available for the VANs prior to this cut-over.
>
> Additionally, Ms. Hall briefed that, due to planned CCR program processes
> improvements (specifically, moving the data validation process to be
> on-line), CCR will stop accepting 838's as a method of registration on 8
Jan
> 01.  At this time, all registrations (new and updates) will be entered
> through the web.  The VANs questioned the necessity of their community to
> upgrade to 4030 if the 838 would stop being accepted in January.  Ms.
Hall
> stated that CCR has to go to 4030 in order to make the implementation
> schedule for the new elements, but that it is each VANs business decision
> whether or not they wish to upgrade or to stop transmitting 838's to CCR.

-----Original Message-----
From: Martin W Sachs/Watson/IBM [mailto:mwsachs@us.ibm.com]
Sent: Friday, September 01, 2000 2:47 PM
To: ebxml-tp@lists.ebxml.org
Subject: requirements


I took a stab at converting the objectives list into a requirements
statement, attached.  It is probably too detailed and may require other
changes.  Please use it as a starting point for the requirements discussion
and let's discuss.

Regards,
Marty

(See attached file: partner-requirements.doc)

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

*********

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
****************************************************************************

*********








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC