<?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">Using a normative organisational model to specify and manage an institution for multi-agent systems</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Benjamin</forename><surname>Gâteau</surname></persName>
							<email>benjamin.gateau@tudor.lu</email>
						</author>
						<author>
							<persName><forename type="first">Crp</forename><surname>Henri</surname></persName>
						</author>
						<author>
							<persName><forename type="first">Tudor -G.-D</forename><surname>Of Luxembourg</surname></persName>
						</author>
						<title level="a" type="main">Using a normative organisational model to specify and manage an institution for multi-agent systems</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">2BD41DFE4D5E2CCEAAE422FD97DE4217</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T14:54+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>Nowadays multi-agent applications are more and more openness. That brings the risk to deal with to autonomous agents i.e. agents not respecting the society rules. To insure a coherent behaviour the application require tools to control and regulate the system overall functioning. Moreover they should provide the system with mechanisms to enforce global laws on the autonomous agents operating in it. This paper presents an institution multi-agent layer called S YNAI. Implemented with different agents, the institution functioning is itself specified as a normative organisation model making explicit how the overall system should be controlled. Using an iTV game application, we illustrate how such a specification is useful to help the agents to function in the system.</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>Nowadays, multi-agent technologies' applications are faced to an increasing openness. Being composed of heterogeneous and autonomous agents, they require tools to control and regulate the system overall functioning. Moreover they should provide the system with mechanisms to enforce global laws on the autonomous agents operating in the system.</p><p>In this paper we present SYNAI, a multi-agent layer dedicated to the rights and duties management and enforcement of autonomous agents within an organisation. This layer belongs to the electronic institution environment called MAB ELI <ref type="foot" target="#foot_0">1</ref> . It is composed of generic institutional agents, supervisors, aiming at controlling and enforcing the domain agents functioning according to the specified normative organisation expressed with the normative organisation model called MOISE Inst . Whereas supervisor agents are dedicated to the system control, the domain agents implement the application functionalities. The supervisor agents themselves operate under the control of a normative organisation that structures and constrains their control behaviour on the domain agents.</p><p>All along the paper, we illustrate the use of MAB ELI with an iTV game issued from the European ITEA Jules Verne Project. We show how this multimedia game can be modelised and controlled with such a platform.</p><p>This paper is organised as follows: section 2 presents an motivations overview for using an explicit normative organisational model to specify SYNAI, the multi-agent institution platform with MOISE Inst , normative organisation model. Its use is illustrated with the iTV application. The succeeding sections present the other main component of the Electronic Institution namely SYNAI, the arbitration system. We describe the institutional agents organisation and how the supervisors arbitrate an organisation by respecting their own organisation specification Finally, before concluding, section 5 compares our work to other approaches.</p><p>In the recent past, multi-agent technologies have been developed and deployed in different applications. Most of these efforts have been largely supported by the existence of multi-agent platforms like JADE <ref type="bibr" target="#b0">[1]</ref> or FIPA-OS <ref type="bibr" target="#b11">[12]</ref>. These platforms have demonstrated the generic services needs and utility for supporting the execution of multi-agent applications such as Agent Management System, Directory Facilitator. The recent developments in the domain (e.g. electronic commerce <ref type="bibr" target="#b1">[2]</ref>) have shown the requirement to enrich those services to provide multi-agent applications with institution platforms. The main purpose was to insure and promote the user's trust in the system functioning by controlling agents during their transactions. In human societies institutions define the game rules <ref type="bibr" target="#b10">[11]</ref>. These rules enclose all kinds of informal or formal constraints that human beings use to interact. Current multi-agent approaches to institution propose these rules modelling through normative systems <ref type="bibr" target="#b9">[10]</ref> that are interpreted by agents that enforce the application's agents to follow them and not to violate them. In the same trend, the work described in this paper is applied to an Interactive Games application (see Fig. <ref type="figure" target="#fig_0">1</ref>): a "questions -answers" TV game show opposing a real players' team present on the TV scene, to a televiewers' team interacting from home into the game with the help of the Avatars, i.e. software agents. Each Avatar is under its respective televiewer control. The quizmaster is also supported by a virtual assistant. His role is to regulate the game. As in all collective games, the aim is to promote a collective behaviour among the the same team's players. An explicit organisation states the roles involved in the game. A set of rules (norms) represents the game rules, the sanctions and rewards in use during the game. However, since avatars are autonomous agents, they can be autonomous with respect to these constraints, e.g. a televiewer is able to decide to answer whereas it is not his turn and to take the risk to be punished. An institution has been thus defined in order to control, regulate and reward or punish agents when they respect or not the Two kinds of agents have been designed: domain agents, avatars controlled by the users, and supervisor agents aiming at managing the organisation and enforcing the game rules on the domain agents. They are organised into two layers: (i) the multiagent interactive game in which domain agents as avatars, operate on behalf of their user, (ii) SYNAI<ref type="foot" target="#foot_1">2</ref> an institution multiagent platform dedicated to the organisation management and to its control by the mean of the supervisor agents. Both kinds of agents (supervisor and domain) are organised and constrained according to a normative organisation described with the MOISE Inst normative organisation description language <ref type="bibr" target="#b4">[5]</ref>. Agents are thus able to reason on the organisation and constraints. They have the possibility to decide to take it into account or not. The institution platform reads this specification in order to supervise and control the agents as well as be informed about its own organisation specification.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Game Player Application</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>In what European city would you find the famous Tivoli Gardens?</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>GEOGRAPHY</head><p>Before focusing on the presentation of the SYNAI specification, we shortly describe MOISE Inst .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Normative organisation description language</head><p>MOISE Inst <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b5">6]</ref> is used to define what we call an organisation specification (OS) with the help of four specifications<ref type="foot" target="#foot_2">3</ref> : structural specification (SS), functional specification (FS), contextual specification (CS) and normative specification (NS).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Structural specification</head><p>The structural specification (SS) expresses a set of roles, groups and links that build the organisation structure (cf. Figure <ref type="figure" target="#fig_1">2</ref>). For instance, a "Team" group is composed of the following roles: "History", "Geo", "Sport", "Science" and "Chief". These roles inherit from "BasicPlayer" or "Player" roles that are abstract, i.e. roles which are not adoptable by agents. Cardinality and compatibility links express constraints on the way agents play roles in groups. For instance, cardinality '1..1' on the composition link ensures constraints that, in a "Team" group instance, roles can be adopted by only one agent at the same time. A compatibility link between "BasicPlayer" and "Chief", allows the same agent to play those two roles or those roles specializations. Thus, according to this specification, one agent may have the possibility to play at most two of those five roles. In order to avoid that five agents play the five "Team" roles, we express a cardinality '4..4' for the group "Team", stating that any well formed instance of this group may contain four and only four agents. g431 m4 g432 m7,m16 g441 m4 g442 m8,m16 g41: "History" topic handled g411: "History" question asked g412: "History" question answered g42: "Geo" topic handled g421: "Geo" question asked g422: "Geo" question answered g43: "Sport" topic handled g431: "Sport" question asked g432: "Sport" question answered g44: "Science" topic handled g441: "Science" question asked g442: "Science" question answered Communication and authority links structure the different roles. For instance, all roles inheriting from "Player" can communicate between them, and the "Chief" has the authority on all "BasicPlayer", which means that all roles inheriting from this role are under the "Chief" authority . "OrgCandidate" is the first role played by every agents coming in the organisation that is why it could be played by a lot of agents at the same time. "OrgCandidate" does not participate in the game (activity to answer question). According to available roles adoptable in the "Team", agents could change to join the group. "GameMaster" is the role played by the only one presenter assistant.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Functional specification</head><p>The functional specification (FS) specifies the global expected system functioning in terms of goals/subgoals that agents operating in it should achieve (cf. Figure <ref type="figure" target="#fig_2">3</ref>). The goal decomposition trees are organised into different social schemes which may be reused within other social schemes. For instance the Question Scheme has "question handled" as root goal and its plan is a sequential achievement of goals "g4", "g5" and of "Score Scheme". The "OrgEnter Scheme" (resp. "OrgExit Scheme") defines the principal behaviours for entering (resp. leaving) an organisation. We also define a scheme relating to the customization of the sanctions by specifying that apply a sanction is a choice between the ejection of a player, the disqualification of the team or the modification of the score. At last, we can also define scheme relating to Avatars 3D rendering with goals to show a happy or sad face for instance making possible the norms definition relating to that.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3">Contextual specification</head><p>To tackle with the applications situatedness in evolving environment, a contextual specification (CS) captures design-time constraints on the organisation evolution as a set of contexts and transitions between them (cf. Figure <ref type="figure" target="#fig_3">4</ref>).</p><p>A context expresses a state in which an agent playing a role has to respect specific rules (see below the norms expression). Transitions define change from one context to another context given different events occurrence. For instance, in our application, it is used to express the different game rounds that impose change to the rules. Here the CS starts with a synchronous state "Begin" which allows the televiewer to connect to the system. A macro-context "Game" is decomposed into three rounds sub-contexts. This global context will be used to define the basic game rules while the three round sub-contexts will be used to define the corresponding specific rules. The "Game" context is also decomposed into two sub-contexts defining the players turn. A round sub-context and a turn sub-context can be active at the same time. Let us notice that the macro-context is active in all its sub-contexts. The rules defined in the "Game" context are thus inherited in sub-contexts and are still valid. Finally the last state is the context in which Avatars quit their team. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4">Normative specification</head><p>Finally, the normative specification (NS) glues all specifications in a coherent and normative organisation. It expresses permissions, obligations and prohibitions of missions referring to the goals of the FS in the context of elements of the SS (roles or groups). Missions group goals into coherent sets according to the way the designer wants to assign them to roles or groups for their achievement. A norm in NS (cf. Figure <ref type="figure" target="#fig_4">5</ref>) is specified with an id, a context, a bearer, a deontic operator referring to a mission and a deadline. The Avatars scenario NS displayed on the Fig. <ref type="figure" target="#fig_4">5</ref> uses functions defined in the MOISE Inst meta-model. The N1 validation condition (nb(T eam) &lt; max(T eam)) is composed of two functions representing the agent number already in the Team group and the maximum of agents allowed in the Team. This norm expresses the fact that the Team must not be full in order to allow an agent entry. Concerning the norms N17 and N18, the function violated() return true if the norm in parameter is not respected. The detection is done by SYNAI agents. We explain how in section 4. This specification can define norms as well as their sanction. A sanction is a norm with a violation condition. The norms issuer is the role which supervises the norm respect. Users who specify their own application modelling do not know how the arbitration works. That is why they have to set the issuer up to "Supervisor" role. The SYNAI layer decides automatically what agents supervise what norms.</p><p>Our model does not provide solution to check if the norms are coherent ones compared to the others. In our example, potential conflicts can occur between norms N15 and N09 because they oblige agents playing role in the "Team" group to accomplish and to not accomplish the mission m16. We have the same between norms N15 and N14, N8 and N9, and N8 and N14. To avoid agents having to make a choice between con-flictual norms to respect, we specify a priority order denoted by a w. in the table. 1 is the higher priority. To abrogate conflictual norms we decrease N9 and N14 priority order.</p><p>The norms allow us to define and constrain the game functioning as well as what happens at the beginning and at the end of the game. The four first norms in Fig. <ref type="figure" target="#fig_4">5</ref> define when it is possible to join and to leave the team. Global game rules are expressed as functioning norms. For instance Prohibition for "Player" role to answer a question during the game represented by N08 authorizes concerned roles during rounds to answer questions. N09 and N14 oblige the "Player" and the "Chief" roles to answer all questions during the first and third rounds. Four norms for each role in the second round allow concerned roles to answer question.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">SYNAI Institution platform normative organisation 4.1 Requirements</head><p>Domain agents play the game by acting in an Organisation specified by the designer in the OS described in the previous section. As depicted on the left of Fig. <ref type="figure" target="#fig_5">6</ref>, an Organisation is an Organisation Specification instantiation which means that agents adopt roles and commit on mission according to the OS. This specification aims at constraining their behaviour. However being autonomous (under an user control) they can decide to not respect the specification stated in the OS. An agent can adopt a role in the Organisation which is not authorize in the OS. If the Organisation is not consistent with the OS, the Organisation is considered as incoherent.  As motivated in this paper beginning, we need an arbitration system able to supervise the Organisation execution and avoid incoherences. That means managing and controlling the functioning of the Organisation by the way of different events corresponding to the agents entry/exit, roles adoption/leaving, context change, missions commitment, goals achievement, etc. Event are basic MOISE Inst elements. They are defined in the MOISE Inst meta-model and in the user CS model.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Institutional Agents Middleware</head><p>To satisfy these requirements, we have defined an institution layer namely SYNAI which filters actions executed in the Organisation by the agents. It aims at checking the OS respect. Receiving requests from agents (messages composed by an event and others parameters), it detects if they violate or not constraints stated in SS, FS and NS (cf. Fig. <ref type="figure" target="#fig_5">6</ref>). For instance it verifies that an agent plays compatible roles or that it is authorized to commit on mission according to the role it is playing.</p><p>A set of different supervisor agents composes SYNAI. Four different agents manage each entity deriving from the OS specification: StructManagerAg for the SS entity, FunctManagerAg for the FS entity, Con-textManagerAg for the CS entity and NormManagerAg for the NS entity. The InstManagerAg is able to manage the Organisation. Each domain agent is supported by an OrgWrapperAg which is a facilitator for the domain agent to access and interact with the supervisor agents. SYNAI agents are sensitive to events and treat them differently according to their role. The interpretation of an event coming with a message triggers action and another message sending.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Institution normative organisation</head><p>In order to supervise the organisation and the norms respect, supervisor agents have to understand the MOISE Inst model. This model advantage is the ability to model both the organisation and its arbitration. Supervisor agents are organised the same way as domain agents i.e. according to the OS specified with MOISE Inst in order to structure and to define their rights and duties (see Fig. <ref type="figure" target="#fig_7">7</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Structural specification :</head><p>The SS is composed of the only group "Institution" grouping the roles that supervisor agents would play in order to manage MOISE Inst model specifications for domain agents. "In-stManager" and "Arbitrator" roles are compatible. All roles inheriting from "Supervisor" role can communicate with each other (communication link from "Supervisor" to itself). The cardinality '1..1' except for "OrgWrapper" ensures that only and only one supervisor agent with play a role in this group.   Functional specification : The FS defines the arbitration system main goal which is to keep the organisation in a coherent state. This consists in a choice between correcting the violation (gOC goal) or blocking the violation intention (gOB goal). This choice defines an arbitration strategy. As expressed in the arbitration scheme, the arbitration steps are: violation detection, violation correction or not (according to the arbitration strategy) and culprit sanction. Constraints come from the SS (cardinalities, links, etc.), from the FS (mission cardinalities) and from the NS (norms). The CS does not constraint agents and so cannot be violated. A violation detection is either a NS violation, or a FS violation or a NS violation. The gVD goal ("Violation Detected") plan expresses that. The same choice defines the gVC ("Violation Corrected") plan.</p><formula xml:id="formula_0">NA01 1 --- Arbitrator O --- --- NA02 1 --- Supervisor Arbitrator O --- --- NA03 1 --- Supervisor O --- --- NA04 1 --- Supervisor O --- --- NA05 1 --- Supervisor O --- --- NA06 1 --- Supervisor Arbitrator O --- --- --- NA07 1 --- Supervisor Arbitrator O --- --- --- NA08 1 --- Supervisor O --- --- --- NA09 1 --- Supervisor O --- --- --- NA10 1 --- Supervisor O --- ---</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>w. deOp</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>CorrArb</head><p>Contextual specification : The CS defines the contexts that are used for the arbitration strategies choice related to the goals gOC or gOB achievement. During the Organisation working, an event can be created and causing the arbitration strategy change: correct violations or block violations.</p><p>Normative specification : The NS norms (cf. the table of the Fig. <ref type="figure" target="#fig_7">7</ref>) express that the organisation must be kept in a coherent state by correcting violations in the "CorrArb" context (NA1 to NA5) and by blocking actions with violation intention in the "BlocArb" context (NA6) and express that the detection must be done in whatever context (NA7 to NA10).</p><p>InstManagerAg plays "InstManager" and "Arbitrator". Each supervisor agent plays the role corresponding to its capabilities: StructManagerAg plays "StructManager", FunctManagerAg plays "FunctionalManager" and so on.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Detection of constraint violation</head><p>In order to supervise an Organisation execution, the SYNAI's agents have to respect their own Organisation Specification and achieved their goals. As seen before, their root goal is to keep the organisation in a coherent state. For that and first of all they have to detect violations. According to events contained in message, institutional agents behave in a certain way by executing some actions and sending messages. The Fig. <ref type="figure" target="#fig_8">8</ref> depicts the interaction diagram between SYNAI agents in order to treat a violation detection. We consider here that a structural violation is in progress. So when StructManagerAg detects a violation, it achieves a goal and for that it acts on the Organisation via FunctManagerAg by sending a message with setGoalSatisfied event and goal "gSVD" as parameter (step 1). At the same time, it notifies InstManagerAg that a violation happened. InstManagerAg considers that goal "gVD" is achieved as the plan is executed (step 2). In order to accomplish mission mAB a sanction must be applied. Step 2 is the creation and the execution of a Sanction Scheme by InstManagerAg playing "Arbitrator" role. Then InstManagerAg is allowed to achieve goal "gCB" because of violation detection and sanction. At last goal "gCoh" is also achieved because it corresponds to the arbitration strategy choice (step 4). Therefore mission mAB is accomplished and Arbitration Scheme is finished (finishScheme event). The arbitration is terminated for this violation and InstManagerAg informs the supervisor which detected the violation by sending violationTreated event.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Related work</head><p>In this paper we introduced SYNAI that could be compared with others Electronic Institution arbitration models coming from the MAS domain. OMNI (Organizational Model for Normative Institutions) <ref type="bibr" target="#b12">[13]</ref> is an organisational model split in several dimensions (normative, organisational and ontological) and levels (abstract, concrete and implementation). The concrete organisational model is composed of roles and interactions structures implemented into social model specifying roles played by agents and into interactions model specifying the actual interactions between agents. Norms used to specify roles and interactions structures are defined within the normative dimension. OMNI differentiates institutional agents bringing particular services (matchmaking, reputation, identification, notary, monitoring, etc.) in order to execute institutions and external agents obliged to respect organisational and normative constraints. Police Agents are in charge of norms execution and violation detection.</p><p>ISLANDER is an Institution Definition Language (IDL) <ref type="bibr" target="#b2">[3]</ref> specifying scenes and protocols in an Electronic Institution. Compared to MOISE Inst the role hierarchy specification is minimal in the sense that we can only define roles and inheritance and compatibility between roles. The agents functioning definition is not possible. This model is more focused on interactions and protocols specification taking part to the scenes definition. The agents have to follow the protocols to evolve in a scene. There are no sanctions defined. AMELI <ref type="bibr" target="#b3">[4]</ref> is the ISLANDER specification execution framework. It provides a social layer which controls and helps the agents to participate in an e-institution with specialized governors. According to the specification available, only the interactions between agents can be controlled.</p><p>MOISE + <ref type="bibr" target="#b7">[8]</ref> is an organisational model specifying agents' structure, functioning and set of deontic expressions. Its separation into three distinct specifications brings more flexibility. This model allows us to define well-structured and precise organisations. However there is no contexts or scene definition in which specific deontic expressions can be applied. S−MOISE + [9] is a platform managing MOISE + organisations. It provides to agents evolving in the society personal "OrgBoxes" as organisation partial view. It serves as interface between heterogeneous agents and the organisation. Even so, there is just one "OrgManager" for controlling agents access into the organisation. Besides, the deontic expressions are enforced but not controlled. For instance, an obligation violation is hardly detectable.</p><p>To conclude, contrary to MOISE Inst , none of these models take into consideration the whole essential specification points of view (structural, functional, contextual and normative). They allow an arbitration system modelling. Arbitration could be done if norms can be controlled. Norms provide enough information to supervise them and to detect if the norm is respected or not. In works above-mentioned nothing is said about the norm violation detection.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Conclusion and perspectives</head><p>We have proposed in this paper the SYNAI platform being part of MAB ELI which is composed of supervisor agents organised with the MOISE Inst meta-model. This meta-model is considered as an institution organisation specification especially through each society roles rights and duties description as well as these rights and duties arbitration.</p><p>Two kinds of agents will evolve in the electronic institution: the domain agents and the supervisor agents. With MOISE Inst we expressed authority roles that SYNAI agents will play, as well as the missions related to their ability to detect norms violations and to punish culprit domain agents.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Global view of the e-Institution for iTV</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Avatars scenario Structural Specification</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Avatars scenario Functional Specification</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Avatars scenario Contextual Specification</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Avatars scenario Normative Specification</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Supervisor agents in SYNAI</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Figure 7 :</head><label>7</label><figDesc>Figure 7: Organisation Specification of SYNAI</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head>Figure 8 :</head><label>8</label><figDesc>schemeFinished</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Multi-Agent Based ELectronic Institution</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">SYstem of Normative Agents for Institution.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">A BNF definition of SS and FS are available in<ref type="bibr" target="#b6">[7]</ref> and of CS and NS in<ref type="bibr" target="#b4">[5]</ref> </note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>There was no intention to impose a unique domain agents definition due to the heterogeneity objective. However we can specify the supervisor agents functionalities operating in SYNAI. But the events definition and the way they are treated is not perfect. Next steps are to transform the events definition into an MOISE Inst Ontological Specification and messages exchange defined inside supervisors into an Interactional Specification.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Jade -a fipa-compliant agent framework</title>
		<author>
			<persName><forename type="first">Fabio</forename><surname>Bellifemine</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Agostino</forename><surname>Poggi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Giovanni</forename><surname>Rimassa</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">4th International Conference and Exhibition on The Practical Application of Intelligent Agents and Multi-Agents</title>
				<meeting><address><addrLine>London -UK</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Agents, markets, institutions, and protocols</title>
		<author>
			<persName><forename type="first">Frank</forename><surname>Dignum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Agent-Mediated Electronic Commerce -The European AgentLink Perspective</title>
		<title level="s">Lecture Notes in Artificial Intelligence</title>
		<editor>
			<persName><forename type="first">Frank</forename><surname>Dignum</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Carles</forename><surname>Sierra</surname></persName>
		</editor>
		<imprint>
			<publisher>Springer Verlag</publisher>
			<date type="published" when="1991">1991. 2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Islander: an electronic institutions editor</title>
		<author>
			<persName><forename type="first">Marc</forename><surname>Esteva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">David</forename><surname>De La</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Cruz</forename></persName>
		</author>
		<author>
			<persName><forename type="first">Carles</forename><surname>Sierra</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">1rst international joint conference on autonomous agents and multiagent systems (AAMAS&apos;02)</title>
				<meeting><address><addrLine>Bologna -Italy</addrLine></address></meeting>
		<imprint>
			<publisher>ACM Press</publisher>
			<date type="published" when="2002">2002</date>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="1045" to="1052" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Ameli: An agent-based middleware for electronic institutions</title>
		<author>
			<persName><forename type="first">Marc</forename><surname>Esteva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Bruno</forename><surname>Rosell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Juan</forename><forename type="middle">A</forename><surname>Rodriguez-Aguilar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Josep</forename><surname>Ll</surname></persName>
		</author>
		<author>
			<persName><surname>Arcos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">3rd international joint conference on Autonomous Agents &amp; Multi-Agent Systems (AAMAS&apos;04)</title>
				<meeting><address><addrLine>New York City -USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM Press</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="236" to="243" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">MOISE Inst : An organizational model for specifying rights and duties of autonomous agents</title>
		<author>
			<persName><forename type="first">Benjamin</forename><surname>Gâteau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Olivier</forename><surname>Boissier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Djamel</forename><surname>Khadraoui</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Eric</forename><surname>Dubois</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">1st International Workshop on Coordination and Organisation (CoOrg 2005)</title>
				<meeting><address><addrLine>Namur -Belgium</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Controlling an interactive game with a multi-agent based normative organizational model</title>
		<author>
			<persName><forename type="first">Benjamin</forename><surname>Gâteau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Olivier</forename><surname>Boissier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Djamel</forename><surname>Khadraoui</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Eric</forename><surname>Dubois</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Coordination, Organization, Institutions and Norms in agent systems workshop (COIN) at the 17th European Conference on Artificial Intelligence (ECAI)</title>
				<meeting>the Coordination, Organization, Institutions and Norms in agent systems workshop (COIN) at the 17th European Conference on Artificial Intelligence (ECAI)<address><addrLine>Riva del Garda -Italy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Architecture e-business sécurisée pour la gestion des contrats</title>
		<author>
			<persName><forename type="first">Benjamin</forename><surname>Gâteau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Djamel</forename><surname>Khadraoui</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Eric</forename><surname>Dubois</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">3ème Conférence sur la Sécurité et Architectures Réseaux (SAR)</title>
				<meeting><address><addrLine>La Londe -France</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">A model for the structural, functional, and deontic specification of organizations in multiagent systems</title>
		<author>
			<persName><forename type="first">Fred</forename><surname>Jomi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jaime</forename><surname>Hübner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Olivier</forename><surname>Simo Sichman</surname></persName>
		</author>
		<author>
			<persName><surname>Boissier</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">16th Brazilian Symposium on Artificial Intelligence (SBIA&apos;02)</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2002">2002</date>
			<biblScope unit="volume">2507</biblScope>
			<biblScope unit="page" from="118" to="128" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">S−MOISE + : A middleware for developing organized multi-agent systems</title>
		<author>
			<persName><forename type="first">Fred</forename><surname>Jomi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Jaime</forename><surname>Hübner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Olivier</forename><surname>Simo Sichman</surname></persName>
		</author>
		<author>
			<persName><surname>Boissier</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the International Workshop on Organizations in Multi-Agent Systems: From Organizations to Organization Oriented Programming in MAS (OOOP)</title>
				<meeting>the International Workshop on Organizations in Multi-Agent Systems: From Organizations to Organization Oriented Programming in MAS (OOOP)</meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2005">2005</date>
			<biblScope unit="volume">3913</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Jones</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Carmo</surname></persName>
		</author>
		<title level="m">Handbook of Philosophical Logic, chapter Deontic logic and contrary-toduties</title>
				<imprint>
			<publisher>Kluwer</publisher>
			<date type="published" when="2001">2001</date>
			<biblScope unit="page" from="203" to="279" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><surname>Douglass</surname></persName>
		</author>
		<author>
			<persName><surname>North</surname></persName>
		</author>
		<title level="m">Institutions, Institutional Change and Economic Performance</title>
				<imprint>
			<publisher>Cambridge University Press</publisher>
			<date type="published" when="1990">1990</date>
		</imprint>
	</monogr>
	<note>Political Economy of Institutions and Decisions</note>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">The fipa-os agent platform: Open source for open standards</title>
		<author>
			<persName><forename type="first">Stefan</forename><surname>Poslad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Phil</forename><surname>Buckle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Rob</forename><surname>Hadingham</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2000">2000</date>
			<publisher>PAAM</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Organizing multiagent systems</title>
		<author>
			<persName><forename type="first">Javier</forename><surname>Vázquez-Salceda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Virginia</forename><surname>Dignum</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Frank</forename><surname>Dignum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Autonomous Agents and Multi-Agent Systems</title>
		<idno type="ISSN">1387-2532</idno>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="307" to="360" />
			<date type="published" when="2005-11">November 2005</date>
		</imprint>
	</monogr>
</biblStruct>

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