Clarification on RDF Message Stream definition #10
Description
Definition of RDF Message Stream
-
There is no clear definition of what is an RDF Message Stream. We introduce "An RDF Message Stream instance" .
What is an instance? We should first say what is an RDF message stream. It seems to be an ordered (unbounded?) sequence of RDF Messages. -
There is a Section 2 titled "RDF Message Streams". It is confusing, because the actual definition of it comes in Section 1.
Stream instance
I don't know if we need to derive the notion of "instance"? what is the rationale? It says it carries RDF messages. This sounds like a container notion but it's not a clear definition.
Producer and consumer
-
I think the producer should be defined first. The definition of consumer says it "listens" on the stream. I think this implies some sort of subscription or active listening, which in reality depends on the type of protocol. We could just say it consumes or accesses the stream using a given protocol.
-
Section 2 contains additional important information about consumers and producers. It might be better to integrate them in one place.
It is strange to say that the stream instance only exists when it is consumed. Why is it the case? The stream exists when it is produced as far as I am concerned. -
A function is called on the stream consumer [...] --> I think this is too "invasive" as a general statement. This really depends on the type of protocol.
-
It might be good to add a graphic depiction of RDF message, stream, producer and consumer.
RDF Message Log
It is not clear what the Log is with respect to the stream. It is defined as an ordered collection of messages. This to me sounds like the stream, with the difference that the log is bounded and the stream is not.
Log example
The example is problematic in the sense that it actually introduces a specific syntax for a serialization. This should only be introduced in Section 3.