- From: Laurent Le Meur <laurent.lemeur@edrlab.org>
- Date: Wed, 11 Mar 2026 14:54:15 +0000
- To: nervy.bright_5x@icloud.com
- Cc: public-tdmrep@w3.org
- Message-Id: <F9A7C070-5AB9-40AE-8AE6-048D9B7F0985@edrlab.org>
Hi, We discussed this with the GitHub team, but it didn't result in a specific way to integrate the opt-out signal as a file in a GitHub repository. An issue is that AI actors are not adhering to new way of expressing TDM opt-out. Best regards, Cordialement, Laurent Le Meur Directeur EDRLab laurent.lemeur@edrlab.org <mailto:laurent.lemeur@edrlab.org> +33 (0)1 83 64 41 34  www.edrlab.org <http://www.edrlab.org/> European Digital Reading Lab 15 rue de la Bûcherie 75005 Paris – France > Le 8 mars 2026 à 09:37, nervy.bright_5x@icloud.com a écrit : > > Dear TDM Rep, > > Thanks for your work on the TDM Reservation Protocol. > > I’m looking for a reliable way to opt out of TDM on my personal GitHub repositories and in my search for a solution I came across the Text and Data Mining Reservation Protocol Community Group. In the TDM Reservation Protocol spec, I see there are methods defined for declaring reservations of TDM rights on an origin server, in HTTP responses, HTML content and more. But I didn’t find any methods that apply to code repositories. Does TDM Rep have any recommendations for how I can reserve my rights on my GitHub repos? Would adding a TDM file at the root of the repo be sufficient? It would be very helpful if this scenario could be added to the spec. > > Kind regards, > > Samuel > > >
Attachments
- text/html attachment: stored
- image/png attachment: 49365AD6-5506-42C4-B130-D6F228638BE3_34_.png
Received on Wednesday, 11 March 2026 16:36:28 UTC