Skip to content

Use consistent RFC 3986 terminology - #417

Open
mikekistler wants to merge 2 commits into
v1.2-devfrom
mdk/uri-terminology
Open

mikekistler wants to merge 2 commits into
v1.2-devfrom
mdk/uri-terminology

Conversation

@mikekistler

Copy link
Copy Markdown

This PR makes some small changes to make URI terminology consistent with the spec and with RFC 3986.

  • Use “relative reference” consistently for RFC 3986 §4.2 references throughout the specification.
  • Keep “URI-reference” for the broader RFC 3986 syntax.
  • Clarify that reusable-action $ref values are fragment-only same-document references.

Markdown validation passed: 0 lint issues, and all 164 hyperlinks checked were valid.

Addresses Terminology: relative URI reference #5538

@mikekistler
mikekistler requested a review from a team as a code owner October 19, 2026 17:23

@baywet baywet left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. However since 1.2.0 already "shipped". We'd need to start a 1.2.1 branch. Or 1.3.0. Depending on the urgency of these changes.

@smikulcik smikulcik left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@baywet

baywet commented Oct 20, 2026

Copy link
Copy Markdown
Member

LGTM. However since 1.2.0 already "shipped". We'd need to start a 1.2.1 branch. Or 1.3.0. Depending on the urgency of these changes.

disregard the comment about branching, I think we're good here. There's a larger discussion to have about 1.2.1 vs 1.3.0 though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants