Name: kettle-design
Owner: HearthSim
Description: Repo for Kettle design collaboration
Created: 2017-02-15 20:41:07.0
Updated: 2017-12-10 05:52:23.0
Pushed: 2017-12-21 15:21:58.0
Homepage: null
Size: 39289
Language: C#
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This repository contains all schemas which formalize the Kettle protocol. The schemas kinda mirror the WIKI content.
The formalization is still an early work in progress. Any help on creating schemas is welcome!
Please file an issue if you notice any kind of problem with the protocol and/or possible implementation problems using the defined schemas.
The schemas are organized in a way the Kettle IRI is laid out. Read Kettle Home and Kettle IRI for an explanation about the philosophies for defining the protocol. Both pages contain elaborate explanations to properly identify any piece of data communicated through the protocol.
Contains schemas to explicitly define higher-level constructs in context of HearthStone. These schemas are re-used multiple times accross different Kettle payloads.
Contains schemas which explicitly define enumerations to force specific values for some properties. These schemas are re-used multiple times accross different Kettle payloads.
Contains structural information of each Kettle payload.
The most important one is kettle:types/payload, which translates to /schemas/types/payload.json relative to the repository location. Every Kettle payload has the structure defined by that schema. This structure defines exactly two properties;
Acts as identifier of the entire payload.
Contains the actual information that is being communicated. The structure of this data is defined by the (sibling) type property. The value of data is NEVER null, but can be empty.
Currently any reference between schemas is made by utilising the Kettle IRI, but JSON implementations don't know how to resolve these resource identifiers to actual schemas. As a consequence, schema validators and JSON payload generators will complain.
We must check if JSON validator software can be setup to properly resolve schema documents through the IRI, else each reference needs to be changed to the hosted location of the schemas (which would be Github or HearthSim.net).
No comments are allowed in a JSON document. Each schema in itself is also a JSON document so schemas which have C-style comments (// example) won't validate.