Meeting minutes
TPAC
<mlagally> https://
Lagally: (goes through the TPAC wiki above)
… what should be presented about use cases there?
Lagally: we have domain-specific use cases (and horizontal ones) within the use cases document above
… there is a section about "retail" as well
… let's pick up some of the domains during TPAC vF2F
David: when to have the discussion?
Lagally: not scheduled yet
… any preference?
David: Jack and myself will be out for another event next week
Lagally: (goes through the schedule)
… next week (Oct. 5, 7) and the week of Oct 25 (26, 27, 28)
Kaz: any preferred date?
… 26?
<mlagally> 1Prefered UC slot during TPAC: 2:00 UTC on Tuesday, Oct 26th
Kaz: NHK also wanted to talk about their media use case
… so maybe we can use the whole 2 hours on that day :)
Lagally: ok
… also some update on Takenaka and WoT-JP CG
Kaz: ok
Minutes
Lagally: (goes through the minutes)
… any objections?
(none; approved)
Editorial updates
Lagally: (goes through the PRs)
PR 131
PR 131 - Cultural Spaces (Museums) use case
Lagally: the proposer wrongly deleted the template itself
… but fixed the problem
David: missing "f" for "affiliation", btw
Lagally: will fix it
… other than that, would merge this PR
… any objections?
(none; merged)
PR 147
PR 147 - Reinstate / Update use-case-template.html
Lagally: some conflicts to be fixed
… will work on that later
PR 117
Lagally: close it
(closed)
PR 148
PR 148 - updated liaison chapter
Lagally: sections for liaison orgs
Kaz: asking ECHONET about brief text on their work
Lagally: yeah, not big text but brief summary
Issues
Issue 135
Issue 135 - Improve references: Use Specref Database references where available for release 2.0
Lagally: some trouble with Specref
… (goes through the Specref entries)
… would like to continue to work on "publication-2.0" issues
Kaz: that means "next publication". right?
Lagally: yes
<mlagally> https://
Lagally: those issues marked as "publication-2.0" above
Retail use cases
Lagally: any high-level introduction?
David: as we develop based on user story
… one of our outcome should be to figure out what would be useful for people
… one of the biggest problems
… a lot of aspects might be important
… one of the things is
… controlling a device in a concrete use case
… e.g., your freezers
… how to hook up things
… interfering things
… we've done our best to justify why given device might need to be standardized
… ecosystem to accomplish some task
… controlling single freezer is not nearly that important
… the store operation, etc., related to the merchants' need
Jack: things related to spoil edge
David: how to do categorization is another question
Kaz: based on geolocation information?
Lagally: would it make sense to have discussion by a smaller group?
… including Michael McCool
… thought there was some ZIP file
David: you can share the resource here
… (shares the information on Conexxus Use Cases - first draft)
… let me see the original document
… (shows the original document)
… sales-related devices
… facilities, data and power equipment
… food preparation and food service devices
… classification field to categorize the devices
Lagally: wondering about "indoor and outdoor freezers" and "kitchen refrigerator"
Jack: a little bit of overlap and some more differences
Lagally: maybe we can pick up some key use cases
… or do we want to categorize them with some fine-grained categories?
David: (shows a use case description)
Jack: yeah, this is an actual use case
David: no outdoor refrigerator here
… let me provide one
… btw, this list of devices is more useful
Lagally: looks a good categorization
… about a gas station?
David: typically :)
Lagally: why don't you create Pullrequests based on the use cases?
David: wondering about category and class
… how to use the "Class"?
Lagally: we've not used it yet
David: can we use the "Class" field to clarify the details?
Lagally: sounds good
David: would provide a use case for the Oct 26 meeting
Lagally: 5 stories under one use case are mentioned here (within the device list)
David: maybe one-page presentation on our situation
… in 10 minutes
Lagally: during the Oct-26 meeting?
David: yes
Lagally: ok
… my question is what/how to review the proposals
David: may remove the classification of indoor/outdoor
Jack: makes sense
Kaz: think you can use the "Category" field for "Retail"
… and use the "Class" field to show actual categorization of your use cases
David: ok
… can do within a few days
Lagally: and some more discussion/review including McCool?
David: ok
Lagally: you can create Pullrequests as well
David: how about aiming 19th?
Lagally: ok
Kaz: nice
… we can start with one specific use case
… and use the "Variants" field to show possible variants
Lagally: let's continue the discussion by email
Kaz: so on 19th possible initial use case description
… and then on 26th actual use case discussion during TPAC vF2F with one pager slide
all: yes
Lagally: aob?
(none)
[adjourned]