v0.33.1

What changed for publishers

• A meaning file with no concepts list is now refused, as the OVDB Directory refuses it. concepts missing, null, a mapping or text gives a meaning-concepts finding at the meaning file. An empty list is accepted, as the Directory accepts it.

One new rule value in --json: meaning-concepts. Exit codes and schema are unchanged.

Known gaps still open (Go accepts, the Directory refuses)
The check does not yet judge what is inside the model and meaning files as the Directory does: the ModelSpec file's version, entity and property rules; the shape of each concept and duplicate concept ids; the bindings of concepts to model entities and properties; and chains between concepts. Fixes are in progress, one family at a time.

Changelog

• af1e491 fix: refuse a meaning file with no concepts list, as the Directory does (#63)