Skip to content

Complete refget → refget sequences naming update#115

Open
nsheff wants to merge 1 commit into
masterfrom
fix/refget-naming-remaining
Open

Complete refget → refget sequences naming update#115
nsheff wants to merge 1 commit into
masterfrom
fix/refget-naming-remaining

Conversation

@nsheff
Copy link
Copy Markdown
Member

@nsheff nsheff commented May 28, 2026

Summary

Changes

  • Line 27: "Refget was designed..." → "Refget sequences was designed..."
  • Line 133: "Refget optionally allows..." → "Refget sequences optionally allows..."
  • Line 137: "unique within the refget implementation" → "refget sequences implementation"
  • Line 161: "by the refget implementation" → "refget sequences implementation"
  • Line 392: "Refget server" → "Refget sequences server" (example)
  • Line 479: "Refget implementations MUST support..." → "Refget sequences implementations..."

Not changed (intentionally)

  • "refget Checksum Algorithm" (lines 108-109) — algorithm is shared across sequences and seqcol
  • refget JSON field name (API spec)
  • "Refget" as naming authority in appendix table
  • Historical specification links

Fixes #94

Completes the naming update from PR #109. Changes remaining
instances where "refget" should be "refget sequences" in
prose text, while preserving "refget" where it correctly
refers to the umbrella term (checksum algorithm section)
or API field names.

Fixes #94
@nsheff nsheff requested a review from tcezard May 28, 2026 12:44
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.

Update refget naming to refget sequence more thoroughly in the specification

1 participant