<kaz> scribenick: mjkoster
<mkovatsc> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda
Matthias: next meeting is a 1.5 hour combined plugfest+testing
McCool: meeting with IIC to discuss
liaisons, working on semantic interoperability and data
modeling
... used the new summary presentation and talked about
iot.schema.org wrt semantics
Matthias: does anyone have a relationship with IIC?
Taki: I am a member of several
task groups
... they are working on a lot of testbeds
... they all support and work with each other
... first we need to propose WoT as part of their technical
framework
Matthias: look for symbiotic opportunities to collaborate
<kaz> SmartThings report
Matthias: reminder on Prague plugfest results
Koster: submitted a results document
Matthias: it looks like a lot of overview
<mkovatsc> https://www.w3.org/2002/09/wbs/1/WoTF2F201806/
Koster: I used the Fujitsu template; maybe I need to edit again, will go fix it
Matthias: registration reminder for the
F2F, we have 22 registration
... planning logistics, lunch will be on us
... no catering for lunch, but we can go out or order in like
the Prague PF
... Reminder to register even if you are participating
remotely
... question #3 on the registration for remote participants
Kaz: it will be better to prepare for remote participation if we have registrations
McCool: please mark which sessions you are attending also, so we can structure the topics
<mkovatsc> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_30_June-5_July_2018,_Bundang,_Korea#OpenDay
Matthias: we have 5 confirmed presentations, still waiting to hear from ETRI and TTA
McCool: IG/WG members can also present id there is something of broad interest
Matthias: anyone have any ideas now?
McCool: presentation on AI services
Matthias: OK, add to the list
... other ideas or anyone know about any ideas from others?
Matthias: timeline for node-wot is end
of the week for a new version with a first pass scripting
API
... for Thing Directory, will have a serializer soon but not
sure about the ontology
... please list any dependencies
McCool: validator will have dependencies
<McCool> McCool: it's not that the validator has dependencies, it is that it needs to be updated
<McCool> ... Ege and I are working on it, hopefully have an update end of this week
<McCool> ... more detail in plugfest call
Matthias: need to add more details about the breakout and plenary sessions
Matthias: we have security and testing topics
Matthias: need to add items for
scripting and TD to discuss the new status quo
... why things are as they are and the meaning of some of the
new patterns
... if there are any issues or suggestions for changes, this is
a good venue to discuss
... task force leads please review and add topics
Matthias: still some inconsistencies in the spec, for example the ontology pattern
[TD] have added security metadata to TD
Sebastian: also discussed the new
approach merging dataschema and interaction
... will discuss more about this on Friday
... fixing some bugs in the ontology file that are affecting
the interaction class
... playground is being updated and may be ready by the end of
the week to use the new TD serialization
<inserted> [Scripting API]
Matthias: scripting API?
Zoltan: text is being updated with
security vocabulary
... PR #119 being worked on
... Zoltan and Daniel will both be out until the Plugfest
... node-wot is being updated
Matthias: new TD format and definitions will be included by the end of the week
McCool: will the implementation be in sync with TD?
Zoltan: yes, they are aligned on the TD spec
<kaz> [Binding]
<inserted> scribenick: kaz
Koster: last 2 weeks, discussion on new binding templates
... worked on design pattern for template of URI
Zoltan: going to update the
TD/Binding documents
... most of the new changes
... who are going to implement them?
... make sure it's implementable
... for the upcoming plugfest in Korea
McCool: discussion during the PF call after this call?
Koster: sound like the next
meeting
... draft copy by the end of this week
Matthias: preparation on template
... participation to fill in
Koster: yeah
... Matsukura-san has updated the template
... think that's ready though we can add items
... pretty straight forward
Lagally: people should upload TD files asap
<inserted> scribenick: mjkoster
Lagally: if there are TDs, we should upload them now and not wait until the last moment
Matthias: there is a dependency on node-wot to generate TDs, so will prioritize that work
McCool: security TF?
<kaz> [Security]
Matthias: discussed privacy
mitigations
... also adding form-based auth
... current metadata is focused on http auth methods
<kaz> [Testing]
Matthias: testing?
... we can cover at the next call
... federico, is there an update on f-interop?
Federico: looking at the
requirements for WoT testing
... there is a semantic testing tool from soumya
... working more on technical interoperability beyond basic
data interop
... discussing new use cases and discussing with Dave about
some new tools
Daniel: is there a mailing list or record of these discussions?
Federico: can include the testing mailing list in the discussion
Kaz: we should clearly identify which work is f-interop and which is W3C for communication scope
Federico: will discuss with Dave,
but f-interop development is done on an open source license so
the discussion should be available
... but the core of f-interop is not open source
McCool: can we treat f-interop as a member and participant?
Federico: let's discuss in the
next hour
... it's not quite the same as the other participants
... we can encapsulate docker images but not our own
implementations
... hoping Dave can join in the next test/plugfest
meeting
... could do a quick update now
Matthias: only 10 minutes, we should adjourn and move to the next call
McCool: should we schedule the f-interop talk at the beginning of the PF/test meeting
Matthias: aob?
... adjourn