Meeting minutes
Guests and IEs
<kaz> Agenda for today
McCool: We will just quickly go through the list and see what is new
… do not think we have any guests
Kaz: No one
McCool: Oh, I see Luca is here
… he is between memberships so to speak, so we invited him as a guest for today
… and I think, Luca, you want to put yourself forward as an IE
Luca: Yes
McCool: We can do this now or later
… we have this process regarding IEs
… want to keep this consistent
… IEs are asked to do a presentation
… Luca, you have already contributed
… so we mainly want to ask to how much people can contribute
… so, Luca, if you want to present your case, we can go forward with that now
Luca: I prepared some slides, we can do that now
… (starts sharing his screen)
… so, I am me
… and I am involved in quite a bit of open source communities
… and standard bodies, e.g. IETF, AoMedia, and of course W3C
… also implementor of WoT in Rust
… deals with profiles, discovery
… works on bare metal
… had a demo
… also supports Linux, as demonstrated in SIFIS home
… main interest is helping with progressing TD 2.0
McCool: Okay, so main question is how much time you can contribute to WoT
Luca: As I told you, I had to reduce my involvement
… shrinking my involvement just to TD and Profiles
… and probably would like to double-check the status on who is going to be the TF lead
… since I am not sure whether this issue has been resolved already
McCool: Just wanted to ask how many hours you are able to contribute as this is part of our policy
Luca: Plan to at least attend TD and Profile calls
… and participate in the main call whenever it is needed
… idea is at least four hours being present and background preparations
McCool: Minimum commitment is 2 hours and you are above that
… we can make a resolution right now or make a call for resolution for two weeks from now
… technically, the chairs make the decision, so this would be a recommendation
McCool: Is it only the WG? Or also the IG?
Kaz: IG can be part of it as well, I think
McCool: So let's do both then
<McCool> proposal: The WoT WG recommends that Luca Barbato is appointed as an Invited Expert to the WoT WG and the WoT IG recommends that he be appointed also as an Invited Expert to the WoT IG.
McCool: This is the proposal, consensus-based, so if no one objects, we consider it passed
Kaz: Just to make sure, technically the chairs assign the IEs :)
McCool: That is why I put "recommends" in the proposal
… but I rather consider this a group decision
… asking the Chairs (and the Team Contact) to confirm Luca as an IE
RESOLUTION: The WoT WG recommends that Luca Barbato is appointed as an Invited Expert to the WoT WG and the WoT IG recommends that he be appointed also as an Invited Expert to the WoT IG.
No objections, resolution has passed
McCool: We will deal with moderations of the profile TF later
McCool: Technically, this is a provisional resolution, so people have two weeks to object, as a general policy
Minutes Review
<kaz> Feb-12
McCool: Reviewed these in the chairs call, fixed a couple of typos, generally they look good now
… resolved the issue regarding the inclusiveness
… made some small changes to the English, but the content stayed the same
… (goes through the rest of the minutes)
… anybody have anything they want to change in the minutes?
No objections, minutes are approved
Quick Items
Scripting API for Web Browsers
Kaz: Still some discussions regarding the Scripting API and its extension to Web Browsers, maybe Daniel and Cristiano want to give some quick update
McCool: Could be reported under the respective agenda item
Kaz: Had some discussion regarding the registry earlier, that is why I was asking
McCool: Can also do it now
<kaz> Feb-19 Scripting minutes
Daniel: Had some discussion in today's call about an issue you opened some time ago, discussed that WoT could work as a library, Scripting API could be provided a polyfill and be limited to existing Browser API (fetch, WebSockets, ...)
… that would be fine for us
McCool: Question is whether you can run everything WoT in the browser, question if you can open a socket in the browser
… need to clarify, in theory it would be possible, right?
Daniel: Currently, we only support the client
… depends on browser vendors
… not sure whether we can support servers right now
McCool: Client side only would also be fine, interesting use case in general
Kaz: At least for today, Daniel and Cristiano wanted to give a heads-up, the detailed discussion can continued during the Scripting calls.
McCool: Go to the Scripting API for further discussions then
Notices
McCool: Any new announcements?
None
Meetups
WoT CG
Ege: There is going to be a meetup after the TD call
McCool: Please put up a recording, can't make it unfortunately
McCool: Then we have the regular office hours
… any other WoT CG news?
Ege: No
WoT JP CG
No updates here
Smart Cities IG
<kaz> Feb-17 Smart Cities IG Slot 1 minutes
<kaz> Feb-18 Smart Cities IG Slot 2 minutes
Kaz: I've put the minutes of the two meetings earlier this week above
… discussed the charter topics
… group will hold the next meeting as a consolidated meeting in March
… on Monday, the 17th
… will make discussing the topics much easier, will also invite related SDOs
… will be discussed via GitHub
… The meeting time will be shifted to 6am Pacific.
… but Japan and Europe will get impacted by the US Daylight Saving Time...
<kaz> Kaz's announcement on the time change
McCool: Yeah, let's discuss that later
… maybe, what we should do here is provide a link to the W3C calendar
McCool: so there is only going to be one meeting now, time will be shifted
Kaz: Technically, Smart Cities IG is a different group from the WoT groups, so please join the Smart Cities IG also if you're interested :)
Cloud-Edge-Client Coordination CG
McCool: Hopefully there is going be a meeting soon, still in the process of launching
Liaisons
ECHONET
McCool: Anything new here?
Kaz: Nothing new here
Conexxus
David: Still struggling a bit at the moment, still discussing PCI (Payment Card Industry) regulations, can we discuss this at some point, Michael?
McCool: Should maybe discuss this in the TD call, generally, feel free to reach out for help
David: PCI refers to regulations regarding financial transactions and related security requirements
OPC Foundations
Sebastian: Making good progress, discussing security aspects, everything is welcome to join the next meeting on the 25th
McCool: Can you create a W3C calendar entry for that?
Sebastian: Good idea
Ege: The next iteration of the WoT Connectivity spec is finished, right?
Sebastian: Good point, it is a different working group lead by Erich Barnsted, is now under review, has reached version 1.1
… but it is independent of W3C, so there is no chance to get a version for review
… need to wait until it is published, is also only using the WoT standard for their use cases, no extensions
McCool: I guess, if you want to review it, you need to join the group
Sebastian: Correct, I am also active there
ETSI ISG CIM
<kaz> Feb-17 minutes
McCool: Last meeting was on Monday
… next meeting will be cancelled due to a holiday in Japan
… will turn to a bi-weekly schedule on average
… apparently, a lot of conflicts on Mondays
… generally, we discussed how the broker actually works
… discussed how to import TDs
… there seem to be some compatibility issues with the RDF they are using
… not sure how to resolve and align the two standards
… need to sit down and test it and discover the issues
… the minutes in the Wiki seem to be outdated, will update them
… (adjusts the Wiki)
… meeting is open to everyone, please join if you are interested in smart cities
… currently, there is not that much attendance, but I was there was
Kaz: Getting concrete use cases and gap analysis (between NGSI-LD and WoT) would be great, thank you for coordinating this
McCool: Currently, I am still scratching my head about how to align the two standards conceptually, e.g., with regard to @type
… but we are making progress
Cancellations
<kaz> Holidays and Events
McCool: There is a holiday in Japan, so we are going to cancel the 24th of February
… we will also cancel the main call and the TD call on the 26th, since Kaz will be unavailable
… TD call on the 27th will be held
McCool: any more cancellations?
None
Sebastian: Also, a heads up to March 3 to 7, when Sebastian is not going to be available
… not consistent across countries, so we are not going to cancel due to that in March
Schedule
McCool: Need to really think about our publication schedule
… have some things coming up in March
<kaz> WG Charter ends on 2 Oct 2025
McCool: we have to start our process in mid-March, but I don't think we are ready yet
… this is only regarding Recs, Notes are different
… we have some different choices here
… simplest choice would probably an extension
… need to think about choices
Kaz: Need to think about how long extension we would need
McCool: TD task force should come up with how much time they need and then make extension based on that
Ege: Maybe my main question is how many promises of the charter we fulfill and if we do a TD 2.0
… if we do everything in the charter then we definitely need more time
McCool: Should do a prioritization
… check whether we can hit the December deadline
Ege: That was 2024
McCool: Should come up with three dates, minimum-viable, main goals, stretch-goals
… then we can evaluate what we can make here
… already need to think about a charter extension, as we won't be able to make it within two weeks
Kaz: Agree with Michael, need to recognize what we have done so far
… e.g., restructuring, policies, etc., then we should evaluate what we can do until the end of the current charter period
… and then we can see how much we will be able to do after that and discuss with the strategy team
McCool: The other option would be another charter
Kaz: Would require an AC review
… so an extension would be easier
McCool: Maximum extension is a year
… so don't go crazy
Kaz: Default extension is six months, but maybe we could try that twice (or AC review)
… after identifying the required time, we could extend twice
… my personal impression is that one year might be needed. Anyway, let's start the analysis of the status, and I can talk with PLH based on the results.
Policies
Koster: Nothing new to review here
… hopefully in two weeks
TF Leads
Profile
McCool: The thing I want to discuss here is profiles
… Ben applied for a grant to work on Profiles, would like to make him a co-moderator
… any comment on that, Luca?
Luca: Could repeat what I said via email, strongly support this
… in the past year, Ben and I were the most active
… so having him as a co-lead would sort of natural
McCool: Would like to make a resolution next time
… please let us know via email, if there are objections
TF Reports
Use Cases
McCool: Call was cancelled today
Scripting API
Kaz: There was an update by Daniel earlier
Use Cases - revisited
McCool: We will not cancel the use case call next week
… will update the calendar
TD / Binding
Ege: Will review issues in the binding templates repository
… during the WoT conference/F2F we discussed the initial connection, need to have some kind of algorithm related to canonicalization
… will be needed for TD 2.0
McCool: Also talked to the NGSI-LD guys about this, need to keep this in mind
AOB
None
[adjourned]