Changes for page Products

From version 17.1
edited by Andrea Omicini
on 11/12/2020 16:33
Change comment: There is no comment for this version
To version 19.1
edited by Andrea Omicini
on 12/12/2020 00:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -48,7 +48,7 @@
48 48  The implementation is Java-based, developed on top of the TuCSoN agent infrastructure, and deployable also on low-cost devices such as Raspberry PI2.
49 49  
50 50  *Space*: [#hm() Home|Products.HomeManager]
51 -\\
51 +<br />
52 52  *Contact*: [Roberta Calegari|RobertaCalegari.WebHome]
53 53  
54 54  
... ... @@ -96,7 +96,7 @@
96 96  * as a reaction language - #respect() supports the notion of reaction as a computational activity to be executed locally to a tuple centre in response to communication events, by providing for both a logic-based syntax for the definition of reactions, and a model for their execution.
97 97  
98 98  *Space*: [#respect() Home|ReSpecT.WebHome]
99 -\<br />
99 +<br />
100 100  *Contact*: [Stefano Mariani|StefanoMariani.WebHome]
101 101  
102 102  1.1 #simpa()
... ... @@ -131,7 +131,7 @@
131 131  Recently a new and extended version of the methodology has been proposed, which takes into account both the Agents and Aartifacts (#aea()) meta-model, and a mechanism to manage the complexity of system description.
132 132  
133 133  *Space*: [#soda() Home|SODA.WebHome]
134 -\\
134 +<br />
135 135  *Contact*: [Ambra Molesini|AmbraMolesini.WebHome]
136 136  
137 137  1.1 #traumatracker()
... ... @@ -143,7 +143,7 @@
143 143  The key functionality of #traumatracker() is to keep track of relevant events occurring during the management of a trauma, for two basic purposes. The first one is about tracking, i.e. to have an accurate documentation of the trauma, to automate the creation (and management) of reports and to enable offlne data analysis. The second one is a first kind of assistance, in terms of the real-time generation of warnings and suggestions to be perceived through the smartglasses, by analysing and reasoning upon the tracked events and data. The system has been designed and developed using cognitive agent technologies based on the Belief-Desire-Intention (BDI) architecture, as supported by the JaCaMo agent platform.
144 144  
145 145  *Space*: [#traumatracker() Home|TraumaTracker.WebHome]
146 -\\
146 +<br />
147 147  *Contact*: [Angelo Croatti>https://www.unibo.it/sitoweb/a.croatti/en], [Sara Montagna>https://www.unibo.it/sitoweb/sara.montagna/en], [Alessandro Ricci>https://www.unibo.it/sitoweb/a.ricci/en]
148 148  
149 149  
... ... @@ -161,7 +161,7 @@
161 161  This suits both roles of Internet agents, that is, as either network-aware entities or (network-unaware) local agents.
162 162  
163 163  *Space*: [#tucson() Home|TuCSoN.WebHome]
164 -\\
164 +<br />
165 165  *Contact*: [Stefano Mariani|StefanoMariani.WebHome]
166 166  
167 167  
... ... @@ -171,5 +171,5 @@
171 171  #tuprolog() is a Java-based light-weight Prolog for Internet applications and infrastructures. For this purpose, #tuprolog() is designed to feature some interesting qualities: it is ~~easily deployable~~, just requiring the presence of a Java VM and an invocation upon a single JAR file; its core is both ~~minimal~~, taking the form of a tiny Java object containing only the most essential properties of a Prolog engine, and ~~configurable~~, thanks to the loading and unloading of predicates, functors and operators embedded in libraries; the ~~integration between Prolog and Java~~ is as wide, deep, clean as possible; finally, ~~interoperability~~ is developed along the two main lines of Internet standard patterns and coordination models.
172 172  
173 173  *Space*: [#tuprolog() Home|Tuprolog.WebHome]
174 -\\
174 +<br />
175 175  *Contact*: [Enrico Denti|EnricoDenti.WebHome]