Published revision: draft-jurkovikj-collab-tunnel-03 · Expires: 28 January 2027
An Experimental HTTP profile for publisher-selected machine-facing representations that remain linked to their canonical resources.
Datatracker Read HTML WordPress source
Problem addressed
A publisher may want to expose a compact or transformed representation for machine consumers without replacing the canonical resource, weakening ordinary validator semantics, or forcing clients to guess undocumented paths.
Core mechanisms
- Canonical URLs and publisher-selected machine URLs.
- Bidirectional discovery using HTTP links and representation metadata.
- Deterministic JSON M-Sitemaps and M-Sitemap Indexes.
- Strong ETags scoped to the exact selected representation.
- Explicit handling of redirects, content coding, caching, and privacy.
Boundaries
TCT does not define authentication, authorization, licensing, mutation, or semantic equivalence. Optional Semantic Validators are a separate extension and do not replace ordinary ETag semantics.
Related implementations
This is an individual Internet-Draft, not an RFC or an IETF standard.