Meeting minutes
Guests, New Members ad IEs
McCool: no guest today
Minutes
McCool: talking with the old IE applicants
… also Koster is working on the IE policy
… (goes through the minutes)
(McCool has trouble with electricity, and Kaz starts to show the agenda/minutes for McCool.)
McCool: Ben is here to have discussion on Profile today
… minutes themselves seem ok
… the text for Profile should say "Profile moving into inactive for now until we resolve the TF leader"
Kaz: fixed
(minutes approved)
Quick items
McCool: inclusiveness of the Binding registry
… (gives summary of the discussion so far)
McCool: latest comments from Ege for Issue 393 summarizing the discussion so far above
… potential issues listed here
… given Ege is not here, just referring to the situation for today
Notices/Meetups
McCool: anything specific?
WoT CG
(none)
WoT JP CG
(none)
Smart Cities
McCool: Intel has joined the IG
… Kaz is organizing the Doodle for the IG call
Cloud-Edge
McCool: launch in progress
Liaisons
ECHONET
(none)
Conexxus
McCool: Annual conf this week
David: nothing new right now but trying to get manufacturers interested
McCool: clarification question. not changing the Things but adding metadata?
David: right
… this is how we can implement RESTful services
McCool: would have test cases first
… if we could see the gaps, would be helpful
David: that's part of the reason we're working on smart safe
McCool: maybe we can document the points :)
OPC
McCool: next meeting on Jan 28
… Sebastian is not here today
ETSI ISG CIM
McCool: liaison call on Monday, Jan 20
… talking about the resources/documents, etc.
… might be relevant to the smart cities discussion
… possible use cases around smart cities
… the call on Jan 27 will be cancelled
… the next meeting will be in 2 weeks
Kaz: getting use cases is important
McCool: need to work on concrete use cases
Schedule
McCool: no big changes
… but please review it
… several holidays on Monday
Policies
McCool: Koster, policy for IEs?
Koster: there is a PR there
PR 1224 - Create invited-expert.md
McCool: please review the PR offline
Koster: got comments from Ege
McCool: possible change from Member to IE
… to be documented also
… to be discussed next week
Koster: (goes through the draft quickly)
… for Chairs and Team Contact to identify the IEs
… a couple of thing defined here
… Requirements:
… contributions are expected
… initial presentation and then regular participation
… Process:
… need fleshing out
… decision within 2-3 weeks
McCool: definition of preliminary invitation, etc.
McCool: link to the application form to be added
… need to clarify the procedure so that the IE applicants can understand it
Koster: would be good to clarify the steps one by one
McCool: minimum requirements for participation, e.g., one hour for meeting
Koster: yeah
… probably 2-3 hours a week
McCool: yeah, that's fine
… everyone, please give your comments on the PR
Kaz: good starting point
… note that we should be kind of strict about the evaluation :)
TF Leads
Profile
McCool: several separate problems
… Luca's participation and possible new TF Lead
… if someone can volunteer, we should have a specific policy too
… also should discuss how much time to be allocated for TF leads
Ben: wanted to ask a question
… myself as a tentative TF lead, e.g., for 6 months
… publish an updated WD or a Note
… gave a proposal/question last year
David: conexxus is interested in Profile
… probably would be helpful for us
… someone probably would join the TF
McCool: several issues here
… Conexxus' participation is great
… but maybe we should look into potential use cases for Profile a bit more
… the purpose is improving the out-of-box interoperability
… if you have time commitment, please work on that
David: bunch of people potentially would work
McCool: please be careful about what you specifically want to work on
McCool: regarding your possible TF lead for 6 months
… is that feasible?
Ben: yes
… but just some concern about the WG's support, etc.
McCool: yeah
… there is still some confusion about what Profile really should be
<benfrancis> wot-profile PR 417 - A start on use cases and requirements for Profiles 2.0
Ben: I've worked on that as above
McCool: let's review that again
… there are requirements for WoT interoperability
… Profile 1.0 is a Note, so Profile 2.0 would make more sense
… actual constraints for applications of TDs
… publishing an updated version of Profile 1.0 Note and get community inputs is also useful, though
… anyway, let's ask people for review
… WoT Profile would be useful for WoT interoperability
… the question is that we don't have a consensus yet
Kaz: ok
… let's ask people to review this PR 417
… my question is when to revisit this topic
McCool: need Ben's participation
Cristiano: would like to see progress on Profile
McCool: David, you're also interested. right?
David: out-of-box interoperability is important
… would like to understand WoT Profile first
… anyway, I'd like to join the discussion
McCool: would be useful for cloud integration, etc.
David: PCI constrain is an issue
… would be good to capture those issues
McCool: any other comments?
Daniel: the idea behind WoT Profile is good
… would agree it would be good to think about better integration between Profile 2.0 and TD 2.0
Mizushima: use cases and requirements should be discussed by the UC TF
McCool: technically, that's true but getting Ben's help for Profile would be useful
… probably relevant to work on possible use cases for Profile
… Ben, is today's discussion helpful for you?
Ben: yeah
… the question is that we don't have enough use cases and requirements for WoT Profile 2.0 yet
McCool: yeah, the updated use cases document would have user story, etc.
Kaz: sorry but we're already out of time
… so let's have some more discussion with Ben offline
… and then clarify when to have the discussion during the main call again (and let everybody know about that)
McCool: yeah, let's do so
Ben: Please email Ben at Krellian.com with any further comments
[adjourned; no TD call today]