Re: License for DPV

Hi Rigo. Thanks for the clarification.

My confusion is related to this statement within the CLA: "Any source 
code created by the Project is not subject to this CLA, but rather 
subject to separate licensing terms for that source code." And that the 
CLA seems more relevant to people contributing to DPV, whereas I'm 
looking for information to tell potential adopters of DPV i.e. under 
what LICENSE they can use the DPV.

To follow good practice and put an explicit LICENSE file in the DPV repo 
to indicate terms under which the adopter can use DPV. From your advice, 
my understanding is (please correct me if I'm wrong here): I put the CLA 
text in the LICENSE file.

P.S. If this is correct, I'll change the LICENSE file text to CLA text 


On 01/03/2022 15:52, Rigo Wenning wrote:
> Harsh,
> this fell between the cracks.
> On 05/01/2022 17:00, Harshvardhan J. Pandit wrote:
>> Hello. I received a query as to what license is applicable when using 
>> DPV.
> For the DPV, the license is in the CLA that has different licenses 
> depending on the status. For Drafts, the CLA applies which is mainly a 
> license to use the contribution. The CLA is rather copyright centric and 
> allows someone to contribute without giving a full patent license to the 
> entire technology in the Spec. This is less relevant for a vocabulary.
>> Since we haven't indicated one anywhere, my assumption was that the 
>> W3C license applies: 
>> (tldr; use as you want with attribution)
> No, it does not. For CGs the CLA applies which allows for derivative 
> works. The question only becomes relevant, once the Group wants to 
> create a recommendation.
>> Please let me know your comments/suggestions. Based on the decision, 
>> there will be a LICENSE file added to the GitHub repo and text 
>> mentioned in specs and other documents.
> No need for that as the CLA applies.
>> Note that contributions to DPV are made as under W3C CLA 
>> This question is about 
>> using DPV.
> The CLA gives a license to use the document for any purpose (including 
> making a competing standard)
> Hope that helps
>   --Rigo

Harshvardhan J. Pandit, Ph.D
Research Fellow
ADAPT Centre, Trinity College Dublin

Received on Tuesday, 1 March 2022 19:31:25 UTC