You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In working on making the Thing Descriptions and API exposed by the gateway W3C compliant I've found it a bit strange that the JSON schema and TypeScript types used to validate Thing Descriptions live in the gateway-addon-ipc-schema and gateway-addon-node repos respectively.
I'm wondering whether we should eventually have a central repo (or directory inside a repo) inside the WebThingsIO GitHub org to define the JSON schema (and TypeScript types) for the Thing Description data model, as used in WebThings. Schemas which can be shared by the gateway, gateway-addon-node, gateway-addon-python, gateway-addon-ipc-schema and wot-adapter repos but which are independent of those defined in the W3C's wot-scripting-api repo in case we need to temporarily diverge from them.
The text was updated successfully, but these errors were encountered:
Depending on what you have in mind, wouldn't be better to use the wot as base and just add to the context the webthings-specific bits with the wt namespace?
In working on making the Thing Descriptions and API exposed by the gateway W3C compliant I've found it a bit strange that the JSON schema and TypeScript types used to validate Thing Descriptions live in the gateway-addon-ipc-schema and gateway-addon-node repos respectively.
I'm wondering whether we should eventually have a central repo (or directory inside a repo) inside the WebThingsIO GitHub org to define the JSON schema (and TypeScript types) for the Thing Description data model, as used in WebThings. Schemas which can be shared by the gateway, gateway-addon-node, gateway-addon-python, gateway-addon-ipc-schema and wot-adapter repos but which are independent of those defined in the W3C's wot-scripting-api repo in case we need to temporarily diverge from them.
The text was updated successfully, but these errors were encountered: