Cloud4all WP103 2013-05-08
Time and date
Important Information for the Meeting
This is a meeting of WP103 within the European Project Cloud4All. However, the minutes of the meeting will be made available to the public to allow people outside Cloud4All to follow our thoughts. If, in the meeting, you want to share confidential information that should not appear in the public minutes, you need to state so in the meeting. This is in line with the Cloud4All Consortium Agreement, section 10.
Please connect to the audio using gotomeeting:
1. To talk free using Web click. https://global.gotomeeting.com/join/705233502 Be sure to set AUDIO to Mic and Speaker (VoIP) - a headset is recommended.
2. Or, call in using your telephone.
Meeting ID: 705-233-502
- Australia: +61 3 9008 7854
- Austria: +43 (0) 7 2088 1036
- Belgium : +32 (0) 28 08 4345
- Canada: +1 (647) 497-9372
- France: +33 (0) 182 880 162
- Germany: +49 (0) 811 8899 6928
- Ireland: +353 (0) 19 030 053
- Italy: +39 0 693 38 75 53
- Netherlands: +31 (0) 208 080 212
- Spain : +34 931 81 6713
- Switzerland: +41 (0) 225 3311 20
- United Kingdom: +44 (0) 207 151 1801
- United States: +1 (805) 309-0027
Access Code: 705-233-502
- Andrés Iglesias from Technosite
- Ignacio Peinado from Technosite
- Guillem Serra from Barcelona Digital
D103.1) Rule sets for the automatic adaptation of the user profile to context-related features: This deliverable is the output of A103.1 and A103.2
Deliverable is due June the 30th, but there is a commitment to deliver it internally at least 3 weeks earlier, so the date is June the 10th.
The outline has been presented, after some minor changes it'll be communicated to SP1 list. In order to have text asap, the context rules will be written narratively as first step. The coding phase is suspended from now on and will be resumed after having a good amount of the deliverable done. We will employ a google doc (not a .doc on google drive) for ease of organisation.
The possibility of employing a brute force approach for avoiding prioritisation of rules was analysed. A estimation of having just four sensors with 100 different significant values and 1000 device/platform/application cases shows that a machine running Redis should have 100GB of RAM to afford O(1) computation, hence we will look for another approach, maybe ading lazyness to the evaluation of rules (like in Haskell)
Regarding device rules, knowledge about motes will be included under this section, including rules for aggregation and location and time windows. The $rightnow concept was clarificated.
- Finalise the outline of the deliverable.
- Communicate it to SP1 list.
- Highlight the state of the art to be explained for the deliverable.