Status of AC review

<kaz> scribenick: domguinard

<kaz> AC review results (member-only)

kaz: so far we've got 24 supports for the AC review which means we have already cleared the threashold.

mm: additionally Intel should also support the WG, so should EVRYTHNG

(discussion on how to deal with liaison with IPSO on the WG Charter)

MK: IPSO does not produce standards
... we should leave them out of the working group charter
... could be added to the IG side.

<kaz> scribenick: kaz

kaz: would be complicated to add to the IG Charter
... but we could add it to the IG wiki

<kaz> scribenick: domguinard

MK: let's leave the WG Charter as it is. We'll reach out to the commenter to explain why we are not adding IPSO

RESOLUTION: leave charter as-is, add IPSO to liasons wiki, outreach to the commenter to explain setup

Group Processes

MK: the technical work is done on GitHub. There are suggestions to link GitHub to the mailing list
... could generate quite a bit of traffic, confuse people with all the details of GitHub

RESOLUTION: we leave the technical work on GitHub

MK: the taskforces will review the issues and communicate the outcomes on the mailing list
... if you open an issue you need to push it forward towards resolution

issue tracker is a good place to see why we reached a decision

MC: do we keep the same GitHub for the IG and the WG? I vote for keeping them all in one GitHub account

MK: good to keep them both in the same place
... once we the WG takes work from the IG we should remove the older work files from the IG repo to avoid confusion

<Zakim> jhund, you wanted to mention tagging

MK: I will look at how to sort this out using GitHub

<jhund> ACTION mkovatsc to propose tagging and folder structure for github

<trackbot> Created ACTION-78 - Propose tagging and folder structure for github [on Matthias Kovatsch - due 2016-10-12].

TD Restructuring

<inserted> TD Restructuring call minutes

SK: we are now discussing a new version of the Thing Description (TD) to be used for the next plugfest
... several issues were raised in the last TD meeting, they are tracked on GitHub
... have a look at the issues and please comment

Scripting API

<kaz> Lisbon F2F minutes

<kaz> scribenick: kaz

MK: Still need to work on Scripting

Hydra

<inserted> Hydra breakout minutes

MK: Victor wanted to work on Hydra, gathering people to work on that
... an item from the TPAC was to better understand what Hydra was bringing

Johannes: got a number of emails providing feedback on the scripting topic, need to summarize and present here

TD Lifecycle

<inserted> TD Lifecycle breakout minutes

MK: can someone report about the lifecycle breakout?

<jhund> ACTION jhund to prepare and announce kick-off for scripting

<trackbot> Created ACTION-79 - Prepare and announce kick-off for scripting [on Johannes Hund - due 2016-10-12].

SK: the lifecycle of a product was presented, there were many open questions, e.g., how to represent this with languages such as RDF or JSON-LD, no concrete outcome yet, many open issues

Servient Synchronization

<inserted> Synchronization minutes

MK: there was a breakout about sync things and proxies

Protocol Mapping

<kaz> Protocol mapping minutes|

MK: needs progress on WS and MQTT mapping

<Zakim> kaz, you wanted to mention other topics: matsukura-san for synchronization, kajimoto-san for lifecycle, joerg for f-interop

Security

MC: we need to organise the work on security

we do not have enough people who are active in the group working on security

MC: intel could help with strong security people but we need other members to also contribute
... we need a variety of people how can look at different use cases

kaz: Hashimoto San could contribute for the automotive side of things

<kaz> scribenick: kaz

kaz: can talk with Hashimoto-san from the Automotive WG and Lukasz Olejnik from the Device and Sensors WG

<kaz> scribenick: domguinard

ACTION McCool is going to push the security topic forward

<trackbot> Created ACTION-80 - Is going to push the security topic forward [on Michael McCool - due 2016-10-12].

F-Interop

kaz: we might want to have some follow up discussion with the F-Interop team

MK: we might want to invite the F-Interop team to give a talk but should probably brainstorm first

Next F2F planning

McCool: still waiting to hear more about logistics for the February F2F and Plugfest
... waiting to see if Intel and host it

OCF liaison

McCool: need to understand where we are with OCF interop

MK: one of the issues is that OCF is a closed group, we need to see how we can collaborate

WoT landing page

MK: volunteers to lead this

EVRYTHNG offered to help / lead that during the TPAC

<kaz> scribenick: kaz

kaz: we need to talk with the W3C MarComm Team as well

<kaz> scribenick: domguinard

<kaz> WoT landing page

MK: we need a logo and a visual identity, we would also need a landing page

<kaz> scribenick: kaz

MK: would like to have a page we can update more freely

kaz: kind of like a sandbox page?

MK: yes

dom: mentions http://webofthings.org/

<kaz> scribenick: domguinard

dom: we would like to add a W3C WoT tab to clarify the relationship between webofthings.org and the W3C WoT activities

<kaz> scribenick: kaz

kaz: relationship between this effort and the existing Comm TF?

MK: more outreaching to the non-Members and let them know about our work

[ adjourned ]