19 Feb 2020


Kaz_Ashimura, Michael_Koster, Michael_McCool, Takahisa_Suzuki, Tomoaki_Mizushima, Ege_Korkan


<kaz> scribenick: mjkoster

what are the actions, what do we need to do?

<kaz> (for the Helsinki f2f meeting)

<kaz> Helsinki f2f wiki

McCool: adding action section to the wiki page
... what are the actions and sub-actions?
... created initial list of actions
... any others?
... Creating the table of implementations

Kaz: is this to add interoperability testing?

McCool: more to capture the results for reporting
... and capture additional information about interoperability
... like reporting pairs that work together in a matrix of interoperability
... producer/consumer pairs
... the implementation report will contain conformance results and interoperability results
... one problem is that assertions are not well aligned with features
... for example, does an implementaiton support actions as a feature, and what assertions are needed to test the feature

Kaz: please use a different file name for the new reporting

McCool: each plugfest should have its own documentation
... planning for the site and expenses
... expecting to prepare for up to 30 participants

Koster: are there testable assertions around interoperability

McCool: there could be conformance testing for one side of the interaction
... we could use node-wot or Node-RED as a generalized tester
... do we need a secondary interface to verify the expected results of actions, write-only properties, etc.
... does anyone disagree with the goal of improving the data capture?
... any other business, other items to add?
... is there any other planning needed? Other actions?

Ege: joined
... how do we capture the interactions part of a mashup?
... how do we capture the client part of the logic?
... how do we capture the onboarding and discovery, which thing is being controlled?

Kaz: describe the structure of the application, infrastructure and network configuration

McCool: add a link to the csv that links to descriptive documents
... have the tool generate client requests

Ege: has a tool that does this

<ege> https://github.com/tum-esi/testbench

McCool: semantic test tool to bound inputs and check results
... aob?
... adjourn

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/02/27 14:03:10 $