{
 "acronym": "TDMRep",
 "adoption": {
  "by": null,
  "level": "unmeasured",
  "probe_run": null
 },
 "aliases": [],
 "analog": "Rights-reservation metadata (like a Creative Commons license badge)",
 "collisions": [],
 "discovery": {
  "mechanism": "well-known file, HTTP response header, or embedded metadata in HTML/EPUB/PDF",
  "path": "/.well-known/tdmrep.json"
 },
 "dispute": null,
 "evidence": [
  {
   "claim": "The CG-FINAL report published 2024-05-10 defines the tdm-reservation and tdm-policy declarations, the /.well-known/tdmrep.json file, HTTP header, and embedded-metadata attachment surfaces, and states plainly it is a Community Group report, not a W3C Standard.",
   "date": "2024-05-10",
   "label": "VERIFIED",
   "url": "https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/"
  },
  {
   "claim": "The TDM Reservation Protocol Community Group's own charter page confirms the group's goal (a simple, practical machine-readable TDM rights-reservation solution) and links the same CG-FINAL report as its output, independently corroborating the spec's existence and governance body from a second W3C-hosted page distinct from the report itself.",
   "date": null,
   "label": "VERIFIED",
   "url": "https://www.w3.org/community/tdmrep/"
  }
 ],
 "form": "well-known-file",
 "governance": "W3C Text and Data Mining Reservation Protocol Community Group",
 "group": null,
 "history": [
  {
   "date": "2026-09-05",
   "note": "seeded from Exa Agent research run"
  },
  {
   "date": "2026-09-06",
   "note": "verified against w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/"
  }
 ],
 "id": "tdmrep",
 "implementation": "unknown",
 "last_verified": "2026-09-06",
 "name": "Text and Data Mining Reservation Protocol",
 "native_status": "W3C Community Group Final Report; explicitly \"not a W3C Standard nor is it on the W3C Standards Track\"",
 "origin": {
  "date": "2022",
  "org": "W3C Text and Data Mining Reservation Protocol Community Group"
 },
 "part_of": null,
 "parties": [
  "agent-site"
 ],
 "phase": "stable",
 "probe": {
  "method": "GET",
  "on_absent": "No TDM reservation file at the well-known path; check per-resource HTTP headers and embedded metadata before concluding no reservation exists, per the spec's own processing-priority rules",
  "parse": "Presence of a tdm-reservation or tdm-policy field in the returned JSON, or equivalently in the TDM-Reservation/TDM-Policy HTTP headers on the resource",
  "path": "{origin}/.well-known/tdmrep.json"
 },
 "question": "Has a rights holder reserved text-and-data-mining rights over this content, and what policy governs any permitted mining?",
 "scope": "general",
 "spec_url": "https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/",
 "step": "permit",
 "summary_md": "TDMRep (Text and Data Mining Reservation Protocol) is a W3C Community Group Final Report, published 2024-05-10, defining a protocol for rights holders to reserve text-and-data-mining rights over otherwise lawfully accessible web content, and to make any TDM licensing policy discoverable [1]. It was created as a technical response to Article 4 of the EU Copyright in the Digital Single Market Directive, which lets rights holders opt out of the TDM exception by an 'appropriate' machine-readable means [1].\n\nThe spec defines a `tdm-reservation` declaration (1 = reserved, 0 = not reserved) and an optional `tdm-policy` pointing to a JSON-LD policy document, attachable four ways: a `/.well-known/tdmrep.json` file at the origin, an HTTP `TDM-Reservation`/`TDM-Policy` response header, or embedded metadata inside HTML, EPUB 2/3, or PDF files, with a defined processing-priority order across these surfaces when more than one is present [1]. The policy document format can express permission scope (research vs. non-research mining), a duty to contact the rights holder, and a duty to compensate financially.\n\nIt does not define an enforcement or authorization mechanism — like robots.txt, a reservation is a signal a crawler may honour or ignore — and it does not define payment rails for the compensation duty it lets a policy express. It is not on the W3C Standards Track; the report itself says so explicitly, and under the W3C Community Final Specification Agreement, different (weaker) patent and process commitments apply than for a Recommendation [1].\n\nAs of this verification (2026-09-06), the CG-FINAL-tdmrep-20240510 report confirms the prior finding of a 2024-05-10 final date, and no successor draft was found during this pass — the Community Group appears to have concluded its work with this final report. Governance now sits with the W3C TDMRep Community Group (public-tdmrep@w3.org mailing list, GitHub issues preferred for discussion) rather than an active working group.\n\nWhat is unresolved: this verification did not independently confirm which publishers or crawlers implement `/.well-known/tdmrep.json` in production; adoption is unmeasured rather than known-zero, and a dedicated probe run against a domain sample would be needed to move this to 'measured'. It is also unresolved how TDMRep's EU-directive-specific framing interacts with the more general-purpose, non-EU-specific AIPREF and Content Signals conventions that address overlapping ground.",
 "track": "w3c",
 "version": {
  "date": "2024-05-10",
  "label": "CG-FINAL-tdmrep-20240510"
 },
 "url": "https://agenticweb.wiki/protocols/tdmrep/",
 "category": "permit",
 "type": "protocol"
}