add(considered): /.well-known/xregistry is a registry server's URI, not a website's - #185
Merged
Merged
Conversation
…ot a website's xRegistry registered the `xregistry` well-known suffix with IANA on 2026-08-19. The host expected to answer it is a metadata registry server for messaging and eventing infrastructure, not a site anyone visits, so there is no visitor, crawler, or agent outcome to write a page around. Records the turn-down and states the general rule the last three such registrations have all hit: the Well-Known URIs registry is a namespace shared by everything that speaks HTTP, not a to-do list for websites. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
ac82a4d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7337a10b.specification-website.pages.dev |
| Branch Preview URL: | https://add-considered-xregistry-202.specification-website.pages.dev |
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 changed
Adds one entry to
src/content/considered/(rendered at/considered/) recording why/.well-known/xregistrydoes not get a spec page. No spec pages, no derived surfaces, no SKILL.md change (page count and categories are unchanged).Why now
Found by the daily standards scan (2026-08-21). IANA's Well-Known URIs registry gained the
xregistrysuffix on 2026-08-19, change controller "xRegistry Authors", reference "xRegistry core v1 specs".Primary sources
Reason:
out-of-scopeThe test is which host is expected to answer.
security.txt,change-passwordandapi-catalogare served by the site a person or crawler visits, and a site is better or worse for serving them./.well-known/xregistryis served by a metadata registry for messaging and eventing infrastructure, whose clients are other services. A content site that never serves it is not a worse website, and the "Why it matters" cannot be phrased in terms of visitors, crawlers, or agents.That the specs are still at release candidate is a second reason to wait, but not the operative one — a 1.0 would not change the scope argument, which is why
reasonisout-of-scoperather thantoo-early.revisit: the document moving from the registry server to the site — i.e. the spec or a consumer starting to expect an ordinary content origin to answer it.Note on the third-in-a-row framing
This is the third registration in a month to fail the same test, after
/.well-known/scitt-keys(#178) and/.well-known/cyclic-trigger(#184), both still open drafts. Rather than write a third near-identical entry, this one states the general rule — the Well-Known URIs registry is not a to-do list for websites — and is positioned as the reference case for it. If you would rather consolidate all three into one entry, say so and I will rework them.Verification limits
raw.githubusercontent.com,xregistry.ioandcncf.iowere unreachable from the scan sandbox, so the entry makes no claim about the contents of the/.well-known/xregistrydocument itself — only about what xRegistry is and whose origin serves it, both of which are sourced from the repository README and the CNCF project listing. The scope argument does not depend on the file's contents.npm run buildpasses (168 pages, unchanged). Draft — not for merge without your call.🤖 Generated with Claude Code