Meeting minutes
past minutes
<dape> Nov-22
past minutes approved
PRs
move section "Terminology and conventions" right after "Conformance"
<dape> PR 353 - refactor: move section "Terminology and conventions" right after "Conformance"
<kaz> 11. Terminology and conventions
Zoltan: nowadays we can remove a lot of duplicated references from terminology
Cristiano: agree to remove all non-WoT related terminology - just use links
Zoltan: let's use ReSpec and Bikeshed web platform cross referencing, include link to README
Issues
issue 355
<dape> Rename Use Cases section, https://
Zoltan: other web specs are using Use Case section, it is related to Scripting API use cases
Kaz: we can change the name of the section to something like "expected features"
… the Scripting editors can make a decision
Cristiano: not attached to the term Use Cases, but it's clear they mean the use cases for the Scripting API
… if other specs are using this structure, we should adhere to this
Zoltan: some specs are using use cases, some others are not
… but WoT use cases don't conflict with Scripting use cases, the latter are used to implement the former
Kaz: we could rename to "Features"
Daniel: no other WoT spec contain "Use Cases"
Cristiano: could join the editors call to discuss this
Conformance section necessity
<dape> Issue 354 - Conformance section necessity
<cris> +1 for keeping
Daniel: looks like we will keep it
Kaz: as a Note, the whole document is non-normative, including in each section a note of not being normative would be too annoying
Zoltan: WoT Scripting is optional, but in order to share code between implementations, it should be specified, so there should be normative sections.
Kaz: it is just an informative document
Zoltan: we should be able to use normative language like MAY, SHOULD, etc, otherwise we cannot have any testing
Daniel: yes, we need to be able to say what to do
Daniel: asking Kaz to check how to proceed
Daniel: time is up
adjourned