Repository navigation
Clarify portable attachment references and digest metadata - #80
Open
Ma11hewThomas wants to merge 6 commits into
Open
Ma11hewThomas wants to merge 6 commits into
Ma11hewThomas wants to merge 6 commits into
Conversation
…-05-attachment-guidance
…-05-attachment-guidance
…-05-attachment-guidance
…-05-attachment-guidance
Ma11hewThomas
marked this pull request as ready for review
October 25, 2026 17:44
This branch has not been deployed
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
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.
Clarifies when to prefer durable attachment references and how producers may retain local paths and digest metadata in namespaced attachment
extra. Local paths remain valid, uploading is optional, and digest structure remains producer-defined. Keeps schema path descriptions concise and the detailed guidance in §12.Tracked in CTRF 0.3.0 preparation. Depends on #79; merge in stack order.
Validation: 22 reference cases, 160 normative cases, 9 standalone and 10 complete inline examples pass with AJV. Embedded-schema byte equality and diff checks pass.