Skip to content

fix(agent-readiness): aipref attachment draft expired — say so on Content Signals - #131

Draft
jdevalk wants to merge 2 commits into
mainfrom
fix/aipref-attach-draft-expired-2026-07-28
Draft

fix(agent-readiness): aipref attachment draft expired — say so on Content Signals#131
jdevalk wants to merge 2 commits into
mainfrom
fix/aipref-attach-draft-expired-2026-07-28

Conversation

@jdevalk

@jdevalk jdevalk commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

One paragraph in the Status of the proposal section of content-signals, splitting the IETF work into its two halves and saying plainly which one is dead. updated bumped to 2026-07-28.

Why now

The page said the IETF and IAB Tech Lab efforts were both ongoing and that "the vocabulary is converging". Half of that is no longer true:

  • draft-ietf-aipref-vocab — alive. Revision -06, last updated 2026-04-27, WG document on the Proposed Standard track.
  • draft-ietf-aipref-attachexpired and archived. Last revision 2025-10-28, so it lapsed in April 2026. Nothing has replaced it, and the WG's August 2026 milestone for an attachment specification is now at risk.

attach is the document that would define how a preference actually binds to content over HTTP — i.e. the thing that would put Content-Signal: in robots.txt on an IETF track. A reader following our page today would reasonably conclude that binding is standards-track. It isn't; right now it rests on the IAB Tech Lab spec and on validator convention.

Status

optional is unchanged and still the honest slot — the page already told readers not to treat this as settled. This is an accuracy fix to how it is unsettled, not a downgrade. No page is being promoted or demoted, and no site capability changes.

Changelog — maintainer's call

No changelog entry included. Per CLAUDE.md this sits in the borderline band: it is a real correction to what the spec says about a topic's standing, but it is one paragraph on an optional page, not a substantive rewrite. Log it as a changed entry, or leave it out? Happy to add one before this leaves draft.

npm run build passes; Prettier and the SKILL.md digest check pass via the pre-commit hook.

🤖 Generated with Claude Code

…tent Signals

draft-ietf-aipref-attach, the document that would bind AI usage
preferences to content over HTTP, expired in April 2026 and has not been
replaced. draft-ietf-aipref-vocab is still alive. The page implied both
halves were converging; split them and name which one a site can act on.

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

cloudflare-workers-and-pages Bot commented Jul 28, 2026

Copy link
Copy Markdown

Deploying specification-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: c81c5c6
Status: ✅  Deploy successful!
Preview URL: https://3799a163.specification-website.pages.dev
Branch Preview URL: https://fix-aipref-attach-draft-expi.specification-website.pages.dev

View logs

The -04 revision expired 1 May 2026, not April. Add the stronger signal:
the attach text has had no edits in the WG's own drafts repository since
September 2025, while vocab was being edited for publication in April.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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