Add com.snowplowanalytics.iglu/client_error/jsonschema/1-0-0

[chuwy]

No description provided.

[chuwy]

Hey @BenFradet (maybe @yalisassoon as well), could you please review this one?

Couple of points:

1. It represents either "resolution error" (schema is not available) or "validation error" (schema was found, but invalidated an instance)
2. It probably won't be used anywhere directly as an instance will always be apart of bigger JSON (e.g. bad row), but it can be used as a reference of what Iglu Client is producing.
3. I intentionally didn't include a schema key which caused an error because I believe this is information that user software (Enricher/Loader) owns and it is up to this software to include it properly. But obviously it must be included in a bad row
4. Example of not-found error and example of data failed validation
5. I'm very unhappy of three error/errors properties with different meanings and dataReports keyword. If you have better ideas - please let me know.

[BenFradet]

Question: did we do away with Validation error - schema was found, but data is invalid or the schema itself is invalid from https://gist.github.com/chuwy/f03247b2c399d134d428aa81863bdfc4?

[BenFradet]

does this relate to the anyOf?

[chuwy]

Yes, some error is always present. Either ResolutionError or ValidationError

[BenFradet]

should there be a minItems?

[chuwy]

Yes, good idea.

[BenFradet]

could we have a desc?

[BenFradet]

we seem to be missing required and additionalProperties

[BenFradet]

this is just one report, no?

[BenFradet]

should there be a minItems?

[chuwy]

The schema is not used anywhere directly. But would be super-nice to have when we'll implement references. Descheduling.