RE: Minutes + Actions 12.06.2015

Hi all,
I added a simple example of a case where we might be interested in supporting multiple timestamps. In the example a sensor generates output at a predefined interval. Each observation made between outputs is associated with the same "generated at" timestamp, but they are additionally associated with their actual observation timestamp ("observed at").

I don't have permissions to edit in the Git but I left it as a comment under issue 11 (see https://github.com/streamreasoning/RSP-QL/issues/11)


Best regards,

Robin Keskisärkkä
PhD Student

[Linköping University]

Department
s-581 83 Linköping
Mobile: +46 (0)704909179
Please visit us at www.liu.se<http://www.liu.se/>



From: Wetz Peter [mailto:peter.wetz@tuwien.ac.at]
Sent: den 15 juni 2015 11:36
To: public-rsp@w3.org
Subject: Minutes + Actions 12.06.2015

Dear all,

thanks for the productive telco last Friday. The current activity on the mailling list leads me to the conclusion, that there are already/still some issues under discussion. Please get involved, so we will end up with a high quality data model :)

I created a wikipage showing the minutes of the telco plus all actions, so everyone who wants to catch up can do so: https://www.w3.org/community/rsp/wiki/Telecon_12.06.2015

We also defined a lot of ACTIONS to do until the next call. I took the liberty and assigned some of them to participants who seemed most reasonable for fulfilling them.

This is an overview of the actions:
ACTION: JPC to state on the Github-Page of our definitions that our model works for point in time semantics, but that it's possible to extend our model to time interval semantics.
ACTION: PW to create a first draft of the vocabulary on Github and start discussion.
ACTION: RK to add a simple example to see how multiple timestamps will be handled.
ACTION: JPC to add "If two graphs in the stream have the same timestamp, then they must have different predicates." to our definitions.
ACTION: JPC to add to our definition of a stream that a stream is ordered based on t and a given p.
ACTION: JPC to do: when we define "bounded substreams" we add a sentence stating that this is a similar concept to "window" from CQL.
ACTION: MDT to ammend the definitions of bounded substreams on github.
ACTION: all to discuss proposal of MDT.
ACTION: JXP to update requirements and use cases of SCEP via a separate wikipage.
ACTION: AL to create a wikipage containing the table frome the slides.
ACTION: JPC to get a link to the Serialization work of the Web of Things WG fro.m Sebastian.

Looking forward to the next call.

Best,
Peter