I have a working JSON schema API that we can pass any JSON file to it and it will validate against a JSON schema.
I need to finish JSON schema representation for:
HSDS - A representation to define the rules for the schema
HSDA - A representation to define the surface area of the API.
I am still polishing my JSON schema chops, but also I'm thinking deeply about a mininum viable definition, as well as potentially more verbose definitions.
I'm thinking that we should be allowing for different levels of compliance.
This thinking overlaps with the schema filtering conversaiton for the API -- whether someone wants to see simple or complex responses, or even POST/PUT to the API - Issue 21.
I have a working JSON schema API that we can pass any JSON file to it and it will validate against a JSON schema.
I need to finish JSON schema representation for:
I am still polishing my JSON schema chops, but also I'm thinking deeply about a mininum viable definition, as well as potentially more verbose definitions.
I'm thinking that we should be allowing for different levels of compliance.
This thinking overlaps with the schema filtering conversaiton for the API -- whether someone wants to see simple or complex responses, or even POST/PUT to the API - Issue 21.