-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New license request: latest W3C licenses #2429
Comments
I'm not sure on OSI status, I believe that requires someone from the W3C to submit the license. cc @dmitrizagidulin since you're far more involved with W3C matters than I am |
ScanCode Comment |
The only differences between this license text and https://spdx.org/licenses/W3C-20150513.html are:
As to 1 - capitalization does not matter for matching, see https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/#b5-capitalization As to 2 - this is also not a substantive difference in terms of the legal text and can be accommodated via markup I would suggest we add markup to agree? |
I'd say that's up to someone at the W3C to determine. @plehegar or @timbl come to mind as far as people who might have input here. All I know is if someone were to select the W3C license when creating a github repo at present, then they would be getting the "old" license, not the current one, that's why I've opened this, to try to smooth that path a bit. |
@ThisIsMissEm thanks for opening this issue btw! |
@ThisIsMissEm - let me explain a bit more: while Looking at this page: https://www.w3.org/copyright/software-license-2023/ , it'd be great if W3C could add along with the "status" statement at the top, to denote the SPDX id and then in the "Changes since the previous document" section, add that this change does not substantively change the license from the previous one dated 2015. SPDX can make a similar note in our license data. @dmitrizagidulin - do you have any input in this regard? |
fixes #2429 See comments in that issue for explanation. Signed-off-by: Jilayne Lovejoy
ok, I made a PR to illustrate what I mean as that might be easier to "see"! In doing so, I noticed that the 2015 variant should have had markup in the third clause to begin with since that was always intended to be templatized for the name and URI |
The thing that specifically did change between the two license versions is the copyright holder, I'd be surprised if that's not a substantial change? In the 2023 document it is:
In the 2015 document it is:
So something that is under 2015 would have a different copyright holder to the 2023 license. |
+1 to what @ThisIsMissEm said, that is the main (and fairly significant) change, as it's a wholly different entity. |
@dmitrizagidulin @ThisIsMissEm - please read https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/#b3-substantive-text - thought I had included the link above, but in any case, this is what we are talking about regarding "substantive" Copyright notice is generally not part of the license text itself. Breaking down the third clause: 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 --> The bit in brackets is presumably intended to have that info filled in, thus for purposes of matching license text to a corresponding SPDX Id, we mark this text as "replaceable" - see https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/#b34-guideline-replaceable-text Copyright © [$year-of-document] World Wide Web Consortium. https://www.w3.org/copyright/software-license-2023/ --> the year (in brackets) is also replaceable text, as described above. As for the name of the copyright holder, what if someone else used this license, then the copyright holder text would also need to be changed. This scenario is a bit different in the sense that the copyright notice is sort of embedded in the license, but it's still part of the required notice to refer to the original author in the case of modifications. Is the original author of this license always W3C (and the other copyright holders for the 2015 version)? |
Quick note about the OSI status. It's in progress. |
+1 to @jlovejoy's comments above. As mentioned, it looks to me that the changes between the license text at https://www.w3.org/copyright/software-license-2023/, as compared to So I think adding markup to |
How license meets inclusion principles
For the same reasons as previous inclusion of W3C licenses. This is just the latest version now that W3C is independent of MIT, with minor other changes.
License Name
W3C Software Notice and Document License (2023-01-01)
Suggested short identifier
W3C-20230101
License or Exception?
license
URL to license text
https://www.w3.org/copyright/software-license-2023/
OSI Status
I don't know
License author or steward
W3C
URL to project(s) that use license
All updated W3C standards and specifications use this license.
paste text of license here
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:
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.
The text was updated successfully, but these errors were encountered: