This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Use JSON-schema instead of kwalify #31
Comments
Closed
Update: JSON Schema is looking more likely at this stage. Note we will still support YAML, but we will use the subset of YAML that is compatible with JSON (with some tweaks necessary for datetime types). IDL/RPC frameworks such as Thrift, protobuf, etc are not appropriate as ppkts are designed to be used outside the scope of an API (e.g. files deposited in repositories like dryad). However, we will look at compatibility layers in the future, with swagger.io being a high priority. |
This was referenced Mar 6, 2016
cmungall
added a commit
that referenced
this issue
Mar 7, 2016
This was referenced Mar 7, 2016
for reference https://jsonapi.org/faq/ - looks like api is not relevant vs where you are at presently |
Closed
cmungall
added a commit
that referenced
this issue
Mar 22, 2016
cmungall
added a commit
that referenced
this issue
Mar 22, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
kwalify becomes unreadable for complex schemas.
We can adopt a JSON schema standard, so long as we stick to the JSON subset of YAML. ProtoBuf may be a possibility if there is a standard mapping to JSON.
Further afield, SHACL may be worth considering
The text was updated successfully, but these errors were encountered: