WG WoT Scripting API WebConf/2023
Agendas from 2023
December 18, 2023
The call will not take place -> replaced by Nordic Smart Cities CG meetup
December 11, 2023
Scribe: Zoltan
- Previous minutes:
- Next Calls
- <break>, Jan 8 resume
- see also https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates
- PRs
- Issues
- Select important issues
- Timeline for Scripting API task-force
- Suggestion: organize the list of open issues
- Next Steps to align with TD and Discovery 1.1
- Work through issues
- Use-cases
- AOB
December 4, 2023
Scribe: Jan
- Previous minutes:
- Next Calls
- Dec 11, 18 (DP not available), <break>, Jan 8 resume
- see also https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates
- PRs
- Issues
- Select important issues
- Timeline for Scripting API task-force
- Suggestion: organize the list of open issues
- Next Steps to align with TD and Discovery 1.1
- Work through issues
- Use-cases
- AOB
November 27, 2023
No call
November 20, 2023
Scribe: Cristiano
- Previous minutes:
- Next Calls
- Nov 27, Dec 4, 11, 18 (DP not available), <break>, Jan 8 resume
- see also https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates
- 2-weeks slot enough?
- PRs
- Issues
- Select important issues
- Timeline for Scripting API task-force
- Next Steps to align with TD and Discovery 1.1
- Work through issues
- Use-cases
- AOB
November 13, 2023
Cancelled
November 6, 2023
Scribe: Jan
- Previous minutes:
- PRs
- 502 refactor: move WoT definitions up in a single place
- 489 Better typescript types
- 511 fix: "Intel" usage to "Intel Corp."
- 513 feat!(typescript): align TypeScript definitions with Discovery API
- 514 refactor: Update working draft with changes done for note2 publication
- 515 feat(typescript): add constructor to ConsumedThing interface
- 517 feat!: remove constructor from ConsumedThing interface
- Issues
- Select important issues
- Timeline for Scripting API task-force
- Next Steps to align with TD and Discovery 1.1
- Work through issues
- Use-cases
- AOB
October 30, 2023
- Cancelled because Daniel or Cristiano can make the call.
- We'll continue the discussion about PRs on GitHub.
October 23, 2023
Scribe: Kaz
(Just had a quick progress check due to lack of participation)
- Previous minutes:
- "After" Publication
- PRs to merge into master
- Follow-up issues with id collision due to namespace definitions (see https://github.com/w3c/wot-scripting-api/issues/506)
- Fixing Re-spec issue
- Using Bikeshed ?
- Scripting API report ( 2 Weeks from now )
- PRs
- Issues
- Select important issues
- Timeline for Scripting API task-force
- Next Steps to align with TD and Discovery 1.1
- Work through issues
- Use-cases
- AOB
October 9 and 16, 2023
Cancelled due to holidays and Kaz not being available.
October 02, 2023
Scribe: Zoltan
- Previous minutes:
- Publication check
- Scripting API report ( 2 Weeks from now )
- PRs
- AOB
September 25, 2023
Scribe: Daniel
- Previous minutes:
- Publication check
- Scripting API report
- What's next
- PRs
- AOB
September 18, 2023
Scribe: Jan
- Previous minutes:
- Publication check
- TPAC - preliminary discussion in relationship with Scripting
- Web Agents
- Web Assembly
- Solid
- Scripting API report
- What's next
- Issues: We have 65 issues open
- Discovery
September 11, 2023
Cancelled due to TPAC.
September 4, 2023
Scribe: Zoltan
- Previous minutes:
- Quick updates
- Publication process - Status check
- TPAC Planning
- WoT TPAC 2023 wiki
- TPAC 2023 official page
- TPAC slots mostly taken -> side-topic?
July 31 - August 28, 2023
Cancelled during summer vacations and resumes on September 4.
July 24, 2023
Scribe: Cristiano
Regrets: Zoltan
- Previous minutes:
- Quick updates
- Publication process - Status check
- TPAC
- Meetings in August
- Cristiano: Types of TS
- PRs
- Test feature (wait for Zoltan), https://github.com/w3c/wot-scripting-api/pull/487
- Issues
- Implementation status&feedback, https://github.com/w3c/wot-scripting-api/issues/481
- Follow up issue for respec error using WEB IDL partial namespace (relates to publication), https://github.com/w3c/wot-scripting-api/issues/480
- Improve Full Web IDL Appendix, https://github.com/w3c/wot-scripting-api/issues/479
- We should clarify the document scope in the Introduction section, https://github.com/w3c/wot-scripting-api/issues/476
- Check if the record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- [Wait/gain more experience]
- Scripting API is not normative in the next charter
- Scripting API Normative (https://github.com/w3c/wot-charter-drafts/issues/84)
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
July 10 and 17, 2023
Cancelled
July 3, 2023
Scribe: Daniel
- Previous minutes:
- Quick updates
- Publication process
- Status check
- TPAC
- Publication process
- PRs
- No open PRs
- Issues
- Implementation status&feedback, https://github.com/w3c/wot-scripting-api/issues/481
- Follow up issue for respec error using WEB IDL partial namespace (relates to publication), https://github.com/w3c/wot-scripting-api/issues/480
- Improve Full Web IDL Appendix, https://github.com/w3c/wot-scripting-api/issues/479
- We should clarify the document scope in the Introduction section, https://github.com/w3c/wot-scripting-api/issues/476
- Check if the record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- [Wait/gain more experience]
- Scripting API is not normative in the next charter
- Scripting API Normative (https://github.com/w3c/wot-charter-drafts/issues/84)
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
June 26, 2023
Cancelled
June 19, 2023
Cancelled
June 12, 2023
No call (W3C team contact not available)
June 5, 2023
Scribe: Zoltan
Regrets: Cristiano
- Previous minutes:
- Quick updates
- Publication process
- Zoom, update links
- TPAC
- PRs
- No open PRs
- Issues
- Implementation status&feedback, https://github.com/w3c/wot-scripting-api/issues/481
- Follow up issue for respec error using WEB IDL partial namespace (relates to publication), https://github.com/w3c/wot-scripting-api/issues/480
- Improve Full Web IDL Appendix, https://github.com/w3c/wot-scripting-api/issues/479
- We should clarify the document scope in the Introduction section, https://github.com/w3c/wot-scripting-api/issues/476
- Check if the record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- [Wait/gain more experience]
- Scripting API is not normative in the next charter
- Scripting API Normative (https://github.com/w3c/wot-charter-drafts/issues/84)
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
May 29, 2023
No call (Whit Monday)
May 22, 2023
Scribe: Jan
- Previous minutes:
- Quick updates
- Daniel asked us to focus on the publication process
- PRs
- 2023 note2 updates2, (https://github.com/w3c/wot-scripting-api/pull/477)
- Fix HTML issues, (https://github.com/w3c/wot-scripting-api/pull/478)
- Issues
- We should clarify the document scope in the Introduction section, https://github.com/w3c/wot-scripting-api/issues/476
- Check if the record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- [Wait/gain more experience]
- Scripting API is not normative in the next charter
- Scripting API Normative (https://github.com/w3c/wot-charter-drafts/issues/84)
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
May 15, 2023
Scribe: Luca
- Previous minutes:
- Quick updates
- Publication Schedule/Decision April 2023
- Scripting API is not normative in the next charter
- Scripting API Normative (https://github.com/w3c/wot-charter-drafts/issues/84)
- PRs
- Prepare Note2 release, https://github.com/w3c/wot-scripting-api/pull/473)
- Update README.md with versioning information, (https://github.com/w3c/wot-scripting-api/pull/462)
- Issues
- Check if the record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
April 24, 2023
Scribe: Daniel
- Previous minutes:
- Quick updates
- Publication Schedule/Decision April 2023
- Scripting API is not normative in the next charter
- Scripting API Normative (https://github.com/w3c/wot-charter-drafts/issues/84)
- PRs
- Align spec with INFRA, (https://github.com/w3c/wot-scripting-api/pull/469)
- Update README.md with versioning information, (https://github.com/w3c/wot-scripting-api/pull/462)
- Issues
- Check if the record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
April 17, 2023
Scribe: Zoltan
Regrets: Cristiano
- Previous minutes:
- Quick updates
- Publication Schedule/Decision April 2023
- Next charter review
- Current status (https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html)
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- Scripting API Normative? (https://github.com/w3c/wot-charter-drafts/issues/84)
- PRs
- Update README.md with versioning information, (https://github.com/w3c/wot-scripting-api/pull/462)
- [WiP] Align spec with INFRA, (https://github.com/w3c/wot-scripting-api/pull/469)
- Issues
- Prioritize short-term items focused on the next publication, https://github.com/w3c/wot-scripting-api/issues?q=is%3Aissue+is%3Aopen+label%3ASpec-improvement
- Update the "expand an ExposedThingInit" steps wrt security definitions, https://github.com/w3c/wot-scripting-api/issues/471
- Update listener internal slots to map<name, structure>, https://github.com/w3c/wot-scripting-api/issues/470
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Check if record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
April 10, 2023
No call (Easter Monday)
April 3, 2023
Scribe: Cristiano
- Previous minutes:
- Quick updates
- Public holidays (Easter Monday) for Monday, April 10, 2023
- Publication Schedule April 2023
- Next charter review
- Current status (https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html)
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- Scripting API Normative? (https://github.com/w3c/wot-charter-drafts/issues/84)
- PRs
- Update README.md with versioning information, (https://github.com/w3c/wot-scripting-api/pull/462)
- Fix internal slot in event handlers, (https://github.com/w3c/wot-scripting-api/pull/463)
- Issues
- Prioritize short-term items focused on the next publication, https://github.com/w3c/wot-scripting-api/issues?q=is%3Aissue+is%3Aopen+label%3ASpec-improvement
- Check pair vs tuple usages Editorial, https://github.com/w3c/wot-scripting-api/issues/466
- Check if record is better than map Editorial, https://github.com/w3c/wot-scripting-api/issues/465
- Explain the new tagging mechanism for experimental features, https://github.com/w3c/wot-scripting-api/issues/458
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
March 20/27, 2023
CANCELED
March 13, 2023
Scribe: Luca
- Previous minutes:
- Quick updates
- Daylight Saving Time (DST) change, https://lists.w3.org/Archives/Member/member-wot-wg/2023Feb/0015.html
- Publication Schedule March/April 2023
- Next charter review
- Current status (https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html)
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- Scripting API Normative? (https://github.com/w3c/wot-charter-drafts/issues/84)
- PRs
- Use biblio references for more URLs (https://github.com/w3c/wot-scripting-api/pull/464)
- add undefined where missing in prose, (https://github.com/w3c/wot-scripting-api/pull/461)
- Update README.md with versioning information, (https://github.com/w3c/wot-scripting-api/pull/462)
- Fix internal slot in event handlers, (https://github.com/w3c/wot-scripting-api/pull/463)
- Issues
- Prioritize short-term items focused on the next publication, https://github.com/w3c/wot-scripting-api/issues?q=is%3Aissue+is%3Aopen+label%3ASpec-improvement
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
March 06, 2023
Scribe: Cristiano
- Previous minutes:
- Quick updates
- Daylight Saving Time (DST) change, https://lists.w3.org/Archives/Member/member-wot-wg/2023Feb/0015.html
- Publication Schedule March/April 2023
- Next charter review
- Current status (https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html)
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- PRs
- add wot-thing-description-types as dependency for scripting api, https://github.com/w3c/wot-scripting-api/pull/460
- add undefined where missing in prose, https://github.com/w3c/wot-scripting-api/pull/461
- Update README.md with versioning information, https://github.com/w3c/wot-scripting-api/pull/462
- Fix internal slot in event handlers, https://github.com/w3c/wot-scripting-api/pull/463
- Issues
- Prioritize short-term items focused on the next publication, https://github.com/w3c/wot-scripting-api/issues?q=is%3Aissue+is%3Aopen+label%3ASpec-improvement
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
February 27, 2023
Scribe: Zoltan
- Previous minutes:
- Quick updates
- Publication Schedule within March 2023
- We are planning to polish the current version of the document focusing on Discovery API and bug fixes. Then we will start working on the next planned items: https://github.com/w3c/wot-scripting-api/issues/433
- Publication Schedule within March 2023
- Next charter review
- Current status (https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html)
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- PRs
- Prioritize short-term items focused on the next publication
- Use bib references in text instead of URLs (https://github.com/w3c/wot-scripting-api/pull/456)
- Issues
- Prioritize short-term items focused on the next publication
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- emitPropertyChange does not take low-level event apis into account https://github.com/w3c/wot-scripting-api/issues/417
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
February 20, 2023
Scribe: Daniel
- Previous minutes:
- Quick updates
- Publication Schedule within March 2023
- We are planning to polish the current version of the document focusing on Discovery API and bug fixes. Then we will start working on the next planned items: https://github.com/w3c/wot-scripting-api/issues/433
- Publication Schedule within March 2023
- Next charter review
- Current status (https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html)
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- PRs
- Prioritize short-term items focused on the next publication
- Some minor typos/alignments
- Update URLs to the last published document (https://github.com/w3c/wot-scripting-api/pull/451)
- Issues
- Prioritize short-term items focused on the next publication
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- emitPropertyChange does not take low-level event apis into account https://github.com/w3c/wot-scripting-api/issues/417
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
February 13, 2023
No meeting due to WoT charter sessions.
February 6, 2023
Scribe: Cristiano
- Previous minutes:
- Quick updates
- Publication Schedule within Jan 2023
- We are planning to polish the current version of the document focusing on Discovery API and bug fixes. Then we will start working on the next planned items: https://github.com/w3c/wot-scripting-api/issues/433
- Proposal for scripting - next charter, https://github.com/w3c/wot/pull/1043
- Cristiano offline next week
- Publication Schedule within Jan 2023
- PRs
- [STALLED-Discovery] feat: reintroduce "local" discovery method (should spawn new issues), https://github.com/w3c/wot-scripting-api/pull/381
- Issue organization
- Grouping issues by theme
- Prioritize short-term items focused on the next publication
- Issues
- Next charter discussion (https://github.com/w3c/wot-scripting-api/issues/422)
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
- emitPropertyChange does not take low-level event apis into account https://github.com/w3c/wot-scripting-api/issues/417
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
January 30, 2023
Scribe: Kaz
- Previous minutes:
- No-meeting
- However, we should review the following old minutes, shouldn't we?
- Quick updates
- Publication Schedule within Jan 2023
- We are planning to polish the current version of the document focusing on Discovery API and bug fixes. Then we will start working on the next planned items: https://github.com/w3c/wot-scripting-api/issues/433
- Proposal for scripting - next charter, https://github.com/w3c/wot/pull/1043
- Publication Schedule within Jan 2023
- PRs
- [STALLED-Discovery] feat: reintroduce "local" discovery method, https://github.com/w3c/wot-scripting-api/pull/381
- Issues
- emitPropertyChange does not take low-level event apis into account https://github.com/w3c/wot-scripting-api/issues/417
- Check the "subscribers" internal slots cited in the spec and see if it make sense to covert those into the new notation, https://github.com/w3c/wot-scripting-api/issues/448
- Check Internal slots for events https://github.com/w3c/wot-scripting-api/issues/447
- Explore other error conditions for fetching a Thing Description https://github.com/w3c/wot-scripting-api/issues/446
- Harmonize the exposing process, https://github.com/w3c/wot-scripting-api/issues/409
- observeallproperties and unobserveallproperties methods are missing, https://github.com/w3c/wot-scripting-api/issues/312
- Discovery API - Alternatives, https://github.com/w3c/wot-scripting-api/issues/364
- Definition missing for "discovery results", https://github.com/w3c/wot-scripting-api/issues/437
- Define exact steps/algorithms instead generic references to "Protocol Bindings" spec, https://github.com/w3c/wot-scripting-api/issues/430
- Consider aligning with IntersectionObserver, https://github.com/w3c/wot-scripting-api/issues/427
- Events
- Emitting no data for events, https://github.com/w3c/wot-scripting-api/issues/402
- Discovery
- The future of the conformance class WoT Discovery, https://github.com/w3c/wot-scripting-api/issues/396
- Align discovery and scripting, https://github.com/w3c/wot-scripting-api/issues/384
- Passing Credentials to Discovery Methods, https://github.com/w3c/wot-scripting-api/issues/390
- [STALLED-Discovery] Consuming composited Thing Description, https://github.com/w3c/wot-scripting-api/issues/363
- Simplify discovery methods, https://github.com/w3c/wot-scripting-api/issues/311
- Consumer cleanup behavior, https://github.com/w3c/wot-scripting-api/issues/395
- [STALLED] Use-case due diligence, https://github.com/w3c/wot-scripting-api/issues/392
- [STALLED-Charter-Update] Conformance section necessity, https://github.com/w3c/wot-scripting-api/issues/354
- Waiting for next steps, re-chartering
- New op values (queryaction and cancelaction), https://github.com/w3c/wot-scripting-api/issues/335
- Types for unreachable definitions cause unwanted comments, https://github.com/w3c/wot-scripting-api/issues/374
- Discussion about read- write-/multipleproperties, https://github.com/w3c/wot-scripting-api/issues/219
- Consider moving terminology definition to WoT Architecture, https://github.com/w3c/wot-scripting-api/issues/360
- Next charter topics, https://github.com/w3c/wot-scripting-api/issues/352
- Finding correct unsubscribe form, https://github.com/w3c/wot-scripting-api/issues/351
- Look into open validation issues, see https://github.com/w3c/wot-scripting-api/labels/validation
- Taskforce relates issues
- Should writeProperty() return a value, https://github.com/w3c/wot-scripting-api/issues/193
- Error Handling, https://github.com/w3c/wot-scripting-api/issues/200
- Support Syntactic Queries in Body, https://github.com/w3c/wot-scripting-api/issues/317
- Handling pagination, https://github.com/w3c/wot-scripting-api/issues/310
- Handle ThingDescriptions as streams, https://github.com/w3c/wot-scripting-api/issues/309
- Produce ExposedThing from a ThingModel instance, https://github.com/w3c/wot-scripting-api/issues/304
- Separate ExposedThing API, https://github.com/w3c/wot-scripting-api/issues/303
- ActionHandler returning InteractionInput always, https://github.com/w3c/wot-scripting-api/issues/302
- Chose a particular security schema for an ExposedThing, https://github.com/w3c/wot-scripting-api/issues/299
- Should title be mandatory in ExposedThingInit?, https://github.com/w3c/wot-scripting-api/issues/300
- Label "Data validation"
- Label "Discovery"
- [Wait/gain more experience]
- Scripting API versioning (https://github.com/w3c/wot-scripting-api/issues/224)
January 23, 2022
Meeting cancelled
January 16, 2022
No meeting due to WoT charter sessions.
January 9, 2022
The meeting is cancelled.
January 2, 2022
The meeting is cancelled.