Meeting minutes
Minutes
Luca: no concern
Luca: no problems
(both approved)
Project management
GitHub Team setting for Profile
Luca: Ben should be included in the GitHub Editor's Team for WoT Profile
Kaz: that's fine
Editors on the spec
Luca: need to update the Editors list on the spec
… should contact former Editors and ask them about their participation
Kaz: we should clarify the criteria
… we can talk about that during the main call again
… at least you should be listed as one of the Editors, though :)
Luca: right :)
Minor PRs
PR 414
Luca: this is an editorial change
… if we can get one more support, this can be merged
Mizushima: ok
Luca: please give support on the GitHub PR 414 too
… I can record that for you too
PR 412
PR 412 - Refine Motivation section
Luca: this is also editorial
Kaz: on the PR, Luca asked McCool for review
… so we should ping him too
Mizushima: "Motivation" is important for the WoT Profile spec
… we should clarify what to be described within the Profile spec first
… it's hard for me to make decision at the moment without the clarification
… e.g., what kind of features to be standardized by the spec
Ege: one quick question for Mizushima-san
… didn't get your point
Luca: there is already an Explainer document which describes what WoT Profile is like
Kaz: I think Mizushima-san's point is
… he does understand the high-level need for Profile described by the Explainer
… but still a bit concerned about the content of the Profile spec itself
Ege: ok
… I like the PR 412 itself
… the content of PR 412 is good
… on the other hand, I got a question about Profile in general
Kaz: in that case, let's merge PR 412 itself
… and then think about general questions about WoT Profile after that
Luca: yeah
… is that OK?
Ege: ok
Kaz: I think we can merge the PR 412 itself but should mention McCool is encouraged to let us know if any problems
Luca: ok
PR 414 - revisited
Luca: can be merged
Kaz: just to make sure, we should ask Ege to confirm it's OK before merging :)
Ege: looks good
Luca: btw, would like to have a standardized reference for Webhook too
General questions on WoT Profile
Mizushima: I don't think the current WoT Profile spec itself is wrong
… but we should clarify what to be described by the spec even clearer
Luca: we should make it sure everybody is on the same page
… would start with "1.3 Out-of-the-Box Interoperability"
<luca_barbato> https://
Luca: this is one way to address Mizushima-san's concern
Ege: what is the "out-of-the-box interoperability"?
Luca: nicer and high level interoperability
… low-level connection methods like Bluetooth and Wifi have that kind of mechanism
… would like to ask Mizushima-san about which part of the document, specifically, this section "1.3 Out-of-the-Box Interoperability" is vague
… can I ask you to work on that as an action item?
Mizushima: I think the section "1.3 Out-of-the-Box Interoperability" is important
… but we should clarify the objective of the WoT Profile spec as a whole
… and then we should clarify the section "1.3 Out-of-the-Box Interoperability"
Luca: the section "1.1 Motivation" has been improved by Ben
… so which part should be still updated/improved how?
Mizushima: we should describe what kind of features are to be described within the Motivation section too
… list of features, e.g., HTTP, Webhooks and SSE
Luca: we provide an Editor's Note
NOTE Of the Profiles defined in this specification, only the HTTP Basic Profile is currently normative. It is planned that future versions of this specification will normatively define the HTTP SSE Profile and HTTP Webhook Profile, but in this version of the specification they are only informative.
Luca: the Editor's Note can be changed in the future
Kaz: I'm OK with the current content of "1.1 Motivation" and "1.3 Out-of-the-Box Interoperability"
… but as I've been mentioning repeatedly, the bigger question from my viewpoint is the overlaps between WoT Profile and the other WoT specs
… so would suggest we work on refactoring for WoT Profile too as we're working on refactoring for TD/Binding
Luca: good question for the next meeting's agenda
… refactoring we can do for the next version includes possible restructuring of the WoT Profile spec
… e.g., making WoT Profile much simpler
Kaz: regarding the WoT Profile structure for the current version and the possible next version, we need to continue the discussion during the main call. right?
Luca: we can continue the discussion during the main call next week
… don't want to make new comers confused with "out-of-box interoperability"
[kaz needs to move to the next call]
Luca: let's continue the discussion next time
Ege: can clarify my point too
[adjourned]