Discovering RDF Messages support in live streams#35
Open
pietercolpaert wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a concise discovery model for live RDF Message Streams across push-based and message-based protocols. It defines how channels such as SSE, WebSockets, Kafka, MQTT 5, broker systems, and Jelly gRPC can advertise that their native protocol messages carry RDF Messages, primarily through RDF-Message-Content-Type or protocol-native equivalents. This makes message boundaries explicit at the transport level, clarifies that blank node identifiers are scoped per protocol message, and prevents consumers from accidentally merging RDF data across messages. The PR also adds interoperability tests for these live stream discovery mechanisms, including JSON-LD context links, WebSocket serialization negotiation, broker metadata, and Jelly gRPC frames.
Fixes #33