Show last authors
1 >What is {{mok/}}
2
3 {{mok short="false"/}} ({{mok/}} for short) is a model for //knowledge self-organisation//, conceived to pursue two main goals:
4
5 * //autonomously aggregate// data to build more "complex" heaps of information — possibly conveying novel knowledge previously unknown or hidden
6 * //autonomously spread// such information toward potentially interested knowledge prosumers — rather than be searched proactively
7
8 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.
9
10 >How {{mok/}} works
11
12 In order to do so, {{mok/}} is designed around three main sources of inspiration:
13
14 * //biochemistry//, providing metaphors for its basic abstractions
15 * //biochemical coordination//, as its computational and coordination model
16 * //behavioral implicit communication//, driving knowledge evolution
17
18 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//.
19
20 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//.
21
22 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.
23
24 >Vision
25
26 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.
27
28 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.
29
30 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.
31
32 >Motivation & Context
33
34 //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.
35
36 They pose peculiar challenges from the infrastructural standpoint:
37
38 * data size—from GBs to TBs
39 * scale—from organization-wide to world-wide
40 * dynamism—new information produced/consumed at fast pace — e.g. tweets
41 * diversity—both in information representation and usage destination openness — new users can enter/leave the system at any time
42 * unpredictability—since they involve humans, whose behaviour is rarely fully predictable
43
44 These challenges are usually faced using //brute force// approaches relying on ever-increasing (hopefully, endless) computational power and (ii) storage— "big data" techniques, non-relational large-scale DBs, "data-in-the-cloud" paradigm, other buzzwords.
45
46 //This won't scale forever//—e.g. what about the end of Moore's law?
47
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
50 This is where {{mok short="false"/}} comes in =)
51
52 {{include reference="Environment"/}}
Partita IVA: 01131710376 - Copyright © 2008-2021 APICe@DISI Research Group - PRIVACY