- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 31 May 2017 22:23:18 +0900
- To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:
https://www.w3.org/2017/05/31-wot-minutes.html
also as text below.
Thanks a lot for taking notes, Michael Koster!
BTW, I got a message form Uday about the Dusseldorf f2f meeting logistics
as follows:
- Lemonbeat is planning to organize a city tour followed by a social
dinner on Monday-10th July after the open day event.
- There would be a registration fee for the social event (tour +
dinner).
- More details of the fee and payment procedures for the social event
will be updated on the Dusseldorf f2f Wiki page in the coming
days.
- Suggestions for hotel rooms and travel options to Dusseldorf will
also be added to the wiki page shortly.
And I've updated the f2f registration site with those points.
Group participants, please visit the following registration site and
get registered by June 12th:
https://www.w3.org/2002/09/wbs/1/WoTF2F201707/?login
Thanks,
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT IG/WG
31 May 2017
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda
See also: [3]IRC log
[3] http://www.w3.org/2017/05/31-wot-irc
Attendees
Present
Barry_Leiba, Daniel_Peintner, Darko_Anicic,
Johannes_Hund, Katsuyoshi_Naka, Kaz_Ashimura,
Kazuaki_Nimura, Kris_Borchers, Kunihiko_Toumura,
Masato_Ohura, Michael_Koster, Michael_McCool,
Niklas_Widell, Takeshi_Yamada, Tomoaki_Mizushima,
Yingying_Chen, Zoltan_Kis, Keiichi_Tokuyama
Regrets
Chair
McCool
Scribe
Michael_Koster
Contents
* [4]Topics
1. [5]OCF Liaison TF
2. [6]Scripting TF
3. [7]TF-LD
4. [8]Thing Description
5. [9]Dusseldorf f2f
6. [10]AOB
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: kaz
mccool: many people are on vacation this week
... but would give some update
<kaz> scribenick: mjkoster
Agenda approved
OCF Liaison TF and Scripting TF met this week
OCF Liaison TF
mccool: working on demo for dusseldorf based on OCF Smart Home
demo
... layering node-wot on iotivity-node
... working on OCF data model description in a friendly format
<kaz> [13]OCF Liaison TF wiki
[13] https://www.w3.org/WoT/IG/wiki/IG_OCF_Liaison_WebConf
Scripting TF
zoltan: scripting TF summary
... follow up from Osaka F2F, architecture diagram refinement
<kaz> [14]Johannes's summary
[14] https://lists.w3.org/Archives/Member/member-wot-wg/2017May/0030.html
zoltan: discussion of container security (for running scripts)
... protocol bindings may need to be isolated
... no changes to the API
... need hardware support for the best security
mccool: may not support running scripts in harware that doesn't
have security support
<inserted> kaz: do we want to feedback our
discussion/requirements for the architecture to the
architecture draft itself?
mccool: don't lose track of this thread, create a github issue
for it
... security-based constraints on architecture - limit the
feature set wrt hw security support
zoltan: will file an issue on implementation recommendations
TF-LD
darko: linked data TF report
... want to participate in the dusseldorf PF
... 3 workstreams: LD for WoT applications and semantic model
for cross-ecosystem discovery
... starting with OCF and an interoperability client that reads
semantic descriptions
... 2. work on recipes that are TD based
... 3. semantic processing for WoT, starting with validation
... also could demonstrate enhanced discovery using semantic
processing
... could demonstrate reasoning in discovery based on
descriptive constraints
(hope I capture it properly)
mccool: OCF input will be provided from mccool and mjkoster
<kaz> [15]TF-LD minutes
[15] https://www.w3.org/2017/05/26-wot-minutes.html
Thing Description
daniel: thing description TF report
... working on serialization formats
... text and binary
<kaz> [16]Sebastian's summary
[16] https://www.w3.org/WoT/IG/wiki/images/9/95/Td_summary_osaka.pdf
daniel: they need examples of practical TD files for analysis,
please send them or publish them
mccool: we should keep and archive TDs that have been
contributed
daniel: dsr working on JSON examples of TD serialization
kaz: we can publish each TD specification after the F2F as a
working draft along as well as the Current Practices document
<dape>
[17]http://w3c.github.io/wot/current-practices/wot-practices-os
aka-2017.html
[17] http://w3c.github.io/wot/current-practices/wot-practices-osaka-2017.html
kaz: maybe the IG can publich the current practices document as
an IG Note and the WG can publish TD snapshots as working
drafts
zoltan: need binding templates
kaz: we can start another repo for binding template draft
zoltan: there is a place in the TD repos for bindings now
mccool: propose making a subdirectory under TD
... a sub-directory
johannes: need to develop the agreement about what information
is needed
... need one example of a current TD
<dape>
[18]http://w3c.github.io/wot/current-practices/wot-practices.ht
ml#protocol-bindings
[18] http://w3c.github.io/wot/current-practices/wot-practices.html#protocol-bindings
daniel: on which level is the protocol binding expected to be ?
mccool: can mjkoster make a PR that clarifies this question?
mjkoster: describe WoT implicit bindings vs. adaptation layer
bindings like OCF
mccool: evolve the binding toward specification
<kaz> kaz: mjkoster, do you want to proceed with binding
discussion as part of the TD TF?
mjkoster: keep the discussion with TD
mccool: but where does the discussion take place?
... start by getting TD hashed out and written down
... we could start as a sub-document of TD
Dusseldorf f2f
<kaz> [19]f2f wiki
[19] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_9-13_July_2017,_Düsseldorf,_Germany
<kaz> [20]registration
[20] https://www.w3.org/2002/09/wbs/1/WoTF2F201707/
mccool: register by June 12
... should have hotel info soon
<kaz> mccool: also please add topics for the meeting on the
wiki
AOB
<kaz> johannes: won't make the next Scripting meeting on June 5
<inserted> zoltan: asks about security discussion
johannes: reschedule to Monday the 12th
zoltan: what are next steps for specification of the TD
elements of a protocol binding for OCF
mccool: create a PR for the example and start describing
<inserted> kaz: which slot to be used for that discussion?
mccool: reuse the OCF liaison call to work on the protocol
binding examples
... could we have items to review by the next meeting?
... first pullrequest by the TD meeting on Friday, June 2?
mjkoster: ok
[adjourn]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [21]scribe.perl version
1.152 ([22]CVS log)
$Date: 2017/05/31 13:10:34 $
[21] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[22] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 31 May 2017 13:24:33 UTC