Web of Things Working Group - Past Calendar

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

Meeting is cancelled but only marking tentative to be able to revert it if needed

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Note: this slot will be used instead for additional charter discussion, and as such will be a WG, not an IG call.

The 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.

IRC: #wot-uc

See https://www.w3.org/events/meetings/45cf6f40-47f5-42bc-92f9-62196c437568/20230307T073000

Now 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.

IRC: #wot-marketing

MOVED 1 WEEK IN ADVANCE

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 / WebEx

This occurrence will be re-purposed to work on the draft WG charter.

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Note: this slot will be used instead for additional charter discussion, and as such will be a WG, not an IG call.

The 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.

IRC: #wot-uc

The 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.

IRC: #wot-uc / WebEx

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

03:00-05:00 PST
06:00-08:00 EST
07:00-09:00 AST
11:00-13:00 UTC
12:00-14:00 CET
20:00-22:00 JST

See also: https://www.timeanddate.com/worldclock/converter.html?iso=20230216T110000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

Day 2: Wednesday, Feb 15 - Main call/Testing slots

05:00-07:00 PST
08:00-10:00 EST
09:00-11:00 AST
13:00-15:00 UTC
14:00-16:00 CET
22:00-24:00 JST

See also:
https://www.timeanddate.com/worldclock/converter.html?iso=20230215T130000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc / WebEx

Now 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.

IRC: #wot-marketing

2nd WoT WG Charter Meeting

Day 1: Tuesday, Feb 14 - Marketing/Use Cases slots

04:00-06:00 PST
07:00-09:00 EST
08:00-10:00 AST
12:00-14:00 UTC
13:00-15:00 CET
21:00-23:00 JST

See also:
https://www.timeanddate.com/worldclock/converter.html?iso=20230214T120000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

The 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.

IRC: #wot-uc / WebEx

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Special_Meetings_to_Discuss_Next_Charter

Special meeting to discuss next WG charter.
Scheduled as a two hour meeting but will be only 1h on Jan 16 and 17.

https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Special_Meetings_to_Discuss_Next_Charter

Special meeting to discuss next WG charter.
Scheduled as a two hour meeting but will be only 1h on Jan 16 and 17.

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Special_Meetings_to_Discuss_Next_Charter

Special meeting to discuss next WG charter.
Scheduled as a two hour meeting but will be only 1h on Jan 16 and 17.

https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Special_Meetings_to_Discuss_Next_Charter

Special meeting to discuss next WG charter.
Scheduled as a two hour meeting but will be only 1h on Jan 16 and 17.

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Gather requirements for next WG charter draft.

Tuesday, Dec 13, 2022 8:00 am | 1 hour | (UTC-05:00) Eastern Time (US & Canada)

See also:
https://www.timeanddate.com/worldclock/converter.html?iso=20221213T130000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

Now 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.

IRC: #wot-marketing

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

Sync meeting for Dec 2022 testfest.

Thursday, Dec 15: 10am Eastern
See also: https://www.timeanddate.com/worldclock/converter.html?iso=20221215T150000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

Sync meeting for Dec 2022 testfest.

Wednesday, Dec 14: 9am Eastern
See also: https://www.timeanddate.com/worldclock/converter.html?iso=20221214T140000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

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.

IRC: #wot / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Sync meeting for Dec 2022 testfest.

Tuesday, Dec. 13: 8am Eastern
https://www.timeanddate.com/worldclock/converter.html?iso=20221213T130000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

Now 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.

IRC: #wot-marketing

Sync meeting for Dec 2022 testfest.

Monday, Dec. 12: 8am Eastern
See also: https://www.timeanddate.com/worldclock/converter.html?iso=20221212T130000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=33&p9=236&p10=248

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

Meeting with Chairs and Team Contact
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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx

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.

IRC: #wot-sec / WebEx

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.

IRC: #wot-script / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-arch / WebEx

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.

IRC: #wot-td / WebEx

The 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.

IRC: #wot-pf / WebEx

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.

IRC: #wot / WebEx

The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.

IRC: #wot-profile / WebEx

Chairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.

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 / WebEx

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.

IRC: #wot-discovery / WebEx