Whilst previous W3C licenses are in the SPDX repository, the 2023-01-01 license version was not yet, there's an open pull request for that here:spdx/license-list-XML#2269

As all the W3C groups tend to use GitHub for specification work, being able to select from the "Add a license" dropdown the latest W3C license is quite useful. A code-search for W3C in license files showed49k code matches and 4k repositories.

The linkhttps://spdx.org/spdx-license-list/request-new-license appears to be broken, so I sent a PR to the spdx repository, hopefully that's the correct process.

The previous version of this license is on the OSI's license list, the current version is not (I suspect just because it's not been updated?)https://opensource.org/license/w3c/ — I have tried to reach out to appropriate people at the W3C to follow the OSI's fairly lengthy process for updating their license.

ThisIsMissEmand others added2 commits

December 6, 2023 21:27

Add W3C software and document license (2023-01-01)

ab1bfb5

Merge branch 'gh-pages' into add-w3c-license

24809a8

Copy link

Contributor

mlinksva commentedDec 28, 2023

I would not mind adding this eventually (though that doesn't mean it would automatically appear in the drop-down, which I think is fine, this really has a niche use case and people familiar with that can copy and paste). In addition to the SPDX and OSI processes (thanks for starting) the "used by" examples probably will need replacing. Not clear to me there's a license in the AS2 repo, and the others use a link which can't currently be detected, needs the full text.

avoid yaml nesting?

5d8c488

Copy link

Author

ThisIsMissEm commentedDec 28, 2023

I would not mind adding this eventually (though that doesn't mean it would automatically appear in the drop-down, which I think is fine, this really has a niche use case and people familiar with that can copy and paste). In addition to the SPDX and OSI processes (thanks for starting) the "used by" examples probably will need replacing. Not clear to me there's a license in the AS2 repo, and the others use a link which can't currently be detected, needs the full text.

The link format seems to be the most common way, rather than embedding the full text of the license.

To clarify, I'm just an independent, but it did come up at an SWICG meeting that having it searchable in the license list would make it easier for CGs and WGs to start repos.

Haven't been able to follow up on SPDX yet. Apparently I missed something in their process.