<kaz> scribe: Nimura

<kaz> scribenick: k_nimura

<kaz> agenda: https://www.w3.org/WoT/IG/wiki/IG_WebConf#Agenda_of_next_WoT_IG_WebConf:_30_November_2016

WG Charter

mccool: our responses with updated draft Charter were sent to Wendy.
... maybe she was on vacation and have not got updates so far

kaz: kaz: Wendy is talking with the W3M as well

F2F logistics

still waiting badget consens in Intel regarding for nest f2f.

thanks giving delays the confirmation process.

oneM2M liaison

mccool: regrets from Yongjing

OCF Liaison

mccool: Michael Koster will talk about it.

Michael Koster's slides

OCF data model presentation by Michael Koster:

CRUD+N mapped to CoAP.

CoAP with security and without security exist.

Resource structure: links point to resource. resource has multiple properies interestingly.

example resource represntation is presented.

data model changes significantly.

standard key words is defined in some RFCs.

No standard http biding but works fine.

Except for JSON and CBOR, any other binary mapping?

EXI could be used but not defined yet.

Resource Type means in OCF is specific resource description.

<zkis> www.oneiota.org

Interface type

OCF interface type "if" defines methods and payloads

Resource instance is expose more than one resource.

you can have multple resource type: temprature of minimum and maximum or so.

interaction model

OCF URI scheme has generic URI.

Details of interaction Model is shown.

another features is batch collection.

more than one resources deals by this.

Restful actuation is presented.

actuation payload can be batch expression.

<kaz> johannes: question about resource type

Resource definition uses RAML and JSON schema.

<kaz> GENIVI VSS

Working progress in Healthcare(continua), automotive(Genivi), UPnP(now part of OCF), Allseen device.

kaz: you wanted to ask about writable and action

mk: yes
... common design pattern is important for interoperability
... we use same data model design through this design pattern
... action pattern also can be described using mapping

TD update

Any report from TD techinical work?

No TD call today.

Scripting update

<kaz> Scripting minutes

johannes: Zoltan's contribution
... also discussion on issue-240 and 235

Regarding the description languages and event handling methods, lists of option for plugfest will be posted..

Security TF

mccool: Ryan is updating the Charter for the TF

Any other business?

dsr: mentions the WG Charter procedure again including the possible announcement on the progress/status

kaz: suggests we check with Wendy and consult with her about the next steps again

Next meeting

kaz: we need to fix the basic logistics for the next f2f about hotel and flight, etc.

mccool: right
... waiting for the conclusion about the logistics for next F2F meeting, not finalizing the details yet.

<kaz> mccool adds updates to the agenda wiki: OCF liaison, translating TD to RDF
... also updates the date to "Dec. 7"

<kaz> [ adjourned ]