Telecon 10.07.2015
Participants
- Alasdair Gray (AG)
- Alejandro Laves (AL)
- Bernhard Ortner (BO)
- Daniele Dell'Aglio (DDA)
- Haroon
- Josiane Xavier Parreira (JP)
- Ali Intizar
Regrets
- Monika Solanki
- Adrian Paschke
- Jean-Paul Calbimonte
- Tara Athan
- Alessandra Mileo
- Peter Wetz
Minutes taken by
- Bernhard Ortner (BO)
Agenda
- Discuss TA's timestamped graph model proposal (see [1])
- Discuss Mini-Vocab (see [2])
- Discuss SCEP page (see [3])
Resources
- Semantics at GitHub: https://github.com/streamreasoning/RSP-QL/blob/master/Semantics.md
Minutes
JP: SCEP - Next step is look for use cases on the Wiki [3]
Tara's Model
AG & DDA: Tara's Model[4] - see Mail on our List [4]
DDA: In the serialization section, it is not clear to me which are the limitation of TriG? Is it really mandatory to define a serialization format, or can we adopt existing standards?
AG: Serialization should considered ?
DDA: We should check how this work overlaps with the one of the serialization group.
AG: Separate mathematical model and serialization
All AGREED ON: Serialzation moved to another page (sub group)
Time Ontology
AL: Time Vocabulary [5], Not clear which engine is the one that adds the receivedAtTime or if there are more engines that do that
AG: It is a n-ary option, so it connects a blank node and you annotate who created the triple
AL: Who models the timepoint when the triples enter the model, e.g. one graph is created by one engine and recieved by another one
AL: How do we relate the engine, the timestamps and the graph?
Benchmark
AL: The list contains metrics
BO: There may be overlaps, e.g. between Stream and RSP System.
AL: it is just a collection of all available metrics
DDA: The final step should be to combine the metrics in order to define KPI Metrics
AG: Suggests: Streams should probably renamed to input, include stored data and queries
AG: Consider existing related benchmarks and put it into the bottom of this page.
BO: Is historical data out of scope
AG: Benchmark should definitly consider historical data
DDA: Add the issue, and in the second step decide if we want to adress it.
Previous Actions
Discuss TA's timestamped graph model proposal
- Email discussion: https://lists.w3.org/Archives/Public/public-rsp/2015Jun/0053.html
- GitHub pull request: https://github.com/greenTara/RSP-QL/blob/master/Semantics.md
Next phone call
- 24.07.2015
Actions
ACTION: AL gets the Time Issue assigned in the GitHub
ACTION: AL Add references about existing benchmarks.
ACTION: DDA add references to existing works
ACTION: Rename according to AG's proposal: Input & RSP System metrics
ACTION: additional section on requirements (e.g. querying historical data)
ACTION: BO: add social Media use case
Links
[1] Discuss TA's timestamped graph model proposal - Discuss Mini-Vocab (see [1])
[2] https://www.w3.org/community/rsp/wiki/Semantic_CEP
[3] https://www.w3.org/community/rsp/wiki/Use_cases
[4] https://github.com/greenTara/RSP-QL/blob/master/Semantics.md
[5] http://www.essepuntato.it/lode/owlapi/
[6] https://raw.githubusercontent.com/streamreasoning/RSP-QL/master/TimeVocab.owl