You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the document says "RSPs should process streams of data actively and in-stream, without the need of storing them". However, there are some reasonable operations that would require partial storage, just not storage of the entire past history. For example, to determine if two streams are isomorphic, some storage would be required due to the possibility of different sequential ordering in the serialization.
The text was updated successfully, but these errors were encountered:
I think this should be removed from the documents.
Syntactic and Semantics should only describe what an RSP is and not how a processing system has to process it. If someone wants to process it by using a DB approach she can do so, or if she wants to use stream processing system that use finite state machines, or any kind of rule engines to process the stream. In general we do not need to specify how it should be process. I think this sentence is on the document because of some historical reasons.
In general data stream processing system separate from the unbounded stream a small fraction of it (a bounded data set) and store it in main memory to be processed, because the semantic of query detection specifies the dataset that is should be applied to for pattern matching. We need this kind of storage anyhow to be able to windowing, but this does not mean to store the whole stream for example in a database.
But if someone has some high performance main memory data base and can store and index data in real-time, our specification of RDF stream should not have anything against it.
+1 for not arguing how to process streams in our documents. we could give "recommendations" or "best practices", but this should also not be our focus.
Currently the document says "RSPs should process streams of data actively and in-stream, without the need of storing them". However, there are some reasonable operations that would require partial storage, just not storage of the entire past history. For example, to determine if two streams are isomorphic, some storage would be required due to the possibility of different sequential ordering in the serialization.
The text was updated successfully, but these errors were encountered: