Web of Things Working Group - Calendar
Export options
You can exclude canceled events by appending include_canceled=0
to the URLs below.
Personal Links
Please log in to export calendars with all the information you have access to.
Public Links
The following links do not contain any sensitive information and can be shared publicly.
- Download as ics
-
Subscribe with this link:
https://www.w3.org/groups/wg/wot/calendar/export
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Use Case Confirmed
- America/New YorkThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Main Confirmed
- America/New YorkThe 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.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe 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.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Scripting API Confirmed
- America/New YorkThe 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.
-
WoT Security Confirmed
- America/New YorkThe 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.
-
WoT Discovery Confirmed
- America/New YorkThe 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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
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.