Paper detail

Stream Containers for Resource-oriented RDF Stream Processing

We introduce Stream Containers inspired by the Linked Data Platform as an alternative way to process RDF streams. A Stream Container represents a single RDF data stream that can be accessed in a resource-oriented way which allows for better interoperability with the existing Semantic Web infrastructure. Stream Containers are managed by webservers that are responsible for implementing the S2R operator, i.e. calculating the window for their clients. The clients on the other hand can use a standard SPARQL processor in combination with HTTP requests to do RDF processing. Query results can be converted back to an RDF stream (R2S operator) by posting the data to a Stream Container. Our approach of resource-oriented RDF stream processing can lead to a better distribution of load and thus to better worldwide scalability. We give a general overview of the proposed architecture as well as the formal semantics of the overall system.

preprint2022arXivOpen access
0citations
0reviews
0saves
Nocode
Nodataset
0institutions

Next steps

Decide what to do with this paper

Use like or dislike for the fast social read. The more specific scholarly feedback stays available below when needed.

Log in to curate

Reading frame

Keep the important context close to the paper

Keep the important signals around this paper in one place: votes, save state, collection context, reviews and the metadata you need before deciding what to do next.

Institutions

Add specific reaction

Move through the context

Research map

Open full explorer

Move through nearby people, institutions, topics and adjacent work without leaving the paper page.

Building this graph slice

BZPEER is loading the nearby papers, people, topics and institutions for this page.

Structured reviews

0 review(s)

ContributeLeave structured feedbackUse the review template when you have a concrete strength, concern or method question.Open review form

No structured reviews yet. High-signal critique starts here.

Work discussion

0 comment(s)

DiscussAdd a high-signal commentKeep quick notes, caveats and replication pointers separate from formal reviews.Open comment form

No discussion yet. The first strong comment sets the tone.