RE: [ebxml-cppa-comment] Re: About negotiation algorithm

[Martin Sachs <msachs@cyclonecommerce.com>]

Dale is correct.  However I believe that the SC will have to give
some consideration to the strategy layer in order at least to determine
what, if any, impediments the present draft is putting in the way of
interoperably negotiating without each party revealing its strategy. The
SC will have to do some work on this, if only to determine whether
rechartering the CPPA TC is necessary.

Regards,
Marty

At 11:30 AM 4/22/2004, Dale Moberg wrote:

I think that if the Negotiation subteam were to extend its scope to utility functions, algorithms for optimization, and tactics of offers,
acceptances, and counterproposals, that we definitely should allow separate undisclosed computational procedures. The NDD probably
leaks information about each party's utility assessments, but not in any great detail or completeness. Whether we would specify a public
default procedure would IMO require a recharter of CPPA to enlarge its scope. Currently the negotiation protocol (understood as
the messages and their exchange patterns) is what is in scope.  Comments?
 
Dale Moberg

-----Original Message-----

From: Vetter, Michael [mailto:Michael.Vetter@iao.fraunhofer.de]

Sent: Thursday, April 22, 2004 2:08 AM

Cc: ebxml-cppa-comment

Subject: AW: [ebxml-cppa-comment] Re: About negotiation algorithm

Hi Marty and Kukoc

 

I am a little confused by your definition of a negotiation algorithm.

In my understanding the strategy in a competitive scenario is purely private and no part of it must be known to the other party. If the parties want to cooperate and to reach a global optimum of the negotiation result they could reveal their utility functions and use a common strategy to compute the result.

The protocol should cover all rules about the order of messages and their content.

A given strategy can be implemented by a large number of algorithms that require more or less resources like processing power and memory.

 

A specification for the strategy part is only needed if you want to provide a standard strategy for negotiation which can be adapted with parameters.

 

Best regards

 

Michael Vetter

____________________________________________________________________________

        Dipl.-Inform. Michael Vetter

        CC Electronic Business Integration

        Fraunhofer IAO (Institut fuer Arbeitswirtschaft und Organisation)

        mail:           Nobelstrasse 12, D-70569 Stuttgart, Germany

        phone:      +49 (0) 711 970 2324

        fax:            +49 (0) 711 970 5111   

        email:      Michael.Vetter@iao.fraunhofer.de

        www:          www.ebi.iao.fraunhofer.de

____________________________________________________________________________

-----Ursprüngliche Nachricht-----

Von: Martin Sachs [mailto:msachs@cyclonecommerce.com]

Gesendet: Mittwoch, 21. April 2004 19:35

An: kukoc-url

Cc: ebxml-cppa-negot; ebxml-cppa-comment

Betreff: [ebxml-cppa-comment] Re: About negotiation algorithm

Hi, Kukoc

Thank you very much for  your question about the negotation algorithm.

Yes, negotiation strategy would be included in what we call the negotiation algorithm.  More precisely, the negotiation algorithm would specify those parts of a party's strategy that must be known to both parties in order to successfully negotiate a CPA.

The negotiation team decided to specify negotiation in two stages.  The first stage is the negotiation protocol as defined in the current version of the draft specification.  The second stage is all those matters related to negotiation algorithm and strategy. We believe that when it is complete, the specification of the protocol will be useful to some parties for simple negotiation. The team will need more expertise in negotiation than it currently has to define a specification for algorithm/strategy. If you have an interest in this area and might be willing and able to contribute, please let us know.

If you wish to send further questions about negotiation or CPPA to the whole team,  you can send them to

ebxml-cppa-comment <ebxml-cppa-comment@lists.oasis-open.org>

without having to be a member of OASIS.

Regards,

Marty

At 08:55 AM 4/21/2004, kukoc-url wrote:

Hi Mr. Martin :

           I am a graduate student form Chung Yuan Christian University Taiwan.

           My major research is ˇ§a rule-driven negotiation agent to improving ebXML cpp/cpa automated negotiationˇ¨.

           I have a question about the concept of negotiation algorithm in Automated Negotiation Specification and hope you can help me to solve this problem.

           Many research about automated negotiation that define automated negotiation system must have two components : negotiation protocol and negotiation strategy.

           After viewing specification, i find there are only have designed the negotiation protocol, the negotiation strategy does not discussed in this specification.

          But in page 10, line 338, there are a component about negotiation algorithm which is the private process ate each negotiating party that implements that partyˇ¦s private negotiation strategy.

          Besides, according to the definition of negotiation strategy by Lomuscio(2000) and Jennings(2001): (1)an agentˇ¦s negotiation strategy is the specification of the sequence of actions(usually offers or response) the agent plan to make during the negotiation; (2)the decision making models which are used by the agents to achieve their objectives.

Question : Are there have the same meaning between the negotiation algorithm in specification and negotiation strategy which is defined above?

Please help me to clear the relationship between them.

Thanks for your opinion about this my question.

Best Regareds

Kukoc

 

------------------------------------------

Shao-Ming Yang ·¨˛Đ©ú

Chung Yuan Christian University

Institute of Informaton Management

E-Mail : kukoc@mis.cycu.edu.tw

------------------------------------------

 

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

Martin Sachs

standards architect

Cyclone Commerce

msachs@cyclonecommerce.com

*************************************
Martin Sachs
standards architect
Cyclone Commerce
msachs@cyclonecommerce.com