Fill in the license attribute in all files available in the database.

[antond-weta]

In order to make the header/license attribute mandatory, as discussed in the comments section of #6 and #4, I'd like to fill in the license in all existing files.

• I've put "Apache-2.0" in all of the files which, as I believe, originate from AMPAS, which are all camera files and the 190-patch training data. Was that the right thing to do? Do we need any other user agreement type of document from AMPAS to add to the database?
• The CIE1931 XYZ data in cmf/cmf_1931.json, do we know where it came from? I understand that the data is available from CIE under the Creative Commons license here . Should I put "CIE" in header/laboratory, "CC BY-SA 4.0" in header/license, and a link to the CIE website in header/comments?
• The ISO7589 illuminant in illuminant/iso7589_stutung_380_780_5.json - where is it from? I understand that the ISO standard itself is not available for free. What should I put in the license field?

[antond-weta]

@aforsythe, @scottdyer could you please comment on this

[lgritz]

Typically, we make changes to the license language in files be an isolated, separate PR submitted by somebody representing the organization controlling the prior license.

[lgritz]

But probably, it's sufficient for somebody else to submit the PR as long as the PR is approved by Alex with an explicit comment that the changes are authorized by AMPAS?

I can't speak to the XYZ or illuminant data. If the json files themselves came from other organizations, they should bear the right license from the original source. But if one of you or AMPAS created the json files by transcribing some published data tables, we should use APACHE-2.0 for the json and just have some acknowledgement/citation of the original published source. A table of measured physical data is just a list of facts, not protected expression, as far as I understand.

[antond-weta]

I've created a PR #15 adding the "CC-BY-4.0" license to the CIE1931 observer file.