Re: Planning to close RDF Stream Processing due to inactivity unless we hear from you

Dear All,

Now there is also renewed interest in RDF stream processing from the
industry. There are a few companies (from startups to corporations)
dabbling in RDF change capture, streaming RDF ingest, and incremental
queries.

I'm representing NeverBlink – a deep-tech startup from Poland. We are
currently working on a few very relevant products:

   - Jelly-RDF <https://w3id.org/jelly> format for RDF stream
   representation (open source, Apache 2.0).
   - Jelly-Patch <https://w3id.org/jelly/specification/patch> format for
   RDF change capture / diff streams (open source, Apache 2.0).
   - Undisclosed larger product that includes various forms of RDF stream
   processing (will be open-sourced this year, and we hope it could become a
   vessel for a lot of the implementation work of the CG).

*We are therefore very interested in restarting this CG's work*,
particularly in the areas of RDF stream abstract models, RDF stream
serializations, RDF change capture streams, streaming SPARQL extensions,
and streaming lifting/annotation (RML).

This is a strong commitment from our side, as we believe that with the
space of RDF streaming slowly heating up, it is the right time to work
towards shared standards. We would be happy to actively help in organizing
the group's activities.

On Wed, 21 May 2025 at 15:13, Ian Jacobs <ij@w3.org> wrote:

> Thank you Danh and Pedro, for the updates. We will keep the group open and
> check in in six months.
>
> It would be great if you provided an update to the community via the CG’s
> wordpress instance linked from:
>  https://www.w3.org/community/rsp/
>
> If you have any questions, let me know. Thank you for your work,
>
> Ian
>
> > On May 20, 2025, at 11:01 PM, Le Phuoc, Danh, Dr. <
> danh.lephuoc@tu-berlin.de> wrote:
> >
> > Dear Pedro and W3C,
> >
> > We're at Technical University Berlin who are working on EU project
> SmartEdge https://www.smart-edge.eu/.  SmartEdge is working on
> distributed RDF processing engines, so, we would like to maintain the
> community group for our standardization and dissemination activities.
> >
> > Also, ECRIM members Rigo and Peter and Jean-Paul (HESSO) are
> participants of SmartEdge project.
> >
> > Best,
> >
> > Danh
> >
> > On 21.05.25, 05:45, "Pedro Martinez-Julia" <pedromj@ieee.org <mailto:
> pedromj@ieee.org>> wrote:
> >
> >
> > On Tue, May 20, 2025 at 06:04:49PM +0000, Team Community Process wrote:
> >> Dear participants in the
> >>
> >> RDF Stream Processing
> >> https://www.w3.org/community/rsp/ <https://www.w3.org/community/rsp/>
> >>
> >> In October 2024 we contacted you because your Community Group appeared
> >> to have become inactive (per [1]). Based on feedback in response to
> >> our message, we did not close the group, with the expectation that the
> >> group would soon become more active. Six months later, your group
> >> appears to still be inactive, and we are more inclined to close it
> >> unless we hear compelling reasons not to.
> >
> >
> > Dear Sir or Madam,
> >
> >
> > We are grateful to you for contacting before closing the group.
> >
> >
> >> If your group is in fact active, we ask that you respond to this email
> >> with answers to these two questions:
> >>
> >> * Is your group publishing any Specifications?
> >
> >
> > Right now, we are not publishing but we have not stopped working on
> > specifications for RDF stream processing. Sadly, the work is slow.
> >
> >
> >> * If so, what is the group expectation about future standardization of
> >> those Specifications at W3C or at some other standards body?
> >
> >
> > Some specifications are being worked on within the NMOP of the IETF. We
> > pan to present and discuss them here, in the W3C, after they stabilize.
> >
> >
> >> We also recommend the following:
> >>
> >> * Let us know where the activity is going on so that we can update
> >> our data and improve our tools.
> >>
> >> * Update your group home page with news of your activities. Chairs
> >> can use the group Wordpress instance of the group to post news; let
> >> us know if you have any questions.
> >>
> >> If you have good reason to believe the group will soon become active,
> >> please let us know.
> >
> >
> > With the little results we currently have, we decided we'd better focus
> > on the technical specifications and clarifying our goals and the common
> > directions.
> >
> >
> >> If you would like to schedule a call to discuss the current status of
> >> your group, your plans, and any obstacles to success, or you simply
> >> have questions about the CG program, please let us know.
> >>
> >> If you are merely hopeful it will, or if you would like us to close
> >> the group, or if we do not hear from you in the next 30 days, we will
> >> plan to close the group.
> >
> >
> > If possible, we would like the group to remain as it is, at least until
> > the end of 2026. This would be somewhat aligned with the global plan we
> > have for now in the IETF-NMOP. Please, consider it. Thank you very much..
> >
> >
> >> Thank you,
> >>
> >> CG/BG System
> >>
> >> [1] https://www.w3.org/community/about/faq/#close-inactive <
> https://www.w3.org/community/about/faq/#close-inactive>
> >
> >
> > Regards,
> > Pedro
> >
> >
> > --
> > Pedro Martinez-Julia
> > Email: pedromj@ieee.org <mailto:pedromj@ieee.org>
> > ---------------------------------------------------------
> > *** Entia non sunt multiplicanda praeter necessitatem ***
> >
> >
> >
> >
> >
> >
> >
>
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 917 450 8783
>
>
>
>
>
>
>

-- 
Piotr Sowiński
Co-founder @ NeverBlink