0.1.16 Release

schema and yaml: correct bugs in schema and use safe YAML load/dump

• schema: rename some "id" values, and fix a major bug where the value of "items" was given as an array of one JSON schema, thereby only validating the first element of a list instead of all elements in the list.
• testsuite: fix test data to match newly corrected schema.
• yaml: always use SafeLoader and SafeDumper or preferably the corresponding LibYAML classes if installed.
• yaml: simplify validation of parser errors by catching a generic Exception rather than yaml.parser.ParserError and IOError, also now implicitly catching a yaml.constructor.ConstructorError caused by the presence of "!!python/unicode" tags.
• version: bump to 0.1.16.

Signed-off-by: Graeme Watt [email protected]

0.1.15 Release

validator: catch exceptions, allow absence of comment, bump version

• Catch ParserError and IOError exceptions when loading YAML files.
• Allow a submission.yaml file without an initial "comment" key.
• Add tests to give 100% coverage.
• Bump version to 0.1.15.

Signed-off-by: Graeme Watt [email protected]

0.1.14 Release

• data file validator: allow data to be passed (needed by hepdata-converter)

Signed-off-by: Graeme Watt [email protected]

0.1.13 Release

• Supports custom data schemas
• Adds support for associated records
• Adds type to additional resources (optional)

0.1.8

global: version bump to 0.1.8

* ALLOW extra top level properties to avoid
  any migration issues when new fields are added.

Signed-off-by: Eamonn Maguire <[email protected]>