<scribe> scribenick: kaz
Matthias: SmartThings' report from Prague?
Koster: done: https://github.com/w3c/wot/blob/master/plugfest/2018-prague/result-smartthings.md
<mkovatsc> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#20_June_2018
<scribe> scribenick: dsr
Matthias congratulates Kaz on his award!
Kaz: I’ve been working hard to support W3C Member companies and was honoured to receive the award
<barryleiba1> Very nice! Congratulations, Kaz, and well deserved. Thanks for all your work.
<kaz> TTC Award
Matthias: any other updates?
Soumya: I chaired a session on the Web of Things during the IoT Week in Bilbao
Some colleague presentations, the session went well!
Matthias: any major comments?
Soumya: no, but a growing interest in role of WoT for interoperability
Matthias: we can discuss the comments at the upcoming F2F
Taki: we’ve received an email from the IIC testing group
scribenick: kaz
McCool: generating draft response and talking within the co-Chairs team
Lagally: what kind of topics would be beneficial for the collaboration with IIC?
scribenick: dsr
McCool: we have several things we
want to discuss with the IIC
... Some topics include security review, semantic interop and
test beds
... We want to invite the security review well in advance of
moving to REC, so perhaps September or October?
... There’s some overlap in membership between IIC and W3C, but
not the same people
Matthias: the PlugFest call follows this call. I want to go over the TDs today, perhaps Soumya can give his presentation and demo next week?
Soumya: I need 5 or 10 mins
got reports from all the participants in Prague f2f: https://github.com/w3c/wot/tree/master/plugfest/2018-prague
<kaz> registration results so far
Matthias: We need to check the
plenary and breakout plans
... provides a summary. In respect to the WoT Architecture, we
need to revisit the use cases and tie them to the
requirements
<kaz> Korea f2f agenda
Matthias: We also need to take a
further look at the message flows.
... In respect to thing descriptions, we need to discuss the TD
model, and the TD lifecycle
... Some terms relating to hardware and software
versioning
... Some questions for how we formalise thing descriptions as
JSON
... e.g. JSON schema, ABNF, etc.
... In respect to WoT Binding, we need some discussion on new
patterns and MQTT
Koster: I will update the agenda with some more details
Matthias: please add your changes by the end of this week
<mlagally> I mentioned that validiating a TD with the plugfest.thingweb tool works quite well - this also contains a JSON schema of the current TD
Matthias: For the scripting API
we have several topics to discuss, including discovery
... and semantic annotations
... I would put this under rechartering as it isn’t something
we have current work for
McCool: I have a raft of security
topics to discuss under the API banner
... Our charter requires us to have security testing plan and I
want us to discuss some ideas on how to address this
... This only needs to be informative and could be in a
separate document
Matthias: in respect to WoT testing …
McCool: I want to talk about wildcards and extensions under testing
Matthias: under liaisons, we
could talk about ECHONET and IIC
... we need to progress our discussion on rechartering
McCool: I am getting a lot of requests for use cases in respect to rechartering, and we should discuss this in the context of different verticals
Matthias: intel have recommended
we look at how WoT can help with respect to at least one
specific vertical in some detail
... Any other topics we need to add to the F2F agenda? [no]
McCool: a first cut at the PlugFest recap would be valuable
Matthias: I’ve upgraded node-wot and will merge the changes into the master at the Eclipse foundation
<mkovatsc> node-wot repo: https://github.com/eclipse/thingweb.node-wot
Matthias: I will notify the mailing list when it is all in place. I have a few small changes still to do and hope to progress them tomorrow.
Lagally: it would be good to have a hosted instance that we can play around with at the PlugFest
Koster: I am planning on something like that and possibly some simulated devices
Matthias: we can try out the
event source in node-wot
... there are many ways to use node-wot, so it is unclear what
a hosted instance should do
McCool: some simple simulations
of basic devices e.g. lights would be nice
... along with a parameterised instance generator
Matthias: it is easy to run
node-wot locally for experimenting with WoT apps
... but the documentation could be improved
... Victor is working on the thing directory with a new version
by the end of this week
... I recommend that people start sharing their thing
descriptions now to give time before the PlugFest to ask
questions and resolve problems
<mkovatsc> https://github.com/w3c/wot/blob/master/plugfest/2018-bundang/preparation-siemens.md
Matthias: this is about aligning the various specs, e.g. security vocabulary
Sebastian plans to discuss this in this Friday’s TD call
Soumya asks about how to handle collections of things
<mkovatsc> Links to sub-Things: https://w3c.github.io/wot-thing-description/#links-serialization-json
Koster: I’ve been looking about how to apply semantic descriptions to the GENIVI hierarchy for automotive
Matthias talks about the use of links to TDs for substructure
<McCool> mccool: time check...
Matthias: scripting API document is on hold as Zoltan is away until the F2F
Koster: I will update the binding doc this week
Matthias asks mjkoster to look into who wants to experiment with binding during the PlugFest
<Zakim> kaz, you wanted to point out this implies potential need for "a group of more than one thing as a thing" and to encourage editors to summarize the changes from the previous drafts
kaz: I want to point out this implies potential need for "a group of more than one thing as a thing" and to encourage editors to summarize the changes from the previous drafts
Matthias: as this is the *Web* of things we need to be able to link between things
scribenick: kaz
Kaz: yeah. how to handle combination/collection of "Things" should be of interest for advanced use cases. we should be able to do that using "links", though
scribenick: dsr
Koster: collections via links, I have some use cases for that
(end of meeting)