- From: Giulia Marangoni <giulia.marangoni@aie.it>
- Date: Wed, 24 Aug 2022 14:50:04 +0000
- To: Leonard Rosenthol <lrosenth@adobe.com>, "Watson, Steve (ELS-AMS)" <S.Watson@elsevier.com>, "Campbell, Duncan" <dcampbell@wiley.com>, TDM Reservation Protocol Community Group <team-community-process@w3.org>, "public-tdmrep@w3.org" <public-tdmrep@w3.org>, Laurent Le Meur <laurent.lemeur@edrlab.org>
- Message-ID: <AM9PR07MB77629BECA3398F613A4FDDB0EB739@AM9PR07MB7762.eurprd07.prod.outlook.com>
Dear All, I’m interested to continue the discussion within this group, to collect ideas and see what pieces of the solution are already there/ what we need. This as a first step; then, as Laurent said, I agree that before formally starting a new development phase we should try to get feedback on the first one. So please keep me into the loop together with my colleague Paola Mazzucchi (paola.mazzucchi@aie.it, who is already member of the TDM group). As I'm currently on maternity leave until end September, Paola is the main contact point on this topic. Some thoughts on the embedding protocol. I think that our past work on content-based identification (we run a pilot project, Ardito, combining content based identification +Doi resolution) could be a useful experience to keep into account. We also think that is important that the link to tdm declaration is persistent, if it is embedded in the content. Paola will be able to tell more. Best Giulia Scarica Outlook per iOS<https://aka.ms/o0ukef> ________________________________ Da: Leonard Rosenthol <lrosenth@adobe.com> Inviato: mercoledì, agosto 24, 2022 3:57 PM A: Watson, Steve (ELS-AMS) <S.Watson@elsevier.com>; Campbell, Duncan <dcampbell@wiley.com>; TDM Reservation Protocol Community Group <team-community-process@w3.org>; public-tdmrep@w3.org <public-tdmrep@w3.org> Oggetto: Re: The final report has been released [via TDM Reservation Protocol Community Group] I am certainly happy to participate in such discussions, but I don’t have the bandwidth to lead/chair at this time. Leonard From: Watson, Steve (ELS-AMS) <S.Watson@elsevier.com> Date: Wednesday, August 24, 2022 at 5:36 AM To: Campbell, Duncan <dcampbell@wiley.com>, Leonard Rosenthol <lrosenth@adobe.com>, TDM Reservation Protocol Community Group <team-community-process@w3.org>, public-tdmrep@w3.org <public-tdmrep@w3.org> Subject: Re: The final report has been released [via TDM Reservation Protocol Community Group] EXTERNAL: Use caution when clicking on links or opening attachments. Bringing this up again. Are any of the other chairs interested in discussing an embedded protocol? Steve ________________________________ From: Watson, Steve (ELS-AMS) <S.Watson@elsevier.com> Sent: 04 August 2022 11:55 AM To: Campbell, Duncan <dcampbell@wiley.com>; Leonard Rosenthol <lrosenth@adobe.com>; TDM Reservation Protocol Community Group <team-community-process@w3.org>; public-tdmrep@w3.org <public-tdmrep@w3.org> Subject: Re: The final report has been released [via TDM Reservation Protocol Community Group] *** External email: use caution *** I am not aware of any further discussion on this. I am in favour of an embedded protocol to express rights when content sharing and syndication are common practise, e.g. in the STM industry. Steve ________________________________ From: Campbell, Duncan <dcampbell@wiley.com> Sent: 04 August 2022 10:59 AM To: Leonard Rosenthol <lrosenth@adobe.com>; Watson, Steve (ELS-AMS) <S.Watson@elsevier.com>; TDM Reservation Protocol Community Group <team-community-process@w3.org>; public-tdmrep@w3.org <public-tdmrep@w3.org> Subject: RE: The final report has been released [via TDM Reservation Protocol Community Group] You don't often get email from dcampbell@wiley.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> *** External email: use caution *** Hi – just following up on this. Has there been any further discussion of an embedded reservation protocol? Duncan From: Leonard Rosenthol <lrosenth@adobe.com> Sent: 24 March 2022 16:10 To: Watson, Steve (ELS-AMS) <S.Watson@elsevier.com>; TDM Reservation Protocol Community Group <team-community-process@w3.org>; public-tdmrep@w3.org Subject: Re: The final report has been released [via TDM Reservation Protocol Community Group] ⛔ This is an external email. Steve – I can’t speak to the legal aspect, but I can say that the situation you raise is EXACTLY why I proposed when we started this group that we should focus on embedded (in assets) TDM rights. The group felt otherwise, and so we have the protocol for those scenarios but (as you note) more is needed. I don’t know if the current chairs wish to continue to work or not, but I would certainly be willing/interested to continue. Leonard From: Watson, Steve (ELS-AMS) <S.Watson@elsevier.com<mailto:S.Watson@elsevier.com>> Date: Thursday, March 24, 2022 at 12:02 PM To: Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>>, TDM Reservation Protocol Community Group <team-community-process@w3.org<mailto:team-community-process@w3.org>>, public-tdmrep@w3.org<mailto:public-tdmrep@w3.org> <public-tdmrep@w3.org<mailto:public-tdmrep@w3.org>> Subject: Re: The final report has been released [via TDM Reservation Protocol Community Group] Hi All, It has been some time since my involvement in this group and I do not know if the group distribution still works. I have a question about content that has been reposted to a platform that is not owned by the rights holder. For example, this situation: * Reader downloads content in PDF format from rightsholder website. TDM rights are reserved and expressed using this protocol. * The content is reposted on a non-commercial content sharing platform. This is permitted by the rightsholder. * A text miner downloads the content from this platform, which does not own the rights to the article and does not reserve TDM rights. Since rights were not reserved, is the text miner allowed to text mine and create a commercial, derivative product? Best regards, Steve ________________________________ From: Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>> Sent: Wednesday, February 16, 2022 7:19:49 PM To: TDM Reservation Protocol Community Group <team-community-process@w3.org<mailto:team-community-process@w3.org>>; public-tdmrep@w3.org<mailto:public-tdmrep@w3.org> <public-tdmrep@w3.org<mailto:public-tdmrep@w3.org>> Subject: Re: The final report has been released [via TDM Reservation Protocol Community Group] *** External email: use caution *** Since the report of the TDM CG is a non-normative document, are there any plans to move this report to a WG to make it a normative reference? I can’t see how we can reasonably ask anyone to implement a non-normative work. Leonard From: W3C Community Development Team <team-community-process@w3.org<mailto:team-community-process@w3.org>> Date: Wednesday, February 16, 2022 at 5:22 PM To: public-tdmrep@w3.org<mailto:public-tdmrep@w3.org> <public-tdmrep@w3.org<mailto:public-tdmrep@w3.org>> Subject: The final report has been released [via TDM Reservation Protocol Community Group] Good news, we have just published the final report of the TDM Representation Protocol. You'll find it at the URL https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2Ftdmrep%2F&data=04%7C01%7Clrosenth%40adobe.com%7Ce16144b97c874c0585fe08d9f16031ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637806217724183064%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=9WEcP5XEpQ0pjhm8U2vj0xCodWtbn60YKqEIwCLewss%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2F2022*2Ftdmrep*2F%26data%3D04*7C01*7Clrosenth*40adobe.com*7Cc71089cdca994be81a5608da0dafa684*7Cfa7b1b5a7b34438794aed2c178decee1*7C0*7C0*7C637837345472341459*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C2000%26sdata%3DUq3DmU*2FJLtbYfdhh*2BlbmTQs73WWupfirDHz7MEj1E0g*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!N11eV2iwtfs!pQaNCly-irjauq0JFRN57qWPPyUib1sCECuXfWmmWQxPo7ucvk5hHjcMbgsPswQMMxsSwF7JAl4ZxUV_%24&data=05%7C01%7Clrosenth%40adobe.com%7C5d81022c628949a2c48508da85b42681%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637969306046163638%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MsHNwGunosz73%2Fra7rErtSpQBzdJAj0tEyPYJ7a5A4I%3D&reserved=0>. It is referenced from the TDMRep Community home page. As multiple EU countries are moving towards the implementation of the DSM directive, publishers are looking for solutions. The Community Group will now focus on communication, its targets being the European Commission, TDM Actors and publishers. In order to communicate effectively, the Community Group will have to work on its governance and define some tools (maybe a presentation website, recorded demos, a brochure, a logo ...). We'll therefore organize multiple calls in 2022. If you are aware of events which could be good supports for presentations, please contact the CG chairs. We're currently thinking about the IPTC Spring Meeting 2022 (May) and the Digital Publishing Summit 2022 (June). ---------- This post sent on TDM Reservation Protocol Community Group 'The final report has been released' https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2Fcommunity%2Ftdmrep%2F2022%2F02%2F16%2Fthe-final-report-has-been-released%2F&data=04%7C01%7Clrosenth%40adobe.com%7Ce16144b97c874c0585fe08d9f16031ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637806217724183064%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4Tzpv0gsTb7qmHk%2FZZIs3CqRFG2gw8GYBmiue%2FPvKt0%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2Fcommunity*2Ftdmrep*2F2022*2F02*2F16*2Fthe-final-report-has-been-released*2F%26data%3D04*7C01*7Clrosenth*40adobe.com*7Cc71089cdca994be81a5608da0dafa684*7Cfa7b1b5a7b34438794aed2c178decee1*7C0*7C0*7C637837345472341459*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C2000%26sdata%3D*2FYrp7ic8NwOVfk*2FPRzMLs3I7lVnt5V2lJleu5sOmiR4*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!N11eV2iwtfs!pQaNCly-irjauq0JFRN57qWPPyUib1sCECuXfWmmWQxPo7ucvk5hHjcMbgsPswQMMxsSwF7JAsHPdGCY%24&data=05%7C01%7Clrosenth%40adobe.com%7C5d81022c628949a2c48508da85b42681%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637969306046163638%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fdjvKXJsSB9hxmaFnwHJ73KwP35Tyd4SpxekqwKNdE4%3D&reserved=0> Learn more about the TDM Reservation Protocol Community Group: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2Fcommunity%2Ftdmrep&data=04%7C01%7Clrosenth%40adobe.com%7Ce16144b97c874c0585fe08d9f16031ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637806217724183064%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6SPIYSMlu7gjfoGbZEcnxVvHLOBg9hEUwzvTLpXg0%2Bo%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2Fcommunity*2Ftdmrep%26data%3D04*7C01*7Clrosenth*40adobe.com*7Cc71089cdca994be81a5608da0dafa684*7Cfa7b1b5a7b34438794aed2c178decee1*7C0*7C0*7C637837345472341459*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C2000%26sdata%3D8kBgdBJodPrfO97FL8sdTQpMc6TouyzoanNlvXHJC8U*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUl!!N11eV2iwtfs!pQaNCly-irjauq0JFRN57qWPPyUib1sCECuXfWmmWQxPo7ucvk5hHjcMbgsPswQMMxsSwF7JArqCNp8m%24&data=05%7C01%7Clrosenth%40adobe.com%7C5d81022c628949a2c48508da85b42681%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637969306046319757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dCQBA6a492Lg%2BgF8jiK5f4vzTAhfyANbH9ym9ReutOE%3D&reserved=0> ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33158992, Registered in The Netherlands. John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ. ________________________________ The contents of this email and any attachments are confidential and intended only for the person or entity to whom it is addressed. If you are not the intended recipient, any use, review, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this message in error, please immediately notify the sender and permanently delete all copies of the email and any attachments. Click here for translations of this disclaimer.<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecure.wiley.com%2Femail-disclaimers&data=05%7C01%7Clrosenth%40adobe.com%7C5d81022c628949a2c48508da85b42681%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637969306046319757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xhYGRvm3PKefRbYEkx%2FWQ4XLAirrs%2FTHdKWT6TBE1fk%3D&reserved=0> ________________________________ ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33158992, Registered in The Netherlands. ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33158992, Registered in The Netherlands. ________________________________ Network Confidentiality Notice Il presente messaggio, e ogni eventuale documento a questo allegato, potrebbe contenere informazioni da considerarsi strettamente riservate ad esclusivo utilizzo del destinatario in indirizzo. Chiunque ricevesse questo messaggio per errore o comunque lo leggesse senza esserne legittimato è avvertito che trattenerlo, copiarlo, divulgarlo, distribuirlo a persone diverse dal destinatario è severamente proibito ed è pregato di darne notizia immediatamente al mittente oltre che cancellare il messaggio e i suoi eventuali allegati dal proprio sistema. Ai sensi del Regolamento UE 2016/679, il Titolare del trattamento garantisce la massima riservatezza ed il pieno rispetto degli obblighi previsti dalla normativa nazionale e comunitaria in merito alla protezione dei dati personali. This message, and any attached file transmitted with it, contains information that may be confidential or privileged for the sole use of the intended recipient. If you are not the intended recipient of this e-mail or read it without entitlement be advised that keeping, copying, disseminating or distributing this message to persons other than the intended recipient is strictly forbidden. You are to notify immediately to the sender and to delete this message and any file attached from your system. In accordance with EU Reg. 2016/679 (GDPR), the Data Controller guarantees the maximum level of confidentiality and full respect of all obligations provided for by the national and the EU legislation currently in force with regard to protection of personal data..
Received on Wednesday, 24 August 2022 14:50:24 UTC