- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Fri, 19 Jul 2019 09:24:25 +0900
- To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:
https://www.w3.org/2019/07/17-wot-minutes.html
also as text below.
Thanks,
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-IG/WG
17 Jul 2019
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#17_July_2019
Attendees
Present
Kaz_Ashimura, Michael_McCool, Taki_Kamiya,
Michael_Lagally, Takahisa_Suzuki, Tetsushi_Matsuda,
Zoltan_Kis, Daniel_Peintner, Kunihiko_Toumura,
Ryuichi_Matsukura, Michael_Koster, Toru_Kawaguchi,
Tomoaki_Mizushima, Ege_Korkan, Sebastian_Kaebisch
Regrets
Chair
McCool
Scribe
zkis, kaz
Contents
* [3]Topics
1. [4]Quick updates
2. [5]Minutes from workshop and f2f in Munich
3. [6]Review feedback
4. [7]TPAC / F2F planning
5. [8]Next IG charter
6. [9]Next WG Charter
7. [10]Profile discussion
8. [11]TF report
9. [12]PlugFest call
* [13]Summary of Action Items
* [14]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: zkis
<McCool> agenda:
[15]https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#17_July_201
9
[15] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#17_July_2019
Quick updates
McCool: TPAC registration and hotel reservation, if you've not
done yet, please do.
... next week IETF meeting. not sure if I can chair the main
call next week. If not possible, Kaz can chair the call
instead.
... archived the proposals in the IG repo
... files can be moved in and out
... will speak on Conexxus strategy conference about WoT and
IoT in retail
Minutes from workshop and f2f in Munich
McCool: Kaz has finished the minutes for the F2F
... if you see errors, please tell Kaz
<kaz> [16]workshop minutes
[16] https://www.w3.org/WoT/ws-2019/minutes.html
<kaz> [17]f2f minutes
[17] https://www.w3.org/2019/06/wot-f2f/06-07-wot-minutes.html
Review feedback
Sebastian: TAG had review of WoT architecture
McCool: privacy protection has to come from higher level than
TD, so it's hard to evaluate the privacy implications
<inserted> [18]July-17 TAG agenda
[18] https://github.com/w3ctag/meetings/blob/gh-pages/2019/telcons/07-17-agenda.md
<inserted> [19]PING comment
[19] https://github.com/w3c/wot-thing-description/issues/794
McCool: we don't have means to protect privacy
... PING is interested to work on the directory API with WoT
WG/IG
Lagally: we didn't include any mandatory API at this point
... an API may not be specified in this charter period
McCool: emphasize TD is just a data format
... but we should commit to working with PING on any future
development, e.g. an API spec
Koster: API means a resource type definition; we need an end to
end system to tell privacy implications
McCool: the spec says privacy should be controlled by the
actions defined
... there is also a possible Discovery API, and others as well
(management API etc)
... See TD issue #794
<kaz> [20]TD issue 794 (PING comment)
[20] https://github.com/w3c/wot-thing-description/issues/794
McCool: security is in TD endpoints, we can't limit people from
making devices that expose private information
... we don't make APIs for devices
... we should remain descriptive
... HTML analogy - privacy is not granted by HTML alone
Taki: In the joint PING call, we received a harsh comment for
not describing protecting privacy for TD model. Therefore, it
would be wise to focus our comment on the future commitment,
rather than making an excuse at this point.
Sebastian: discussed with security experts in Siemens; this is
a typical privacy discussion which will never find solution,
concerns will appear anyway
McCool: right, it's a best effort thing, we have risk
assessment and mitigation described
... this is an important topic for the next charter
... moving on with the agenda
Kaz: if they can provide several concrete points for important
privacy issues, probably we need to incorporate those issues
and possibly we need to publish an updated Candidate Rec.
However, we should mark the issues as "v.next" if they're not
fatal for the current version.
... note that we need to wrap up everything during the
extension period (6 months)
TPAC / F2F planning
McCool: we should defer this to the plugfest call
... topics need to be filled in
<inserted> [21]f2f wiki
[21] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_16-20_September_2019,_Fukuoka,_Japan
McCool: please edit the wiki page
Next IG charter
McCool: feedback from Alan Bird
<kaz> scribenick: kaz
[22]IG Charter draft
[22] http://w3c.github.io/wot/charters/wot-ig-2019.html
[23]Alan's comment (member-only)
[23] https://lists.w3.org/Archives/Member/member-wot-wg/2019Jul/0016.html
[24]McCool's PR for Alan's comment
[24] https://github.com/w3c/wot/pull/838
McCool: (shows the changes)
[25]Changes
[25] https://github.com/w3c/wot/pull/838/files
McCool: industry vertical potion
... getting Michael Lagally's input
Lagally: suggesting reword
... "including PlugFests for specific vertical industries"
... to
... "including interoperability events for specific vertical
industries"
Sebastian: what about "Hackathon" instead of PlugFest?
McCool: "organize and run interoperability testing events,
including events for specific vertical industries,"?
... implementations to be collected
... we don't have official conformance testing
... on the other hand, we have online testing events as well
... plugfest is for testing interoperability
... (saves the updated text)
... group agrees to my suggested change above
... and the next comment from Lagally
... "would change the order a bit and put SDOs and industry
alliances higher in the rank"
Lagally: also we should have community guys as well
McCool: how about SDOs first?
... then industry alliances
... and then providers
... SDOs are grouped with industry alliances
... alliances are also grouped with providers
Lagally: ok
McCool: next Wendy's comment
Sebastian: deadline?
Kaz: there is a specific procedure
... W3M review first (we're here) and then AC review next
... AC review takes one month
[26]Wendy's comment
[26] https://github.com/w3c/wot/issues/835
Kaz: do you want to respond to Wendy's comment as well as
Alan's?
McCool: good question
... putting a comment to Wendy's GitHub issue
[27]McCool's response
[27] https://github.com/w3c/wot/issues/835#issuecomment-512242000
Next WG Charter
McCool: should discuss the updated WG Charter next time with
Matthias
[Kaz's note: the current WoT WG Charter has been extended till
Dec-31. AC announcement has been sent out. also the [28]WoT WG
Charter document has been updated accordingly.]
[28] https://www.w3.org/2016/12/wot-wg-2016.html
Profile discussion
McCool: main issue is timing
... when to add it
... reopen the CR spec and add it now?
... or defer to v.next?
Lagally: I'm not suggesting we reopen the spec now
... rather would propose to create a separate document
Sebastian: would be good to have some concrete proposal based
on slides
Lagally: we already had discussion but can provide some
[29]Profile discussion last week
[29] https://www.w3.org/2019/07/10-wot-minutes.html#item08
Lagally: we can use the half of the Architecture call tomorrow
for the profile discussion
Sebastian: I'll be travelling tomorrow
McCool: would be better to discuss it during the TD call Friday
then
Lagally: ok
TF report
McCool: we're out of time, anything important to report today?
(none)
PlugFest call
Sebastian: PlugFest call today?
McCool: Michael Lagally will moderate it after this call
Lagally: in 5 mins
... stay on this webex
... and use "#wot-pf" IRC channel
[adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [30]scribe.perl version 1.154 ([31]CVS log)
$Date: 2019/07/18 07:56:51 $
[30] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[31] http://dev.w3.org/cvsweb/2002/scribe/
Received on Friday, 19 July 2019 00:25:31 UTC