Skip to content

add(considered): /.well-known/vacation-rental.json is registered, not adopted - #199

Draft
jdevalk wants to merge 1 commit into
mainfrom
considered/vacation-rental-2026-09-05
Draft

add(considered): /.well-known/vacation-rental.json is registered, not adopted#199
jdevalk wants to merge 1 commit into
mainfrom
considered/vacation-rental-2026-09-05

Conversation

@jdevalk

@jdevalk jdevalk commented Sep 5, 2026

Copy link
Copy Markdown
Owner

What changed

One new file: src/content/considered/vacation-rental-json.md, rendered at /considered/. No spec page.

Why now

vacation-rental.json was added to the IANA Well-Known URIs registry on 19 August 2026 — provisional, referencing https://vacationrentalprotocol.com/spec/well-known-uri-v0.1, with an individual as change controller.

Why it did not get a page

This one is worth logging because it fails a different test from the recent run of registry turn-downs (scitt-keys, cyclic-trigger, xregistry), all of which were out-of-scope — infrastructure that happens to speak HTTP.

  • Scope: passes. A holiday-let site is an ordinary content origin, and this is a file such a site would publish for booking software to find. Same shape as api-catalog or nodeinfo.
  • Adoption: fails. No implementation, no consumer, no third-party discussion of the format anywhere I could search. The registration and its v0.1 document appear to be the entire public footprint.

So: too-early, and the revisit condition is simply someone using it.

Per the routine, this is flagged for you rather than decided unilaterally — if you think it earns a page anyway, say so and I will write one. My read is that a page recommending it today would be recommending a file no software reads.

Caveat on sourcing

vacationrentalprotocol.com was not reachable from this scan's environment, so the specification document itself is unverified. Everything the entry asserts is drawn from the IANA registry row, and the entry says so in the body rather than implying I read the spec.

Sources


Opened by the daily standards scan (ops/routines/daily-standards-scan.md). Draft — not for auto-merge.

… adopted

Provisional registration on 2026-08-19 pointing at a v0.1 document, with an
individual change controller. The scope test passes — this is a file a content
origin would serve, not infrastructure — but no implementation, consumer, or
third-party discussion is findable, so it is too-early rather than out-of-scope.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying specification-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2208f99
Status: ✅  Deploy successful!
Preview URL: https://940ffeee.specification-website.pages.dev
Branch Preview URL: https://considered-vacation-rental-2.specification-website.pages.dev

View logs

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.

1 participant