When adding a license exception, you must enumerate each allowed license needed to satisfy the expression for the crate, even ones that are already allowed globally. Instead, the allowed list should just be additive to any existing global license setting.

See #119

Unfortunately, the formatting in the licenseText's JSON value is broken for a lot of licenses (e.g. regarding indentation and paragraphs). For any processing the plain text version of the license text, if provided by upstream, should be the source of truth. To capture that, I propose to include a link to the plain text version, if any, into the license details. Preferably this would go to a new

I was impressed with the extensive explanation on data and intellectual property (IP) rights around the world at http://opendefinition.org/guide/data/. The page is an important resource to getting a global understanding of (the jungle of) data/content and IP.

However, in order for this page to be cited/linked by the many, we should be able to get rid of the disclaimer that this is not legal advis

Currently, one can get the basic information from autogen itself by running it without any arguments or with the -h flag, but it would also be useful to be able to run man autogen to get all the information.

Note: it might conflict with, e.g., https://www.gnu.org/software/autogen/manual/autogen.html if we were to publish to the standard man page location with the name autogen, so we may

Desired Behaviour (for enhancement suggestions only)

Not all fields have a description in the datapackage.json schema.

Clarify the meaning of each field with a description.

This would also help resolve #54

As discussed on the tech call, we would like to restructure the examples to allow for users of the spec to select the specific language/syntax desired (e.g. some HTML/JavaScript that would show only examples which are of interest).

Basic documentation is still missing, ideally at least these documents should be written:

• README.md to quickly introduce the topic and this library.
• Wiki pages to introduce license management topics, best practices and usage examples.

Symfony uses a single-star opening line (/*) and has blank lines above/below (example), whereas CakePHP uses a double-star opening line (/**) and has no blank lines above/below (example).

Current error logging doesn't give too much info.
For instance see #7 , guild ID in footer and the actual command with parameters being showed in instance of UserInputError could help in debuging.