|
From: | Julius Schwartzenberg |
Subject: | Re: Allow specifying the license with an HTTP header |
Date: | Fri, 2 Oct 2020 23:06:55 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Icedove/68.9.0 |
On 02-10-2020 21:54, Stephen Paul Weber wrote:
An idea I came up with would be to standardize a new HTTP header, something along the lines of "content-license". It would seem appropriate to have such a header any time along a "content-type" header.The problem I see with this is that most JavaScript files served over HTTP thesedays are composed on many different sources with different copyrights and licenses and original source locations. So it's not just one header with alicense and you're done. It really needs to be inline in the file to separatedifferent-ly licensed parts from each other clearly.
Would the combined work not have a single license effectively?Otherwise there could be something such as "content-license: mixed" or different freedoms could be expressed in separate independent headers. Only when all required freedoms are permitted, LibreJS would proceed with execution.
[Prev in Thread] | Current Thread | [Next in Thread] |