Meeting minutes
agenda
<kaz> (quick check of the agenda for today)
Minutes from July 24th 24th
<kaz> July-24
Ege: any remarks?
… minutes approved
PRs from WG non-members
Ege: OK with me, any other opinions?
… we could invite them to join the WG
Kaz: we can quickly check with chairs and I can send an invitation if the Chairs are OK. In any case, they can join the WoT WG whenever they want since they're W3C Members.
TD
PR 2035 - PR template
Ege: this is a template for creating consistent PRs with the required content
… is this reasonable, too much?
Cristiano: what about PRs that don't fall into either category?
Ege: for example, initial connection could be treated as a new feature in the template
Ege: no objections, merged
Tool chain sub TF
<kaz> [ Sub TF new slot: Tuesday 14:30 CEST (8:30 EDT) ]
Ege: does anyone want to attend these calls? If so, let Ege know and he will send the invite
Ege: we have found some limitations in the toolchain work, issues with LinkML that need to go through a resolution process
… in the meantime, we need to add a post processing step
Ege: Another issue is what format to use when generating text, markdown or direct HTML
Ege: any other discussion on these points?
Initial connection container
Ege: PR #1201
<kaz> wot PR 1201 - Initial Connection Figures
<kaz> Preview
Cristiano: added some changes to the connection lifecycle diagrams
… for some reason the changes are not showing up
<kaz> latest preview
Cristiano: there is a file duplication problem in the document
Ege: (makes corrections to the document for "initial-connection-Websocket-entities.png")
Ege: Still waiting for Luca's change
Luca: I will try to do it by tomorrow
Luca: also working on the CSS for diagrams
Luca: (PR #2032)
Kaz: There are 2 approaches to incorporating accessibility checking, use accessibility-ready generator or check the accessibility later using a checker
… It's a recommendation and not a requirement, but would be an improvement to incorporate
initial connection issue #1248
<kaz> wot-thing-description Issue 1248 - Reduce intrinsic protocol level redundancy
Ege: Umbrella issue to list the issues with relevant discussion points
… Put all the proposals into a HackMD document
… Organized the use cases and summarized
… Notable points, shared connection between multiple things, and a wrapper schema for protocol settings
Luca: multiple base definitions and reusable connections overlap and should have one solution
Ege: the proposal is to remove base and add other features
Luca: sometimes there is an implicit base derived from the context (source) of the TD
<kaz> Issue 977 - Introducing assumptions about TD instances that have no IP addresses
Ege: issue #977 discusses this
… any thing missing from the summary?
Luca: more discussion on what to do with base
Cristiano: great summary, thanks. The requirement for all forms to have href may also need to change
<EgeKorkan> w3c/
Ege: See issue #1070
Ege: Here is the design proposal
<EgeKorkan> https://
Ege: adding a "bases" object
… added URL templating
Ege: reusing the forms keyword
… connections object
… this is the concrete proposal for people to review and build on
Daniel: there is a simple case of bases when there is only one base
… it could create a default dependsOn
Cristiano: agree, keep the common use case easy
… we should consider relaxing the backward compatibility
… Like the connection design but we could improve the vocabulary
… concepts like sessions and keepalive
Luca: security schemes are also connections
… in TD2 they can be combined
… for example TLS
… also Oauth
Ege: sharing a security session across connectivity connections
… there might be a connection without a base
Kaz: we need to merge the stories
… it would make sense to create a separate .md
Ege: we are out of time, meeting adjourned
[adjourned]