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.
Contents
- 1 WebConf Information
- 2 Call Logistics
- 3 Schedule
- 4 Useful resources
- 5 Ongoing Items
- 6 Cancellations and Schedule Updates
- 7 Agenda
- 8 Repo Management
- 9 Past Content
WebConf Information
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.
Special Meetings to Discuss Next Charter
- Calendar: https://www.w3.org/events/meetings/504ef715-9e3b-44a7-b8a5-34eab01da99a/20230116T080000
- Dates: Jan 16-18
- Monday Jan 16: 8am-9am Eastern; logistics Link for Members, Link for IEs
- Tuesday Jan 17: 8am-9am Eastern; logistics Link for Members, Link for IEs
- Wednesday Jan 18: 8am-10am Eastern; logistics Link for Members, Link for IEs
- Thursday Jan 19: 8am-10am Eastern (tentative); logistics Link for Members, Link for IEs
- Proposals should go here: https://github.com/w3c/wot/tree/main/proposals/deliverable-proposals
- Charter template/starting point: https://github.com/w3c/wot/blob/main/charters/wot-wg-2022-draft.html
- To do: check latest template at https://github.com/w3c/charter-drafts/blob/gh-pages/charter-template.html
- Liaisons: https://github.com/w3c/wot/issues/978#issuecomment-1359830278
Preparation
- Deliverable proposals have all been merged
- Please make PRs against WG 2023 Draft Charter going forward for proposed deliverables
- Draft completed, please review before April 5 and review minutes (linked in the README at https://github.com/w3c/wot-charter-drafts)
Session 1
Day 1 - Jan 16
Length: 1h
Chair: McCool
Scribe: Ege
- Organization (15m)
- Starting Point:
- Template (5m)
- Use Cases and Requirements (30m)
- Process (15m)
- (link to Process presentation)
- Adoption policy - discussion issue
- Coverage (15m)
- Process (15m)
Day 2 - Jan 17
Length: 1h
Chair: McCool
Scribe: Kaz
- Organization (25m)
- Schedule for remainder of current charter
- Charter Extension - how long is really needed? (10m)
- Registries - what are they, do we want to use them? (25m)
- Deliverables (5m)
- Short review of PRs
Carried forward:
- Security
- Onboarding process
- Consolidation of security assertions
- Key distribution e.g. via DID
- Discovery
- Geolocation (TD/data vocab + query filters)
- Normative query language (e.g. JSON Path)
- Registry for Introductions?
- Architecture update
- TD update
- Profile update
- Scripting
Day 3 - Jan 18
Length: 2h
Chair: Sebastian
Scribe: Michael McCool (first hour), Michael Koster (second hour)
- Organization (10m)
- Generic (5m)
- Simple fixes: https://github.com/w3c/wot/pull/1058
- Policy and Workflow (40m)
- Extension (10m)
- Extend current charter 4mo or 6mo?
- Either way, we would plan to start new charter June 1 (or earlier), and proceed with planned high-priority items e.g. OPC UA liaison and TD 2.0.
- Even if do 6mo extension, should stick to the proposed schedule, which is based on 4mo
- License (5m)
- Propose using W3C Software and Document License, as in our current charter
- PR: https://github.com/w3c/wot/pull/1062
- Clarify policies (15m)
- prioritize WoT's actual industry applications working with existing IoT standards like OPC UA and ECHONET Lite Web API
- Issue (Use cases - Adoption Policy): https://github.com/w3c/wot-usecases/issues/206
- clarify the relationship between the WoT-WG and related groups/organizations, e.g., WoT IG, WoT CG, WoT-JP CG, DID WG, JSON-LD WG, OPC, ECHONET, ITU-T, Matter, ... (see below for other liaison discussions)
- prioritize WoT's actual industry applications working with existing IoT standards like OPC UA and ECHONET Lite Web API
- Example deliverable template for liaisons:
- What: Binding Templates, Vocabulary and Ontology, Conformance tests
- How: A separate joint WG?, WoT WG as a joint WG?, a TF within the WoT WG?, just part of the TD/Binding discussion?
- Who: Editors from W3C, OPC and/or ECHONET?
- Resources: Technical Requirements for OPC UA liaison
- PR: https://github.com/w3c/wot/pull/1059
- Decision Policy (10m)
- Extension (10m)
- Deliverables - continued (50m)
- Security
- Work items: https://github.com/w3c/wot/pull/1053
- Deliverables: https://github.com/w3c/wot/pull/1057
- Onboarding process
- Consolidation of security assertions
- Key distribution e.g. via DID
- Discovery
- Work items: https://github.com/w3c/wot/pull/1052
- Deliverables: https://github.com/w3c/wot/pull/1060
- Geolocation (TD/data vocab + query filters)
- Normative query language (e.g. JSON Path)
- Filters (also used for geolocation)
- Registry for Introductions?
- Architecture update
- TD update
- Profile update
- Scripting
- Bindings Templates update
- Registry?
- Security
Day 4 - Jan 19
Length: 1h
Chair: McCool
Scribe: Kaz/?
- Organization (10m)
- Agenda
- Review Current Draft
- Issues and PRs
- Next Steps
- AOB
Session 2
Day 2 - Feb 14
Length: 2h
Chair: McCool
Scribe: Kaz
- Organization (5m)
- Review of first draft
- Capture of issues that need to be addressed in first draft:
- Assignment of Owners
Day 2 - Feb 15
Length: 2h
Chair: McCool
Scribe: Sebastian/Daniel
- Organization (5m)
- note: we need to add an issue to the strategy funnel repo for this rechartering procedure - Kaz will work on that.
- Review Issues and PRs
- Discuss remaining issues and assign Owners
- Review and close old PRs and issues, e.g. in wot
Day 3 - Feb 16
Length: 2h
Chair: McCool
Scribe: Cristiano/Ege
- Organization (5m)
- Review Issues, PRs, and Status
- Things to Fix
- Remaining issues in WoT repo
- Discuss remaining issues and assign Owners
- Additional work items for Digital Twins
- Document Organization
- Next Step
- When are we done?
- Any other W3C groups or external groups to mention?
- Remaining work - how to review and finalize?
- Schedule
- Strategy funnel issue
- When are we done?
Session 3
Day 1 - Feb 21
Length: 1h
Chair: McCool
Scribe: Lagally
- Organization (5m)
- Review old wot Issues
- https://github.com/w3c/wot/labels/WG%20New%20Charter%20Plans%202023
- All closed, please review and open new issues in wot-charter-drafts
- Review Issues, PRs, and Status
- Document Organization
- Next Steps
- Are we done?
- Strategy funnel issue
Day 2 - Feb 23
Length: 1h
Chair: McCool
Scribe: Luca
- Organization (5m)
- Review Issues, PRs, and Status
- Document Organization
- Next Steps
- Are we done?
- Strategy funnel issue
Session 4
Day 1 - Feb 27
Length: 1h
Chair: McCool
Scribe: Andrea
- Organization (5m)
- Review Issues, PRs, and Status
- Details - https://github.com/w3c/wot-charter-drafts/pull/64
- Mission Statement - https://github.com/w3c/wot-charter-drafts/pull/42
- Bindings - https://github.com/w3c/wot-charter-drafts/pull/40
- Profile
- Scope - merge items from https://github.com/w3c/wot-charter-drafts/pull/55
- CG Collab - https://github.com/w3c/wot-charter-drafts/pull/41
- Other
- Next Steps
- Are we done?
- if so, create strategy funnel issue, resolution text
Day 2 - Feb 28
Length: 1h
Chair: McCool
Scribe: Kaz
- Organization (5+5m)
- Review Issues, PRs, and Status (45m)
- Next Steps (5m)
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not...
Day 3 - Mar 1
Length: 1h
Chair: McCool
Scribe: Cristiano
- Organization (5+5m)
- Daylight Savings announcement
- Review Issues, PRs, and Status (45m)
- Mission Statement
- Scope
- Architecture Status
Day 4 - Mar 2
Length: 1h
Chair: McCool
Scribe: Kaz
- Organization (5+5m)
- Review Issues, PRs, and Status (45m)
- Charter Items
- Liaisons (invite PLH)
- TD/TM
- Other issues
- Next Steps (5m)
- Update extension schedule
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not...
Session 5
Day 1 - Mar 8
Length: 45m
Chair: McCool
Scribe:
- Organization (5m)
- Review Issues, PRs, and Status (35m)
- Next Steps (5m)
- Update extension schedule
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not... mtg Mar 9 during Arch slot?
Day 2 - Mar 9
Length: 1h (-5m)
Chair: McCool
Scribe:
- Organization (5m)
- Process
- What needs to be decided?
- Making Architecture normative or informative
- What are some smaller, more manageable questions that we can answer first?
- If Architecture is not normative, what do we do instead?
- Moving assertions to other deliverables is just one option
- Where can existing *categories* of normative content be moved, in theory?
- ... but probably not details of individual assertions
- better to defer detailed discussion/refinement of individual assertions to new charter
- Making Architecture normative or informative
- How can we make this decision?
- Process, analysis, proposals, resolution, consensus or ... (gasp) vote?
- What is the deadline?
- What needs to be decided?
- Related Issues
- Should Scripting API be normative?
- Some assertions in Architecture, e.g. about the runtime, are there because the Scripting API is not normative.
- Should there be a normative Security and Privacy document?
- Some assertions about secure transport (for example) do not really belong in existing deliverables.
- Proposed new topics like onboarding also don't really fit into existing deliverables.
- What constitutes "evidence of implementability"?
- In some cases, we have assertions at risk even though the assertion is clearly implementable, i.e. support for secure updates or use of DTLS 1.3.
- Should Scripting API be normative?
- Next Steps (5m)
- Update extension schedule
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not... when do we meet again? See: Process, above
Session 6
Day 1 - Mar 13
Length: 1h (-5m)
Chair: McCool
Scribe: Luca
- Organization (5m)
- Review PRs and Issues
- Architecture
- Related:
- Should Scripting API be normative?
- Should there be a normative Security and Privacy document?
- Should Profiles be managed as a registry (in the TD spec)?
- https://github.com/w3c/wot-charter-drafts/issues/80
- Next Steps (5m)
Day 2 - Mar 15
Length: 30m (part of main call)
Chair: McCool
Scribe: Sebastian/Kaz
- Resources
- Organization (5m)
- need a resolution to send for AC review
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- need a resolution to send for AC review
- Identifying what to be resolved before the AC Review
- Mission, Motivation, Scope
- WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
- Normative delivarables
- abstract description of each expected deliverable (including why it's necessary)
- Architecture? - https://github.com/w3c/wot-charter-drafts/issues/16
- Scripting API? - https://github.com/w3c/wot-charter-drafts/issues/84
- Security and Privacy document?
- Should Profiles be managed as a registry (in the TD spec)? - https://github.com/w3c/wot-charter-drafts/issues/80
- relationship among deliverables
- abstract description of each expected deliverable (including why it's necessary)
- Coordination
- policy on how to deal with contributions and liaisons, etc.
- Relationship among WoT Groups
- Relationship with related groups and SDOs
- Mission, Motivation, Scope
- How to deal with the details?
- We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
- Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
- Next Steps (5m)
Day 3 - Mar 16
Length: 1h - 5m Chair: McCool
Scribe: Kaz
- PRs
- Issues
- Next Steps
Session 7
Day 1 - Mar 22
Length: 30m (part of main call)
Chair: McCool
Scribe: Sebastian/Kaz
- Organization (5m)
- Draft Charter
- need a resolution to send for AC review
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- Identifying what to be resolved before the AC Review
- Mission, Motivation, Scope
- WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
- Normative delivarables - abstract description of each expected deliverable (including why it's necessary)
- Architecture
- Discovery
- Thing Description (including Binding)
- Profile
- Informative Deliverables
- Use Cases and Requirements
- Security and Privacy GUidelines
- Test suite / Implementationr reports
- Best Practices
- Scripting API
- Binding sub-documents
- relationship among deliverables should be clarified (separately from the Charter discussion itself)
- Timeline
- What to be done by when?
- Coordination
- policy on how to deal with contributions and liaisons, etc.
- Relationship (1) among WoT Groups and (2) between WoT and other SDOs should be clarified (separately from the Charter discussion itself)
- Mission, Motivation, Scope
- How to deal with the details?
- We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
- Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
- Contributions - which PRs and Issues are related to which topics above?
- Next Steps - timeline for the rechartering procedure
Day 2 - Mar 23
Length: 30m (part of main call)
Chair: McCool
Scribe: Sebastian/Kaz
- Organization (5m)
- Draft Charter
- need a resolution to send for AC review
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- Identifying what to be resolved before the AC Review
- Mission, Motivation, Scope
- WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
- Normative delivarables - abstract description of each expected deliverable (including why it's necessary)
- Architecture
- Discovery
- Thing Description (including Binding)
- Profile
- Informative Deliverables
- Use Cases and Requirements
- Security and Privacy GUidelines
- Test suite / Implementationr reports
- Best Practices
- Scripting API
- Binding sub-documents
- relationship among deliverables should be clarified (separately from the Charter discussion itself)
- Timeline
- What to be done by when?
- Coordination
- policy on how to deal with contributions and liaisons, etc.
- Relationship (1) among WoT Groups and (2) between WoT and other SDOs should be clarified (separately from the Charter discussion itself)
- Mission, Motivation, Scope
- How to deal with the details?
- We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
- Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
- Contributions - which PRs and Issues are related to which topics above?
- Next Steps - timeline for the rechartering procedure
Session 8
Day 1 - Mar 27
Length: 2h (replacing Scripting and Security)
Chair: McCool
Scribe: Luca
- Organization (5m)
- Review PRs
- Review Issues
- Resolution to send for AC review
- Actual resolution will be in main call
- This will just confirm that the draft is complete
Day 2 - Mar 29
Length: 30m (part of main call)
Chair: McCool
Scribe:
- Organization (5m)
- Review PRs
- Review Issues
- Final Review
- Mission Statement
- Background and Motivation
- Scope
- Deliverables
- Timeline
- Decision Process
- Resolution to send for review
- CALL FOR RESOLUTION to send charter draft for W3M/wide review in main call on April 5
- Resolution to send for AC review will happen after the W3M/wide review is complete, probably on May 17 - technically can be finalized by June 14 (4 weeks minimum review time).
- Allows group time to react to review comments before July 1. However, if this involves resolutions we will have to allow 1 week for final review.
- Note that technically our current charter goes to the end of July, so if necessary (e.g. if there is a major objection we have to deal with) we can use this time for further charter revisions.
Upcoming Publication Moratoriums
- None currently
Events
Past
- 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
- 18 May 2022: Japanese WoT CG
- 6-10 June 2022: Testfest
- 12-16 September 2022: TPAC
Upcoming
- TBD
Useful resources
- Kaz's slides on WoT Deliverable Options
- 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
Ongoing Action Items
Publication
Wide Review
Communications
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
- Security
- Accessibility
- Internationalization
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 and Architecture
To Do
- Clean up and label issues (all repos)
Explainers
NECESSARY for wide review process. Would be good to link them together.
- Complete:
- 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
Collaborations
Status of collaborations with Other W3C Groups.
WoT CG
- GitHub Issues to discuss the next steps, labelled with 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
- Open Issues
- 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
WoT Japanese CG
- Next event: Publishing, including Metaverse, October-ish
- Last event: Smart Building Use Cases, on April 22
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
- Joint discussion with the Spatial Data on the Web WG (SDW-WG) on Jun 23 - draft minutes
- joint call during TPAC not possible, instead want online meeting
- We need to define next-charter deliverables, e.g. geolocation ontologies, discovery extensions, etc.
- Next joint meeting on July 21 during the SDW call
Accessibility IG
- To Do: Update/Add Use Cases and Requirements
Charters
WG Rechartering
- AFTER the 12mo extension
- Draft WG Charter for the next period, 2022
- To do: update draft based on latest template for 2023
- To do: 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
- Planned meetings Jan 16-18 to finalize new draft
- Monday Jan 16: 8am-9am Eastern
- Tuesday Jan 17: 8am-9am Eastern
- Wednesday Jan 18: 8am-10am Eastern
- 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
- Issue for gathering collab requirements: https://github.com/w3c/wot/issues/1016
- Joint meeting planned for July 1
- Logistics: https://www.w3.org/events/meetings/12b636a2-d435-4752-bd77-6fde10d1b74e
- Planed slides for presentation: https://github.com/w3c/wot/blob/main/liaisons/opcf/2022-07-01-OPC-UA-WOT-Pre-Meeting.pdf
- 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
- They'd like to start with collaboration with the WoT-JP CG and bring feedback/input to the WoT-WG later.
- Kaz will join their meeting on July 22 to confirm the next steps.
- They already have liaison with ISO TC184/SC4 and ECLASS.
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
OneDM
OGC/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
- resources
- 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
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
- BACNET
- Brick
- OneM2M
- GaiaX
- Solid CG
- EdgeX Foundry
- Home Assistant
- CSA/Matter (formerly Zigbee Alliance/CHIP)
- Intel is now a member, McCool reviewing draft documents
- could just review Zigbee simple liaison
Cancellations and Schedule Updates
NOTE: If a meeting is marked as "tentative" in the W3C Calendar it means it is cancelled - people editing such calls should also put "CANCELLED" in the title. We are not "cancelling" meetings in that system since it can't be undone.
- Monday
- Scripting API call cancelled on March 20
- Tuesday
- Use Case
- Next call - March 14 (8am EASTERN, 2pm CET)
- hold the meeting every Tuesday for a while
- Editors' calls only if necessary
- Marketing
- Now 30m only, starting a half-past the hour
- Chairs and team contact will generally attend only first meeting each month
- Use Case
- Wednesday
- Profile cancelled March 29
- Thursday
- Architecture cancelled March 30
Note: Please look in W3C Calendar for updated WebEx invites for Use Cases and Editor's calls. Note that if you see both a canceled meeting and an "active" meeting, it means I had to "uncancel" a meeting by creating a new entry, and the meeting will be held.
Agenda
29 March 2023
Chair: McCool
Regrets: any?
Scribe: Koster
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- Quick updates
- any?
- Planning
- Test Dev Meeting
- First meeting for TD
- Global Meeting: second hour of TD slot - 3/29 15:00 UTC
- JP Meeting: 3/28 14:00 JST - done yesteday
- Second meeting for Architecture - to be decided
- Use Arch call Mar 30 to finalize Dev review material for Arch?
- Arch call cancelled March 30, reviews to be done offline
- Dev meetings for Arch on April 12? (Second hour of TD call slot)
- Third meeting for Discovery - to be decided
- Use Discovery calls Apr 3/10 to prep Dev review material for Discovery?
- Dev meetings for Discovery on April 17? (Discovery call slot)
- First meeting for TD
- Testfest during the week of April 3
- 3 days - 1h meeting a day
- Tuesday at 10am Eastern (after use cases call)
- Wed at 9am Eastern (testing call)
- Thursday at 9am Eastern (after arch call)
- Binding Meetup
- JP Meetup by WoT-JP CG
- two more meetings with IPA DADC (Takenaka) and NHK to be organized after the Test Dev Meeting
- What about a possible Global Meetup?
- JP Meetup by WoT-JP CG
- Test Dev Meeting
- Publications progress check
- WG Charter
- Draft proposed WG Charter
- How to proceed?
- need a resolution to send for AC review
- continue Charter Meetings... see Session 6, Day 2 agenda
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- what to be described by the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool has created a draft, please review and comment on the PR, will update as appropriate
- Will just do one for all of WoT... PR is against Arch repo where other similar documents are
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
22 March 2023
Chair: Sebastian
Regrets: McCool
Scribe: Cristiano
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- Quick updates
- Use Case policy discussion
- Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Use Case Requirements - Template - Geolocation PR
- Should be discussed during the Use Cases calls.
- Use Case policy discussion
- Planning
- Testing
- Testing Developer Meeting during the week of March 27 - Doodle
- Global Meeting:
- Reuse second hour of TD slot: 3/29 15:00 UTC
- Use Architecture call too?
- JP Meeting:
- 3/30 11:00 JST
- Note: Takenaka can't make March 30th, so should consider 3/28 13:00 JST as well.
- WoT-JP guys need clarification on what all the at-risk features really mean before the JP Meeting.
- Is 1h enough for both Arch and TD? What about Discovery?
- We may need to have additional Dev meetings...
- What order do we do them in? Material for TD is mostly ready, others not.
- Proposal (McCool):
- Use Arch call Mar 23 to finalize charter
- Use Dev meetings Mar 28/29 to review TD assertions
- Use Arch call Mar 30 to finalize Dev review material for Arch
- Use Discovery calls Apr 3/10 to prep Dev review material for Discovery
- Schedule additional Dev meetings for Arch and Discovery, maybe April 5 and April 12.
- Global Meeting:
- Testfest during the week of April 3
- 3 days - 1h meeting a day
- Tuesday at 10am Eastern (after use cases call)
- Wed at 9am Eastern (testing call)
- Thursday at 9am Eastern (after arch call)
- Testing Developer Meeting during the week of March 27 - Doodle
- Binding Meetup
- JP Meetup by WoT-JP CG
- two more meetings planned with IPA DADC and NHK to be organized
- What about a possible Global Meetup?
- JP Meetup by WoT-JP CG
- Testing
- Publications progress check
- WG Charter
- Draft proposed WG Charter
- How to proceed?
- need a resolution to send for AC review
- continue Charter Meetings... see Session 6, Day 2 agenda
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- what to be described by the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool has created a draft, please review and comment on the PR, will update as appropriate
- Will just do one for all of WoT... PR is against Arch repo where other similar documents are
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
15 March 2023
Chair: McCool
Regrets: any?
Scribe: Sebastian
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes - review skipped?
- Quick updates
- Use Cases call on March 14 cancelled due to DST change confusion - When to have the next call?
- Discussion:
- Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Use Case Requirements - Template - Geolocation PR
- Discussion:
- Cancellations and TF Meeting Schedule
- Use Cases call on March 14 cancelled due to DST change confusion - When to have the next call?
- Planning
- Testing
- Testfest during the week of March 20 - Doodle
- Current candidates
- Monday, 3/20 12:00 UTC (5:00 PDT, 9:00 ADT, 13:00 CET, 21:00 JST)
- Monday, 3/20 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST)
- Monday, 3/20 14:00 UTC (7:00 PDT, 11:00 ADT, 15:00 CET, 23:00 JST)
- Wednesday, 3/22 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST)
- Thursday, 3/23 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST)
- Thursday, 3/23 14:00 UTC (7:00 PDT, 11:00 ADT, 15:00 CET, 23:00 JST)
- Current candidates
- Testing Developer Meeting during the week of March 27 - Doodle
- Global Meeting candidates:
- 3/27 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Toumura
- 3/28 12:00 UTC (5:00 PDT, 9:00 ADT, 13:00 CET, 21:00 JST) w/o Lagally
- 3/28 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Lagally
- 3/29 01:00 UTC (18:00-1d PDT, 21:00-1d ADT, 02:00 CET, 10:00 JST) w/o Lagally
- 3/29 02:00 UTC (19:00-1d PDT, 22:00-1d ADT, 03:00 CET, 11:00 JST) w/o Lagally
- 3/29 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Lagally
- 3/30 01:00 UTC (18:00-1d PDT, 21:00-1d ADT, 02:00 CET, 10:00 JST) w/o Lagally
- 3/30 02:00 UTC (19:00-1d PDT, 22:00-1d ADT, 03:00 CET, 11:00 JST) w/o Lagally
- 3/30 09:00 UTC (02:00 PDT, 05:00 ADT, 11:00 CET, 18:00 JST) w/o Koster
- 3/30 13:00 UTC (6:00 PDT, 10:00 ADT, 14:00 CET, 22:00 JST) w/o Lagally
- 3/30 14:00 UTC (7:00 PDT, 11:00 ADT, 15:00 CET, 23:00 JST) w/o Lagally
- JP Meeting candidates
- 3/28 13:00 JST
- 3/30 11:00 JST
- Global Meeting candidates:
- Testfest during the week of March 20 - Doodle
- Testing
- Binding Meetup
- JP Meetup by WoT-JP CG
- two more meetings planned with IPA DADC and NHK to be organized
- What about a possible Global Meetup?
- JP Meetup by WoT-JP CG
- Binding Meetup
- Publications progress check
- WG Charter
- Draft proposed WG Charter
- How to proceed?
- need a resolution to send for AC review
- continue Charter Meetings... see Session 6, Day 2 agenda
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- what to be described by the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
8 March 2023
Chair: McCool
Regrets: Sebastian
Scribe: Daniel
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- Quick updates
- Next Use Cases call on March 14
- Discussion:
- Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Use Case Requirements - Template - Geolocation PR
- Discussion:
- Cancellations and TF Meeting Schedule
- Next Use Cases call on March 14
- Planning
- Testing
- Developer Meeting - Doodle
- Another Testfest during the week of March 20 - Doodle
- Binding Meetup
- JP Meetup by WoT-JP CG
- held on Feb 27 with ECHONET
- two more meetings planned with IPA DADC and NHK
- What about a possible Global Meetup?
- JP Meetup by WoT-JP CG
- Testing
- Publications progress check
- WG Charter
- Draft proposed WG Charter
- Question: Should Scripting API be a REC Track spec?
- See also: Scripting minutes
- Question: Should Scripting API be a REC Track spec?
- Minutes from the Charter meetings
- Session 1
- 16 Jan 2023 - reviewed on Feb 1
- 17 Jan 2023 - reviewed on Feb 1
- 18 Jan 2023 - reviewed on Feb 1
- 19 Jan 2023 - reviewed on Feb 1
- Session 2
- Session 3
- Session 4
- Session 1
- How to proceed?
- Another meeting tomorrow on March 9, in place of Architecture?
- need a resolution to send for AC review
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- what to be described by the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
- Another meeting tomorrow on March 9, in place of Architecture?
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- Draft proposed WG Charter
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
1 March 2023
Used for charter discussion.
22 February 2023
Chair: McCool/Sebastian
Regrets: any?
Scribe: Ege
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- Quick updates
- Next Use Cases call on Feb 28?
- Note: Use Cases call will be held every Tuesday for a while.
- Discussion:
- Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Use Case Requirements - Template - Geolocation PR
- Marketing call on Feb 28 to discuss the policy on collaboration with CGs
- Cancellations and TF Meeting Schedule
- Next Use Cases call on Feb 28?
- Planning
- Testing
- Developer Meeting
- Another Testfest in March?
- Binding Meetup
- JP Meetup by WoT-JP CG on Feb 27
- What about a possible Global Meetup?
- Testing
- Publications progress check
- WG Charter
- Minutes from the Charter meetings - https://github.com/w3c/wot-charter-drafts/pull/12
- Draft proposed WG Charter
- How to proceed?
- Another meeting Feb 23, in place of Architecture - will confirm by email.
- Probably need another call - suggest using Discovery Feb 27 slot
- When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
- Aim for draft charter end of Feb 27, have resolution to send for AC review on Mar 1 in main call.
- Probably we should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked
- Probably still need to clarify what to be described by the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- Charter Organizational Issues
- Issues/PRs on the old wot repo cleaned up
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
15 February 2023
Cancelled due to the Charter Meeting.
8 February 2023
Chair: Sebastian/McCool
Regrets: any?
Scribe: Daniel
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: Luca Barbato from Luminem
- New IE request: none
- Minutes
- Quick updates
- Next Use Cases call on Feb 14? - conflict with the 2nd Charter meeting?
- Note: Use Cases call will be held every Tuesday for a while.
- Discussion: Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Marketing call on Feb 28 to discuss the policy on collaboration with CGs
- New Wiki for Profile TF
- Use Case Requirements - Template - Geolocation PR
- Debriefing from the meeting between Sebastian and PLH around OPC UA liaison (see below)
- Next Use Cases call on Feb 14? - conflict with the 2nd Charter meeting?
- Planning
- WoT Workshop in 2024?
- Normally done for "new" topics... Digital Twins? Smart Cities? Edge Computing?
- Another Testfest during current (extended) charter? March?
- Developer Meeting
- Next F2F meeting? TPAC? Special WoT meeting/Testing before/after? In Spain or elsewhere in the EU?
- WoT Workshop in 2024?
- Cancellations and TF Meeting Schedule
- Publications progress check
- Milestones calculator
- publication schedule
- Planning for the Developer Meeting on Testing?
- WG Charter
- Doodle poll for the 2nd Charter Meeting
- Draft proposed WG Charter
- Several PRs against charter draft still open
- How to proceed:
- Each TF refines PRs (moved to a new repo to make it easier to see diffs)
- WG work on current set of PRs for draft WG 2023 charter until Feb 8
- WG will propose a resolution to merge into a first draft charter
- WG will schedule a set of meetings the week of Feb 13 to restructure, with the goal of publishing the final draft representing the consensus on Feb 22
- need to clarify what is really needed for the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- Charter Organizational Issues
- Older charter discussion
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
1 February 2023
Chair: McCool/Sebastian
Regrets: any?
Scribe: Sebastian
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- Quick updates
- Next Use Cases call on Feb 7
- Note: Use Cases call will be held every Tuesday for a while.
- Discussion: Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Debriefing from the meeting between McCool and PLH?
- PLH is OK with proposed fixes to Arch 1.1 (for DTLS 1.3) and Discovery (DID and DNS-SD) without a new CR
- Would like DID to check Discovery updates
- Also OK with testimonial/implementation approach, OPC UA to be discussed further
- Next Use Cases call on Feb 7
- Cancellations and TF Meeting Schedule
- Publications - Milestones calculator
- PROGRESS CHECK: continue to check the progress
- WG Charter
- Current WG Charter has been extended till July 31
- Review the minutes from the Charter meeting?
- Next steps - how to proceed?
- Draft proposed WG Charter
- Several PRs against charter draft still open
- Another set of meetings
- Doodle poll
- Each TF refines PRs (will move to a new repo to make it easier to see diffs)
- WG work on current set of PRs for draft WG 2023 charter until Feb 8
- WG will propose a resolution to merge into a first draft charter
- WG will schedule a set of meetings the week of Feb 13 to restructure, with the goal of publishing the final draft representing the consensus on Feb 22
- need to clarify what is really needed for the Charter
- abstract description of each expected deliverable (including why it's necessary)
- relationship among deliverables
- policy on how to deal with contributions and liaisons, etc.
- Charter Organizational Issues
- Older charter discussion
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
25 January 2023
Chair: Sebastian/McCool
Regrets: any?
Scribe: Michael Koster
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- Quick updates
- Debriefing from CCNC2023 - International Workshop on IoT Interoperability and the Web of Things (IIWOT'23)
- Next Use Cases call?
- proposal to have a meeting on Jan 31
- just one-time or regular calls?
- Policy for use case collection to be decided, e.g., how to get use cases from which industry how, and how to extract requirements from those industry-based use cases
- Call Logistics and Schedule
- Cancellations and TF Meeting Schedule
- Need to move from WebEx to Zoom by June 30
- Calendar entries need to be extended - wait until extension approved, then will update
- Publications - Milestones calculator
- All the three CRs were published on Jan 19:
- WoT Architecture 1.1
- WoT Thing Description 1.1
- WoT Discovery
- However, several issues which may require a 2nd CR, e.g., https://github.com/w3c/wot-discovery/issues/449
- need to talk with PLH
- WoT Profile updated WD was also published on Jan 18
- PROGRESS CHECK: continue to check the progress
- current plan
- proposed schedule for extension
- also update the schedule on the WoT main wiki
- All the three CRs were published on Jan 19:
- WG Charter
- current Charter will be extended by 6 months so that we can finalize our specs and new WG Charter
- Kaz has sent an extension request to W3M; will be discussed by W3M today on Jan 25
- Special Charter meeting
- Next steps?
- Several PRs against charter draft still open
- Another set of meetings?
- Proposal:
- Each TF refines PRs over next two weeks
- Feb 14, Use case call slot: Meeting to merge PRs into "first draft", decide how to restructure
- Proposal:
- Clarify what is really needed for the charter?
- Charter Organizational Issues
- Older charter discussion
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- Review Liaisons - should be discussed as part of the new WG Charter topic.
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- AOB?
11 January 2023
Chair: McCool/Sebastian
Regrets: any?
Scribe: Cristiano
- Guests, New Members, and Invited Experts
- W3C Patent Policy 2020 for both the WoT-WG and the WoT-IG
- Patent Policy FAQ - Q6
- Membership classes and fees
- New Member: none
- New IE request: none
- Minutes
- CCNC2023 - International Workshop on IoT Interoperability and the Web of Things (IIWOT'23)
- McCool will remotely give a 45m keynote speech at the workshop on Jan 11. - PR 1047 for draft slides
- Videos and/or slides from commercial apps potentially useful
- CG contributions too, but need to ask for permission; ex MagentaZuhauseApp
- Quick updates
- Cancellations and updates
- Chairs and each TF Moderators should clarify the schedule around year end/new year.
- Special charter meeting Jan 16-18; see below
- Use Cases update
- Jan-10 minutes
- Next meeting: to be confirmed
- Policy for use case collection specifically for the next Charter period?
- Testfest updates
- 2022.12.Online - work area for the Testfest 2022 Dec.
- Cancellations and updates
- Publications - Milestones calculator
- All the three CR Transition Requests, Architecture, TD and Discovery, have been approved.
- Kaz is working with the Webmaster for publication - preferably before EOY
- Architecture CR Transition Request
- Note: need Resolution to close Issue 809
- TD CR Transition Request
- Discovery CR Transition Request
- However, issue with DID that needs a normative change: https://github.com/w3c/wot-discovery/issues/449
- Architecture CR Transition Request
- Kaz is working with the Webmaster for publication - preferably before EOY
- Problem: we will not be able to reach PR during the current charter
- Proposed Resolution: In order to have time to reach PR status for our deliverables, the WoT WG will request a 4-month extension to the current charter, to May 31, 2023
- This would also imply the next charter would start June 1, 2023
- Proposed Resolution: In order to have time to reach PR status for our deliverables, the WoT WG will request a 4-month extension to the current charter, to May 31, 2023
- Testimonials
- Need to start collecting these, note they are now separate from implementation descriptions
- Who/For What/Until When/How?
- Other notes
- IANA registration for Discovery has been fixed
- See: wot entries
- Working on registering DID service endpoint names
- McCool made a PR against DID repos
- BUT needs an @context for DID document
- Can update the example, but... needs a normative reference or assertion
- But since can't make normative changes in CR, we can't do this...
- Proposal: proceed with CR as resolved but will need an updated CR to address DID issue
- IANA registration for Discovery has been fixed
- Profile:
- Resolution during the main call on Nov-2
- WoT Profile ED
- Latest Draft Implementation Report
- WD candidate publication still in progress
- WD draft has been prepared
- gathered implementation experience in the Dec 12-16 Testfest/plugfest.
- Societal Impact Questionnaire
- https://w3ctag.github.io/societal-impact-questionnaire/
- McCool will create draft, can be edited by others and submitted next week
- Will just do one for all of WoT... PR against Arch repo
- PROGRESS CHECK: continue to check the progress based on the updated plan
- also update the schedule on the WoT main wiki
- Some deadlines need to be updated, for example TD
- potential delay due to the lack of implementations for at-risk features
- All the three CR Transition Requests, Architecture, TD and Discovery, have been approved.
- New WG Charter
- Special Meeting Series on Jan 16-18 to complete a finalized new WG charter
- Proposals should go into https://github.com/w3c/wot/tree/main/proposals/deliverable-proposals
- Use Case calls held Dec 20 and Jan 10 to gather requirements
- Developing summary coverage-map.md document for review in charter discussion
- We should clarify our policy for the next WG Charter period, e.g., prioritize WoT's actual applications for industries working with existing IoT standards like OPC UA and ECHONET Lite Web API.
- For that purpose, we should consider how to deal with the liaisons with OPC and ECHONET within the new WG Charter.
- See also https://github.com/w3c/wot-usecases/issues/206
- Example deliverable template:
- What: Binding Templates, Vocabulary and Ontology, Conformance tests
- How: A separate joint WG?, WoT WG as a joint WG?, a TF within the WoT WG?, just part of the TD/Binding discussion?
- Who: Editors from W3C, OPC and/or ECHONET?
- Resources: Technical Requirements for OPC UA liaison
- Special Meeting Series on Jan 16-18 to complete a finalized new WG charter
- Other topics
- Relationship between the WoT-IG/WG and the WoT CG
- Usage of the W3C WoT Twitter account - Kaz would suggest we simply split the CG work from the chartered WG/IG work including the Twitter account to avoid this kind of discussion for topic by topic.
- Relationship between the WoT-IG/WG and the WoT CG
- Review Liaisons
- OPC UA
- Now discussing next steps with OPC UA execs and W3M
- Tech requirements: https://github.com/w3c/wot/blob/main/liaisons/opcf/tech_reqs.md
- Need another DTDL meeting
- Post-TPAC due to Erich's availability
- OPC UA
- Review Collaborations
- Anything?
- Review Ongoing Action Items
- TF Reports
- 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
-
git branch -m master main
-
git fetch origin
-
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.