<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Todor Tagarev</style></author><author><style face="normal" font="default" size="100%">Venelin Georgiev</style></author><author><style face="normal" font="default" size="100%">Valeri Ratchev</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Taxonomy of Essential Services</style></title><secondary-title><style face="normal" font="default" size="100%">Radioelectronic and Computer Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Comprehensive approach</style></keyword><keyword><style  face="normal" font="default" size="100%">Critical Infrastructure</style></keyword><keyword><style  face="normal" font="default" size="100%">Planning</style></keyword><keyword><style  face="normal" font="default" size="100%">risk management</style></keyword><keyword><style  face="normal" font="default" size="100%">security policy</style></keyword><keyword><style  face="normal" font="default" size="100%">threats</style></keyword><keyword><style  face="normal" font="default" size="100%">Uncertainty</style></keyword><keyword><style  face="normal" font="default" size="100%">Vulnerabilities</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2012</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May 2012</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Radioelectronic and Computer Systems 6(58)</style></publisher><pub-location><style face="normal" font="default" size="100%">Sevastopol, Ukraine</style></pub-location><pages><style face="normal" font="default" size="100%">191-196</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Communities, countries and alliances cannot be efficient in preparing to meet diverse threats to their security within traditional organizational stovepipes. The boundaries between ‘internal’ and ‘external’ threats are getting fuzzier, and the vulnerabilities of governments, businesses and communities feed on each other, while the comprehensive approach is gaining traction in ever more security fields. The implementation of the comprehensive approach poses a number of methodological challenges. While it clearly requires coordination of various capabilities of a multitude of actors, it is less apparent which is the suitable organising concept. This paper takes as a starting point the concept of ‘essential services’ and suggests a taxonomy, that would allow to treat threats, vulnerabilities and risk in a common comprehensive framework. The taxonomy has been developed with a specific purpose in mind, and thus refers to European Essential Services (EES). We nevertheless reason that it can be replicated to support decision making at other levels, e.g. in national security policy making and planning. </style></abstract><issue><style face="normal" font="default" size="100%">58</style></issue></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">David Camacho</style></author><author><style face="normal" font="default" size="100%">José M.Molina</style></author><author><style face="normal" font="default" size="100%">Daniel Borrajo</style></author><author><style face="normal" font="default" size="100%">Ricardo Aler</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">MAPWEB: Cooperation between Planning Agents and Web Agents</style></title><secondary-title><style face="normal" font="default" size="100%">Information &amp; Security: An International Journal</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Agent Architecture</style></keyword><keyword><style  face="normal" font="default" size="100%">Information System</style></keyword><keyword><style  face="normal" font="default" size="100%">Intelligent Agents</style></keyword><keyword><style  face="normal" font="default" size="100%">Multi-Agent Systems</style></keyword><keyword><style  face="normal" font="default" size="100%">Planning</style></keyword><keyword><style  face="normal" font="default" size="100%">Web Agents</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2002</style></year></dates><volume><style face="normal" font="default" size="100%">8</style></volume><pages><style face="normal" font="default" size="100%">209-238</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The paper presents MAPWEB (Multi-Agent Planning on the Web), a multi-agent system for cooperative work between different intelligent software agents whose main goal is to solve user planning problems using the information stored in the World Wide Web (WEB). MAPWEB is made of heterogeneous mixture of intelligent agents whose main characteristics are cooperation, reasoning, and knowledge sharing. The architecture of MAPWEB uses four types of agents: UserAgents that are the bridge between the users and the system; ControlAgents (Manager and Coach Agents) that are responsible for managing the rest of the agents; PlannerAgents that are able to solve planning problems; and, finally, WebAgents whose aim is to retrieve, represent, and share information obtained from the WEB. MAPWEB solves planning problems by means of cooperation between PlannerAgents and WebAgents. Instead of using the PlannerAgent to solve the whole planning problem, the PlannerAgent focuses on a less restricted (and therefore easier to solve) problem (what we call an abstract problem) and cooperates with the WebAgents to validate and complete abstract solutions. In order for cooperation to take place, a common language and data structures have also been defined.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record></records></xml>