RE: Trading-Partner Requirements document

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

Tony,

This is a very good set of comments.  Here are some rejoinders, embedded in
your text. I will take them up at the conference call today.

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



Tony Weida <TonyW@EDIFECS.COM> on 10/04/2000 10:48:59 AM

To:   Martin W Sachs/Watson/IBM@IBMUS, ebxml-tp@lists.ebxml.org
cc:
Subject:  RE: Trading-Partner Requirements document



Some comments on the requirements document ...

General

The document frequently refers to processes, sometimes qualified as
application process, discovery process, internal process, back end process,
bilateral process, business process or non-business process.  It would be
helpful to agree on a small, consistent set of names and definitions for
"process" and related terms.  I'd be glad to work on that.   As an example,
I like to think of internal (business) processes interacting by means of a
(business) collaboration protocol:  Each business collaboration protocol
prescribes a particular set of interactions between two or more internal
business processes operated by independent business entities that
collaborate to reach common or complementary goals.  This terminology is
consistent with the ebXML  Business Process Metamodel.

MWS:  I agree and will do this.  Discovery Process is already defined.
Business
process and non-business process were supposed to be deleted and replaced
by
Application Process.


Introduction

p 1, The purpose ... is to define the requirements for the "Party Profile"
and "Party Agreement" (not just Party Profile)

MWS:  true.


Definitions

p 2, definition 6 (Partner): Should say "A party that is involved in a
Partner Agreement." (not Party Agreement)

MWS:  Thanks (typo).

As mentioned above, process and related terms should be individually
defined.


Requirements

There are two separately numbered sets of requirements, the first for
specification of documents, and the second for the overall specification.
For convenient reference, I'd prefer to have a unique identifier for each
requirement (either by using a single numeric sequence, or by uniquely
prefixing each separately numbered subset of the requirements).

MWS:  You are probably right but I don't know how to make Word add the
prefix in a numbered list.  To use a single numbered list, we would have to
eliminate the global distinction between the documents and the requirements
on the
specification and prefix every item by "The document shall" or "the
specification
shall", which is a bit clumsy.  Any other suggestions are welcome.

p 4, specification requirement 7: should say "a predefined model of an
Application Process"  (as the term is used in the requirements doc), not
process in general.

MWS:  Correct (another typo)


Ideas for Later Phases

Idea 8: As an example of multiple service interfaces, I'd say "A single
service interface might include ..."

MWS:  I agree with the problem but not the solution.  The correct
solution is to append the following to the second sentence: ", each one
defined in a separate service interface".

Respectfully,
Tony Weida
Edifecs Commerce

> -----Original Message-----
> From: Martin W Sachs/Watson/IBM [mailto:mwsachs@us.ibm.com]
> Sent: Tuesday, October 03, 2000 3:50 PM
> To: ebxml-tp@lists.ebxml.org
> Subject: Trading-Partner Requirements document
>
>
> I have attached the latest version of the Trading-Partner Requirements
> document.
>
> Since no comments were received on the prior version, the changes consist
> only of a few minor wording changes and two new explanatory paragraphs
for
> Requirements numbers 4 and 5.
>
> I expect that we can ratify this document at the face-to-face and move on
> to beginning to produce a specification.
>
> 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
> ******************************************************************
> *******************
>
>  << File: partner-requirements.doc >>