Web of Things Interest Group - Past Calendar
Export options
You can exclude canceled events by appending include_canceled=0
to the URLs below.
Personal Links
Please log in to export calendars with all the information you have access to.
Public Links
The following links do not contain any sensitive information and can be shared publicly.
- Download as ics
-
Subscribe with this link:
https://www.w3.org/groups/ig/wot/calendar/export
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Use Case Confirmed
- Europe/BerlinThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Use Case Confirmed
- Europe/BerlinThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Marketing - First of the Month Confirmed
- America/New YorkThe 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.
-
CANCELLED WoT Discovery Tentative
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Architecture Confirmed
- Europe/BerlinThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Use Case Tentative
- Europe/BerlinThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Use Case Confirmed
- Europe/BerlinThe WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications as well as relevant horizontal technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Charter Confirmed
- America/New Yorkhttps://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. -
WoT Charter Confirmed
- America/New Yorkhttps://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. -
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Charter Confirmed
- America/New Yorkhttps://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. -
WoT Charter Confirmed
- America/New Yorkhttps://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. -
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Use Cases Confirmed
- America/New YorkGather requirements for next WG charter draft.
Tuesday, Dec 13, 2022 8:00 am | 1 hour | (UTC-05:00) Eastern Time (US & Canada)
-
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Testfest - 4 Confirmed
- America/New YorkSync 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 -
WoT Testfest -3 Confirmed
- America/New YorkSync 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 -
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Testfest - 2 Confirmed
- America/New YorkSync 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 -
WoT Marketing Confirmed
- America/New YorkNow with the Microsoft Teams link. Testing for one week and then changing the rest.
The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Testfest - 1 Confirmed
- America/New YorkSync 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 -
WoT Scripting API Tentative
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
Special WoT Marketing Confirmed
- America/New YorkMeeting 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. -
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Testfest Confirmed
- America/New YorkWeb of Things testing, with a focus on Architecture and Profiles, but also finishing up Discovery and Thing Description.
-
WoT Testfest Confirmed
- America/New YorkWeb of Things testing, with a focus on Architecture and Profiles, but also finishing up Discovery and Thing Description.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Testfest Confirmed
- America/New YorkWeb of Things testing, with a focus on Architecture and Profiles, but also finishing up Discovery and Thing Description.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Testfest Confirmed
- America/New YorkWeb of Things testing, with a focus on Architecture and Profiles, but also finishing up Discovery and Thing Description.
-
WoT Testfest Confirmed
- America/New YorkWeb of Things testing, with a focus on Architecture and Profiles, but also finishing up Discovery and Thing Description.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
OPC UA / W3C WoT - Technical Discussion Confirmed
- Europe/BerlinDraft agenda:
- Welcome and meeting logistics
- Short round of introductions of the new participants
- discussion about https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- organize regular OPC UA / WoT technical meetings
-
Web of Things Working Group and Web of Things Interest Group Confirmed
- America/VancouverThe agenda for this meeting is here: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2022#Wednesday.2C_September_14
As this is only a 2h meeting no break will be scheduled.
-
Web of Things Working Group and Web of Things Interest Group Confirmed
- America/VancouverThe agenda for this meeting is here: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2022#Monday.2C_September_12
As this is only a 2h meeting no break will be scheduled.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkNote: this will be a special 2h meeting
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.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles (NEW) Confirmed
- America/New York(note: this is a new entry, replacing the cancelled event)
The WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery (Uncanceled) Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Testfest - 5 Confirmed
- America/New YorkTestfest synchronization call.
See https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online -
WoT Testfest - 4 Confirmed
- America/New YorkTestfest synchronization call.
See https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online -
WoT Testfest - 3 Confirmed
- America/New YorkTestfest synchronization call.
See https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online -
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Testfest - 2 Confirmed
- America/New YorkTestfest synchronization call.
See https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online -
WoT Testfest - 1 Confirmed
- America/New YorkTestfest synchronization call.
See https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online -
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT DTDL Confirmed
- America/New YorkSpecial Call, to be held during Use Case/Editor's Call slot. To discuss alignment between WoT TD and Microsoft's DTDL.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
Pre-Meeting OPC UA / W3C WoT Joint Activity Confirmed
- Europe/BerlinFirst preliminary meeting to bring together the interested parties, to explain the exact plans, the current status of the formal cooperation between OPCF and W3C, and the next steps.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT DTDL Overview Confirmed
- America/New YorkSpecial Call, to be held during Use Case/Editor's Call slot. To discuss alignment between WoT TD and Microsoft's DTDL, starting with an in-depth review of DTDL's specification, goals, and capabilities.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Testfest Day 5 Confirmed
- America/New YorkSynchronize testing activities. Focus on Discovery and TDs.
-
WoT Testfest Day 4 Confirmed
- America/New YorkSynchronize testing activities. Focus on Discovery and TDs.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Testfest Day 3 Confirmed
- America/New YorkSynchronize testing activities. Focus on Discovery and TDs.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Testfest Day 2 Confirmed
- America/New YorkSynchronize testing activities. Focus on Discovery and TDs.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Testfest Day 1 Confirmed
- America/New YorkSynchronize testing activities. Focus on Discovery and TDs.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT TD/Binding Templates Confirmed
- America/New YorkThe WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT protocols and payload encodings.
-
WoT Testing Confirmed
- America/New YorkThe WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for organizing general testing procedures, data collection, and implementation report tooling for WoT deliverables.
Note that the Testing/Plugfest call uses the same WebEx as the WoT Main call, but a different IRC channel.
-
WoT Main Confirmed
- America/New YorkThe Main WoT Web Conference is a joint IG/WG call for discussing general WoT IG and WG topics and logistics, and to provide an opportunity to summarize and coordinate the activities of the various task forces. For information on individual task forces, please see the WoT Web Page or look at the other WoT schedule entries.
-
WoT Profiles Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.
-
WoT Chairs Confirmed
- America/New YorkChairs call, typically to finalize agenda prior to main call. Just IG/WG/CG chairs and W3C staff, with the occasional guest.
-
WoT Marketing Confirmed
- America/New YorkThe WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web presence, Social Media presence, and more.
-
WoT Discovery Confirmed
- America/New YorkThe WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
WoT Security Confirmed
- America/New YorkThe WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of the WoT and providing recommendations to support appropriate security technologies and to mitigate security and privacy risks.
-
WoT Scripting API Confirmed
- America/New YorkThe WoT Scripting API task force is responsible for specifying an application programming interface (API) representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose interactions for locally defined Things.
-
WoT Architecture Confirmed
- America/New YorkThe WoT Architecture task force is responsible for both the abstract architecture and interoperability profiles for the Web of Things.