Sample interpreter test suite

[jonaslagoni]

This adds a sample testing suite test for the keyword not. I don't think they are fully there (the output) but at least it is a start.

We are using somewhat the same structure as the official JSON Schema test suite.

However, instead of having a tests property, we use definition. This is what I refer to as the Data definition format here - #8 (comment).

At the moment I use a JSON Schema variant, somewhat the same properties as the spec, but instead of having the meaning of validation, it is a data definition.

[jdesrosiers]

The not keyword is not a good example to start with. We still have to discuss what not even means in a DDL context. I'm inclined to simply say it's a pure validation keyword and has no meaning when interpreted as a DDL.

[jonaslagoni]

The not keyword is not a good example to start with

Good point, gonna redo with your examples 🙂

We still have to discuss what not even means in a DDL context. I'm inclined to simply say it's a pure validation keyword and has no meaning when interpreted as a DDL.

I guess it is 😄

To me, there are no doubts that it must be included, as to whether we whitelist or blacklist (with not) types, we still indirectly say what the underlying data format should be.