Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional Metadata #65

Open
GarthDB opened this issue Jun 13, 2019 · 4 comments
Open

Additional Metadata #65

GarthDB opened this issue Jun 13, 2019 · 4 comments

Comments

@GarthDB
Copy link

GarthDB commented Jun 13, 2019

Can the ZWave Adapter add more information to the things? Specifically, I was wondering if it could things like the manufacturer or product name?

The larger context of the question: I started building a homebridge-plugin to add the gateway to Homekit, but there is data that HAP devices support that the Things API doesn't provide.

That information could be explicitly allowed in the wot spec, but could it just be tacked on as optional metadata?

@dhylands
Copy link
Contributor

I've requested this as well here: WebThingsIO/gateway#1396
Please add comments to that bug.

Currently the only way to add additional information is to create an additional property. So it would be possible to create a read-only string property called model (or product or whatever) and have it contain the model string.

The classifier could add these to all devices until such time as we get something better.

@GarthDB
Copy link
Author

GarthDB commented Jun 14, 2019

That's an interesting idea (using the read-only string properties), but it would be really nice if we could work toward a defined standard spec for this information added to the full spec.

@benfrancis
Copy link
Member

Note that the W3C Thing Description specification currently has some additional types of metadata for a Thing we could add support for, or propose new ones.

The manufacturer and product name could be used as the default "name" ("title" in the W3C spec) for a device. We could also implement the "support" member which provides a URL for example.

Although this is not something we've implemented so far, the W3C spec also allows for "Context Extensions" to add additional metadata using external vocabularies.

@GarthDB
Copy link
Author

GarthDB commented Jun 14, 2019

@benfrancis just checking if I understand the Context Extensions, I could add a uri to a json schema that would describe/allow for additional properties?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants