<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Achieving Mediated Agreements using Agreement Space Modeling</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">C</forename><surname>Carrascosa</surname></persName>
							<email>carrasco@dsic.upv.es</email>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Sistemas Informáticos y Computación (DSIC)</orgName>
								<orgName type="institution">Universidad Politécnica de Valencia</orgName>
								<address>
									<addrLine>Camino de Vera s</addrLine>
									<postCode>n -46022</postCode>
									<settlement>Valencia</settlement>
									<country key="ES">Spain</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">M</forename><surname>Rebollo</surname></persName>
							<email>mrebollo@dsic.upv.es</email>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Sistemas Informáticos y Computación (DSIC)</orgName>
								<orgName type="institution">Universidad Politécnica de Valencia</orgName>
								<address>
									<addrLine>Camino de Vera s</addrLine>
									<postCode>n -46022</postCode>
									<settlement>Valencia</settlement>
									<country key="ES">Spain</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Achieving Mediated Agreements using Agreement Space Modeling</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">2FFD21DF90D485BAA2789D7E5F9E099F</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T15:06+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>An agreement is an arrangement between two or more entities to do something. This implies a context in which terms the agreement is developed. This paper presents a model of such agreement context as an euclidean space. On the other hand, an agreement can also be seen as a Constraint Satisfaction Problem (CSP) which solution space models an agreement space. This will allow to have a mediator that could not only model the agreement as an space, but also to check the viability of the agreement as it is being built. This mediator, that could even give some counsels about the agreement terms being formulated, is called here Counselor Agent. The protocols to interact with such agent to build an agreement are also presented.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>According to the Merrian-Webster dictionary, agreement is "an arrangement as to a course of action. Compact, treaty a: a contract duly executed and legally binding b: the language or instrument embodying such a contract". This agreement, this contract, assumes or implies a context in which it is going to be carried out. So, using a classical example by Castelfranchi <ref type="bibr" target="#b2">[3]</ref> regarding the way an speech act tries to induce different motives for goal adoption in the addressee, when a general commands to a soldier 'Fire!', the soldier could interpret such an order in different ways according to the several meanings of such expression (he could shoot, or offer to the general some matches, or look for the firemen, or burn a fire, ...), but the most probable outcome is that he wouldn't doubt between such options and shoot his weapon, due to the context of the situation, that is, there is an implicit agreement between general and soldier regarding orders and military concepts.</p><p>This paper continues the work of <ref type="bibr" target="#b1">[2]</ref>[1] that define an agreement by means of a multi-dimensional Euclidean space approach. This modeling will allow to use geometrical properties or operations to work with such agreements, and even to model the agreement problem as a constraint-satisfaction problem (CSP) and to solve it using the Hyperpolyhedron Search Algorithm (HSA =) <ref type="bibr" target="#b10">[11]</ref>. This paper focuses in the way to use this modeling as a CSP by a mediator (Counselor Agent), which could be able to on-line evaluate the feasibility of such an agreement, or even give some advises as the agreement negotiation evolves. In order to do that, several agreement-related interaction protocols have been defined to be used by the participant agents to reach an agreement upon a set of agreed terms. So, one of the main differences between this approach and previous works related with agreements and agents, is the focus of the approach. In works as Contract-related agents <ref type="bibr" target="#b7">[8]</ref>, the focus is in the agent, and the way he may deal with the concept of contract. The work here presented focuses in the concept of agreement as an upper abstraction over the idea of agent, organization or other entity. Modeling the agreement in this way, is what can be really useful to a counselor mediating in such agreement.</p><p>The rest of the paper is structured as follows. Context Spaces are introduced in section 2. Section 3 provides a set of general definitions needed to describe the proposed protocols and algorithms. Agreement-related interaction protocols are described in section 4 and section 5 explains how the Counselor Agents works to help participant agents to reach an agreement. A simple example is shown in section 6 and, finally, section 7 summarizes this approach and concludes.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Context Space</head><p>This term is used in the pervasive computing field related to context-aware computing <ref type="bibr" target="#b9">[10]</ref>  <ref type="bibr" target="#b8">[9]</ref> to define a theory that models contexts based on intuitions from state-space models. In this way, the context space of an application is determined by the types of information, deemed relevant and obtainable by the designers, that is the context attributes, and the domain of possible values in each attribute. Each one of these attributes is considered one dimension in a multidimensional Euclidean space. This multi-dimensional space defines the space in which context can be perceived. This approach also includes a context algebra to express situations in terms of Context Spaces and to reason about such situations by means of a set of operators and calculations. The operators defined are the scalar difference (it calculates the degree of similarity between two comparable context states), and the intersection (it produces a new context space containing shared regions of values of the same attributes between two comparable context spaces).</p><p>By representing situations and system's state as multi-dimensional objects, it is possible to generically describe and consequently reason about context of a system. A region of acceptable values is defined as a set which satisfies some predicate, hence, it can consist of any information (numerical or non-numerical) that best reflect the context attribute behavior (in terms of possible values) for the specific situation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Agreements Concepts</head><p>This section presents some generic concepts and definitions related to agreements needed to explain the algorithms and protocols designed for a counselor agent to guide the agreement process. A more detailed definition can be found in <ref type="bibr" target="#b1">[2]</ref>[1].</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Agreement Definitions</head><p>An agreement is the definition of a working context for two or more beings or entities (agents, organizations, . . . ) so that it is obtained as the result of a negotiation process.</p><p>Definition 1 (Agreement). An agreement Ag is defined as Ag = (E, Cx), where: </p><formula xml:id="formula_0">-E = {E 1 , E 2 , . . . E n } is a set of entities participating in Ag, so that ∀E i , i = 1, . . . n, ∃!O i = {o ij }, j = 1, . . . m, ontology or set of concepts known by E i -Cx = {(cx o , cx I o )|cx o ∈ i O i , cx I o ⊆ D o },</formula><formula xml:id="formula_1">(i = 1..n), then D = {o/o ∈ O i △ O k , ∀i = k/i, k = 1.</formula><p>.n} (the symmetric difference of all the agreement participating entities' ontologies), <ref type="foot" target="#foot_0">1</ref> and the ADU (Ag) is defined as</p><formula xml:id="formula_2">ADU (Ag) = i O i − D.</formula><p>The ADU (Ag) is formed by all the concepts that at least one pair of entities participating in the agreement Ag share (Figure <ref type="figure" target="#fig_0">1</ref>). If this set is empty, entities have not anything in common and they can not reach any kind of agreement.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Agreement Process</head><p>An agreement Ag has two phases:</p><p>1. Reaching an agreement (defining the agreement context Cx): It comprises the negotiation process between two or more entities (belonging to E) to reach an agreement. In fact, it is decided in two levels: (a) A decision must be taken about what are the concepts around which such agreement is going to be related, that is, Cx ⊆ ADU (Ag). (b) After that, the specific terms of such agreement must be fixed, that is, the values or intervals for the concepts in Cx. 2. Agreement execution: In this phase each entity must fulfill the accomplished agreement executing the needed actions or calculus according to the context defined by such agreement. This execution could not even imply any kind of additional coordination.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3">Agreement Space</head><p>As it has been stated before, an agreement can be seen as the definition of a common context. As commented in section 2 an space metaphor such as the one used in Context Spaces can be used to express such contexts. So, an agreement space can be defined.</p><p>Definition 3 (Agreement Discourse Space). The Agreement Discourse Space of an agreement Ag ADS(Ag) is defined by considering as a dimension (in an Euclidean space) each concept included in an Agreement Discourse Universe of an agreement Ag. That is, the ADS(Ag) is an n-dimensional space, where n is the cardinality of the ADU (Ag) (number of common terms). Figure <ref type="figure" target="#fig_0">1</ref> shows an example with 3 dimensions, where the points represent the possible combination values of such space (assuming a discrete domain for every dimension).</p><p>Definition 4 (Agreement Space). According to the first phase of an agreement, a decision must be taken about the concepts, that is, the dimensions in which the agreement will be expressed. So, an Agreement Space is a projection of the Agreement Discourse Space onto the dimensions defining the agreement. That is, this space will be defined by the features the different entities E i making the agreement are going to negotiate (Cx), each one of such features defining a dimension in this space (∀i :</p><formula xml:id="formula_3">d i ∈ dim(E i , Ag)).</formula><p>In order to be possible an agreement Ag, for all entity E i participating in the agreement there will exist at least one other participating entity E j so that dim(E i , Ag) ∩ dim(E j , Ag) = 0.</p><p>The Agreement Space is, then, the result of eliminating the unnecessary dimensions that are not relevant for the agreement. For example, in Figure <ref type="figure" target="#fig_0">1</ref> the y dimension is not relevant, so the way the entities will deal with y concept is not controlled by the agreement, and the Agreement Space is reduced to the marked 2-dimensional area, that is, the projection over x and z dimensions of the defined ADS.</p><p>In this way, the outcome of the first phase of the agreement will be the definition of this Agreement Space, fixing the satisfying values for each one of the different dimensions comprising this space. The second phase of the agreement will be to carry out the execution of the agreement taking into account that it has to be carried out inside the previously defined Agreement Space.</p><p>Definition 5 (Local Agreement Space). The Local Agreement Space for entity E i in the agreement Ag is defined as the projection over the dimensions of interest of entity E i in such Agreement Space.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Agreement-Related Interaction Protocols</head><p>WS-Agreement <ref type="bibr" target="#b5">[6]</ref> is a standard proposed by the Global Grid Forum (GGF) that includes the definition of a simple interaction protocol to support oneto-one negotiation, with the likely aim to support different mechanisms in the future through definition of multiple interaction protocols. So, the work by <ref type="bibr" target="#b6">[7]</ref> for what they called service agreement where one consumer of a service chooses one service provider from n available by means of the FIPA Iterated Contract Net Interaction Protocol <ref type="bibr" target="#b4">[5]</ref>.</p><p>In this proposal, a Counselor Agent (see Section 5) mediates in the agreement process in order to help the participant agents to reach an agreement related to a common vocabulary. The mediation is achieved though a set of services available to all participants that help to find a common Agreement Space, inside which agents can interact being ensured that the terms of the agreement are fulfilled.</p><p>This section presents two new interaction protocols that has been defined to deal with the services offered by the Counselor Agent: ADU Definition and Agreement Counselor, that will be addressed by the ADU Interaction Protocol and the Mediated-Agreement Interaction Protocol, respectively.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">ADU Interaction Protocol (ADUIP)</head><p>This interaction protocol controls the service of the Counselor Agent related to the definition of the Agreement Discourse Universe of a group of entities, that is, the common vocabulary shared by such entities (see Definition 2). This protocol describes a general phase, previous to the agreement itself, that can be used in many other situations in which establish a common vocabulary is needed. Figure 1. An Entity E i sends a Call For Counselor to all entities offering the service of Counselor indicating an AgreementID. 2. If any Counselor agrees to E i , then E i will send a Request for Counselor to one of them, C j , that will serve as counselor for agreement AgreementID. 3. Counselor C j sends a Call For Agreement to all entities in the system, indicating an Agreement ID and a deadline to this phase of joining to the agreement. 4. Each entity E k that wants to participate in the agreement will send to C j an agree message with his ontology before deadline is met. 5. After deadline, C j will calculate the ADU using the ontologies received from the entities that will participate in the agreement, communicating them if the ADU is empty that there is a failure, because there is no possibility of agreement.</p><p>The ADU Interaction Protocol is only focused on provide a framework to participant agents for exchanging their ontologies (or fragments of them). It does not try to solve the ontology alignment problem, which is out of the scope of this paper.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Mediated-Agreement Interaction Protocol</head><p>After the existence of a common vocabulary is ensured by ADU protocol, the participant entities can negotiate the terms of any agreement. A two-phases protocol is proposed to reach an agreement among a group of entities (agents or organizations) mediated by a counselor. The final goal of this protocol is to construct the Agreement Space by means of the following steps:</p><p>1. Defining the context: It will be formed by the dimensions of the Agreement Space, that is, the concepts that will be dealt in the agreement, and that will be part of the ADU (in fact, this context will be a projection of the ADU in the dimensions of the Agreement Space). Defining the agreement terms, that is the different values or intervals for the dimensions defining the context that will define the Agreement Space. This process will be done by applying one by one the constraints suggested by the participants. Moreover, it is regulated by a mediator-the Counselor-which guides the negotiation process to achieve an accord among the participants. Its main task is to check that any additional constraint is consistent with the current constraint set. That is, if they formed a convex hull.</p><p>The protocol here presented is described from the Counselor point of view, and, its purpose is to help in the Agreement Space definition. This protocol (see Figure <ref type="figure">3a</ref>) is divided into two main parts: the first one deals with the definition of the context, and the second one with the definition of the agreement terms (see Figure <ref type="figure">3b</ref>). (a) An Entity E i sends a Call For Agreement with AgreementID to the Counselor Agent that has previously calculated the ADU, indicating that he wants to begin an agreement with some or all the other entities involved in such ADU. (b) If the Counselor agrees to E i , then he sends a Call For Context to all the entities associated to the previous ADU, indicating an Agreement ID and a deadline to this phase of joining to the agreement. (c) Each entity E k that wants to participate in the agreement will send to the Counselor an Agree message with his agreement dimensions (that is, the concepts he is interested in negotiate for the agreement, and that are part of the previous ADU) before deadline is met. (b) The Counselor sends a Call For Terms message to all the participating entities with the proper AgreementID to ask for agreement terms.</p><p>(c) Each one of the participating entities will send an Inform message to the Counselor for each one of the negotiation terms (in the form of a constraint) that he is interested in. Such messages will be processed by the Counselor to build the AS.</p><p>(d) For each Inform message, the Counselor will respond either with a Reject message, if the new term is not consistent with the agreement or is redundant, or with an Accept message if the new term is consistent.</p><p>(e) The process of receiving and analyzing new agreement terms continue till there is no more terms (according to a deadline-based method).</p><p>(f) The Counselor informs the participating entities either the final agreement terms, or that the agreement has not been possible.</p><p>The final result is the definition of the Agreement Space, modeled as a hyperpolyhedron formed by all accepted constraints (agreement terms). During the execution of the agreement, all interactions have to be inside this space as the participants have agreed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Using Agreement Spaces for Mediators</head><p>It is not so strange, when trying to reach an agreement to use a mediator to, not only watch over the fulfillment of the different processes involved in reaching an agreement, but also to counsel about the final values or intervals of the agreement due to its global unbiased view of the agreement. So, this figure is also interesting when trying to automatize the agreements, that is, to carry out agreements between agents, virtual organizations or other pieces of software. Different approaches to automatic mediators can be seen in the literature such as the PERSUADER system <ref type="bibr" target="#b11">[12]</ref> or AutoMed <ref type="bibr" target="#b3">[4]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1">Agreement Space as a CSP</head><p>As it was stated before, after the Agreement Space is defined, the different entities involved in the agreement must fix (possibly through a negotiation process) some concrete values or intervals for the different dimensions comprising the Agreement Space. For such negotiation, each one of these entities will have some intervals of satisfying values for the different dimensions it is interested in. These satisfying intervals may be expressed as constraints for the different dimensions that should be satisfied for the agreement. So, if this first phase of an agreement is seen from a mediator point-of-view, it can be seen as the solution of a Constraint-Satisfaction Problem (CSP), defined by the whole set of constraints of the different entities. Being the Agreement Space n-dimensional, each one of such constraints defines a (n − 1)-dimensional plane. As the Agreement Space is defined by the intersection of all such planes, it can be described how such space is by studying such planes. Therefore, this agreement mediator should be able to detect if an agreement is possible, checking if there exists an Agreement Space as a result of all these constraint planes intersection.</p><p>The idea is to define the Agreement Space as the solution space of a CSP and to build an agreement by applying entities' conditions as constraints in the space (applying the HSA = <ref type="bibr" target="#b10">[11]</ref> algorithm to build the hyperpolyhedron modeling the CSP that will define the Agreement Space). A solution is reached if all constraints are consistent. Furthermore, if the resulting space is convex then it can be ensured that all interactions are inside the Agreement Space.</p><p>As it is an agreement, an Agreement Space (AS) is defined by a set of entities and their context (E, Cx), where the context is composed by variables, their domains an all the constraints. In this way, the AS is defined by extending a common CSP definition.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2">Counselor Algorithm</head><p>The Counselor has the responsibility of helping the participants in the agreement to find the Agreement Space, considering it as a CSP. It is an iterative process that adds new constraints one by one, guaranteeing that the new constraint is consistent with the previous ones. Constraints are inequalities of the form n i=0 a i x i ≤ b, where x i are the variables of the CSP. The set of all constraints defines an hyperplane and which union defines the limits for the valid values for all the variables involved in the agreement. The participants in the agreement will take values inside the resulting hyperpolyhedron.</p><p>Using the mediated-agreement protocol defined in Section 4.2, the Counselor obtains the constraints from the participants and creates the Agreement Space using a variant of HSA = algorithm. This algorithm is applied inside the Agreement Terms Definition subprotocol (see Figure <ref type="figure">3b</ref>) each time a new constraint C i is received from a participant (by means of an Inform message). So the Agreement Space is incrementally constructed from scratch.</p><p>If C i is inconsistent or redundant, the agent that proposed it is informed by a Reject message. The agent can redefine the constraint and submit a new one if necessary.</p><p>Consistence and redundancy are checked using the HSA = algorithm. Basically, when a new constraint C i arrives the algorithm checks if each vertex of the current hyperpolyhedron satisfies C i . If none vertex satisfy C i then the constraint is inconsistent and it is rejected. That is because the space defined by the constraint does not contain any of the vertex of the hyperpolyhedron. On the other hand, if all vertex satisfy C i then the constraint is redundant. That is because the complete hyperpolyhedron is included inside the space defined by the constraint. In any other case, the constraint is consistent and it is added to the hyperpolyhedron.</p><p>When all constraints are added to the Agreement Space and it is not empty then there is an agreement among all the participants. If the Agreement Space is not empty, then it is ensured that it is convex, so any 'movement' between two points inside this space is always inside it. Therefore, it is guaranteed that any negotiation process produced inside the agreement terms will never violate the agreement.</p><p>The following section presents an example of reaching an agreement using a Counselor Agent, interacting with the above presented interaction protocols, focusing in the Agreement-terms definition subprotocol. Assuming that agents have some common vocabulary (checked with the ADU protocol) and they defined the above three dimensions as the agreement context, then the Counselor asks them for the terms of the agreement. There is no rule about the order in which agents propose the terms (constraints) nor the order in which they arrive to the Counselor. Depending on it, one constraint can be detected as redundant or just as a refinement of an existing one. But it does not affect to the final Agreement Space. This is a very simple case, in which restriction are defined over one dimension, but it is enough to follow and understand the process of construction of the Agreement Space. Let be C the counselor, T teacher, S1 student 1 and S2 student 2. An example of the process can be followed in Table <ref type="table" target="#tab_1">1</ref>. In the sequence of messages on this table it can be seen how the Counselor communicates to the rest of participants the context of the agreement (message 1). After that, the participants send their own constraints one by one (messages 3, 6, 9, 12, 15, 18, 21, 24 and 27) and the Counselor accepts or rejects them. For example, in message 18, S2 proposes a constraint that is redundant, since one more restrictive has been accepted in 12-13. But restrictions proposed in messages 15 and 27 have been accepted because they refine (they are more restrictive) that the ones accepted in 6-7 and 21-22 respectively.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Conclusions</head><p>Context Spaces seem to be a valid approach to model agreements and allows to use well known techniques to solve the task of reaching an agreement and controlling its subsequent execution. The agreement is modeled as an object in the Euclidean space.</p><p>The problem of defining the space associated to an agreement can be seen as a CSP, since the agreements conditions can be modeled as constraints and the agreement is expressed as a set of restrictions over a set of data. The conjunction of all these restrictions will define an convex hyperpolyhedron delimiting the agreement space, that is, the space where all the computations fulfilling such agreement will be carried out, the context of such computations.</p><p>Mediators can be used during the negotiation process to reach an agreement to check that any additional constraint keeps this space convex, along with controlling the feasibility of the agreement. For doing that, mediators can suggest more relaxed or more strict constraints in order to maintain the consistence of the space and the possibility of an agreement. This paper has presented not only the advantages using such a or Counselor in reaching an agreement, but also the way this Counselor works and how to interact with him by means of some interaction protocols specifically designed for agreement reaching processes.</p><p>As future work, the dynamic of the agreement is going to be studied, because to guarantee an agreement, besides the existence of the agreement space, the convergence of individual negotiation processes has to be guaranteed to avoid systems that oscillate without ending in a concrete agreement for some initial situations.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Agreement Discourse Universe and Agreement Discourse Space with the projection to a 2-dimensional Agreement Space</figDesc><graphic coords="4,266.64,115.83,198.35,148.77" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. ADU Interaction Protocol</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>1 .</head><label>1</label><figDesc>Context Definition: An initiator requests the Counselor for an agreement.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>2 .Fig. 3 .</head><label>23</label><figDesc>Fig. 3. (a) Mediated-Agreement Interaction Protocol (b) Agreement terms definition subprotocol</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>-Student 2 1 .</head><label>1</label><figDesc>minimum 15 classes: n ≥ 15 2. duration between 45 and 90 min: d ≥ 45 and d ≤ 90</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>where D o is the domain of the ontology term cx o . Thus, this context is formed by a set of ontological terms cx o with its corresponding set of valid instances cx I o that have been agreed by E.Definition 2 (Agreement Discourse Universe). The Agreement DiscourseUniverse of an agreement Ag -ADU (Ag)-is the whole set of concepts known by all the entities participating in the agreement. So, if O i is the set of all the ontologies known by the entity E i participating in the agreement Ag</figDesc><table /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 1 .</head><label>1</label><figDesc>Example of Agreement Terms Definition</figDesc><table><row><cell cols="2">Agent Mess</cell><cell>Param</cell><cell cols="2">Agent Mess</cell><cell>Param</cell><cell cols="2">Agent Mess</cell><cell>Param</cell></row><row><cell>1 C</cell><cell>inform</cell><cell cols="2">n, d ,p 11 C</cell><cell>call-for-terms</cell><cell></cell><cell>21 T</cell><cell>inform</cell><cell>d ≤ 120</cell></row><row><cell>2 C</cell><cell>call-for-terms</cell><cell></cell><cell>12 T</cell><cell>inform</cell><cell>d ≥ 60</cell><cell>22 C</cell><cell>accept</cell><cell>d ≤ 120</cell></row><row><cell>3 T</cell><cell>inform</cell><cell cols="2">n ≥ 10 13 C</cell><cell>accept</cell><cell>d ≥ 60</cell><cell>23 C</cell><cell>call-for-terms</cell></row><row><cell>4 C</cell><cell>accept</cell><cell cols="2">n ≥ 10 14 C</cell><cell>call-for-terms</cell><cell></cell><cell>24 T</cell><cell>inform</cell><cell>p ≥ 20</cell></row><row><cell>5 C</cell><cell>call-for-terms</cell><cell></cell><cell>15 S1</cell><cell>inform</cell><cell>n ≤ 20</cell><cell>25 C</cell><cell>accept</cell><cell>p ≥ 20</cell></row><row><cell>6 S1</cell><cell>inform</cell><cell cols="2">p ≤ 30 16 C</cell><cell>accept</cell><cell>n ≤ 20</cell><cell>26 C</cell><cell>call-for-terms</cell></row><row><cell>7 C</cell><cell>accept</cell><cell cols="2">p ≤ 30 17 C</cell><cell>call-for-terms</cell><cell></cell><cell>27 S2</cell><cell>inform</cell><cell>d ≤ 90</cell></row><row><cell>8 C</cell><cell>call-for-terms</cell><cell></cell><cell>18 S2</cell><cell>inform</cell><cell>d ≥ 45</cell><cell>28 C</cell><cell>accept</cell><cell>d ≤ 90</cell></row><row><cell>9 S2</cell><cell>inform</cell><cell cols="2">n ≥ 15 19 C</cell><cell>reject</cell><cell cols="2">d ≥ 45, red 29 C</cell><cell>inform-done</cell></row><row><cell>10 C</cell><cell>accept</cell><cell cols="2">n ≥ 15 20 C</cell><cell>call-for-terms</cell><cell></cell><cell></cell><cell></cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">The symmetric difference is defined as A△B = (A∩B ′ )∪(A ′ ∩B), where A ′ denotes the complementary set of A</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">shows this protocol, that is composed of the following steps:</note>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Example</head><p>Let it be a set of agents interested in taking piano classes. The group is formed by one teacher and two students. They agree to negotiate over three dimensions: the number of classes (n), its duration (d) and its price (p). Initially, participants have their own preferences (modeled as constraints).</p><p>- </p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Modelling agreement spaces</title>
		<author>
			<persName><forename type="first">C</forename><surname>Carrascosa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rebollo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IBERAMIA 2008 Workshop on Agreement Technologies</title>
				<editor>
			<persName><forename type="first">Marc</forename><surname>Esteve</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Adriana</forename><surname>Giret</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Alberto</forename><surname>Fernández</surname></persName>
		</editor>
		<meeting><address><addrLine>WAT; Vicente Julián</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2008">2008. 2008</date>
			<biblScope unit="page" from="79" to="88" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Agreement spaces for counselor agents (short paper)</title>
		<author>
			<persName><forename type="first">C</forename><surname>Carrascosa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rebollo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of 8th Int. Conf. on Autonomous Agents and Multiagent Systems (AAMAS 2009</title>
				<editor>
			<persName><forename type="first">Sichman</forename><surname>Decker</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Castelfranchi</forename><surname>Sierra</surname></persName>
		</editor>
		<meeting>of 8th Int. Conf. on Autonomous Agents and Multiagent Systems (AAMAS 2009<address><addrLine>Budapest, Hungary</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2009">May, 10-15, 2009. 2009</date>
		</imprint>
	</monogr>
	<note>To appear</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Prescribed mental attitudes in goal-adoption and norm-adoption</title>
		<author>
			<persName><forename type="first">C</forename><surname>Castelfranchi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence and Law</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="37" to="50" />
			<date type="published" when="1996">1996</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Automed: an automated mediator for bilateral negotiations under time constraints</title>
		<author>
			<persName><forename type="first">M</forename><surname>Chalamish</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kraus</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">AAMAS &apos;07: Proceedings of the 6th international joint conference on Autonomous agents and multiagent systems</title>
				<meeting><address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="1" to="3" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">FIPA Iterated Contract Net Interaction Protocol Specification</title>
		<author>
			<persName><surname>Fipa</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2001">2001</date>
			<publisher>FIPA</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<author>
			<persName><forename type="first">G</forename><surname>Forum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Web services agreement specification</title>
				<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
	<note>ws-agreement</note>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Incorporating agreements on service options into bpel-based services</title>
		<author>
			<persName><forename type="first">F</forename><surname>Ishikawa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Yoshioka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Honiden</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the International Conference on Computational Intelligence for Modelling, Control and Automation and International Conference on Intelligent Agents, Web Technologies and Internet Commerce Vol-1 (CIMCA-IAWTIC&apos;06</title>
				<meeting>the International Conference on Computational Intelligence for Modelling, Control and Automation and International Conference on Intelligent Agents, Web Technologies and Internet Commerce Vol-1 (CIMCA-IAWTIC&apos;06<address><addrLine>Washington, DC, USA</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE Computer Society</publisher>
			<date type="published" when="2005">2005</date>
			<biblScope unit="page" from="796" to="803" />
		</imprint>
	</monogr>
	<note>CIMCA &apos;05</note>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Contract Related Agents</title>
		<author>
			<persName><forename type="first">J</forename><surname>Knottenbelt</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2006-12">December 2006</date>
		</imprint>
		<respStmt>
			<orgName>Department of Computing, Imperial College London</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD thesis</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Extending the context space approach to management by business objectives</title>
		<author>
			<persName><forename type="first">A</forename><surname>Padovitz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Bartolini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Zaslavsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">W</forename><surname>Loke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">HP OpenView University Association (HP-OVUA), 12th Workshop</title>
				<meeting><address><addrLine>Porto, Portugal (FEUP)</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005-07-13">10 -13 July 2005, 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Towards a theory of context spaces</title>
		<author>
			<persName><forename type="first">A</forename><surname>Padovitz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">W</forename><surname>Loke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Zaslavsky</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Second IEEE Annual Conference on Pervasive Computing and Communications Workshop</title>
				<editor>
			<persName><forename type="first">C</forename><surname>Das</surname></persName>
		</editor>
		<editor>
			<persName><surname>Kumar</surname></persName>
		</editor>
		<meeting>the Second IEEE Annual Conference on Pervasive Computing and Communications Workshop<address><addrLine>Orlando Florida; USA</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE Computer Society</publisher>
			<date type="published" when="2004-03-17">14 -17 March 2004. 2004</date>
			<biblScope unit="page" from="38" to="42" />
		</imprint>
	</monogr>
	<note>Workshop on Context Modeling and Reasoning</note>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Constraint satisfaction by means of dynamic polyhedra</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Salido</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Giret</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Barber</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Operational Research Proceedings</title>
				<imprint>
			<publisher>Springer Verlag</publisher>
			<date type="published" when="2001">2001. 2001</date>
			<biblScope unit="page" from="405" to="412" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Resolving goal conflicts via negotiation</title>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">P</forename><surname>Sycara</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of AAAI-88</title>
				<meeting>AAAI-88</meeting>
		<imprint>
			<date type="published" when="1988">1988</date>
			<biblScope unit="page" from="245" to="250" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
