[rsp] work in progress

Dear all,

As said in last friday's call, we are still receiving comments for editing the Group Note:
https://docs.google.com/document/d/1bXPD5OTebOR7SckgIyoFFB_kLAerfvI1pBgot0izO3U

We have made a large number of changes, including general editing and integration of the query features wiki page. This last part needs a bit more consolidation. Please feel free to edit and/or comment on the doc or if you want to share something in this list, do it as well.

The other main point was the selection of tasks for the 2nd year. According to Avi's braninstorming tool, we have the top 5 following things:
Agree on query evaluation semantics





71




Structuring complex logic that a RSP engine could process (design patterns, tools, ...)





69




Syntax for RSP query language





67




Semantics of RSP language





66




Propose
 reference event model (well-aligned with existing time ontologies, 
supporting different time models, supporting serialisation, )

There is clearly a large interest in agreeing on an RSP language (1,3,4). So if you all agree this would be our main task. As discussed last friday we'd like to do it iteratively: we can agree on a basic query language and then preogress adding more operators/features.

As for the other suggestions (2 & 5). I do not fully understand proposal 2. Can you (those who proposed it) elaborate a bit more? 
About proposal 5 it is linked to serialisation and usage of well defined vocabularies (e.g. owl tie, prov) for representing stream items, if I understand right. Then this can be undertaken in depth by the serialisation taskforce that has already started within the RSP group.

Cheers from rainy Lausanne,

Jean-Paul