Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[open-regulatory-compliance] Solving copyright & licensing information in client-side JavaScript, CSS etc.

Dear all,

I’m a long-time lurker, but finally have something meaningful to share. I have been working on this for a long time already, but given that JS/CSS is distributed to the users, it seems like it might be relevant for CRA compliance too.

After several workshops and iterations, a bunch of us finally agreed to a solution to the problem that client-side _javascript_, CSS etc. gets distributed to the user without proper (or typically any) license and copyright information.

Upon tripple-checking with everyone involved, I finally wrote about it here (incl. a small PoC):

https://matija.suklje.name/solving-copyright-licensing-information-in-client-side-_javascript_-css-and-similar-agreeing-on-a-useful-solution 

TL;DR:

  1. apply REUSE.software best practices, just as you would with writing in any  other programming language
  2. use a tool of your choice to generate either:
    • an SBOM – SPDX, CycloneDX, or whatever you prefer, and/or
    • an attribution file, of whatever kind you prefer
    • whatever document/file/webpage you feel is the most appropriate way to fulfill your licensing obligations
  3. make sure that the file/page from 2. is linked in a <link> rel="license" href=""> HTML tag in the HTML <head> 
  4. create something in the web UI to present this link too, using a <a rel="license" href=""> in the HTML <body> 

Next steps:

1. include it in REUSE.software documentation/FAQ

2. spread the word and start implementing it – I’m counting on you here


cheers,

Matija

--

gsm:    tel:+386.41.849.552

www:    https://matija.suklje.name

xmpp:   hook@xxxxxxxxxxxxxxxxxxxxxxxxxxx

matrix: @hook:kompot.si 

Back to the top