Repository navigation
Replies: 1 comment 2 replies
|
Taking your third question up on the offer, rather than letting it sit. If the change controller asks what sits behind this registered path, we can hand over a dated series rather than a claim: AgentBI probes Most recent run, 2026-10-26, vantage KR (Seoul), one route, one attempt, redirects not followed:
One detail worth stating because it has been a live difference in this thread: all 62 row-2 positives also declare What this record is and is not. It is one observer, one vantage, and a hand-built list of well-known consumer/retail hosts, not a random draw — so it is evidence that the path is served in the wild, at a scale someone else can check with their own route. It is not evidence of "widely used" on its own; that needs Dean's run and anyone else's beside it, read through the same frame. We will keep running it daily. |
Uh oh!
There was an error while loading. Please reload this page.
Since 26 October 2026,
ucpis in the IANA Well-Known URIs registry (request protocol-registries/well-known-uris#92, opened by @igrigorik): status provisional, change controller Ilya Grigorik, reference the overview's profile structure section. https://www.iana.org/assignments/well-known-uris/Three things it opens, offered as questions:
Citing the registration in the spec. The overview defines the profile path but does not point to the registry entry. One line next to the path would let implementers see it is registered, and with which status.
One origin, several well-known resources. The same origin may also serve
agent-card.json(A2A, registered as permanent; the overview already uses it as an A2A endpoint example) andapi-catalog(RFC 9727, Standards Track: "A request to the api-catalog resource will return a document providing information about, and links to, the Publisher's APIs."). Should a business that publishes an api-catalog list its UCP profile there, or is the profile meant to stay the single entry point for commerce? A short note would keep implementations from diverging.From provisional to permanent. RFC 8615, Section 3.1: "The experts can change a provisional entry's status to permanent; in doing so, the experts should consider how widely used a value is and consult the community beforehand." The runs in Four measurements of the UCP surface, no shared denominator: a proposal for a common reporting frame #867 count hosts serving a profile at this path under a shared frame. If the change controller ever asks, that is the kind of record the expert would look at.
All reactions