Main WoT WebConf

The Main WoT Web Conference is 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 follow the links below to the individual task force Wiki pages.

WebConf Information

• Quick start guide for W3C teleconferences
• Table of all the WoT calls on our Web page
• W3C WG Calendar
• Main WoT WebConf
• Scripting APIs | Security | Discovery | Marketing | Use Cases | PlugFest/Testing | TD | Architecture

Call Logistics

Please check times carefully in your timezone. Daylight Savings time started in the US on March 13. All meetings are set in W3C relative US Eastern time. On March 27, most places in Europe will also start Daylight savings. Therefore in Europe and in places without daylight savings, times for meetings will shift around these dates.

Time

Wednesdays at

• 8am US Eastern
• 5am US Pacific
• 1pm GMT (and UTC, for now)
• 2pm Central Europe
• 10pm Japan

WebEx

• WebEx coordinate on the IG archive (Member-only)
• WebEx coordinate on the WG archive (Member-only) (identical information to the above (for those who participate in only the WG))

Note: To avoid a repetition of fraudulent calls, the ICS files, host codes and meeting passwords should not be shared on the public list or a public wiki or other web page, e.g. in the agenda or minutes.

IRC

• IRC #wot channel: http://irc.w3.org/?channels=wot
• Custom clients: irc.w3.org, port 6667

The IRC is used for the minutes, speaker queue, and sharing links etc.

Schedule

Deliverable and F2F Meeting Plan

The schedule is under discussion; please see the draft in the wot repo.

Upcoming Publication Moratoriums

• None currently

Events

• 22 December 2021 and 28 January 2022: Japanese CG
• 3 February 2022: ITU-T Webinar
• 8 March 2022: AB Discussion
• 11 March 2022: Japanese CG Event - ECHONET
• 14-18 March 2022: Plugfest/Testfest
• 23 March 2022: LE restructuring discussion with members of the AB
• 25 March 2022: Japanese CG Event - Use Case Study Meeting
• 22 April 2022: Japanese CG Event - Smart Buildings

Upcoming

• 18 May 2022: Japanese WoT CG
• 6-10 June 2022: Testfest
• 12-16 September 2022: TPAC

Useful resources

• Kaz's slides on Tools for W3C Spec Work
• W3C WoT WG Calendar/IG Calendar
  • Please export ICS files using "Personal Links", after logging in as a W3C member, to get personal calendar entries with joining information

Ongoing Items

Cancellations and Schedule Updates

• Marketing cancelled June 28
• The following Scripting calls are cancelled in June
  • June 27
• Use Case calls held biweekly but (generally) suspended until 9 Aug
  • Can reinstate calls on demand if necessary
  • EXCEPTION: DTDL In-Depth Discussion on 21 June (same time as the use case call)
    • Please plan to attend if you can!
    • Next DTDL mtg: July 19
• Editors' calls held biweekly (only if necessary) starting from 10 May
  • Now on Tuesdays at 8am Eastern alternating with Use Cases
  • NOTE: Architecture will use the (new) Editor's call slot for the next few weeks!
  • Using Editor's call Webex

Note: Please look in W3C Calendar for updated WebEx invites for Use Cases and Editor's calls.

• WebEx info for Members
• WebEx info for IEs

Ongoing Action Items

Publication

Wide Review

• Guide to Wide Review

Communications

• Accessibility - Voice Interfaces?

Done

• Accessibility questionnaire; applies to all
• Security questionnaire; applies to all
• TD: Internationalization: completed, reviewed, (almost) all updates merged

Mostly Done

• TD: TAG: still under review, TAG has done first pass, "largely happy", but want to re-review after seeing Architecture

In Progress

• Architecture (TAG)
  • Architecture - issue
  • Discovery - issue
• Privacy
  • Architecture - issues
  • TD - issues
  • Discovery - issues
• Security
  • Architecture - issues
  • TD - issues
  • Discovery - issues
• Accessibility
  • Architecture - issues
  • TD - issues
  • Discovery - issues
• Internationalization
  • Architecture - issues
  • Discovery - issues

Drafts

• Architecture (TAG)
  • To do: Profile
• Privacy
  • See: https://github.com/w3cping/privacy-request/issues/new/choose
  • To do: Profile
• Security
  • See: https://github.com/w3c/security-request/issues/new/choose
  • To do: Profile
• Internationalization:
  • See: https://github.com/w3c/i18n-request/issues/new/choose
  • To do: Profile
• Accessibility
  • See: https://github.com/w3c/a11y-request/issues/new/choose
  • To do: Profile

To Do

• Clean up and label issues (all repos)

Explainers

NECESSARY for wide review process. Would be good to link them together.

• Complete:
  • TD
  • Architecture
  • Discovery
• Explainers in progress for:
  • Profiles (Lagally) - draft, review needed

Process

• Async PR process proposal
• Agreed to discuss as part of charter renewal

Resources

• Tools for W3C Spec Work
• Useful material for process, minute-taking IRC setup, wide review, etc.
• Any comments or requests for improvement?

Editors

• Ongoing topics to discuss in Editor's call:
  • Terminology discussion
  • Document consistency check between Architecture and other specs (Scripting, Discovery)
  • Draft implementation reports
  • Schedule review

Use Case Review

• Use case coverage and due diligence
  • Expectations discussion
  • Coverage table
  • Requirements Table (proposed)

Collaborations

Status of collaborations with Other W3C Groups.

WoT CG

• GitHub Issues to discuss the next steps, labelled with CG:
  • Issue 294 - How does the CG work and how does CG keep in sync with IG?
  • Issue 293 - Tools: What tools does CG want to use that are normally given to IGs and WGs?
  • Issue 292 - Expectations: What does CG expect from the collaboration with the IG and what does IG expect from CG?
• To Do:
  • work on WoT CG charter (See CG charter guide and repo)
  • define which Marketing TF activities should move to the WoT CG
  • define other collaboration: https://github.com/w3c/wot-marketing/issues/288

WoT Japanese CG

• Last event: Smart Building Use Cases, on April 22
  • Proposal as a GitHub Issue
  • Announcement
  • Connpass site

Spatial Data on the Web IG

• Ontology needed for geolocation data for use with WoT
• Overlap with some external liaisons, e.g. with OGC, OpenAR, IEEE

Accessibility IG

• To Do: Update/Add Use Cases and Requirements

Charters

WG Charter Extension

• Draft WG Charter for 12mo extension available on GitHub
  • got W3M approval for the AC review and 2-mo extension to finalize the procedure
  • Now the AC Review is ongoing (till June 21)
    • 16 supports; 2 suggestion; 3 abstain
  • Please ask your AC Rep to respond! We need 20 supports.

WG Rechartering

• AFTER the 12mo extension
• Draft WG Charter for the next period
• Still need to update deliverables, calendar, etc.
• See https://github.com/w3c/wot/issues/978
• Need to finalize and submit the new WG charter a few months before the end of the extended charter
• should consider a common model for IoT security as well as data model and protocol

Liaisons

Status of engagements with external standards organizations.

OPC UA

• Joint meeting planned for July 1
  • Logistics: https://www.w3.org/events/meetings/12b636a2-d435-4752-bd77-6fde10d1b74e
• PR for technical objectives: https://github.com/w3c/wot/pull/1020
• Met with Jeff about the next steps on the OPC UA liaison on March 24
  • minutes (Member-only)
  • need to clarify the technical details on our expectations
  • need to have further informal discussions with OPC representatives too
• Next steps
  • Dedicated liaison calls including WoT and OPC UA representatives (Sebastian)
  • Requirements discussion based on the current use case and proposed WoT/OPC UA technical requirements
  • OPC UA PlugFest participation (similar to ECHONET)

ITU-T SG20

• Next steps
  • ITU-T wants to "... focus on ontologies, digital twin and AI related aspects in the smart city context."
  • Plan to develop a document on a new smart cities ontology as an initial step.
  • Gyu Myoung Lee shared slides from WF-IoT
  • Next SG20 mtg is 19-28 July 2022; need further followup before then
  • We have proposed Gyu Myoung Lee joining a near-future main call for a 15 discussion

ECHONET

• Next steps:
  • Clearly define concrete use cases and technical requirements for ECHONET/WoT Binding
  • Gap analysis: Identify missing features needed in WoT-next (to be covered in next charter)
  • Initial discussion to be done within the WoT-JP CG while we (WoT-WG/IG) are concentrating on spec finalization.

IEC CDD (Common Data Dictionary)

• Ontologies for various industries - IEC61360, IEC62656
  • Units are a current topic of discussion, relevant to Profiles
• Previous contacts with ISO TC184/SC4:
  • need clarification on how to refer to their ontologies from TD
  • some specific examples would be useful
  • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
• New contact with current IEC SC 3D - talking about how to proceed
  • Kaz had a meeting with the Chair of the IEC SC 3D on April 18.
  • They would like to have some more internal discussion within IEC.
  • Probably it would be better to start some initial discussion within the WoT-JP CG first, and then bring feedback/input to the WoT-WG next.
  • They have liaison with ISO TC184/SC4 and ECLASS already.
  • Kaz will talk about the next steps with them o June 13 again.

ECLASS

• overlap with IEC discussion (see above)
• need clarification on how to refer to their ontologies from TD
• also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
• an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed

T2TRG/IETF

• May 5 - [link Digital Twin Meeting]
• Presentation given March 10
  • https://github.com/t2trg/2022-03-summary
  • Led to new DDOS security consideration for Discovery

OCG/OpenAR - Geospatial Data

• Overlap in collaboration with Spatial Data on the Web IG
• some discussion during the Use Cases call on Jan-25
• Continue the discussion in Use Cases call

Microsoft DTDL

• Meeting planned for June 21 during Use Case slot
• Seeking alignment
• resources
• engaged with Microsoft, talking about how to proceed

IEEE P2874

• IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• Next meeting 29 June
• Need to follow up on June 1 meeting

Possible

• ASHRAE
• Brick
• OneM2M
• GaiaX
• Solid CG
• EdgeX Foundry
• Home Assistant
• CSA/Matter (formerly Zigbee Alliance/CHIP)
  • Intel is now a member, McCool reviewing draft documents

Agenda

29 June 2022

NOTE:

• July 18 will be a bank holiday in Japan.
  • So it would be better to postpone the next Testfest till the week of July 25 instead.

22 June 2022

Chair: McCool

Regrets: Sebastian

Scribe: Lagally

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
  • New participant(s): Welcome back, Matthias Kovatsch :)
• Minutes
  • June-15
• Quick updates
  • Joint discussion with Microsoft DTDL on Tuesday, June 21
    • Minutes
    • Next steps:
      • Another meeting in about month, in UC slot: July 19
      • Agenda:
        • Goal is interconversion
        • need test plugfest project
        • need mapping of features, identification of gaps in our specs (both TD and Discovery), vocabulary
  • Joint discussion with the Spatial Data on the Web WG (SDW-WG)
    • will be done during the SDW-WG meeting on Jun 23 at 13:00 UTC (9:00 EDT, 10:00 ADT, 15:00 CEST, 22:00 JST); joint with OGC
    • About 10m; McCool will present summary
    • joint call during TPAC not possible, instead want online meeting
    • We need to define next-charter deliverables, e.g. geolocation ontologies, discovery extensions, etc.
    • Probably want a working meeting or two prior to TPAC
  • WoT WG Charter review concluded
    • Results: 21 supports; 2 suggestions; 3 abstains
    • The draft Charter will be modified based on the suggestions (need to remove the descriptions of 2.0 specs - Kaz to implement).
    • Kaz will bring the results to the W3C Management so that we can move ahead.
  • Cancellations and updates
• TPAC 2022
  • 12-16 September, 2022 at Sheraton Wall Centre Vancouver, Canada
  • Doodle to identify good slots for WoT discussions
  • Joint meetings with related groups under discussion
    • Spatial Data on the Web - not at TPAC
    • DID
    • JSON-LD
    • Automotive
  • Registration opens end of June (probably June 30)
  • Please start to book your flights and hotels ASAP
    • Please see the logistics page for the hotel booking information.
    • Early Bird rate – until 31 July: EUR 290 [Rate limited to the 4 first persons of a same company]
    • Remote Early Bird rate – until 31 July: EUR 95 [Rate limited to the 4 first persons of a same company]
  • GitHub repo for TPAC2022-Health-rules
    • Issues to solicit opinions/questions
  • Sheraton rules
• Publications
  • Wide Review action item
  • Status update on Thing Description 1.1 draft publication
  • Update on Discovery CR Candidate: two-week review starting one week ago
    • Call for a Resolution to publish WD planned for June 29 Main Call
    • If find problems, post PR or raise issue and label "CR Candidate"
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Testfest held on June 6-10
  • current status of the Implementation Reports and features at-risk
    • TD - merged
    • Discovery - merged
    • Architecture - new
    • Profile - new
  • TODO:
    • Gaps in implementation reports
    • potential at-risk items in CR that we can resolve by PR (see testing/todo.csv)
    • another testfest in July
      • Focus on Profiles
• Review Charter Extensions and Renewal
  • Items for the next WoT-WG Charter period?
• Review Liaisons
  • OPC-UA meeting planned for July 1
• Review Collaborations
• WoT Web Page: WoT-CG vs WoT-IG Marketing TF
  • Should the CG manage the WoT web page?
  • Github issue, pros and cons.
  • need to clarify which information to be handled by the CG and which by the IG/WG
    • Question 1: Do we want to transfer all the WoT Marketing site to the CG?
    • Question 2: Do we want to handle the CG(s) as part of the consolidated "WoT@W3C Activity" like the " Publishing@W3C Activity"?
    • Call for meeting on 5 July in Marketing call to discuss, come to a consensus, follow up with discussion in main call
• Review Ongoing Action Items
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

15 June 2022

Chair: McCool

Regrets: Sebastian

Scribe: Koster

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
• Minutes
  • June-8
• Quick updates
  • Joint discussion with the Spatial Data on the Web WG (SDW-WG)
    • will be done during the SDW-WG meeting on Jun 23 at 13:00 UTC (9:00 EDT, 10:00 ADT, 15:00 CEST, 22:00 JST); joint with OGC
    • About 10m; McCool will present summary, propose joint call during TPAC
  • Cancellations and updates
• TPAC 2022
  • 12-16 September, 2022 at Sheraton Wall Centre Vancouver, Canada
  • Registration opens end of June
  • Please start to book your flights and hotels
    • Please see the logistics page for the hotel booking information.
    • Early Bird rate – until 31 July: EUR 290 [Rate limited to the 4 first persons of a same company]
    • Remote Early Bird rate – until 31 July: EUR 95 [Rate limited to the 4 first persons of a same company]
  • GitHub repo for TPAC2022-Health-rules
    • Issues to solicit opinions/questions
  • Sheraton rules
• Publications
  • Wide Review action item
  • Status update on Thing Description 1.1 draft publication
  • Update on Discovery CR Candidate: two-week review starting now
    • old WD update dropped, moving to new version, new review
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Testfest held last week (June 6-10)
  • current status of the Implementation Reports and features at-risk
    • TD - new
    • Discovery - new
    • Architecture
    • Profile
  • TODO:
    • Gaps in implementation reports
    • potential at-risk items in CR that we can resolve by PR (see testing/todo.csv)
    • another testfest in July
      • Focus on Profiles
• Review Charter Extensions and Renewal
  • We still need 2 more (preferably 5 more) supports for the AC review
  • got 2 comments to remove the Ver. 2.0 specs for the extended Charter period
• Review Liaisons
• Review Collaborations
• WoT Web Page: WoT-CG vs WoT-IG Marketing TF
  • Should the CG manage the WoT web page?
  • Github issue, pros and cons.
  • need to clarify which information to be handled by the CG and which by the IG/WG
    • Question 1: Do we want to transfer all the WoT Marketing site to the CG?
    • Question 2: Do we want to handle the CG(s) as part of the consolidated "WoT@W3C Activity" like the " Publishing@W3C Activity"?
    • Call for meeting on 5 July in Marketing call to discuss, come to a consensus, follow up with discussion in main call
• Review Ongoing Action Items
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

8 June 2022

Chair: Sebastian/McCool

Regrets: Michael Lagally

Scribe: Kaz

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
  • (Potential?) New participant: Elodie Thieblin from Siemens
• Minutes
  • June-1
• Quick updates
  • Debrief from IEEE P2874 on June 1 at 1pm EDT
    • McCool gave a presentation using existing proposal.
  • Joint discussion with the Spatial Data on the Web WG during the OGC Technical Committee Meeting on June 15 at 08:45-09:30 UTC (10:45-11:30 CEST, 05:45-06:30 ADT, 17:45-18:30 JST)
    • Also a June 23 meeting at 13:00-14:00 UTC; propose we aim for this instead
    • About 10m; McCool will present summary, propose joint call during TPAC
  • Cancellations and updates
• TPAC 2022 Site is open now
  • 12-16 September, 2022 at Sheraton Wall Centre Vancouver, Canada
  • Registration opens end of June
  • GitHub repo for TPAC2022-Health-rules
    • Issues to solicit opinions/questions
  • Sheraton rules
• Publications
  • Wide Review action item
  • Explainers action item
  • Resolution for the Thing Description 1.1 draft publication as an updated WD (as a CR candidate)
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Testfest ongoing this week
    • please see above link for instructions
    • Need in particular manual.csv updates
  • Work still needed prior to CR transition
  • Gaps in implementation reports
    • Need to bring forward TD 1.0 results, update TD implementation report
  • Final test inputs to: wot-testing/data/input_2022
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
      • May have at-risk items in CR that we can resolve by PR
      • Discussing having another testfest in July for Profiles
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• WoT Web Page: WoT-CG vs WoT-IG Marketing TF
  • Should the CG manage the WoT web page?
  • Github issue, pros and cons.
• Review Ongoing Action Items
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

1 June 2022

Chair: McCool

Regrets: Sebastian, Ege, Lagally

Scribe: Koster

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
• Minutes
  • May-25
• Quick updates
  • IEEE P2874 Updates
    • June 1 at 1pm EDT
    • McCool is organizing a presentation using existing proposal.
  • Cancellations and updates
• TPAC Logistics Questionnaire
  • 12-16 September, 2022 at Sheraton Wall Centre Vancouver, Canada
  • 26 groups answered (Member-only)
    • Would be good to refine our response, esp. number of attendees
  • GitHub repo for TPAC2022-Health-rules
    • Issues to solicit opinions/questions
  • Sheraton rules
• WoT Web Page: WoT-CG vs WoT-IG Marketing TF
  • Should the CG manage the WoT web page?
  • Github issue, pros and cons.
• Review Ongoing Action Items
• Publications
  • Wide Review action item
  • Explainers action item
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
    • Need to bring forward TD 1.0 results, update TD implementation report
  • Final test inputs to: wot-testing/data/input_2022
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • Another testfest planned for 6-10 June
      • Doodle ongoing to decide the times for Testfest during the week of June 6-10.
      • May have at-risk items in CR that we can resolve by PR
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

25 May 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Daniel

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
• Minutes
  • May-18
• Quick updates
  • IEEE P2874
    • McCool is organizing a presentation using existing proposal.
    • To be held 1 June 2022 at 1:00pm Eastern Time
    • Draft Presentation
  • Cancellations and updates
  • JP Member meeting debriefing
• Publications
  • Wide Review action item
  • Explainers action item
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
  • Calls for WD Updates
    • Note: limit to 1 week review period acceptable for the following?
    • TD planning to finalize a draft for a WD update next week (call for resolution expected)
    • Architecture finalized a branch last week for a WD update (call for resolution to publish)
• Review other Ongoing Action Items
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
    • Have brought forward TD 1.0 results and updated TD implementation report
  • Final test inputs to: wot-testing/data/input_2022
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Need to update other draft implementation reports for each deliverable
      • Discovery
      • Architecture
      • Profile
    • Another testfest planned for 6-10 June
      • Doodle to decide the times for Testfest during the week of June 6-10.
      • Proposal: 8am Eastern Monday and Tuesday, 10am Eastern Wednesday, Thursday, and Friday
      • May have at-risk items in CR that we can resolve by PR
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
  • Marketing
    • Should the CG manage (some of) the WoT web pages?
    • Identifying specific pages and activities
    • Content vs. site management
    • Distinguishing WG and CG pages (e.g. watermarking)
    • Github issue, pages and activities, pros and cons.
• AOB?

18 May 2022

Chair: McCool/Sebastian

Regrets: Kaz and JP Members (due to the JP Members meeting)

Scribe: Sebastian

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
• Minutes
  • May-11
• Quick updates
  • IEEE P2874 Invitation
    • Geolocation and WoT
    • Wednesday 1 June 2022 at 1pm Eastern
    • Would be good to capture additional requirements for geolocation, e.g. for BIM
    • McCool will organize a presentation using existing proposal and this input
  • Cancellations and updates
  • JP Member meeting on May 18
    • There will be the W3C Japanese Member meeting (Member-only) today on Wednesday May 18, so Kaz and the JP Members can't make the calls on May 18.
    • Please see Kaz's slides on Tools for W3C Spec Work to capture minutes, etc.
    • Kaz has sent out updated WebEx coordinates with hostkeys so that the co-Chairs or other participants can become the host for the calls.
      • Profile: WebEx info for Members, WebEx infor for IEs
      • Main call: WebEx info for Members, WebEx infor for IEs
      • TD: WebEx info for Members, WebEx infor for IEs
• WoT Web Page
  • Should the CG manage the WoT web page?
  • Github issue, pros and cons.
• Review Ongoing Action Items
• Publications
  • Wide Review action item
  • Explainers action item
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
    • Need to bring forward TD 1.0 results, update TD implementation report
  • Final test inputs to: wot-testing/data/input_2022
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • Another testfest planned for 6-10 June
      • Doodle ongoing to decide the times for Testfest during the week of June 6-10.
      • May have at-risk items in CR that we can resolve by PR
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

11 May 2022

Chair: McCool

Regrets: Sebastian

Scribe: Lagally

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
• Minutes
  • May-4
• Quick updates
  • Cancellations and updates
    • Editor's call now on Tuesdays at 8am Eastern alternating with Use Cases
    • TO CONFIRM IN MAY 11 MAIN CALL:
      • Use Case calls held biweekly but suspended until 9 Aug
      • Editors' calls held biweekly only if necessary starting from 10 May
  • JP Member meeting on May 18
    • There will be the W3C Japanese Member meeting (Member-only) on Wednesday May 18 next week, so Kaz and the JP Members can't make the calls on May 18.
    • Calls will not be cancelled but we will have to review how to capture minutes, etc.
  • T2TRG work meeting held 4 May 2022 on Digital Twins
  • W3C IG/WG Calendar updates for Use Case and Editors' call
• Review Ongoing Action Items
• Publications
  • Wide Review action item
  • Explainers action item
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
    • Need to bring forward TD 1.0 results, update TD implementation report
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • Another testfest planned for 6-10 June
      • May have at-risk items in CR that we can resolve by PR
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

4 May 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Sebastian

• Guests, New Members, and Invited Experts
  • Guest: Erich Barnstedt, Microsoft
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
    • FYI: Alexander Power agreed to start with the WoT CG discussion.
• Minutes
  • Apr-27
• Quick updates
  • Cancellations
  • W3C IG/WG Calendar
• Guest Introductions and Discussion
  • Microsoft
  • DTDL
  • Alignment in next charter?
  • OPC UA collaboration - ontology, etc.
  • Digital Twin Consortium
• Meeting Schedule Proposed Changes
  • Use case call temporary suspension
  • Moving editor's call (into Use case call slot?)
• Review Ongoing Action Items
• Publications
  • Wide Review action item
  • Explainers action item
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest in May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

27 April 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Sebastian

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
    • FYI: Alexander Power agreed to start with the WoT CG discussion.
• Minutes
  • Apr-20
• Review Ongoing Action Items
• Quick updates
  • Cancellations
  • W3C IG/WG Calendar
  • Brief report from the Sustainability discussion during the AC meeting on Apr 27 (Member-only)
• Publications
  • Wide review:
    • Guide to Wide Review
    • Done
      • Security questionnaire done; applies to all
      • TD: TAG: still under review, TAG has done first pass, "largely happy", but want to re-review after seeing Architecture
      • TD: Internationalization: completed and has been reviewed, still some outstanding issues
    • In progress:
      • Architecture (TAG)
        • [link Architecture] - draft issue
        • Discovery - draft issue
      • Privacy
        • See: https://github.com/w3cping/privacy-request/issues/new/choose
        • [link Architecture] - draft issue
        • TD - issue
        • Discovery - draft issue
      • Security
        • See: https://github.com/w3c/security-request/issues/new/choose
        • [link Architecture] - draft issue
        • TD - issue
        • Discovery - draft issue
      • Internationalization:
        • [link Architecture] - draft issue
        • Discovery - draft issue
          • Discovery has completed i18n questionnaire but still needs explainer
      • Accessibility
        • Draft questionnaire complete
        • [link Architecture] - draft issue
        • [link Discovery] - draft issue
        • [link TD] - draft issue
    • To do:
      • Clean up and label issues (all repos)
  • Explainers:
    • Complete:
      • TD: https://github.com/w3c/wot-thing-description/pull/1397
    • Explainers in progress for:
      • Architecture (Lagally) - draft
      • Discovery (McCool) - placeholder only
      • Profiles (McCool/Lagally/Ben) - placeholder only
    • Need to turn these into actual drafts
    • NECESSARY for wide review process
    • Would be good to link them together
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest in May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

20 April 2022

Chair: McCool

Regrets: Lagally, Sebastian

Scribe: Daniel

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request: none
• Minutes
  • Apr-13
• Ongoing Action Items
• Quick updates
  • Cancellations
    • No pending cancellations
  • W3C IG/WG Calendar
  • Collaboration Updates
    • IEC CDD Liaison
    • WoT Japanese CG
    • Microsoft DTDL
• Publications
  • Wide review:
    • Guide to Wide Review
    • Done
      • Security questionnaire done; applies to all
      • TD: TAG: still under review
      • TD: Internationalization: completed and has been reviewed
    • Next steps:
    • Security
      • Review is separate from TAG request, see: https://github.com/w3c/security-request/issues/new/choose
    • Privacy
      • All still need to do. NOT covered by TAG review. See https://github.com/w3cping/privacy-request/issues/new/choose
    • Internationalization:
      • Checklist
      • Issue tracker
      • Discovery, Profiles, Architecture all still need to do.
      • Discovery has completed i18n questionnaire but still needs to trigger review
    • To do:
      • Clean up and label issues (all repos)
      • Note that other questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
      • Still need to create other review requests, e.g. for PING
  • Explainers:
    • TD Complete: https://github.com/w3c/wot-thing-description/pull/1397
    • Explainers in progress for:
      • Architecture (Lagally)
    • Still need drafts for
      • Discovery (McCool)
      • Profiles (McCool/Lagally/Ben)
    • Would be good to link them together...
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Testing
  • Work still needed prior to CR transition
  • Gaps in implementation reports
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions and testimonials
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest in May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Review Charter Extensions and Renewal
• Review Liaisons
• Review Collaborations
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Reviews of S&P Considerations mostly complete
    • Still need to do some cleanup in Architecture (propose flattening structure)
    • Updating WoT Security Testing Plan
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

13 April 2022

Chair: Sebastian/McCool

Regrets: Lagally

Scribe: McCool/Ege

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
  • New IE request
    • Alexander Power
• Minutes
  • Apr-6
• Kaz's presentation on Tools for W3C Spec Work - 10 mins
• OPC-UA liaison: Next steps?
  • Proposed Technical Requirements
    • Need to gather input and refine using PR reviews
    • Need to align with/align the OPC UA use case (see below)
  • Process
    • opt 1. Dedicated liaison calls including both the WoT guys and OPC guys?
    • opt 2. Requirements discussion based on the current use case?
    • opt 3. OPC guys' PlugFest participation like ECHONET?
• Quick updates
  • Cancellation
    • See above; any more?
  • W3C Calendar system
    • People should visit the IG Calendar and the WG Calendar to get the ICS files and add the information to their own personal calendar.
  • Editors' sync-up call on Tuesday
    • April 12 and 19 calls cancelled due to Easter holidays
    • Ongoing topics to discuss:
      • Terminology discussion
      • Document consistency check between Architecture and other specs (Scripting, Discovery)
      • Draft implementation reports
      • Use case coverage - see below
  • WoT Japanese CG updates?
    • planning the next event on smart building use cases on April 22
      • Proposal as a GitHub Issue
      • Announcement
      • Connpass site
  • Use Case due diligence:
    • Expectations discussion
    • Coverage table
    • Requirements Table (proposed)
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y
    • Kaz talked with PLH about the next steps, and PLH sent a request for approval to W3M.
      • still not discussed...
      • We can send our request for the AC Review if it's approved.
      • NOTE: Got some belated comments on Privacy & Security
        • Sam's comments on the Strategy Issue 298
        • Kaz has responded - see [link]
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • should consider a common model for IoT security as well as data model and protocol
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • Discovery
    • Normative feature freeze April 11
    • Recent PRs to Security and Privacy Considerations converted to normative content
  • Any other updates?
  • Wide review:
    • Done
    • Security questionnaire: https://github.com/w3c/wot-architecture/blob/main/publication/ver11/security_and_privacy.md
      • TAG Wide Review request issue for TD has been updated
    • Internationalization:
      • TD has completed and been reviewed
    • In progress:
      • Discovery has completed i18n questionnaire but still needs to trigger review for security and internationalization; need explainer still
    • To do:
      • Clean up and label issues (all repos)
      • Note that other questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
      • Still need to create other review requests, e.g. for PING
  • Explainers:
    • TD Complete: https://github.com/w3c/wot-thing-description/pull/1397
    • Explainers in progress for:
      • Architecture (Lagally)
    • Still need drafts for
      • Discovery (McCool)
      • Profiles (McCool/Lagally/Ben)
    • Would be good to link them together...
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Marketing
  • How to deal with Issue 290?
    • Checking with Coralie as well
  • How to collaborate with the WoT CG?
    • GitHub Issues to discuss the next steps, labelled with CG:
      • Issue 294 - How does the CG work and how does CG keep in sync with IG?
      • Issue 293 - Tools: What tools does CG want to use that are normally given to IGs and WGs?
      • Issue 292 - Expectations: What does CG expect from the collaboration with the IG and what does IG expect from CG?
    • To Do:
      • work on WoT CG charter
      • define which Marketing TF activities should move to the WoT CG
      • define other collaboration: https://github.com/w3c/wot-marketing/issues/288
• Testing still needed prior to CR transition
  • Gaps in implementation reports
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • CR transition for Arch and TD are mid-Apr
      • PR transition is planned for mid-May
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest start of May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Liaisons
  • ITU-T SG20
    • Some followup needed
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • got contacts from ISO TC184/SC4
      • need clarification on how to refer to their ontologies from TD
      • some specific examples would be useful
      • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
    • got another contacts from IEC SC 3D - talking about how to proceed (meeting on Apr-18)
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • had a call with Jeff about the next steps on the OPC UA liaison on March 24 - minutes (Member-only)
      • need to clarify the technical details on our expectations
      • should have an informal discussion with the OPC guys too
  • T2TRG/IETF
    • Presentation given March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • Led to new DDOS security consideration for Discovery
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Microsoft DTDL
    • got another contact from Microsoft Japan - talking about how to proceed with WoT Chairs and Lagally
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire complete, see above
    • Need to update (and implement...) WoT Security Testing Plan
  • Discovery
    • Normative feature freeze Real Soon Now (TM), working on Security PRs (which will have assertions now...)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

6 April 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Cristiano

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Mar-30
• Kaz's presentation on Tools for W3C Spec Work - 10 mins
• OPC-UA liaison: How to proceed?
  • Proposed Technical Requirements
    • Need to gather input and refine using PR reviews
    • Need to align with/align the OPC UA use case (see below)
  • Process
    • opt 1. Dedicated liaison calls including both the WoT guys and OPC guys?
    • opt 2. Requirements discussion based on the current use case?
    • opt 3. OPC guys' PlugFest participation like ECHONET?
• Quick updates
  • Cancellation
    • any?
  • W3C Calendar system
    • People should visit the IG Calendar and the WG Calendar to get the ICS files and add the information to their own personal calendar.
  • Editors' sync-up call on Tuesday
    • Apr-5 call was planned to be used for the OPC liaison discussion but cancelled due to lack of participation in the end.
      • initial discussion today
    • Ongoing topics to discuss:
      • Terminology discussion
      • Document consistency check between Architecture and other specs (Scripting, Discovery)
      • Draft implementation reports
      • Use case coverage - see below
  • WoT Japanese CG updates?
    • planning the next event on smart building use cases on April 22
      • Proposal as a GitHub Issue
      • Announcement
      • Connpass site
  • Use Case due diligence:
    • Expectations discussion
    • Coverage table
    • Requirements Table (proposed)
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y
    • Kaz talked with PLH about the next steps, and PLH sent a request for approval to W3M. - not discussed on March 30 but probably today on April 6
      • We can send our request for the AC Review if it's approved.
      • Got some belated comment for Privacy - see Sam's comments on the Strategy Issue 298
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • should consider a common model for IoT security as well as data model and protocol
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • Discovery needs new normative content
    • Still pending, unfortunately; schedule has been updated
    • need a new context file too...
    • Set of pending PRs to clean up Security and Privacy Considerations
  • Any others?
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Final version here: https://github.com/w3c/wot-architecture/blob/main/publication/ver11/security_and_privacy.md
      • TAG Wide Review request issue for TD has been updated
    • Note that other questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
    • Still need to create other review requests, e.g. for PING
  • Explainers:
    • One for TD nearing completion: https://github.com/w3c/wot-thing-description/pull/1397
    • Still need explainers for Architecture, Discovery, and Profiles
    • Would be good to link them together...
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Marketing
  • How to collaborate with the WoT CG?
    • GitHub Issues to discuss the next steps, labelled with CG:
      • Issue 294 - How does the CG work and how does CG keep in sync with IG?
      • Issue 293 - Tools: What tools does CG want to use that are normally given to IGs and WGs?
      • Issue 292 - Expectations: What does CG expect from the collaboration with the IG and what does IG expect from CG?
    • To Do:
      • work on WoT CG charter
      • define which Marketing TF activities should move to the WoT CG
      • define other collaboration: https://github.com/w3c/wot-marketing/issues/288
• Testing still needed prior to CR transition
  • Gaps in implementation reports
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • CR transition for Arch and TD are mid-Apr
      • PR transition is planned for mid-May
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest start of May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Liaisons
  • ITU-T SG20
    • Some followup needed
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • had a call with Jeff about the next steps on the OPC UA liaison on March 24 - minutes (Member-only)
      • need to clarify the technical details on our expectations
      • should have an informal discussion with the OPC guys too
  • T2TRG/IETF
    • Presentation given March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • Led to new DDOS security consideration for Discovery
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire complete, see above
    • Need to update (and implement...) WoT Security Testing Plan
  • Discovery
    • Normative feature freeze Real Soon Now (TM), working on Security PRs (which will have assertions now...)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

30 March 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Daniel

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Mar-23
• Kaz's presentation on Tools for W3C Spec Work - 10 mins
• OPC-UA: See below
• Quick updates
  • European Summertime started on 27 March 2022:
    • The WoT calls start one hour later than last week IN EUROPE but that is the original time.
    • In other places (US, Canada, Japan, etc) the times remain the same.
  • Cancellation
    • any?
  • W3C Calendar system
    • People should visit the IG Calendar and the WG Calendar to get the ICS files and add the information to their own personal calendar.
  • Editors' sync-up call on Tuesday
    • Mar-29 - Kaz had updated his slides on "Tools for W3C Spec Work" and reviewed it again - presentation later during this call
    • Ongoing topics to discuss:
      • Terminology discussion
      • Document consistency check between Architecture and other specs (Scripting, Discovery)
      • Draft implementation reports
  • WoT Japanese CG updates?
    • held an event on WoT use cases in general based on the updated Use Cases Note on 25 March 2022
      • Official announcement on the CG repo
      • Draft minutes
    • planning the next event on smart building use cases on April 22
      • Proposal as a GitHub Issue
      • Announcement
  • Use Case due diligence:
    • https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y
    • Kaz talked with PLH about the next steps.
      • PLH has sent a request for approval to W3M and they'll discuss the request today on March 30.
      • We can send our request for the AC Review if it's approved.
      • See also the comments on the GitHub Issue
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • should consider a common model for IoT security as well as data model and protocol
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • Discovery needs new normative content
    • Still pending, unfortunately; schedule has been updated
    • need a new context file too...
    • Set of pending PRs to clean up Security and Privacy Considerations
  • Any others?
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Final version here: https://github.com/w3c/wot-architecture/blob/main/publication/ver11/security_and_privacy.md
      • TAG Wide Review request issue for TD has been updated
    • Note that other questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
    • Still need to create other review requests, e.g. for PING
  • Explainers:
    • One for TD nearing completion: https://github.com/w3c/wot-thing-description/pull/1397
    • Still need explainers for Architecture, Discovery, and Profiles
    • Would be good to link them together...
  • PROGRESS CHECK: continue to check the progress based on the updated plan
    • also update the schedule on the WoT main wiki
    • potential delay due to the lack of implementations for at-risk features
• Marketing
  • How to collaborate with the WoT CG?
    • GitHub Issues to discuss the next steps, labelled with CG:
      • Issue 294 - How does the CG work and how does CG keep in sync with IG?
      • Issue 293 - Tools: What tools does CG want to use that are normally given to IGs and WGs?
      • Issue 292 - Expectations: What does CG expect from the collaboration with the IG and what does IG expect from CG?
    • To Do:
      • work on WoT CG charter
      • define which Marketing TF activities should move to the WoT CG
      • define other collaboration: https://github.com/w3c/wot-marketing/issues/288
• Testing still needed prior to CR transition
  • Gaps in implementation reports
  • Ongoing, using wot-testing event repo for 2022.03.Online testfest:
    • Capture test data
    • Capture implementation descriptions
    • Capture results
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • CR transition for Arch and TD are mid-Apr
      • PR transition is planned for mid-May
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest start of May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Liaisons
  • ITU-T SG20
    • Some followup needed
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • had a call with Jeff about the next steps on the OPC UA liaison on March 24 - minutes (Member-only)
      • need to clarify the technical details on our expectations
      • should have an informal discussion with the OPC guys too
  • T2TRG/IETF
    • Presentation given March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • Led to new DDOS security consideration for Discovery
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire complete, see above
    • Need to update (and implement...) WoT Security Testing Plan
  • Discovery
    • Normative feature freeze Real Soon Now (TM), working on Security PRs (which will have assertions now...)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

23 March 2022

Chair: McCool

Regrets: Sebastian

Scribe: Lagally

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Mar-16
• Quick updates
  • European Summertime will start on 27 March 2022:
    • The WoT calls will start one hour later than this week IN EUROPE ONLY (but that is the original time :).
    • In other places (US, Canada, Japan, etc) the times will remain the same
  • Cancellation
    • any?
  • W3C Calendar system
    • People should visit the IG Calendar and the WG Calendar to get the ICS files and add the information to their own personal calendar.
  • AB meeting on March 23 (2nd part of the TD call) about W3C LE at 11am EDT for WoT participants.
  • Editors' sync-up call on Tuesday
    • Mar-22 - Kaz explained the slides on "Tools for W3C Spec Work"
    • Ongoing topics to discuss:
      • Terminology discussion
      • Document consistency check between Architecture and other specs (Scripting, Discovery)
      • Draft implementation reports
  • WoT Japanese CG updates?
    • planning yet another event Friday, March 25 on WoT use cases in general based on the updated Use Cases Note
      • Official announcement on the CG repo
      • Connpas site
  • Use Case due diligence:
    • https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv
  • Chairs survey about TPAC 2022 - need to finalize our feedback
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • PLH's message on the Chairs list (Member-only) - response expected by 28 March
    • similar questionnaire for the group participants is also available - response expected by 23 March
      • 11 responses, 7 say "somewhat likely" or "likely" -> "somewhat likely"
      • McCool will roll up responses and submit "somewhat likely" this afternoon for group response
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y
    • Kaz will talk with the reviewers for security and privacy again.
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • should consider a common model for IoT security as well as data model and protocol
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
    • Still pending, unfortunately; we are now behind schedule.
    • need a new context file too...
    • Set of pending PRs to clean up Security and Privacy Considerations
  • Any others?
  • continue to check the progress based on the updated plan and the schedule on the WoT main wiki - need to consider the potential delay due to the Plugfest/Testfest on March 14-18
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • PR to update Architecture here: https://github.com/w3c/wot-architecture/pull/723
      • Review completed, would like to merge and update TAG/PING Wide Review request issues ASAP
    • Currently under TD spec; however, written so one will work for all; planning to move to Architecture
    • Note that other questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
  • Explainers:
    • One for TD nearing completion: https://github.com/w3c/wot-thing-description/pull/1397
    • Still need explainers for Architecture, Discovery, and Profiles
    • Would be good to link them together...
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236 (pending; collaboration)
    • https://github.com/w3c/wot-marketing/issues/219 (propose closing)
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • WoT Community Group
    • Ege and Cristiano are the co-Chairs of the WoT CG now.
    • To Do:
      • work on WoT CG charter
      • define which Marketing TF activities should move to the WoT CG
      • define other collaboration: https://github.com/w3c/wot-marketing/issues/288
• Testing needed prior to CR transition
  • Testfest/Plugfest reports and next steps
  • Planned outcomes:
    • Capture test data
    • Capture implementation descriptions
    • Update draft implementation reports for each deliverable
      • TD
      • Discovery
      • Architecture
      • Profile
    • May need to organize another testfest
      • CR transition for Arch and TD are mid-Apr
      • PR transition is planned for mid-May
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest start of May would let us fill gaps
      • In the meantime testing is ongoing and test Things should stay online
• Liaisons
  • ITU-T SG20
    • Some followup needed
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Sebastian presented the idea of UA Binding for WoT at the OPCF TCB (February 9, 2022)
    • receive positive feedback to setup a joint activity that should result into a W3C Note / OPC UA Companion document (details have to be clarified)
  • T2TRG/IETF
    • Presentation given March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • Led to new DDOS security consideration for Discovery
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire complete, see above
    • Need to update (and implement...) WoT Security Testing Plan
  • Discovery
    • Normative feature freeze Real Soon Now (TM), working on Security PRs (which will have assertions now...)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

16 March 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Sebastian

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Mar-9
  • Scripting API's possibility for a normative Note Track document - still need discussion?
    • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
    • https://github.com/w3c/wot-scripting-api/issues/354
    • see also the W3C Process 2021 and the Documents published at W3C
    • Question: Do we really want to go for that direction? If so need to check with the AC Reps of the WoT participants too, and should set a deadline, e.g., end of June
• Quick updates
  • US Daylight saving has started on 13 March 2022:
    • Plugfest/Testfest on 14-18 March is held at 8-10am EDT. Due to the Daylight Saving time, the time in non-US countries is different from last week. See also timeanddate for the time in your timezone.
    • The calendar on the WoT page ha been also updated accordingly.
  • Cancellation
    • Main call on Mar-16 for just logistics confirmation
    • Testing/Plugfest delayed by one hour on Mar-16
    • All the other TF calls will be cancelled on March-14-18
  • W3C Calendar system
    • People should visit the IG Calendar and the WG Calendar to get the ICS files and add the information to their own personal calendar.
    • Chairs' and Editors' calls now added (but only Chairs and Editors need attend)
  • AB meeting on March 23 about W3C LE at 11am EDT for WoT participants - McCool will register it to the WoT WG/IG calendars
  • Editors' sync-up call on Tuesday
    • Mar-15 call cancelled - next call will be held on Mar-22
    • Topics:
      • Continuing terminology discussion
      • Document consistency check between Architecture and other specs (Scripting, Discovery) to be continued
      • Draft implementation reports
      • Procedure and tools on publishing specs in general - Kaz will give an updated Tutorial like the one 2 years ago - to be discussed on March 22
  • WoT Japanese CG updates?
    • report from the collaborative discussion event with ECHONET on Mar-11
      • Official announcement on the CG repo
      • draft minutes
  • Chairs survey about TPAC 2022
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • PLH's message on the Chairs list (Member-only) - response expected by 28 March
      • similar questionnaire for the group participants is also available - response expected by 23 March
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y
    • Kaz has reminded the reviewers for security and privacy directly again.
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • should consider a common model for IoT security as well as data model and protocol
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases and Requirements was published as an updated Note on Mar-7
  • WoT Thing Description was also published as an updated WD on Mar-11
    • TD Ver 1.1 namespace, https://www.w3.org/2022/wot/td/v1.1, is also available
    • needed to fix the JavaScript to switch the default values within examples, e.g., Example 4
  • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
    • • Still pending, unfortunately; we are now behind schedule.
      • need a new context file too; how to allocate it?
      • would get review by TD guys but probably having a separate namespace for Discovery would be better
  • Any others?
  • continue to check the progress based on the updated plan and the schedule on the WoT main wiki - need to consider the potential delay due to the Plugfest/Testfest on March 14-18
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • PR to update draft here: https://github.com/w3c/wot-thing-description/pull/1382
      • Draft of security and privacy questionnaire done, review completed
    • Currently under TD spec; however, written so one will work for all; planning to move to Architecture
    • Probably should go ahead and create the issues for Wide Review but note that questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236 (pending; collaboration)
    • https://github.com/w3c/wot-marketing/issues/219 (propose closing)
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • WoT Community Group
    • Ege and Cristiano are the co-Chairs of the WoT CG now. - Kaz has given some instruction about CGs to them.
    • discussion on the expectation for the collaboration between the WoT-IG/WG and the WoT CG done during the WoT Chairs call today, March 16
    • To Do: work on WoT CG charter, need to define which Marketing TF activities should move to the WoT CG, and other collaboration: https://github.com/w3c/wot-marketing/issues/288
• Testing needed prior to CR transition
  • Testfest/Plugfest in progress
  • Planned outcomes:
    • Capture test data
    • Capture implementation descriptions
    • Update draft implementation reports for each deliverable
      • TD report updated post testfest
    • May need to organize another testfest
      • CR transition for Arch and TD are mid-Apr
      • PR transition is planned for mid-May
      • May have at-risk items in CR that we can resolve by PR
      • A final testfest start of May would let us fill gaps
• Liaisons
  • ITU-T SG20
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Sebastian presented the idea of UA Binding for WoT at the OPCF TCB (February 9, 2022)
    • receive positive feedback to setup a joint activity that should result into a W3C Note / OPC UA Companion document (details have to be clarified)
    • waiting for further details from OPCF TCB
  • T2TRG/IETF
    • March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • 15m WoT update scheduled
    • IoT Security discussions among other topics
    • McCool working on a Draft slides.
    • New security consideration for Discovery: https://github.com/w3c/wot-discovery/pull/286
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire draft complete
    • Now need to develop testing plan
  • Discovery
    • Normative feature freeze EXCEPT for issues related to this PR:
      • https://github.com/w3c/wot-discovery/pull/274
    • Defining Discovery process for Clients/Consumers ("Discoverers")
    • Now aiming for Feb 28 for normative feature freeze (see schedule updates)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

9 March 2022

Chair: McCool/Sebastian

Regrets: none

Scribe: Sebastian

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020 for WoT-IG (since it's RECHARTERED)
  • W3C Patent Policy 2017 for WoT-WG (since it's EXTENDED)
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Mar-2
• Quick updates
  • Daylight saving starts on 13 March 2022:
    • Next week we'll have the Plugfest/Testfest on 14-18 March, and the time will be 8-10am EDT. Due to the Daylight Saving time, the time in non-US countries will be different from this week. Please see timeanddate to see the time in your timezone.
    • see also the announcement from the MarComm Team (Member-only)
    • The calendar on the WoT page should be also updated accordingly.
  • Cancellation
    • Discovery TF call will not be cancelled on Mar-14
    • Main call on Mar-16 for just logistics confirmation
    • Testing/Plugfest delayed by one hour on Mar-16
    • All the other TF calls will be cancelled on Marh-14-18
  • Report from the discussion on I18N during the TD call on Mar-2
    • insist to use UTF-8
    • I18N review for Discovery, Architecture, etc., also to be done shortly
  • Any updates on Calendar entries in the W3C Calendar system?
    • All meetings listed under both IG and WG
    • IG: https://www.w3.org/groups/ig/wot/calendar
    • WG: https://www.w3.org/groups/wg/wot/calendar
    • Probably should add special events e.g. Plugfest - done
    • People should visit the above IG/WG calendar pages to get the ICS files and add the information to their own personal calendar. - would go through how to do that** Any updates on Calendar entries in the W3C Calendar system?
    • All meetings listed under both IG and WG
    • IG: https://www.w3.org/groups/ig/wot/calendar
    • WG: https://www.w3.org/groups/wg/wot/calendar
    • Probably should add special events e.g. Plugfest
    • Need to discuss cancellations first
    • Outlook invites are already removed.
  • Report from the Meeting with AB about Legal Entity on March 2 - see also Tzviya's message (Member-only)
    • AB meeting on March 23 at 11am EDT for WoT participants - McCool will register it to the WoT WG/IG calendars
  • Editors' sync-up call on Tuesday
    • Mar-8 call was cancelled; Mar-15 also cancelled
    • Topics:
      • Continuing terminology discussion
      • Document consistency check between Architecture and other specs (Scripting, Discovery) to be continued
      • Draft implementation reports
      • Procedure and tools on publishing specs in general - Kaz will give an updated Tutorial like the one 2 years ago - to be discussed on March 22
  • WoT Japanese CG updates?
    • collaborative discussion event with ECHONET on Mar-11
      • Official announcement on the CG repo
      • connpass site for participation
      • WoT Events page also updated with the event
  • Chairs survey about TPAC 2022
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • PLH's message on the Chairs list (Member-only) - response expected by 28 March
      • similar questionnaire for the group participants is also available - response expected by 23 March
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y
    • draft charter has been updated based on the a11y's comment - see also https://github.com/w3c/wot/pull/1014
    • Kaz has asked for security and privacy, but no response yet - directly talk with them
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • should consider a common model for IoT security as well as data model and protocol
• Conformance statements in informative documents... "Note Track"
  • Scripting is considering - wants Resolution
  • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
  • https://github.com/w3c/wot-scripting-api/issues/354
  • see also the W3C Process 2021 and the Documents published at W3C
  • Question: Do we really want to go for that direction? If so need to check with the AC Reps of the WoT participants too, and should set a deadline, e.g., end of June
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note was published on Mar-7
  • TD 1.1 updated WD is still ongoing
    • static HTML for publication available
    • Ver. 1.1 namespace to be allocated. Kaz talked with the Systeam and will allocate a necessary .htaccess for redirection from www.w3.org to w3c.github.com
    • guide for publication available
    • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
      • Still pending, unfortunately; we are now behind schedule.
      • need a new context file too; how to allocate it?
      • would get review by TD guys but probably having a separate namespace for Discovery would be better
  • Any others?
  • continue to check the progress based on the updated plan and the schedule on the WoT main wiki - need to consider the potential delay due to the Plugfest/Testfest on March 14-18
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • PR to update draft here: https://github.com/w3c/wot-thing-description/pull/1382
      • Draft of security and privacy questionnaire done, review completed
    • Currently under TD spec; however, written so one will work for all; planning to move to Architecture
    • Probably should go ahead and create the issues for Wide Review but note that questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • WoT Community Group
    • Election for Chairs concluded. Ege and Cristiano are the co-Chairs of the WoT CG now. - see also Kaz's message
    • need to clarify the relationship between the WoT-IG/WG and the WoT CG - invite Ege and/or Cristiano to the WoT Chairs call for that purpose
• Testing needed prior to CR transition
  • Done:
    • Created some of the templates for participants
  • To do:
    • Clarify what to do for each TF and company
      • McCool will submit an example for Intel
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Sebastian presented the idea of UA Binding for WoT at the OPCF TCB (February 9, 2022)
    • receive positive feedback to setup a joint activity that should result into a W3C Note / OPC UA Companion document (details have to be clarified)
    • waiting for further details from OPCF TCB
  • T2TRG/IETF
    • March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • 15m WoT update scheduled
    • IoT Security discussions among other topics
    • McCool working on a Draft slides.
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire draft complete
    • Now need to develop testing plan
  • Discovery
    • Normative feature freeze EXCEPT for issues related to this PR:
      • https://github.com/w3c/wot-discovery/pull/274
    • Defining Discovery process for Clients/Consumers ("Discoverers")
    • Now aiming for Feb 28 for normative feature freeze (see schedule updates)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

2 March 2022

Chair: McCool/Sebastian

Regrets: Sebastian

Scribe: Daniel

• Guests, New Members, and Invited Experts
  • W3C Patent Policy 2020
    • NOTE: Both the WG/CG got rechartered/extended and we're now organized by the Patent Policy 2020.
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Feb-23
• Quick updates
  • TD call will start exactly on the hour; visitor that only has 30m
  • Calendar entries now available in W3C system for all WoT meetings
    • All meetings listed under both IG and WG
    • IG: https://www.w3.org/groups/ig/wot/calendar
    • WG: https://www.w3.org/groups/wg/wot/calendar
    • Probably should add special events e.g. Plugfest
    • Need to discuss cancellations first
    • Will be deleting Outlook invites and sending out invites from W3C system soon
  • Daylight saving starts on 13 March 2022:
    • see also the announcement from the MarComm Team (Member-only)
  • Meeting with AB TODAY on March 2 - see also Tzviya's message (Member-only)
    • March 2, 21:00 UTC
    • March 2, 15:00 UTC
    • March 3, 3:00 UTC
  • Editors' sync-up call on Tuesday
    • Mar-1
    • Continuing terminology discussion
    • Document consistency check between Architecture and other specs (Scripting, Discovery) to be continued
    • Also had discussion on the draft implementation reports
    • Need to see the procedure and tools on publishing specs in general - Kaz will give an updated Tutorial like the one 2 years ago.
  • WoT Japanese CG updates?
    • updates on outreach events, etc.?
  • Conformance statements in informative documents... "Note Track"
    • Scripting is considering - wants Resolution
    • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
    • https://github.com/w3c/wot-scripting-api/issues/354
    • see also the W3C Process 2021 and the Documents published at W3C
  • Chairs survey about TPAC 2022
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • PLH's message on the Chairs list (Member-only) - response expected by 28 March
      • similar questionnaire for the group participants is also available
    • dedicated Chairs calls on 1 March (9:00 EST and 20:00 EST (=14:00 UTC and 25:00 UTC))
      • McCool and Kaz attended the meeting. - See also McCool's message (Member-only)
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y, will ping security and privacy
    • a11y is asking for small update to the draft charter - got resolution last week, have updated the draft Charter: https://github.com/w3c/wot/pull/1014
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note and TD 1.1 2nd WD to be published. - sorry for the delay but still ongoing
    • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
      • Still pending, unfortunately; we are now behind schedule.
  • Any others?
  • continue to check the progress based on the updated plan and the schedule on the WoT main wiki
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • PR to update draft here: https://github.com/w3c/wot-thing-description/pull/1382
      • Draft of security and privacy questionnaire done, needs review
    • Currently under TD spec; however, written so one will work for all; will gather feedback under PR and complete, then move to Architecture
    • Probably should go ahead and create the issues for Wide Review but note that questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • There was some confusion about the Chair selection procedure, so Kaz has just sent out a reminder with concrete instruction to the internal-wot list - Candiates of the Chairs to respond on that list
    • See also CG Chair Selection wiki
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Sebastian presented the idea of UA Binding for WoT at the OPCF TCB (February 9, 2022)
    • receive positive feedback to setup a joint activity that should result into a W3C Note / OPC UA Companion document (details have to be clarified)
    • waiting for further details from OPCF TCB
  • T2TRG/IETF
    • March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • 15m WoT update scheduled
    • IoT Security discussions among other topics
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire draft complete
    • Now need to develop testing plan
  • Discovery
    • Normative feature freeze EXCEPT for issues related to this PR:
      • https://github.com/w3c/wot-discovery/pull/274
    • Defining Discovery process for Clients/Consumers ("Discoverers")
    • Now aiming for Feb 28 for normative feature freeze (see schedule updates)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

23 February 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Zoltan/Kaz

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Feb-16
• Quick updates
  • Editors' sync-up call on Tuesday
    • Feb-22 meeting was cancelled
    • Continuing terminology discussion, e.g., "Consumer", expected during the Scripting call and the Architecture call
    • Document consistency check between Architecture and other specs (Scripting, Discovery) to be continued
  • WoT Japanese CG updates?
    • updates on outreach events, etc.?
  • Conformance statements in informative documents... "Note Track"
    • Scripting is considering - wants Resolution
    • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
    • https://github.com/w3c/wot-scripting-api/issues/354
    • see also the W3C Process 2021 and the Documents published at W3C
  • Chairs survey about TPAC 2022
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • See also PLH's message on the Chairs list (Member-only) - response expected by 28 March
      • similar questionnaire for the group participants - see member archive
    • dedicated Chairs calls on 1 March (9:00 EST and 20:00 EST (=14:00 UTC and 25:00 UTC))
• Rechartering and Charter Extensions
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y, will ping security and privacy
    • a11y is asking for small update to the draft charter - need Resolution
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note and TD 1.1 2nd WD to be published. - sorry for the delay but still ongoing
    • TD should have final PRs today (Feb 4 -> Feb 9 in schedule...)
    • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
  • Any others?
  • continue to check the progress based on the updated plan and the schedule on the WoT main wiki
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • PR to update draft here: https://github.com/w3c/wot-thing-description/pull/1382
      • Draft of security and privacy questionnaire done, needs review
    • Currently under TD spec; however, written so one will work for all; will gather feedback under PR and complete, then move to Architecture
    • Probably should go ahead and create the issues for Wide Review but note that questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • There was some confusion about the Chair selection procedure, so Kaz has just sent out a reminder with concrete instruction to the internal-wot list - Candiates of the Chairs to respond on that list
    • See also CG Chair Selection wiki
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Sebastian presented the idea of UA Binding for WoT at the OPCF TCB (February 9, 2022)
    • receive positive feedback to setup a joint activity that should result into a W3C Note / OPC UA Companion document (details have to be clarified)
    • waiting for further details from OPCF TCB
  • T2TRG/IETF
    • March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • 15m WoT update scheduled
    • IoT Security discussions among other topics
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
    • Home Assistant
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
    • Security and Privacy Questionnaire draft complete
    • Now need to develop testing plan
  • Discovery
    • Normative feature freeze EXCEPT for issues related to this PR:
      • https://github.com/w3c/wot-discovery/pull/274
    • Defining Discovery process for Clients/Consumers ("Discoverers")
    • Now aiming for Feb 28 for normative feature freeze (see schedule updates)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

16 February 2022

On deck:

• ITRF/T2TRG Review/Sync - March 10 - 15m WoT Update
• TPAC Questionnaire
• Conexxus - Retail Demo - Node-RED/Hitachi/Intel - May in Tuscon
• AB Members Restructuring and LE Update
• Wide Reviews and Tasks, incl Explainers

Chair: Sebastian/McCool

Regrets: any?

Scribe: McCool

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Feb-9
• Quick updates
  • Editors' sync-up call on Tuesday
    • Feb-15 minutes
    • Continuing terminology discussion, e.g., "Consumer", expected during the Scripting call and the Architecture call
    • Some proposals for "Virtual Thing", "Service", "Digital Twin" in progress:
      • https://github.com/w3c/wot-architecture/issues/708
      • https://github.com/w3c/wot-architecture/issues/709
    • Document consistency check between Architecture and other specs (Scripting, Discovery) to be continued
  • WoT Japanese CG updates?
    • updates on outreach events, etc.?
  • Conformance statements in informative documents... "Note Track"
    • Scripting is considering
    • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
    • https://github.com/w3c/wot-scripting-api/issues/354
  • Chairs survey about TPAC 2022
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • See also PLH's message on the Chairs list (Member-only) - response expected by 28 March
    • dedicated Chairs calls on 1 March (9:00 EST and 20:00 EST (=14:00 UTC and 25:00 UTC))
• Rechartering and Charter Extensions
  • IG Rechartering
    • New IG Charter officially available - new IG period till 31 December 2023
  • WG Charter Extension
    • current WG Charter has been extended till 31 May 2022
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews - got ok by i18n and a11y, will ping security and privacy
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • NOTE: We need to use the auto-generated "groups/wg/wot" and "groups/ig/wot" URLs instead of "WoT/WG" and "WoT/IG" directly - see also PR 1013
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note and TD 1.1 2nd WD to be published. - sorry for the delay but still ongoing
    • TD should have final PRs today (Feb 4 -> Feb 9 in schedule...)
    • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
    • PR to update schedule: https://github.com/w3c/wot/pull/1012
  • Any others?
  • continue to check the progress based on the updated plan and the schedule on the WoT main wiki
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • Currently under TD spec; considering whether have one or per-deliverable
    • Probably should go ahead and create the issues for Wide Review but note that questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • There was some confusion about the Chair selection procedure, so Kaz has just sent out a reminder with concrete instruction to the internal-wot list - Candiates of the Chairs to respond on that list
    • See also CG Chair Selection wiki
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Next step: clarification on concrete binding for smart factory use cases
  • T2TRG/IETF
    • March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • 15m WoT update scheduled
    • IoT Security discussions among other topics
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
  • Discovery
    • Normative feature freeze EXCEPT for issues related to this PR:
      • https://github.com/w3c/wot-discovery/pull/269
    • However, probably not merging the above PR, and need to solve other issues with defining Consumer process
    • Now aiming for Feb 28 for normative feature freeze (see schedule updates)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

9 February 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Ege

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Feb-2
• Quick updates
  • Editors' sync-up call on Tuesday
    • Feb-8 minutes
    • ReSpec issues caused by <dfn> tags to be checked
    • Terminology discussion, e.g., "Consumer", expected during the Scripting call and the Srchitecture call
    • Document consistency check between Architecture and other specs (Scripting, Discovery) to be continued
  • WoT Japanese CG updates?
    • updates on outreach events, etc.?
  • Conformance statements in informative documents... "Note Track"
    • Scripting is considering
    • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
    • https://github.com/w3c/wot-scripting-api/issues/354
  • Chairs survey about TPAC 2022
    • would get feedback on possible hybrid setting for TPAC 2022 on 12-16 Sep. 2022
    • See also PLH's message on the Chairs list (Member-only) - response expected by 28 March
    • dedicated Chairs calls on 1 March (9:00 EST and 20:00 EST (=14:00 UTC and 25:00 UTC))
• Rechartering and Charter Extensions
  • IG Rechartering
    • AC Review (Member-only) concluded
    • got W3M approval - Kaz to work with the Comm Team to send out an announcement
  • WG Charter Extension
    • got W3M approval for interim 4mo extension to complete the procedure (horizon review + AC review) - Kaz to work with the Comm Team to send out an announcement
      • Currently ends at end of May.
    • Draft WG Charter for 12mo extension available on GitHub
    • Strategy Issue 298 for horizontal reviews
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note and TD 1.1 2nd WD to be published. - sorry for the delay but still ongoing
    • TD should have final PRs today (Feb 4 -> Feb 9 in schedule...)
    • Discovery needs new normative content (Feb 4 -> Feb 28 in schedule...)
    • PR to update schedule: https://github.com/w3c/wot/pull/1012
  • Any others?
  • continue to check the progress based on on the updated plan and the schedule on the WoT main wiki
  • Wide review: Security TF will look at questionnaire for all deliverables
    • Draft here: https://github.com/w3c/wot-thing-description/blob/ver11-cr-security-and-privacy-quest/publication/ver11/cr/security_and_privacy.md
    • Currently under TD spec; considering whether have one or per-deliverable
    • Probably should go ahead and create the issues for Wide Review but note that questionnaires are still being developed (also true for other groups, e.g. Accessibility, Internationalization) - need to also extract MD or text format. Other groups may have done the last already, investigating.
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • Official call-for-chairs message sent out - Candiates of the Chairs to respond
    • See also CG Chair Selection wiki
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
    • ITU Webinar on "Architecting the Web of Things" done on Feb 3 at 09:00 EDT / 15:00 CET
    • McCool's slides: WoT Intro
    • Sebastian's slides: Thing Description and its Applications
    • Kaz's slides: W3C’s Standardization on WoT and Smart Cities
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Next step: clarification on concrete binding for smart factory use cases
  • T2TRG/IETF
    • March 10, 12 noon EST mtg planned
    • https://github.com/t2trg/2022-03-summary
    • 15m WoT update scheduled
    • IoT Security discussions among other topics
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
  • Discovery
    • Normative feature freeze EXCEPT for issues related to this PR:
      • https://github.com/w3c/wot-discovery/pull/269
    • However, probably not merging the above PR, and need to solve other issues with defining Consumer process
    • Now aiming for Feb 28 for normative feature freeze (see schedule updates)
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

2 February 2022

Chair: McCool/Sebastian

Regrets: none

Scribe: Lagally

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Jan-26
• Quick updates
  • Editors' sync-up call on Tuesday
    • Feb-1 minutes (Member-only)
    • Scripting issues (renaming the Use Cases section)
    • Document consistency between Architecture and other specs (Scripting, Discovery)
    • Event handling issue (proposal to have additional discussion during the Architecture call on Feb-3 in addition to the TD call on Feb-2)
    • Status updates (Discovery, Security, Terminology)
    • Further discussion to be continued during the TF calls
  • WoT Japanese CG updates?
    • brief report from the second kick-off session on Jan 28
    • updates on outreach events
  • Conformance statements in informative documents... "Note Track"
    • Scripting is considering
    • https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
    • https://github.com/w3c/wot-scripting-api/issues/354
• Rechartering and Charter Extensions
  • IG Rechartering
    • AC Review (Member-only) concluded
    • got 21 supports and 2 abstains
    • sent a request for approval to W3M (expected to be discussed today, Feb-2)
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available on GitHub
    • Kaz has created the Strategy Issue 298 to get horizontal reviews
    • Meanwhile, PLH is asking W3M for 4mo extension to complete the procedure (horizon review + AC review).
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note and TD 1.1 2nd WD to be published. - still ongoing
  • Any others?
  • continue to check the progress based on on the updated plan and the schedule on the WoT main wiki
  • Wide review: Security TF will look at questionnaire for all deliverables
• Marketing
  • WoT CG next step?
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • Official call-for-chairs message sent out - Candiates of the Chairs to respond
    • See also CG Chair Selection wiki
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
    • ITU Webinar on "Architecting the Web of Things" now set for Feb 3 at 09:00 EDT / 15:00 CET, for 2h
    • McCool's slides: WoT Intro
    • Sebastian's slides: Thing Description and its Applications
    • Kaz's slides: W3C’s Standardization on WoT and Smart Cities
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Next step: clarification on concrete binding for smart factory use cases
  • T2TRG/IETF
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• TF Reports
  • Scripting
    • wot-scripting-api issue 354 about a WG Note as a normative spec (which is not endorsed by W3C or not under the W3C Patent Policy)
  • Security
  • Discovery
    • Normative feature freeze EXCEPT for this PR, still under discussion:
      • https://github.com/w3c/wot-discovery/pull/269
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

26 January 2022

Chair: Sebastian/McCool

Regrets: any?

Scribe: Daniel

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Jan-19
• Quick updates
  • Editors' sync-up call on Tuesday
    • Jan-25 minutes (Member-only)
    • discussion on the Extension plan - to be reviewed during the main call
    • WoT main wiki also to be updated
    • Further discussion continued during the TF calls
  • WoT Japanese CG updates?
    • will hold the second kick-off session on Jan 28 - added to the Activity page
    • plans for outreach events
• Rechartering and Charter Extensions
  • IG Rechartering
    • AC Review (Member-only) concluded
    • got 21 supports and 2 abstains
    • sent an approval request to W3M
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available
    • Kaz got clarification from PLH that we actually need horizontal reviews for this proposed Charter, and will work on that.
    • Meanwhile, PLH will ask W3M for 4mo extension for the procedure.
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases updated Note and TD 1.1 2nd WD to be published. - ongoing
  • Any others?
  • continue to check the progress based on on the updated plan and the schedule on the WoT main wiki
• Marketing
  • WoT CG
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • Call for nominations for CG chairs: so far, Ege, Cristiano, and Lagally
    • To finalize, discussion needs to move to CG meeting/mailing list; and be decided by CG members; Dave has sent out an message
  • Wiki page improvements
    • Description on each TF added: https://github.com/w3c/wot-marketing/issues/231 to be closed
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
    • ITU Webinar on "Architecting the Web of Things" now set for Feb 3 at 09:00 EDT / 15:00 CET, for 2h
    • got confirmation that the speakers/talks W3C WoT (15m-20m for each; McCool, Kaz, Sebastian to present)
    • McCool's slides: WoT Intro
  • ECHONET
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • Next step: clarification on concrete binding for smart factory use cases
  • T2TRG/IETF
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • some discussion during the Use Cases call on Jan-25
    • Continue the discussion during the next Use Cases call
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

19 January 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Ege

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Jan-12
• Quick updates
  • Editors' sync-up call on Tuesday
    • Jan-18 minutes (Member-only)
    • need to update the publication schedule - Extension plan, WoT main wiki
    • Further discussion continued during the TF calls
    • need to find a better slot to get more participation - Doodle poll ongoing
  • New date/time for Architecture and Profile
    • Profile: 7am ET on Wednesday (one hour before the main call)
    • Architecture: 6am ET on Thursday
    • See also the updated WebConf wiki
    • c.f. WoT Chairs call at 6am ET on Wednesday
  • WoT Japanese CG updates?
    • will hold the second kick-off session on Jan 28
    • plans for outreach events
  • Smart Cities updates?
    • nothing specific
• Rechartering and Charter Extensions
  • IG Rechartering
    • AC Review (Member-only) ongoing
    • got 17 supports and need 3 more - Please ask your AC Rep to respond!
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available
    • Kaz is asking PLH about the status.
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • WoT Use Cases and Requirements to be published.
  • Call for Resolution for TD 1.1 2nd WD release - TODAY
  • Any others?
  • Need to check the progress based on the updated plan - Need to update the schedule again.
• Marketing
  • WoT CG
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • Call for nominations for CG chairs: Ege and Cristiano
    • To finalize, discussion needs to move to CG meeting/mailing list; and be decided by CG members; McCool to do
  • Wiki page improvements
    • Description on each TF: https://github.com/w3c/wot-marketing/issues/231
    • Proposed structure: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
    • ITU Webinar on "Architecting the Web of Things" now set for Feb 3 at 09:00 EDT / 15:00 CET, for 2h
    • checking with ITU-T about the possible speakers/talks W3C WoT (proposing 60m total; McCool (15m), Kaz (15m), Sebastian (30m) to present)
  • ECHONET
    • Plugfest report on ECHONET contribution has been addedto https://github.com/w3c/wot-testing/blob/main/events/2021.09.Online/RESULTS too.
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • PR for a use case based on Industry 4.0
    • see minutes of joint discussion during the vF2F on Oct 28
  • T2TRG/IETF
    • see minutes of joint discussion during the vF2F on Oct 28
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • see minutes of joint discussion during the vF2F on Oct 14
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

12 January 2022

Chair: McCool/Sebastian

Regrets: any?

Scribe: Cristiano

• Guests, New Members, and Invited Experts
  • W3C 2017 Patent Policy
  • Patent Policy FAQ - Q6
  • Membership classes and fees
• Minutes
  • Dec-22
• Quick updates
  • Editors' sync-up call on Tuesday
    • Jan-11 minutes (Member-only)
    • Discussion on Architecture
      • proposal to use 3 labels ("normative change", "editorial" and "non-normative") to categolize the PRs on REC-track document
      • proposal to use wot-architcture issue 646 to check the results of the spec alignment reviews
    • Further discussion continued during the TF calls
    • need to find a better slot to get more participation
  • When to start the new date/time for Architecture and Profile?
    • Currently: Thursday, 05:00-07:00 EST / 10:00-12:00 UTC time and date for your timezone
    • New doodle polls: Architecture call, Profile call
  • WoT Japanese CG updates?
    • will hold the second kick-off session on Jan 28
    • Also just started initial discussion on potential outreach events, e.g., for publishing industry
  • Smart Cities updates?
    • nothing specific
  • Articles mentioning WoT
    • https://www.iotforall.com/introduction-to-the-web-of-things
• Rechartering and Charter Extensions
  • IG Rechartering
    • AC Review (Member-only) ongoing
    • got 12 supports and need 8 more - Please ask your AC Rep to respond!
  • WG Charter Extension
    • Draft WG Charter for 12mo extension available
    • not discussed by W3M yet... - Kaz will check with PLH.
  • WG Rechartering AFTER the 12mo extension
    • Draft WG Charter for the next period
    • Still need to update deliverables, calendar, etc.
    • See https://github.com/w3c/wot/issues/978
    • Need to finalize and submit the new WG charter a few months before the end of the extended charter
    • For example, do we want to make the Scripting API a REC-track document again?
• Discuss decision process:
  • See https://github.com/w3c/wot/pull/1005
  • Each TF should discuss and provide input to PR
• Publications
  • Call for Resolution to publish updated WoT Use Cases and Requirements
  • Call for Resolution for TD 1.1 2nd WD release
    • some feedback was provided after the call for review 2 weeks ago
    • deep review was provided by Ben https://github.com/w3c/wot-thing-description/issues/1324
    • some PRs are derived, which deal with the findings https://github.com/w3c/wot-thing-description/pulls?q=is%3Apr+is%3Aopen+label%3A%222nd+WD%22
    • there are editorial ones and there are PRs that have assertion impact #1341, #1340, and #1339
    • do we need more time for review those PRs? Postpone resolution to tomorrow's Arch call?
  • Wide Review process
    • Needs to be started immediately for normative deliverables:
      • https://www.w3.org/2021/Process-20211102/#wide-review
      • https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review
    • Also needed for certain informative deliverables
      • Use Cases and Requirements
  • Need to check the progress based on the updated plan - Need to update the schedule again? If so, how?
• Marketing
  • WoT CG
    • https://github.com/w3c/wot-marketing/issues/236
    • WoT Community Group
    • Use for mailing list, announcements, open events (eg Open Day), update page to point to main web page...
    • Call for nominations for a second chair in addition to Ege
    • NOTE: Technically, the WoT CG is a different group from the WoT-IG/WG, so the Call-for-Nomination message should be sent to the CG mailinglist in addition to the IG/WG lists.
  • Wiki page improvements
    • Description on each TF: https://github.com/w3c/wot-marketing/issues/231
    • Proposed structure: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf
• Testing needed prior to CR transition
  • To do:
    • Create draft Implementation report for each deliverable
      • TD report updated post testfest
        • Want to update implementation descriptions in Testing/Plugfest call today
• Liaisons
  • ITU-T SG20
    • ITU Webinar on "Architecting the Web of Things" now set for Feb 3 at 09:00 EDT / 15:00 CET, for 2h
    • checking with ITU-T about the possible speakers/talks W3C WoT (proposing 60m total; McCool (15m), Kaz (15m), Sebastian (30m) to present)
  • ECHONET
    • Plugfest report on ECHONET contribution to be put under https://github.com/w3c/wot-testing/blob/main/events/2021.09.Online/RESULTS as well?
    • Next step: clarification on concrete binding for smart home use cases
  • ISO TC184/SC4
    • IEC CDD (Common Data Dictionary) - ontologies for various industries - IEC61360, IEC62656
    • need clarification on how to refer to their ontologies from TD
    • some specific examples would be useful
    • parts are also used as upper ontology for ECLASS, so we will pick up a few things if we start with ECLASS
  • ECLASS
    • need clarification on how to refer to their ontologies from TD
    • also a question about ECLASS logo on the WoT web page --> we have to ok for doing so
    • an example was given during the F2F that used ECLASS for Thing metadata, but there may be other use cases for interaction annotation; to be discussed
  • OPC UA
    • PR for a use case based on Industry 4.0
    • see minutes of joint discussion during the vF2F on Oct 28
  • T2TRG/IETF
    • see minutes of joint discussion during the vF2F on Oct 28
  • OneDM
  • SDW/OCG/OpenAR - Geospatial Data
    • see minutes of joint discussion during the vF2F on Oct 14
  • Possible
    • ASHRAE
    • Brick
    • APA - need use case PR
    • Microsoft DTDL
    • OneM2M
    • GaiaX
    • Solid CG
    • EdgeX Foundry
    • IEEE P2874 - Spatial Web Protocol, Architecture, and Governance Working Group
• TF Reports
  • Scripting
  • Security
  • Discovery
  • Marketing
  • Use Cases
  • PlugFest/Testing
  • Thing Description/Binding Templates
  • Architecture and Profiles
• AOB?

Repo Management

Renaming Master to Main

See: Renaming the "master" branches to "main" (Member-only)

• Make sure to update your forks and local copies
• BEFORE making change in local copies or fork, check in all pending edits/updates
• Do NOT rebase a fork until you make this change
• To change in forks, look under Settings/Branches and change "master" to "main"
• For local copies...
• Simple way: delete and reclone
• Alternatively, for local direct clones of the w3c repo
  • 1. git branch -m master main
    2. git fetch origin
    3. git branch -u origin/main main
• See above link for instructions

You can understand what this does better by reading the git branch docs.

Here -m "moves" the branch (renaming master to main locally, basically) and -u associates a remote "upstream" branch with a local branch, so that git pull does the right thing (for instance). Note this means that you MUST update the remote first before trying to update your local copies. If you have other remotes you don't have to do anything, just either use the new branch name explicitly (e.g. git fetch upstream; git merge upstream/main) or make sure the upstream repo has renamed master to main if you want fetch and merge corresponding branches in one step using git pull upstream. Here upstream is the name that I (McCool) use for a remote pointing at the w3c repo in MY setup. I cloned my original local copies from my own fork on github, so I have origin pointing at my own fork. I then used git remote add upstream https://github.com/w3c/wot-testing to add an additional remote called upstream pointed at the corresponding W3C repo I can use for rebasing, etc. I do PRs by pushing up changes to my own fork, then doing PRs to the W3C repos from there using the web interface. See above link for more instructions.

Past Content

• /2021
• /2020
• /2019
• /2018
• /2017
• /2016
• /2015