I'm seeing some inconsistencies in the
I'm seeing some inconsistencies in the schemas related to complex values (e.g.
navigation.position, design.keel) and am curious if it's intentional or a mistake.
According to the description of the full data model (https://github.com/SignalK/specification/blob/master/mdbook/src/data_model.md#full-format), the {latitude: …, longitude: :} value for navigation.position is still nested in a value field, and the schema (https://github.com/SignalK/specification/blob/master/schemas/definitions.json#L813) accurately describes it that way.
However, some paths, like design.keel, don't have their properties nested inside of value
https://github.com/SignalK/specification/blob/master/schemas/groups/design.json#L501-L538
I assume that's just an oversight?1 Reply
Now that I'm looking closer at it, it looks like
design.keel.angel and design.keel.lift are stand-alone paths with value/meta. design.keel.type is just the oddball because it doesn't have value/meta.
I think I've come across a few others like this but can't remember which ones. I'll see if I can find it
design.rigging is another example. The schema just has configuration and masts as bare properties, no value/meta
drive.type on propulsion is also a naked value https://github.com/SignalK/specification/blob/master/schemas/groups/propulsion.json#L142-L152
fuel.type https://github.com/SignalK/specification/blob/master/schemas/groups/propulsion.json#L182-L191
The schema for sails is also abnormal. It has meta/source/timestamp alongside name/type/material/brand/etc. https://github.com/SignalK/specification/blob/master/schemas/groups/sails.json