Skip to content
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.

Use JSON-schema instead of kwalify #31

Closed
cmungall opened this issue Feb 20, 2016 · 2 comments
Closed

Use JSON-schema instead of kwalify #31

cmungall opened this issue Feb 20, 2016 · 2 comments

Comments

@cmungall
Copy link
Member

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

@cmungall
Copy link
Member Author

cmungall commented Mar 6, 2016

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.

@mjy
Copy link

mjy commented Mar 7, 2016

for reference https://jsonapi.org/faq/ - looks like api is not relevant vs where you are at presently

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants