[Asdf] enum abuse in OneDM playground

[Carsten Bormann <[e-mail]>]

The sdf linter didn’t catch this yet:

(1) enum definitions without the redundant “type”: “string”:

** sdfobject-genericdefaulttransitiontime.sdf.json: type nil in {"enum"=>["100 Milliseconds", "1 Second", "10 Seconds", "10 Minutes"]}
** sdfobject-genericlevel.sdf.json: type nil in {"enum"=>["100 Milliseconds", "1 Second", "10 Seconds", "10 Minutes"]}
** sdfobject-genericonoff.sdf.json: type nil in {"enum"=>["Off", "On"]}
** sdfobject-genericonoff.sdf.json: type nil in {"enum"=>["100 Milliseconds", "1 Second", "10 Seconds", "10 Minutes”]}

(2) enum definitions with (correct) string values but the conflicting “type”: “number”:

** sdfobject-level.sdf.json: type "number" in {"enum"=>["Up", "Down"]}
** sdfobject-level.sdf.json: type "number" in {"enum"=>["MinimumDeviceValuePermitted", "SetToPreviousValue"]}
** sdfobject-onoff.sdf.json: type "number" in {"enum"=>["SetOnOffTo0", "SetOnOffTo1", "TogglePreviousOnOff", "SetPreviousOnOff"]}

Wondering whether this is a bug in the models or something that we should address (allow?) in the 1.next spec.

Grüße, Carsten