-
Notifications
You must be signed in to change notification settings - Fork 339
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
Change @context
of Thing Descriptions
#2809
Labels
Milestone
Comments
I think I'm right in saying that as long as there aren't collisions in the annotation names, it would be possible to add the WebThings schema annotations without a prefix. E.g.
|
This was referenced May 26, 2021
Closed
benfrancis
added
the
wot-thing-description
W3C WoT Thing Description specification
label
Jul 26, 2021
This was referenced Sep 28, 2021
Note: The context URL for TD 1.1 has now been specified as |
benfrancis
added a commit
to benfrancis/gateway
that referenced
this issue
Dec 8, 2022
benfrancis
added a commit
to benfrancis/gateway
that referenced
this issue
Dec 15, 2022
benfrancis
added a commit
to benfrancis/gateway
that referenced
this issue
Dec 15, 2022
This was referenced Dec 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Blocks: #2802
Once the Thing Descriptions exposed by the gateway are W3C compliant, we should update the
@context
member to include the stringhttps://www.w3.org/2019/wot/td/v1
to reflect that.Open questions:
https://webthings.io/schemas/
as a context in order to add semantic annotations from the WebThings capability schemas. Does this mean we'll need to add a prefix to all of those annotations? e.g.Note: This should only be done once we've made all the other changes to make Thing Descriptions W3C compliant.
See WebThingsIO/api#157 for some past discussion
The text was updated successfully, but these errors were encountered: