Copyright license is unclear

[jfinkels]

The README states

The source material in this repository licensed under the AFL or BSD license.

However, no copy of the exact copyright license is included in this repository. Can you please include a copy of the text of the exact license? This may be important if someone wishes to, for example, include a copy of the schema.json meta-schema as part of a software package.

[awwright]

This is probably workable, but most IETF work doesn't seem to include a license in the repository itself, you normally get a license from one of several external locations; the primary one being RFC 5378 (which applies since the work is intended for IETF submission as an Internet-Draft).

Is there something in particular you're looking to copy?

[handrews]

Looking at two active RFC authors ( https://github.com/mnot/I-D and https://github.com/dret/I-D ) shows that it's common practice to only have the license in the draft text.

I was going to argue that "AFL or BSD" is a SPDX license expression and therefore has a precise meaning already, but actually neither of those is a license abbreviation:

https://spdx.org/licenses/

We should probably at least give a precise identification.

[RemyRylan]

@handrews Has there been anymore decision making? I've put together a thoroughly typed TypeScript definition for JSONSchema, and I'd like to include documentation for each property directly from the spec.

Can I do this? What license should I release it under (and which exact version)? Of AFL or BSD, I'd highly prefer to release under BSD (it's more similar to MIT, which all of my existing packages are licensed as).

[handrews]

@jayrylan the spec itself is under whatever licensing the IETF uses (it's documented somewhere, but I don't remember where). I'm pretty sure you can quote anything you want as long as you a. identify which draft it is and b. make it clear that you are citing a work-in-progress since this is still in the draft stage.

The question here is about the licensing for... um... actually I have no idea. It's probably left over from when the web site used to be in the same repository as the spec? Quote it like you'd quote any IETF draft and you'll be fine :-)

[awwright]

Traditionally RFCs are shared on the sneakernet, so I know there's no problem with redistribution. Anyways, if I didn't mention already, all of my work is public domain, for what that's worth.

…

On Fri, Oct 26, 2018, 19:02 Henry Andrews ***@***.***> wrote: @jayrylan <https://github.com/jayrylan> the spec itself is under whatever licensing the IETF uses (it's documented somewhere, but I don't remember where). I'm pretty sure you can quote anything you want as long as you a. identify which draft it is and b. make it clear that you are citing a work-in-progress since this is still in the draft stage. The question here is about the licensing for... um... actually I have no idea. It's probably left over from when the web site used to be in the same repository as the spec? Quote it like you'd quote any IETF draft and you'll be fine :-) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#532 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAatDZmnYjw_3D6ASEH2hRpJCEprVItaks5uo76dgaJpZM4RceOS> .

[RemyRylan]

Thank you very much, @handrews @awwright. Judging from https://trustee.ietf.org/license-info/IETF-TLP-3.htm, I should release under BSD-2-Clause, since that page points to https://opensource.org/licenses/bsd-license.php.

I'm going to attach the following copyright statement along with the following BSD 2 Clause license:

Copyright (c) 2018 IETF Trust, Austin Wright, Henry Andrews, Geraint Luff,
and Cloudflare, Inc. All rights reserved.

In the npm package.json file, I'm going to include the following:

{
  "contributors": [
    {
      "name": "Austin Wright",
      "email": "[email protected]"
    },
    {
      "name": "Henry Andrews",
      "email": "[email protected]"
    },
    {
      "name": "Geraint Luff",
      "email": "[email protected]"
    }
  ]
}

And then lastly, in the TypeScript definition file itself, I'm going to include this as the top level comment for the definition:

/**
 * JSON Schema
 *
 * Documentation corresponds to the work-in-progress draft-07 of JSON Schema.
 *
 * The latest published drafts are:
 * - draft-handrews-json-schema-01
 * - draft-handrews-json-schema-validation-01
 *
 * For more information, visit: http://json-schema.org/.
 *
 * Draft date: March 19, 2018
 */

I should be releasing this coming week, the package itself doesn't actually include any primary dependencies, but does have plenty of code quality related development dependencies that I need to release first. I'll ping you guys when it's out and if you'd like I can make you all contributors to the repo, I'd like for the community to have access to a really great comprehensive TypeScript definition for JSON Schema.

Please let me know if there are any revisions I should make to anything in the notices/contributors.

[Relequestual]

Closing in favour of #1160