Meeting minutes
minutes review
<kaz> Apr-9
<kaz> Apr-10
Ege: any changes or corrections?
… minutes from April 9th and April 10th asre approved
registry
<EgeKorkan> w3c/
Ege: did everyone get the notification of teh creation of the registry repository
Kaz: we should make an official announcement to the main WG/IG before we start using it
word use "Binding Templates"
Ege: the word "template" is confusing
<EgeKorkan> https://
Ege: are there any opinions?
<kaz> Binding Issue 143 - "Protocol Binding" vs. "Binding Template"
Daniel: thinking about the wording now, the word "template" is misleading and we should get rid of the word
Ege: "binding specification" has been proposed
Kaz: I agree with Daniel. The mechanism is called binding and that would make sense
David: we had some confusion about using binding vs. profile, we could use a clearer picture of what is meant by binding
Ege: so we need to decide the exact wording
… to differentiate between the document form and document instances
<kaz> Web of Things (WoT) Modbus Binding Template
Koster: there are many documents in the registry, is there one that is the binding document
Ege: there is one human readable document we can call the binding
Ege: need a word to describe what is happening in a single form instance
David: in normal OOP, there is a duality between object and object class
… "instance" is self-explanatory
Ege: the document is an interface definition and instances are declaration
Koster: binding definition might be useful
David: binding definition and binding or binding instance
Ege: interface vs. instantiation
Ege: here are the ideas so far (list in the github issue)
… The choices are Definition, Specification, Vocabulary
… Document, or nothing
<dezell> one moment
David: do we need to choose 2 words?
Ege: we need to first name the repository entries
<dezell> #1 or #2
Ege: we need to change the word "templates" in the registry name
David: for "bindings" we are referring to the definitions, not the instances
<dezell> Agreed preference for #1
Toumura: I propose "binding description"
<kaz> Possible altrenatives for "Templaates" for Binding:
<kaz> 1. Definition
<kaz> 2. Specificaiton
<kaz> 3. nothing
<kaz> 4. Vocabulary
<kaz> 5. Document
<kaz> 6. Description
<Zakim> dezell, you wanted to talk about definition/declaration dualtiy
<kaz> Ege's summary from today's discussion on Issue 143
Ege: hopefully we can resolve this in the main call
Data mapping and manageable affordances
<kaz> TD.Next Usability and Design Work Items
Ege: we need to summarize the user stories and generate requirements
… first we can collect the related issues and user stories
… write a review document first, then generate requirements from that document
… any other opinions?
… we should have a separate document for each item
<kaz> TD.Next Feature Aiming Work Items
Ege: (creates initial content for the data mapping item)
Kaz: the link to the analysis document is broken
… In addition, we should think about existing solutions for each item like you mentioned ECHONET Lite Web API for historical data
Ege: any more suggestions?
Ege: do the same for the manageable affordances work item
Kaz: We need to be able to describe a group of things, because we got another request about that from ECHONET. think it would be useful for NGSI-LD collaboration as well.
Ege: (captured)
Ege: everyone please contribute input for the data mapping analysis document
<EgeKorkan> TD Issue 2094 - Collecting Analysis on Data Mapping
David: we should put links to the issues in the minutes
<EgeKorkan> Binding Issue 143 - "Protocol Binding" vs. "Binding Template"
Ege: any other business for today?
… adjourned, happy easter