Open benfrancis opened 2 years ago
Draft PR #21 implements the first three by allowing the old and new formats.
Similarly, I suggest adding back in support for links as a deprecated alternative to forms.
@tim-hellhake What do you think about also marking the following members as deprecated?
name
- Why does this still exist, wasn't it replaced by title?value
- Why do values of properties get sent in the Thing Description? That should never have happened.href
- This should not be needed in a Thing resource, only a Things resource until we implement the W3C Directory Service APIbaseHref
What's the difference between this and base
?We should also consider vendor-prefixing the following members on some way:
pin
credentialsRequired
e.g. using a new JSON-LD context
{
"schema": [{"wtg": "https://webthings.io/schemas/webthings-gateway" }],
"wtg:pin": {},
"wtg:credentialsRequired": {}
}
For better or worse the schemas defined in definitions.json are currently used by the WebThings Gateway application to validate parts of Thing Descriptions and to generate TypeScript types used to represent them.
There are certain changes needed to these schemas in order to validate W3C compliant Thing Descriptions. Notably:
Ideally we would also remove or vendor-prefix non-standard members of the Thing Description
Before releasing these changes we'll need to evaluate the impact on any existing add-ons which may use these terms directly.