1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
|
-----------------------
ContextKit
-------------------------
Context and Conversations
* The stuff that happens around you.
* Shared by the people that you interact with.
* Implicit part of a conversation.
* Ignoring context makes you look absent minded.
-------------------------
Context and Computers
* Conversation between Man and Machine also has context.
* What has the user done with the computer? "Recent documents",
"Browsing history", "Recently written emails", ...
* Getting additional clues without help from user: time of day, day of
week, geographical location, sitting still or moving, holding like a
camera or like a phone, Internet connectivity, ..
* Use those clues to improve the Man / Machine conversation.
* "Essential Digital Companion". (Yeah, right)
* Quite fuzzy, experimentation should be easy.
-------------------------
Context and Connecting People
* Computers facilitate conversations between people
* People want to share their context with their peers.
* Computers should help share the context of a conversation between
people as well.
-------------------------
So?
* Bring together 'context providers'
- DeviceKit, GeoClue, Meta tracker, Telepathy, BlueZ, ConnMan, oFono,
Sensors, ...
* Standardize high-level interfaces across desktops
- GNOME, KDE, Maemo, Moblin, Sugar, ...
* With bindings for all languages
- C, Glib, Qt, Python, Perl, JavaScript, C#, ...
* No silver bullet, regular programming, no magic enabler needed.
* Restrict, simplify, do the minimal useful thing
-------------------------
ContextKit
* "Global variables for the Desktop"
* Disciplined way of 'setting' those variables
* Concrete list of variables
* Rich type system
* Well integrated into many languages
-------------------------
Status
* First generation framework done
* Some properties defined
* Some buy in from other Nokia research projects.
* Only for Qt / C++ (sorry)
* A bit too static still
-------------------------
Architecture
* Decoupled
* Publish/subscribe for property values
* Run-time introspection
* XML property declarations with cache
* No central daemon
-------------------------
Demo and Docs
* Context Commander
* Subscriber
* Provider
-------------------------
Desktop Types
* Little hobby of mine
* Intersect a number of dynamic type systems to find the core
- Null, numbers, strings, lists, maps
Missing: association lists, turn out to be more useful
than maps for interchange.
* Define language neutral static types
- Enums, time, coordinates, ...
* Write bindings of static types for static languages, documentation
systems, introspection APIs.
-------------------------
Nano-DOM
* Mapping of subset of XML into Desktop Types.
* Used to define context properties
<key name="Battery.ChargeLevel"
type="percentage">
<doc>...</doc>
</key>
<key>
<name>Battery.ChargeLevel</name>
<type>percentage</type>
<doc>...</doc>
</key>
"key", { "name": "Battery.ChargeLevel", "type": "percentage",
"doc": "..." }
-------------------------
Static Desktop Type
* Dynamic desktop types: simple, fixed.
* Static desktop types: expressive, extensible
* Hierarchy, parameters.
<type name="uniform-list" base="list">
<params>
<type doc="Type of the elements"/>
</params>
<doc>...</doc>
</type>
<key name="Use.RecentDocuments">
<type>
<uniform-list type="nepomuk-uri"/>
</type>
<doc>...</doc>
</key>
-------------------------
Future
* Finding a home on freedesktop.org
* Lobbying for mind share
* Adding GVariant and Python into the picture
* Getting the D-Bus protocol right
* Simple aggregation in client, maybe
(Sum, append, average, max, ...)
* 'Context Cron'
|
