Web of Things Working Group - Calendar

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

The WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.

The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.

The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.

The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.

IRC: #wot-marketing

The Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.

Currently suspended, tentatively to restart post-TPAC, possibly after change to the schedule.

The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.

The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.