G'day Matija, One (minor) comment: in the section entitled "Is <https://matija.suklje.name/persistent-copyright-licensing-information-in-client-side-javascript-css-and-similar-a-proposal-call-for-help#is-this-really-enough> this really enough? <https://matija.suklje.name/persistent-copyright-licensing-information-in-client-side-javascript-css-and-similar-a-proposal-call-for-help#is-this-really-enough>", the 4th paragraph starts with this text:
The bigger question is whether communicating the license solely through its > SPDX ID is enough, since you would technically not be including the whole > license text(s). A minor but important detail that I think is worth calling out somewhere in/near this section is that despite its name, the SPDX-License-Identifier tag's value is an SPDX License Expression <https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/>, *not* an SPDX License Identifier (though of course all SPDX license identifiers also happen to be valid SPDX license expressions). This can be a source of confusion for newcomers to SPDX (especially anyone looking to consume such data), and I think it's important to always encourage folx to think from the get-go in terms of expressions and not identifiers (even though single identifiers happen to be the typical case). Cheers, Peter On Fri, Oct 11, 2024 at 10:25 AM Matija Šuklje via lists.spdx.org <matija= [email protected]> wrote: > Dear all, > > I’ve been working on a way to keep license/copyright info in-situ in web > front-end code even after minification. > > In short, I propose: > - using REUSE/SPDX Snippet Tags > - in comment blocks that use the `/*! comment */` format (note the > exclamation > mark!) > > My proposal relies on already existing specifications, just the > combination is > novel. It is also intended to work with already existing tools. > > If it works out, I would propose to add relevant verbiage to the REUSE > spec. > (It seems a not generic enough for SPDX, but if it SPDX would like to > adopt > it, I’d love that!) > > < > https://matija.suklje.name/persistent-copyright-licensing-information-in-client-side-javascript-css-and-similar-a-proposal-call-for-help > > > > I’m fairly confident in the theory. > > When it comes to praxis, I have some PoC and the while the results are not > optimal – in no small part due to my lack of skill –, they are optimistic. > > I did learn a lot about building JS project, but at this point people > smarter > than me are required. > > So, please, read it, try it, let’s discuss and make this a reality! :D > > > > cheers, > Matija > -- > gsm: tel:+386.41.849.552 > www: https://matija.suklje.name > xmpp: [email protected] > matrix: @silverhook:matrix.org > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1923): https://lists.spdx.org/g/spdx/message/1923 Mute This Topic: https://lists.spdx.org/mt/108953343/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/spdx/leave/2655439/21656/1698928721/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
