Barry Pitfield
Barry Pitfield
PR for issue #389. The api has been separated out and published on npm `@bkp7/schema-js-api` for now. This PR references version 0.0.5 of `@bkp7/schema-js-api` which is basically the code cut...
The discovery.json schema and supporting [documentation](http://signalk.org/specification/1.0.4/doc/rest_api.html) are ambiguous as regards the following questions: Q: is the format of group of endpoints eg. `"v1"` fixed or is it freetext? Q: is...
The DNS-SD specification doesn't have anywhere to specify the versions or paths to services advertised. The provision of a REST API is optional, so the endpoint info doesn't have to...
Currently the only permitted endpoints are: - signalk-http - signalk-ws - signalk-tcp Should these be permitted: - signalk-https - signalk-wss - signalk-udp Any others ? Redirect doesn't seem like a...
Currently the _http._tcp server web interface can only be defined in the optional DNS-SD advert, and if specified there it MUST be at the root. There is nowhere to specify...
Within meta there is a `untis` property which explicitly defines the (SI) units which the associated value is specified in. There is no-where to indicate the vessel level preferred units....
Currently: - REST API (signalk-http) MAY be implemented - Websockets (signalk-ws) not clear whether implementation is mandatory or optional - TCP streaming (signalk-tcp) MAY be implemented - but no documentation...
Following on from #423, there are a number of cases where there is a "value", but there is no capability to allow "values" in order to cater for multiple sources....
The delta.json schema has a mandatory section `updates` which is documented and being used in the wild. It also has the following sections which are optional: `subscribe` - appears to...
There are currently no automated tests in place for schema validity and these should be added to prevent recurrence of invalid schemas (issues #434 and #320). The current json validator...