Meeting minutes
Logistics
IRC channel for the WoT Profile call will be "#wot-profile"
Kaz sent out the WebEx information to the group lists
the Architecture wiki will have the information on the Profile call as well
Agenda
minutes review
publication timeline
(including wide review)
McCool: we can talk about the wide review procedure during the main call later
Profile topics
Lagally: requirements
… to avoid any misunderstandings
… then out of the box interoperability
… deployment scenarios
… implementability and test plan
… validation
… anything to be added?
(none)
<McCool> https://
McCool: the above is the guide for the wide reviews
… the question is if we need to bump the feature freeze date
Lagally: let's start with the minutes review
McCool: ok
Minutes
Lagally: (goes through the minutes from the Architecture call on Jan 13)
Lagally: better to have "WoT Architecture" as the section title for the section 4
fixed and approved
Lagally: note the REQUIREMENTS/profile-requirements.md has been renamed to REQUIREMENTS/profile-requirements-13.1.md
Publication timeline
timeline and schedule on the main wiki
McCool: (explains the current proposed plan)
… just discussed during the Chairs call this morning
… we've missed some of the deadlines
… should be marked as "tentative"
… regarding feature freeze
… everything is bumped
… Kaz proposed we concentrate the document consistency check first, and possibly bump the test fest depending on the feature freeze timing
Lagally: what do you mean by "feature freeze"?
McCool: nothing to be changed
… we can start the process for the wide review in parallel
Lagally: we do wide reviews and then fix the features
… 31 Jan is not the final freeze. right?
McCool: right
… one remaining topic for TD is webhooks
Kaz: let's concentrate on the WoT Profile spec for this call
… we can talk about TD later during the TD call
McCool: that's true
Lagally: we can start wide review for WoT Profile
… (put "XX January" as the expected date for the placeholder)
… note we have many blocker issues for Profile
… so it's not realistic for Profile to have the Testfest even in mid-March
… we should deliver our spec as high quality as possible
McCool: to be clear, TD 1.1 is not major version up but version up
… many of the expected features defined by the Use Cases document to be implemented by the major updated version
… on the other hand, looking at the WoT Profile by itself, what would be the reasonable schedule?
Lagally: we're holding discussion on our expectations
… let's have more discussion during the main call too
McCool: ok
… wanted to identify the dates for Profile
Kaz: if we can't tell concrete dates today, maybe we could think about how and when we identify the dates
… for example, continue the discussion on requirements, and in 2 weeks we can tell the dates
Lagally: would like to continue the discussion on our requirements
Requirements
McCool: regarding "Ambiguities", need to narrow the choices
Lagally: how to fix?
McCool: select single choice
Lagally: ok to remove "*" now?
McCool: yes
Kaz: btw, we should mention the requirements with "*" need clarifications/improvements
Lagally: (adds description for that)
bf: the term "ambiguities" is ambiguous
… the use of PUT or POST is clear
… but what "choice of properties vs actions" means?
… "observe protocols" also
Lagally: choice of actions/properties should be done in the TD
bf: with the clarification, you can remove my "*" (request for clarification)
Limit and reduce complexity
Lagally: what about Cristiano?
Cristiano: let's see the issue
wot-profile issue 156 - Profile requirements
Cristiano: you can remove my "*" from the requirements
Ege: important to define what is complex
Lagally: which requirement are you talking about?
Ege: "complexity"
Ege: need to determine what we exactly mean
<cris> +1
Cristiano: the point is fine
<Ege> +1 to cris
Ambiguities - revisited
Lagally: can you support it now?
Cristiano: ok
Ege: ok
Lagally: now, I'm saving the updated requirements as "19.1"
https://
[adjourned]