Meeting minutes
Previous minutes
<kaz> Mar-16
<Michael McCool walks over minutes>
McCool: please add note from Ege that assertion template is sorted
Kaz: fixed
McCool: Any objections?
--> none -> minutes approved
Testfest
McCool: Merged already some PRs
PR 262
<kaz> PR 262 - Added TDs from ECHONET
Lagally: w.r.t. PR #262. Does it pass validation?
Ege: Yes, it does
McCool: uses v1 TD context
Lagally: files could be used for PlugFest interoperability testing
McCool: Good point. Could merge it
Lagally: Where do I find official v1 JSON Schemas?
Ege: in TD repo, under "validation" directory
Lagally: Took this schema and got error reports
… run into issues with language tag
… validation is failing
Ege: Please open issue
Lagally: Error with having language tag in context
Ege: Did a quick check and do not see the behavior? Please provide sample TD that fails
<kaz> https://
Lagally: Will take another look
… maybe a problem with my validator
McCool: back to issue with context file
… I think we should merge this PR#262
… later on sort out v1 TDs
<Ege> TD ver 1.1 namespace
<Ege> official TD schema: https://
<Ege> new TD context: https://
<Ege> an online validation that uses @language tag: https://
<McCool> proposal: we will use previous TD submissions for TD1.1 (compatibility) testing if the only change needed is to update the context URL to the TD 1.1 version.
<McCool> proposal: we will use previous TD 1.0 submissions for TD1.1 (compatibility) testing if the only change needed is to update the context URL to the TD 1.1 version.
RESOLUTION: we will use previous TD 1.0 submissions for TD1.1 (compatibility) testing if the only change needed is to update the context URL to the TD 1.1 version.
McCool: Merge PR#262 now?
… need to fix conflict anyway
McCool: resolved conflicts for 262
Daniel: Can add both contexts instead of replacing v1 to v1.1
<McCool fixing @context in TDs of PR#262>
McCool: issues with some TDs, will fix them after merging PR
Ege: will take the task to clean it up
PR#264
Lagally: Fix in blue pump
… I think we can merge
<Ege> GH issue about the @context: https://
<Ege> by the way @mlagally, having type null does not mean that you are not returning any payload. It means that you are returning null. For more information, please see: https://
<mlagally> thanks Ege
<kaz> PR 264 - fixing operation parameters
McCool: I thought empty is invalid
Ege: type null means value null
… I think you just want to leave it out... having it absent
Lagally: Okay.. please do not merge it
<kaz> https://
PR#263
<kaz> (PR 263 closed without merging)
<McCool> https://
Daniel: add TD example to use both global&local uriVariables
McCool: TD passes -> merge
McCool: Can try to add global uriVariables in my examples
… need second implementation
Implementations and Descriptions
McCool: Split up implementation description
… testimonials based on organization
… I added impl.html template
… I added testimonial.html template
… need to fix and clean-up some more information
… I will clean-up Ditto and node-wot
McCool: Ege did you do node-wot PR?
Ege: Yes
McCool: I see, it seem in the wrong directory
Ege: node-wot.html provides enough information
… can leave out usage and public repo
McCool: not all implementations have public repo
… if not available, no problem
… I will move the file to the correct place
Ege: DP and CA can still comment on the node-wot content
McCool: Okay, I will leave Ege to resolve possible concerns
Ege: on Architecture level
… we provide impl description
… we provide testimonials description
McCool: re-structuring break my tool
… how far are we with the test results
Fady: Assertion tester close to be ready...
McCool: Afterwards I have to update my tool
… draft report could be ready by tomorrow
… worked on impl report, see PR#181
… run into issues.. got just one result
… fixed index file to resolve the issues
<kaz> wot-profile PR 181 - WIP: Implementation Report
<kaz> (McCool goes through the content of the PR 181)
McCool: class rfc in <p> tag caused issues
… we need to use <span>
McCool: nested rfc assertions cause issues also
… doing these changes changes the numbering
Lagally: I suggest not merging now
… would break things
McCool: I won't merge .. but we need to resolve these issues
Lagally: how many assertions?
McCool: About 50 ... but several were split .. so the number is not correct
<McCool showing profile report>
McCool: need to split MUST and MUST NOT
Kaz: draft version online?
McCool: Yes, it is checked in
<kaz> draft
<Ege> I have to leave now and cannot attend the plugfest call
McCool: BTW, I did update Intel devices and I am still working on bringing them on the VLAN
… other new devices / announcement ?
Lagally: Oracle things evolved..
… sync and async action
… no way to query action status.. at the moment
… Note: Ditto TDs failed for me validations
… relevant for Ege
Daniel: Ege left, should create issue
Lagally: Will do
<kaz> [Testfest adjourned; 5min break]
Plugfest
McCool: we should review the projects/scenarios
… should we generate issues for projects?
Kaz: would be nicer to do so
McCool: yeah
… (creates an issue as an example)
… Project (2022-03 Plugfest): TDs for Commercial Devices
… (adds description)
… Victron Energy OctoGX (solar power charger management)
… Goal Zero Yeti 1500X (Lithium battery 1.5kWh AGM battery 9kWh, solar charger, inverter, etc.)
… Shelley Door/Window 2
… Home Assistant/Weatherflow Tempest
Kaz: Doesn't Goal Zero itself have any smart management capability?
McCool: actually it does have
… this is kind of hybrid mechanism
… it's kind of wired, though
Kaz: maybe interesting to think about the possible connection with Siemens' power management cloud
McCool: yeah
… (shows the information on Victron Energy's site)
… DC distribution systems including inverters
Issue 267 - Project (2022-03 Plugfest): TDs for Commercial Devices
McCool: a lot smart home systems send the data to the cloud
… others can create similar issues about their projects
… (creates yet another project on "Retail Demo")
Issue 268 - Project (2022-03 Plugfest): Retail Demo
Validation
Lagally: working on validation
… based on the official JSON Schema
… have not checked all the TDs
… (shows "ProfileSchema.json")
… consolidated validation results here
ditto_floor-lamp-1_ConnectionStatus.td.jsonld.txt
Lagally: can be a starting point
TD-Profile validation results in general
McCool: Oracle's blue pump uses Actions?
Lagally: yes
… will bring more tomorrow
McCool: any description about this work?
Lagally: TD itself describes the device but no scenario description
Kaz: would be nice to have human-readable document
… for example, ECHONET guys mentioned they were using some script to extract key features from JSON data to generate a human-readable table
Lagally: sounds useful
McCool: yeah, good to generate that kind of mechanism
… reasonable to have a tool
Kaz: not for today, but good to start to think about that kind of tool
David: this maybe a place for better/best practices
… including security risks/mitigations
McCool: there are strong recommendation
… note that the security best practice document is out-dated
wot-thing-description PR 1402 - WIP: Additional Security and Privacy Considerations
McCool: we should have clear place to find necessary information
<McCool> https://
McCool: btw, any other projects to be discussed today?
David: no
(discussion about logistics, e.g., VLAN)
McCool: MQTT stuff may work with wifi
… my plan this time is building the system from scratch
… e.g., for RGB light, Temp sensor, and Door switch
… we used to have TD for Philips Hue
… should have TDs for Temp sensor and Door switch too
David: let me know if you need my help
… we have a group
McCool: (shows the diagram on David's email)
(a cooler including door sensor and temp gauge connected with Node-red)
McCool: please connect me to the engineers
David: there are so many complicated ways and we need a standard
Kaz: can we add the diagram in your message to the Issue 268?
David/McCool: sure :)
Kaz: tx
McCool: pictures would be helpful
… anything else?
… btw, the LED is (not three LEDs but) one LED which changes the color
… any other business?
Lagally: (mentions the user name and password for the Plugfest)
Kaz: please send the information by email to the Members list too (rather than recording on these public minutes :)
McCool: let's continue the discussion tomorrow!
[adjourned]