spdx / license-list-XML

This is the repository for the master files that comprise the SPDX License List
Other
355 stars 288 forks source link

New license request: W3C Software and Document license - 2023 version #2600

Closed bact closed 2 weeks ago

bact commented 2 weeks ago

How license meets inclusion principles

License Name

W3C Software and Document license - 2023 version

Suggested short identifier

W3C-2023

(the existing W3C may need to be deprecated and replaced by a dated identifier, perhaps W3C-2022)

License or Exception?

license

URL to license text

https://www.w3.org/copyright/software-license-2023/

OSI Status

I don't know -- but its previous version is OSI-approved.

Please see @coolharsh55 comments below https://github.com/spdx/license-list-XML/issues/2600#issuecomment-2453010346

License author or steward

World Wide Web Consortium

URL to project(s) that use license

paste text of license here

Software and Document license - 2023 version

Status: This document is in effect since 1 January 2023.

This work is being provided by the copyright holders under the following license.

License

By obtaining and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.

Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the work or portions thereof, including modifications:

The full text of this NOTICE in a location viewable to users of the redistributed or derivative work. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C software and document short notice should be included. Notice of any changes or modifications, through a copyright statement on the new code or document such as "This software or document includes material copied from or derived from [title and URI of the W3C document]. Copyright © [$year-of-document] World Wide Web Consortium. https://www.w3.org/copyright/software-license-2023/"

Disclaimers

THIS WORK IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENT WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENT.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the work without specific, written prior permission. Title to copyright in this work will at all times remain with copyright holders.

Versions

This version: https://www.w3.org/copyright/software-license-2023/ Latest version: https://www.w3.org/copyright/software-license/ Previous version: https://www.w3.org/copyright/software-license-2015/

Changes since the previous document

The 2023 version updates identification of the copyright holder.

coolharsh55 commented 2 weeks ago

Thanks Art. The W3C page https://www.w3.org/Status.html identifies its license as OSI approved - though the OSI archive only refers to 2015 version. The 2023 license has a change log that only adds identification of copyright holder and no other material changes. So I think the latest license also is OSI conformant though not explicitly in its list.

swinslow commented 2 weeks ago

Hi @bact,

As described in the notes for W3C-20150513, the 2023 changes made by W3C to the license were only changes to the copyright notice in the middle of the license (under the third bullet point). Changes to copyright notices are ignored pursuant to the SPDX Matching Guidelines.

Given that, the 2023 changes made by W3C are still a match to W3C-20150513, so a new license ID / entry on the License List is not required. Please see also the discussion at #2429 earlier this year and the corresponding PR at #2447 which clarified this.

bact commented 2 weeks ago

Thank you @swinslow for clarifications and pointers. I will close this.