Jump to content

Telecon 03.03.2026

From RDF Stream Processing Community Group

3rd March 2026

Agenda:

  • Task force update/discussion: 
  • RDF Messages (Piotr)
  • Consumption/Ingestion (Jean-Paul)
  • Processing, Implementation, benchmark (Pieter Bonte)
  • Other businesses: 
  • i)Reviewing remaining action points from previous meetings
  • ii)How to group UCs and connect to task forces
  • iii)Events/next F2F meetings?

Participants

  • Danh Le Phuoc (TU Berlin)
  • Robin Keskisärkkä (LiU)
  • Anastasiya Danilenka (NeverBlink)
  • Piotr Sowiński (NeverBlink)
  • Pieter Colpaert (Ghent)
  • Mario Scrocca (Cefriel)
  • Anh Le Tuan (TUB)
  • Rafael (TUB/BMW)

Execuses:

  • Pieter
  • Tobias

Minutes (Piotr, Anatasiya) Agenda: Task force update/discussion:

  • RDF Messages (Piotr)

Consumption/Ingestion (Jean-Paul) Processing, Implementation, benchmark (Pieter Bonte)  Other businesses: Reviewing remaining action points from previous meetings How to group UCs and connect to task forces Events/next F2F meetings? RDF Messages (Piotr): We had a TF meeting. It was productive, discussed issues. Minutes from meeting are available: https://www.w3.org/community/rsp/wiki/RDF_Messages_Task_Force/Meeting_2026-02-13 We made fixes in the spec: PRs are available on GH. One PR is still open, comments are welcome on RDF Message Stream definition: https://github.com/w3c-cg/rsp/pull/18 Refined note about Message Scope Under review: message stream producer and consumer and how it relates to http and mqtt protocols. It caused discussions in TF meeting, so more input is welcome. Serialization format discussion: we use directives for message separations (like in triples and quads in RDF 1.2). We will discuss it at the next TF meeting. JSON-LD and YAML-LD examples. Are under discussion. Got feedback with JSON-LD group. No concrete results, but a few takeaways to discuss in the next TF meeting. PieterC: where the serialisations should be described? Currently JSON-LD and the likes are in the spec. What is the final goal? Piotr: move to the separate document. Now it is in the same document because it is easier and more visible PieterC: should RDF messages be supported in JSON-LD group or should it be in CG? We can ask JSON-LD group add an implementation of RDF messages to them Piotr: JSON-LD people are a bit confused, so we need to finalise it within our group first and then reach out to them. PieterC: does JSON-LD charter have a streaming part? Piotr: they removed streaming from the chart Piotr: we need to review PR, come up a with new directive-based delimiting. Work on serialisation and profiles/ Danh: will there be another TF meeting? Piotr: a poll for the TF will be send next week to decide on the date. Other TFs Danh: providing use cases – Mario were to provide a use case on traffic data, there was also some more use case from Anh Mario: Was waiting for a page in the wiki to write down the use case on transport data Anh: no progress so far Danh: We need to create a wiki to gather use cases Danh: Any other use cases? Piotr: Yes, we can contribute some use cases. Other topics Danh: any other topics? Danh: currently only RDF Messages is moving forward. Other TFs are not present today. Danh: Pieter Bonte reported some progress, on processing, ingestion, a dataset for that. There is a lot of interest in building systems for RSP, but many systems are out of date. Danh: NeverBlink has a system, but closed-source, yes? Piotr: Yes, but will be open core, but release will be done later to the open source community. We can provide academics with a free academic license for benchmarking and research. We can also share conformance results. PieterC: We are mostly in the JS community, we are working on relevant project. Will coordinate internally to see what we can contribute. Danh: we also have a commercial interest for vehicle-related use cases. We work with companies on an embedded version of CQELS. In April we may open-source a vehicle solution aligned with COVESA. Danh: We have some benchmarking results for stream reasoning with this system. Danh: Riccardo last time talked about benchmarking... but we are more interested in domain specific benchmarks (e.g., number of vehicles served) Danh: any other items for today? PieterC: Piotr and I submitted a poster paper for ESWC, about RDF Messages. PieterC: we want to attract more people to the RSP CG, more people interested in our work. Danh: We are planning for a COST action for the community... November is the deadline. We have to start moving on this topic. Danh: if no further items, we will close the meeting. Danh: This time I will send the invite earlier to ensure more people can attend. Danh: see you next month, April 7. TODO: Danh: coordinate with Pieter to create a use case wiki Piotr: a poll for the RDF Messages TF next meeting

Retrieved from "https://www.w3.org/community/rsp/wiki/index.php?title=Telecon_03.03.2026&oldid=801"