Meeting minutes
Sebastian: welcome to the main call
guests
Sebastian: no new members
minutes
<kaz> Mar-15
Sebastian: remember we are currently in day light saving mode, therefore we set all the meeting for one hour early
… next week everything will be back to normal operation
… we also postpone the testfest
… we talked also about developer meeting and the social impact questionnaire
… we use the main call time to talk about WG charter too
… there still some few PR to optimize the content of the charter
… mainly to attract new members
… found a mistake in the minutes, issue 28 was actually a PR
… finally we talked about remaining issues
… we have still to look at issue 14
… with a related proposal from Ben
… any comments?
… ok minutes approved
Quick updates
Use case policy discussion
Sebastian: is this already clarified?
Kaz: I added this point to the agenda
… I want to have that added to the use case call agenda, and have further discussion during the use case calls. We don't need to talk about this now.
Lagally: I need a generic conversation about use case details need to be present
… the conclusion is we make this a dedicated agenda item
… in a next use case call
Kaz: yes, just please start from that next time
Lagally: agreed
Testing
Dev Meeting
Sebastian: we need to make progress to our open gaps
… at least two implementations
… there is a developer meeting planned for next week
… there is a document where you can find more details
<sebastian> Dev Meeting logistics
<Ege> https://
Ege: I prepared two slide decks about the details of each assetions
<sebastian> Google Doc for Architecture
Ege: presentation is public and you can give comment
<sebastian> Google Doc for TD
Kaz: we should update goals on the logistics page. Also we should clarify when to have what based on McCool's proposal on the main wiki.
Ege: we will discuss about it in the testing call
Sebastian: meeting is planned for one hour
… do we need more time?
… next week we might focus only on TD assetions
… after TD is done we can focus on Arch
… finally discovery for the week after
… keep this suggestion in mind for the testing call
… one hour is not enough
Lagally: we would need the arch call next week, there are some points that we have to finish
Sebastian: ok let's discuss the Charter part later during the Charter agenda item.
… any other points?
… there is also a joint meeting planned with JP community group
… they need clarifications about the at-risk features before the meeting
… Ege's slides should help here
Kaz: I spoke with JP community chair, I want to stress the need for clarifications about at risk features. Especially about what they really mean.
<Mizushima> +1 kaz
Kaz: context and editor intention need to be explained.
Sebastian: would be ok to talk about it during the meeting
Kaz: that's why we should hold two dev meetings separately, one for TD first, and another for Testing (as McCool proposes here)
Sebastian: should we make resolution here?
Kaz: we can
Lagally: suggest to make a resolution here
… usually there are no many head count in the testing call
… we can make a resolution about the basic plan now, and think about the details on the logistics later during the Testing call. discuss details in the testing call
<sebastian> proposal: the developer meeting will be split in 3 seperate meetings: Use Dev meetings Mar 28/29 to review TD assertions, Use Arch call Mar 30 to finalize Dev review material for Arch, and Use Discovery calls Apr 3/10 to prep Dev review material for Discovery
Kaz: Let's say "global developer meeting" for this resolution. Probably the JP version meeting will be also split into 3 meetings but we can make a resolution for the global one now.
RESOLUTION: the global developer meeting will be split in 3 seperate meetings: Use dev meetings Mar 28/29 to review TD assertions, use Arch call Mar 30 to finalize Dev review material for Arch, and use Discovery calls Apr 3/10 to prep Dev review material for Discovery
Sebastian: Ege, please organize further details in the testing call
Ege: ok
Testfest
Sebastian: planned for 3 days
… 1h meetings
… seems there is a problem in the timing table in the agenda
Lagally: test fest week is during easter vacation break in some countries - may have limited attendance
Sebastian: there will be public holidays
… but not a big impact on our calls
Lagally: just keep in mind that people might take vacation
binding meetup
Sebastian: do we need some of our group join this meeting?
Kaz: We can organize another meetup event with the WoT CG guys, and I thought Ege was working on that.
Schedule
<kaz> Schedule
Sebastian: we have some delay in our plan
… we have not completed the charter review
… is not ready to be submitted
… there is the reason why we updated the time table
<kaz> PR 1083 - Adjust dates for new charter in schedule
Sebastian: do you think the new schedule is reasonable?
Kaz: the proposed updated schedule, is fine. We should be aware that our schedule is getting tighter and tighter. We need to follow it.
… for this reason we might need to prioritize work and use other task force calls to finish up undone items
… sacrificing only arch and profile is not fair
Sebastian: I agree
… maybe we can do some charter discussion in today's TD call
… maybe it make sense to have a look regarding the issue of binding naming
Kaz: I agree, we should be careful not to put detailed discussion in the charter itself
… also if possible we should not only arch call but TD call too. Just keep in mind that it might be too late for some geographic areas.
… we can use other calls like security call and scripting API call
Ege: in the TD call I allocated 30 min for charter discussion
Cristiano: we can use scripting too
… just keep in mind that we have to move our deadline for the pubblication of scripting API doc
Sebastian: ok not really useful for US and JP
Kaz: we can make preliminary decisions today
… and then propose it to McCool, Ben, etc.
Lagally: we can use 30 min of tomorrow's Arch call
Kaz: remember that we don't need to work out all the existing issues on Github
… we just need to decide what should be included and what not.
<sebastian> proposal: to do the charter discussion we should spend time in today's TD call (about binding topic), 20min in tomorrow's Arch call, and use the complete scripting call session
RESOLUTION: to do the charter discussion we should spend time in today's TD call (30min about binding topic), 20min in tomorrow's Arch call, and use the complete scripting call session
Sebastian: going back to the schedule is that ok to merge it?
Kaz: please be aware the procedure would be wide review as with the specification around one month, then W3M review around 2 weeks, then AC review around one month.
… at the minimum.
Charter PRs
Sebastian: please review the list and provide your feedback
<kaz> remaining issues marked as "WG New Charter Plans 2023"
Ege: the PR92 and PR93 have implications of the next profile document
… it would be nice to have Michael Lagally in the call
Lagally: I can't but we can talk about it tomorrow in the architecture call
Kaz: among those five remaining issues, protocol bindings issues have potentially to much detail
… I am ok with the current wording within the normative deliverable section and the informative deliverable section.
… this discussion should happen first before any low level detail
Sebastian: maybe we can decide to postpone the detailed discussion
Questionnaire
Sebastian: first proposal from McCool
… PR ready
<sebastian> wot-architecture PR 897 - Societal Impact Questionniare
Liaisons and collaborations
Sebastian: no news on the Liaisons
… waiting for w3c for the response to the MOCA for OPC liaison.
Ege: FYI, WoT CG update. Sick AG will present a digital twin solution using WoT
<Ege> https://
<Ege> https://
Ege: and next up we have Siemens and Microsoft
… with their use cases about WoT
Sebastian: no other updates?
(none)
[adjourned]