Modifiche per il documento Panoramica

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,36 +1,33 @@
1		-{{include document="Main.MacroSheet"/}}{{include document="MoK.MacroSheet"/}}{{velocity}}
2		-= #moklong() =
	1	+>What is {{mok/}}
3	3
4		-=== What is #mok() ===
5		-
6		-#moklong() (#mok() for short) is a model for //knowledge self-organisation//, conceived to pursue two main goals:
	3	+{{mok short="false"/}} ({{mok/}} for short) is a model for //knowledge self-organisation//, conceived to pursue two main goals:
7	7	* //autonomously aggregate// data to build more "complex" heaps of information — possibly conveying novel knowledge previously unknown or hidden
8	8	* //autonomously spread// such information toward potentially interested knowledge prosumers — rather than be searched proactively
9	9
10		-Thus, #mok() promotes the idea that //data is alive//, that information is a living thing continuously and spontaneously interacting with other information as well as with its prosumers, evolving itself accordingly.
	7	+Thus, {{mok/}} promotes the idea that //data is alive//, that information is a living thing continuously and spontaneously interacting with other information as well as with its prosumers, evolving itself accordingly.
11	11
12		-=== How it works ===
	9	+>How {{mok/}} work
13	13
14		-In order to do so, #mok() is designed around three main sources of inspiration:
	11	+In order to do so, {{mok/}} is designed around three main sources of inspiration:
15	15	* //biochemistry//, providing metaphors for its basic abstractions
16	16	* //biochemical coordination//, as its computational and coordination model
17	17	* //behavioral implicit communication//, driving knowledge evolution
18	18
19		-As far as the basic #mok() abstractions are concerned, in #mok() knowledge //atoms// are generated by knowledge sources in shared spaces – //compartments// –, self-aggregate to shape knowledge //molecules//, and autonomously move toward knowledge prosumers – //catalysts// –, whose actions (either epistemic or not) are represented as //enzymes//.
	16	+As far as the basic {{mok/}} abstractions are concerned, in {{mok/}} knowledge //atoms// are generated by knowledge sources in shared spaces – //compartments// –, self-aggregate to shape knowledge //molecules//, and autonomously move toward knowledge prosumers – //catalysts// –, whose actions (either epistemic or not) are represented as //enzymes//.
20	20
21		-As far as the #mok() computational and coordination model is concerned, #mok() features //biochemical tuple space like repositories// – compartments – for the creation, aggregation, diffusion and consumption of knowledge atoms and molecules. As such, compartments are in charge of locally evolving knowledge and of (ii) distributing knowledge across networked compartments, according to the (biochemically inspired) coordination laws installed—//reactions//.
	18	+As far as the {{mok/}} computational and coordination model is concerned, {{mok/}} features //biochemical tuple space like repositories// – compartments – for the creation, aggregation, diffusion and consumption of knowledge atoms and molecules. As such, compartments are in charge of locally evolving knowledge and of (ii) distributing knowledge across networked compartments, according to the (biochemically inspired) coordination laws installed—//reactions//.
22	22
23		-As far as the user interaction model is concerned, #mok() borrows concepts from the cognitive theory of behavioral implicit communication to enable //anticipative coordination// driven by users' epistemic actions. Briefly, any action undertaken by users is interpreted by #mok() so as to mind-read users intentions and react accordingly.
	20	+As far as the user interaction model is concerned, {{mok/}} borrows concepts from the cognitive theory of behavioral implicit communication to enable //anticipative coordination// driven by users' epistemic actions. Briefly, any action undertaken by users is interpreted by {{mok/}} so as to mind-read users intentions and react accordingly.
24	24
25		-=== Vision ===
	22	+>Vision
26	26
27		-Summing up, a #mok() system should be seen as a network of shared information repositories, in which some source entities continuously and spontaneously put data chunks.
	24	+Summing up, a {{mok/}} system should be seen as a network of shared information repositories, in which some source entities continuously and spontaneously put data chunks.
28	28
29	29	Such data may then aggregate so as to reify some (potentially) relevant "knowledge-related patterns" – e.g. linking two news stories talking about the same person or written by the same author, read by the same prosumer or both related to a third news story – and (ii) diffuse among these networked shared spaces toward the (potentially) interested users—e.g. papers about MAS should strive to reach MAS researchers' repositories.
30	30
31		-Users can interact with the system through epistemic actions – e.g. read a post, contribute to a wiki, highlight words in an article, ... – which are tracked and exploited by the #mok() system to influence knowledge evolution transparently to the user—e.g., a user highlighting a given word may imply such user being highly interested in such topics, thus #mok() can react by, e.g., increasing rank position of related topics in a search query.
	28	+Users can interact with the system through epistemic actions – e.g. read a post, contribute to a wiki, highlight words in an article, ... – which are tracked and exploited by the #mok() system to influence knowledge evolution transparently to the user—e.g., a user highlighting a given word may imply such user being highly interested in such topics, thus {{mok/}} can react by, e.g., increasing rank position of related topics in a search query.
32	32
33		-=== Motivation & Context ===
	30	+>Motivation & Context
34	34
35	35	//Knowledge-intensive environments// and //socio-technical systems// are systems combining business processes, technologies and people's skills to store, handle, make accessible – in one word, manage – very large repositories of information—e.g. wiki portals, online press, enterprise social networks, etc.
36	36
...	...	@@ -47,5 +47,5 @@
47	47
48	48	One possible research line departs from the following question: why do we stick to view data as passive, "dead" things to run algorithms upon in the traditional I/O paradigm?
49	49
50		-This is where #moklong() comes in =)
51		-{{/velocity}}
	47	+This is where {{mok short="false"/}} comes in =)
	48	+