Add a license

[martinthomson]

Source from https://www.w3.org/Consortium/Legal/2023/copyright-software-short-notice.html As linked from https://www.w3.org/copyright/software-license-2023/

Closes #346.

[apasel422]

Can we also set https://docs.npmjs.com/cli/v11/configuring-npm/package-json#license in impl/package.json for completeness?

[martinthomson]

Given that this is "private": true, I don't see there being much point.

[apasel422]

Given that this is "private": true, I don't see there being much point.

IIUC, private just means that the package won't be published, but it seems orthogonal to the license, since someone can download the repository without using the package through NPM.

I'm mainly interested in this for the case in which a tool automatically imports the end-to-end tests for use with a non-simulator implementation.

It also doesn't seem out of the question that we could publish this package at some point.

[martinthomson]

In the case where someone downloads the repository or pulls specific resources from it, wouldn't they be pulling from here, where there is a license? The reason I mentioned the "private" attribute in package.json is that this precludes distribution of the impl/ directory via NPM, which is the only way in which a license might be needed there.

If the package ever is published, that's a different story. We'd need to populate a bunch of fields in addition to the license.