What changed
The Agentic Resource Discovery specification reached v0.91 on 26 August 2026, and it still reads Status: Proposal 1. This version restates the description layer in terms of JSON-LD and namespaces: an entry is a JSON-LD node whose terms come from a default namespace unless it declares otherwise, and existing manifests remain valid entries unchanged 1. What it adds is a @context seam, so an entry MAY draw terms from additional namespaces without any change to the specification 1. The New Stack reports the query side: a REST interface whose required POST /search endpoint searches by task, plus optional endpoints for browsing available resources 2.
What the specification leaves open on purpose
The interesting half is what nobody standardised. The spec leaves open which namespaces beyond the default are recognised, and expects that set to grow 1; each discovery service sets its own rules for what it returns and which sources it trusts 2. Conformance covers the envelope and the search endpoint, and stops where the useful part starts: relevance and trust. Two conforming services can answer one task query with different resources, and both are right. The New Stack judges the DNS comparison insufficient for that reason 2. I would go further: the divergence is designed in and has no ceiling, since the vocabulary seam and the trust policy are both left to the participants. So you do not integrate a protocol here. You integrate one discovery service, and its ranking is the dependency.
Impact on your team
If you publish MCP tools or A2A agents 1, one move is cheap today and one is not. Cheap: confirm your manifest reads as a JSON-LD node under the default namespace, because v0.91 keeps existing manifests valid unchanged 1. Expensive: building a client against POST /search 2 while the document still says Proposal 1. I would wait on that. The policy question will not wait, and it is yours whatever the protocol does: when a search returns several capable resources, who picks the one your agent calls? If the answer is the discovery service, name that service and what it trusts now, before it becomes a runtime default nobody chose.