RE: TDMRep CG call tomorrow, warning about time, new doc to study

regrets

Tzviya Siegman
Information Standards Principal
Wiley
201-748-6884
tsiegman@wiley.com<mailto:tsiegman@wiley.com>

From: Laurent Le Meur <laurent.lemeur@edrlab.org>
Sent: Monday, March 22, 2021 8:24 AM
To: public-tdmrep@w3.org
Subject: TDMRep CG call tomorrow, warning about time, new doc to study

⛔
This is an external email.
Greetings,

This is a reminder that we'll have a call tomorrow Tuesday, at 11 am EST = 15 pm UTC = 16:00 CET (time in your country<https://urldefense.com/v3/__https:/www.timeanddate.com/worldclock/fixedtime.html?msg=TDMRep&iso=20210323T15&p1=1440&ah=1__;!!N11eV2iwtfs!8WU4rcZ_C06oCoJjTQL8W1meLu_VZ5TD6GNClmLSWFZoH6i-90A_P3BOqKDsog$>), using the usual Zoom info (you can request it from the co-chairs).
It is better IMO  to keep the US EST time during this interim period because noon is not a perfect time for calls, even in the US :-), and because Europe will move to summer time in a week.

So, European colleagues, be careful : it is one hour earlier than usual!!

We've prepared a new document for discussion: Proposal based on http headers<https://urldefense.com/v3/__https:/github.com/w3c/tdm-reservation-protocol/blob/main/proposals/proposal-http-headers.md__;!!N11eV2iwtfs!8WU4rcZ_C06oCoJjTQL8W1meLu_VZ5TD6GNClmLSWFZoH6i-90A_P3D_Mf7DMA$>  details a plausible option for our technical solution.
We'll focus on this document during the call, therefore please prepare your questions.
If you are expert in the handling of http headers on Web servers or reverse proxies, your experience will be welcome.
Issues not solved during the call will require Github issues, to be discussed during the next 15 days.

After this call, we'll prepare 2 other documents : a proposal based on a file stored on the origin server (à la robots.txt) and a proposal based on metadata embedded in html content (à la meta robots or using json-ld metadata). Other proposals may also be drafted depending the options participants want to study.

Questions we'll also have to answer as a group are:
- should we define an hybrid solution in which TDM Agents have to look at different places where TDM information could be (e.g. content then headers then file at origin)? In such a case what should be the order of priority of the different options (which could contradict each other)?
- can we make our simple solution compatible with vertical solutions like the Article Sharing Framework of the STM Association or the Assert your rights of the EPC / Copyright Hub ? (check https://github.com/w3c/tdm-reservation-protocol/blob/main/docs/initiatives.md<https://urldefense.com/v3/__https:/github.com/w3c/tdm-reservation-protocol/blob/main/docs/initiatives.md__;!!N11eV2iwtfs!8WU4rcZ_C06oCoJjTQL8W1meLu_VZ5TD6GNClmLSWFZoH6i-90A_P3Dsw0ELYg$> for details).

Also, if are an ODRL expert, we'll need your expertise to draft a proposal of license based on ODRL2.

Best regards
Laurent  Le Meur
EDRLab