{
 "url": "https://agenticweb.wiki/compare/rsl-vs-tdmrep/",
 "title": "RSL vs TDMRep: differences & adoption",
 "description": "Really Simple Licensing vs Text and Data Mining Reservation Protocol: The map lists them as complementary: sites and agents commonly implement both.…",
 "markdown_url": "https://agenticweb.wiki/compare/rsl-vs-tdmrep/index.md",
 "markdown": "# Really Simple Licensing (RSL) vs Text and Data Mining Reservation Protocol (TDMRep)\n\nThe map lists them as complementary: sites and agents commonly implement both.\n\n[3 Permit](/category/permit/) [Really Simple Licensing](/protocols/rsl/) · [3 Permit](/category/permit/) [Text and Data Mining Reservation Protocol](/protocols/tdmrep/)\n\n|  | [Really Simple Licensing](/protocols/rsl/) RSL | [Text and Data Mining Reservation Protocol](/protocols/tdmrep/) TDMRep |\n| --- | --- | --- |\n| Lifecycle step | 3 Permit: What may the agent do here? | 3 Permit: What may the agent do here? |\n| Answers | What machine-readable license, price, and authorization terms govern how AI systems and crawlers may access or reuse a publisher's content? | Has a rights holder reserved text-and-data-mining rights over this content, and what policy governs any permitted mining? |\n| Governed by | RSL Collective, a vendor consortium; issue tracker at github.com/rslstandard/rsl | W3C Text and Data Mining Reservation Protocol Community Group |\n| Status (issuer's words) | Recommendation (RSL's own maturity label, not a W3C/IETF Recommendation) — Document RSL-SPEC-1.0, Category 'Industry Specification' | W3C Community Group Final Report; explicitly \"not a W3C Standard nor is it on the W3C Standards Track\" |\n| Version | RSL 1.0 (2025-12-10) | CG-FINAL-tdmrep-20240510 (2024-05-10) |\n| Form / transport | document format | well-known file |\n| Found at | /rsl.xml | /.well-known/tdmrep.json |\n| Implementation | shipping | shipping |\n| Evidence | 2 verified | 2 verified |\n| Primary use case | Control AI crawling and training use | Control AI crawling and training use |\n| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |\n| Specification | [https://rslstandard.org/rsl](https://rslstandard.org/rsl) | [https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/](https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/) |\n\n## When to use which\n\n- Choose Really Simple Licensing when your question is “What machine-readable license, price, and authorization terms govern how AI systems and crawlers may access or reuse a publisher's content?” and you accept its maturity: status \"Recommendation (RSL's own maturity label, not a W3C/IETF Recommendation) — Document RSL-SPEC-1.0, Category 'Industry Specification'\", implementation shipping.\n- Choose Text and Data Mining Reservation Protocol when your question is “Has a rights holder reserved text-and-data-mining rights over this content, and what policy governs any permitted mining?” and you accept its maturity: status \"W3C Community Group Final Report; explicitly \"not a W3C Standard nor is it on the W3C Standards Track\"\", implementation shipping.\n\nGuidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.\n\n## Read the full articles\n\n- [Really Simple Licensing](/protocols/rsl/): What machine-readable license, price, and authorization terms govern how AI systems and crawlers may access or reuse a publisher's content?\n- [Text and Data Mining Reservation Protocol](/protocols/tdmrep/): Has a rights holder reserved text-and-data-mining rights over this content, and what policy governs any permitted mining?\n\nAsk the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).\n\n[rsl.json](/data/protocols/rsl.json) · [tdmrep.json](/data/protocols/tdmrep.json) · [Markdown](/compare/rsl-vs-tdmrep/index.md)\n"
}