pdf - 395 K - Ecole des mines de Nantes

More documents

Recommendations

Info

2.5.2 The Brainstorm designIn the Brainstorm approach, an object becomes an agent thanks to its associations to agentcapabilities that are provided by the meta-level [62]. The meta-level is composed of metaobjectsand each of them provides a single capability. So an agent is composed of an objectand a set of meta-objects. Agent capabilities include communication, perception, knowledge.For example, the communication meta-object intercepts the messages received by the objectand treats them. In addition, a second meta-level is composed of reaction and deliberationmeta-objects that manage the behavior of the first meta-level.The second meta-level has a similar role as the Supervision Module in the DIMA approach.Yet here behaviors are not aggregated by the agentified object but defined at the meta-level.The drawback is that it requires that meta-objects are supported.2.5.3 The FIPA-OS designIn FIPA-OS the root class for agents is the abstract class FIPAOSAgent that essentiallyspecifies behavior for:- registering/unregistering to the agent management services defined by FIPA specifications;- receiving messages;- handling Tasks.A Task defines an activity of an agent. It has explicitly defined states and it can have subtasks.It registers to certain types of messages that it is in charge of handling. Thus a Task isautomatically activated when some kinds of messages are received. A Task may create a newthread, enabling agents to perform parallel processing.This approach provides a good modularity for handling messages by delegating this job toTasks automatically. On the opposite, other approaches centralize message treatment in acommunication module. However, there is no global supervision of the agent’s behavior foractivating or interrupting activities.MSc EMOOSE Thesis – http://www.emn.fr/EMOOSE 23
3 MetadataDuring the earlier investigations in the start of the project, metadata was examined as a basefor inferring virtual semantic links between resources. However, the use of metadata wouldimply to abandon the generic nature of our solution. The issue of interoperability presented inthe last section about metadata illustrates this problem. It was therefore decided not make anyuse of metadata in our solution.Note: we consider the word “metadata” as a singular as many authors do.3.1 DefinitionMetadata is literally “data about data”. More precisely, Dempsey and Heery define it as:“Data associated with objects which relieves their potential users of having to have fulladvance knowledge of their existence or characteristics.” [63]The term ‘user’ can refer to a program or service (e.g. a software agent) as well as a person.The object described by the metadata can be a resource of any type: web page, text, image…It can also be an aggregation of several resources, as long as it can be manipulated as a singleone [64].Metadata can reflect the following features of the resources [64]: content (intrinsic), context(about the creation of the resource), intrinsic structure (associations between resourcescontained in the resource) and extrinsic structure (associations between the resource and otherresources).There exist different sorts of metadata that can be characterized on many different points [64,65] including:- Source: internal/external, creation at resource creation time or later.- Creator: human (resource creator/user) or program (portal, resource creation tool).- Nature: created by non-specialists or by experts.- Status: static/dynamic, long-term/short term.- Granularity level: relates to a single resource or a collection of resources.3.2 Roles and useDifferent actors need metadata for different purposes [66-68]. First, users need resourcedescriptions to search across the range of available resources in order to find, identify andinterpret them. They must be able to combine and compare descriptions in order to select theresources that fit to their needs then obtain them.Then metadata increases the accessibility of resources to users. In particular, metadata enablesrepository administrators to create catalogs or indexes that ease searches and resourcediscovery. The creation of such indexes can be automatically performed by a program if allthe resources of the target repository or repositories have consistent metadata. It also allowsfor the use of search engines, particularly when the resources are not text-based.MSc EMOOSE Thesis – http://www.emn.fr/EMOOSE 24
Page 1: Vrije Universiteit Brussel - Belgiu
Page 4 and 5: ContentsAbstract 1Acknowledgements
Page 6 and 7: (4) Table UP_SUP (matches User Prof
Page 9 and 10: content providers’ interpretation
Page 11 and 12: - Active profiling consists in aski
Page 13 and 14: 2 Agents2.1 Overview2.1.1 Definitio
Page 15 and 16: (1) each agent has incomplete infor
Page 17 and 18: MASs need an organization for speci
Page 19 and 20: However, the usefulness of personal
Page 21 and 22: they often provide implementation o
Page 23: 2.5 Design2.5.1 The DIMA designIn [
Page 27 and 28: This requires some agreement and st
Page 29 and 30: 4 PerspectivesRecommender systems m
Page 31 and 32: way Lego blocks should be assembled
Page 33 and 34: usiness intelligence is generated.
Page 35 and 36: important than memory space optimiz
Page 37 and 38: The graph is then formatted to be v
Page 39 and 40: Chapter 4: Implementation1 Implemen
Page 41 and 42: (1) A Name Server (NS) maps every a
Page 43 and 44: the agent terminates, the thread is
Page 45 and 46: 4 Application level4.1 OverviewThe
Page 47 and 48: 4.3 User Agent MakerThis agent has
Page 49 and 50: Thus the profile, node and link cla
Page 51 and 52: BIProviderR : Provide_Business_Inte
Page 53 and 54: to enable users to explicitly speci
Page 55 and 56: ConclusionA “minimalist” approa
Page 57 and 58: Appendix A: Addendum onIndustrial I
Page 59 and 60: Appendix B: SQL Tables Design1 Tabl
Page 61 and 62: Appendix C: Conference PaperA paper
Page 63 and 64: very large repositories of learning
Page 65 and 66: popularity of the link (the bigger
Page 67 and 68: Appendix D: Source Code1 Agent infr
Page 69 and 70: public static bool ProcessIsMainHos
Page 71 and 72: string path = MakePath(".", Middlew
Page 73 and 74: System.Messaging.MessageQueue queue
Page 75 and 76:
public static NameServer GetNS(){if
Page 77 and 78:
}}}table[agentId] = address;}}/// /
Page 79 and 80:
****** NON-STATIC PART ******// Tab
Page 82 and 83:
}}}return (AgentId) first;using Sys
Page 85 and 86:
{}return Subject.GetHashCode() + Na
Page 87 and 88:
name in order to allow for the retr
Page 89 and 90:
}// Start agent's main Thread.Threa
Page 91 and 92:
}DirectoryFacilitator.GetDF().Unreg
Page 93 and 94:
{/// /// Allows for specific conver
Page 95 and 96:
}Monitor.Exit(aLock);public overrid
Page 97 and 98:
Allows for synchronized Message exc
Page 99 and 100:
esource./// /// public string GetMa
Page 101 and 102:
}}private void RunTerminationExamin
Page 103 and 104:
}private Message RequestUACreation(
Page 105 and 106:
}msgQueue.AddFilters(new MessageCat
Page 107 and 108:
Message received: interrupt preterm
Page 109 and 110:
19. Class Architecture.DBManagerAg
Page 111 and 112:
}}connection.Close();/// /// For sa
Page 113 and 114:
using System.Collections;namespace
Page 115 and 116:
namespace Architecture.Profiles{usi
Page 117 and 118:
private UP(DataRow row) : this(newU
Page 119 and 120:
}DataRow[] rows = Row.GetChildRows(
Page 121 and 122:
}adapter.Update(Data);//***********
Page 123 and 124:
internal static readonly string LAS
Page 125 and 126:
}}Row[OCCURRENCES] = Occurrences +
Page 127 and 128:
}get{}return Data.Rows.Find(_name);
Page 129 and 130:
private static SqlDataAdapter adapt
Page 131 and 132:
}foreach (ILink link in links){if (
Page 133 and 134:
}}}private DataRow Row{get{return D
Page 135 and 136:
18. N. Good, et al. Combining colla
Page 137 and 138:
49. D. Derbyshire, et al., Agent-Ba
Page 139:
83. Council for Higher Education Ac
show all

pdf - 395 K - Ecole des mines de Nantes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?