docs: Draft RFDs for annotations and text addressing - #970
Merged
Conversation
…heme to support it Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
JeanMertz
force-pushed
the
rgrant-dev-annotation-channel
branch
from
September 10, 2026 14:19
13bc4bc to
7493e1f
Compare
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
2 participants
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.
D59, "Text Addressing Within Events" allows any range of text or range of entries to be pointed at or selected. It respects the
select=feature of the existingjp://URI, so what is addressed can be discontinuous.D52, "Event Annotations" provides a way to annotate any
jp://URI. Annotations are stored inannotations.jsonand not sent to the LLM provider layer. Aschema-idhelps tools identify what they wrote and can decode.