okf: clarify URL encoding for cross-link targets (SPEC 5.4)#186
Open
manumishra12 wants to merge 1 commit into
Open
okf: clarify URL encoding for cross-link targets (SPEC 5.4)#186manumishra12 wants to merge 1 commit into
manumishra12 wants to merge 1 commit into
Conversation
Section 5 did not state whether link targets require URL/percent encoding. Adds a short subsection: targets are ordinary markdown/CommonMark destinations resolved as bundle paths; keep segments URL-safe so no encoding is needed, and when a segment must carry a URL-unsafe character it MAY be percent-encoded and consumers SHOULD percent-decode before matching. Additive and backward-compatible. Addresses GoogleCloudPlatform#112.
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.
What
Adds a short subsection (SPEC section 5.4, "Link target encoding") clarifying whether OKF cross-link targets require URL/percent encoding — something section 5 does not currently address.
Clarification
Additive and backward-compatible (SPEC section 11 minor-version rules); no existing bundle changes meaning.
Addresses #112.