ebxml-cppa-negot message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Revised "Composition of an NDD for a CPA Template" section
- From: Martin Sachs <msachs@cyclonecommerce.com>
- To: ebxml-cppa-negot <ebxml-cppa-negot@lists.oasis-open.org>
- Date: Sun, 13 Jul 2003 23:51:06 -0400
Following is the revised NDD-composition section per my previous
posting. Comments, please.
Regards,
Marty
1.1 Composition of an
NDD for a CPA Template
Formally, the
negotiation defined in this specification begins when an offering
Party, Party A presents an initial offer, consisting of a
CPA Template and the corresponding NDD, to Party
B. If the Party A cannot obtain Party Bs
NDD, Party A can offer its own NDD. If Party
A can obtain Party Bs NDD, Party A SHALL make
use of Party Bs NDD in composing the NDD for the
initial offer to avoid situations in which the negotiation is certain to
fail. The new NDD would be a composite of the two sets of
requirements that is acceptable to both Parties as a starting
point in negotiation. In the rest of this section, the normative
statements are normative only if the offering Party has obtained
the other Partys NDD.
Party As taking Party B's NDD into account will
speed up convergence as well as recognition of fatal incompatibilities
and reduce the possibilities of unnecessary rejects during negotiation.
In other words, composing a CPA Template and combined
NDD before starting negotiation simplifies the Negotiation
Process by:
1. Removing subjects from negotiation that can be handled by simple matching.
2. Quickly recognizing the existence of fatal incompatibilities. For fatal incompatibilities, human to human contact to resolve the incompatibilities is RECOMMENDED.
In composing the NDD of the CPA Template, Party A SHALL exclude from the new NDD anything that Party A understands (from Party B's NDD) is not negotiable or is unacceptable to Party B. For example, for an enumeration, the new NDD SHALL include only those choices that are common to both of the original NDDs. For a range of values, Party A SHALL put in the new NDD only the common range. If, for some element, Party A had specified values of 1-9 and Party B had specified values of 3-12, the new NDD SHALL specify values 3-9. The intersection process might identify items with no common ground, making successful negotiation unlikely.
Party A SHALL NOT include items in the new NDD that were not in Party B's original NDD because Party B did not intend to negotiate on the items that it did not put in its original NDD. For those items that were not in Party B's initial NDD, Party A MUST either accept what is in Party B's CPP or MUST recognize that there is an irreconcilable conflict.
*************************************
Martin Sachs
standards architect
Cyclone Commerce
msachs@cyclonecommerce.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]