Minutes of the 09/03/2021 call [via TDM Reservation Protocol Community Group]

Introduction



The number of participants of the Community Group has now reached 25 people. 



Validation of the charter 



The proposed charter of the CG is accessible on Github on https://github.com/w3c/tdm-reservation-protocol/blob/main/charter.md. It is similar to other W3C CG charters, taken as examples. 



The Charter is approved unanimously by the participants. Community members who didn’t attend the meeting are kindly invited to send comments, if any, before the next meeting. 



Review of the goals and requirements



During the discussion, it is made clear that the requirements are related to the technical specification, not the implementations of the specification; said differently, rightsholders will have a flexible use of the different features of the specification. For instance they will be able to express a licence only if available, and choose between expressing their licences via human readable information **or** machine-readable information.



To make it clearer, the Core requirements will be introduced via the phrase “The technical specification shall”. 



Note: It is nevertheless important to note that TDM Actors will have to implement every feature in their TDM Agents, therefore we’ll have to be very careful not to multiply options.



Because they cannot be verified against a technical solution, what was called “High level requirements” is now called “Goals”. 



Because “Primary” and “Secondary” Requirements was not clear, these are renamed “Core Requirement” (what the technical solution must fulfill) and “Additional Requirements” (which will complement Core Requirements in specific cases). The second slot is currently empty, the Group may decide  if items should be  added here during our work.   



The Goals and the Requirements are approved unanimously by the participants. Community members who didn’t attend the meeting are kindly invited to send comments, if any, before the next meeting. 



Review of the Vocabulary



One of the comments made on the Goals was that “publishers” was used but not defined. A simple definition was therefore added to the vocabulary. This definition would be more accurate for distributors of digital publications on the Web. Calling them “publishers” is non perfect but still usable in our context, where we refer to publishing as the act of making content available to a public.



The Vocabulary is approved unanimously by the participants. 



Workplan



How do we plan our work, avoid multiple threads of discussion and foster participation? 



The way to go, agreed during the call, is to proceed in sequence, focussing on one solution at a time, from the simplest to more elaborated solutions. Next steps will be: 



Study a solution based on http headers;
Study a solution based on a central file hosted on a Web server hosting Web resources;
Study a solution based on the embedding of metadata in Web resources. 




As inspiration can come from past and existing initiatives (https://github.com/w3c/tdm-reservation-protocol/blob/main/docs/initiatives.md), we will start by studying the robots.txt initiative and the co-chairs, with the help of the participants, will try to schedule presentations of other initiatives by their experts . For instance, RightsML (IPTC) and Assert your rights (Copyright Hub) could be the subject of such presentations.



How will participants be able propose technical solutions for discussion within the group?



Different solutions are discussed: Google Docs, Github Wiki and raw Github documents in markdown. The issue with Google Docs is that they are separate from the Github framework in which we are working. The issue with Github Wiki pages is that history of changes are difficult to see and Issues or Pull Requests cannot be synchronized with changes. 



The final choice is therefore to rely on pure Github documents, using Pull Requests. A How To written by Ivan Herman (https://iherman.github.io/misc-notes/docs/BasicGitHubContributionIntro) will be of great help for newcomers to Github. 



The co-chairs will initiate the work by providing a template document for use in the first step of our work, i.e. a solution based on http headers. 



----------

This post sent on TDM Reservation Protocol Community Group



'Minutes of the 09/03/2021 call'

https://www.w3.org/community/tdmrep/2021/03/11/minutes-of-the-09-03-2021-call/



Learn more about the TDM Reservation Protocol Community Group: 

https://www.w3.org/community/tdmrep

Received on Thursday, 11 March 2021 18:02:14 UTC