- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 5 Oct 2016 22:42:20 +0900
- To: Public Web of Things IG <public-wot-ig@w3.org>
- Message-ID: <CAJ8iq9WBjWNYMH+6gnu6o-txH1cOQcKti_9yUPLZ7NR9zAX5og@mail.gmail.com>
available at:
https://www.w3.org/2016/10/05-wot-minutes.html
also as text below.
Thanks a lot for taking notes, Dom!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT IG
05 Oct 2016
[2]Agenda
[2]
https://www.w3.org/WoT/IG/wiki/IG_WebConf#Agenda_of_next_WoT_IG_WebConf:_5_October_2016
See also: [3]IRC log
[3] http://www.w3.org/2016/10/05-wot-irc
Attendees
Present
Darko_Anicic, Kaz_Ashimura, Michael_Koster, Dom_Guinard,
Masato_Ohura, Matthias_Kovatsch, Michael_McCool,
Sebastian_Kaebisch, Uday_Davuluru, Victor_Charpenay,
Wonsuk_Lee, Takeshi_Yamada(observer),
Keiichi_Tokuyama(observer), Daniel_Peintner,
Kazuaki_Nimura, Johannes_Hund, Ryuichi_Matsukura
Regrets
Chair
Matthias_Kovatsch, Michael_McCool
Scribe
domguinard
Contents
* [4]Topics
1. [5]Status of AC review
2. [6]Group Processes
3. [7]TD Restructuring
4. [8]Scripting API
5. [9]Hydra
6. [10]TD Lifecycle
7. [11]Servient Synchronization
8. [12]Protocol Mapping
9. [13]Security
10. [14]F-Interop
11. [15]Next F2F planning
12. [16]OCF liaison
13. [17]WoT landing page
* [18]Summary of Action Items
* [19]Summary of Resolutions
__________________________________________________________
Status of AC review
<kaz> scribenick: domguinard
<kaz> [20]AC review results (member-only)
[20] https://www.w3.org/2002/09/wbs/33280/wotwg2016/results
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> [21]TD Restructuring call minutes
[21] https://www.w3.org/2016/10/05-wot-td-minutes.html
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> [22]Lisbon F2F minutes
[22] https://www.w3.org/2016/09/22-23-wot-minutes.html
<kaz> scribenick: kaz
MK: Still need to work on Scripting
Hydra
<inserted> [23]Hydra breakout minutes
[23] https://www.w3.org/2016/09/22-wot-td-minutes.html#item02
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> [24]TD Lifecycle breakout minutes
[24] https://www.w3.org/2016/09/22-wot-td-minutes.html#item01
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> [25]Synchronization minutes
[25] https://www.w3.org/2016/09/22-23-wot-minutes.html#day2-item07
MK: there was a breakout about sync things and proxies
Protocol Mapping
<kaz> [26]Protocol mapping minutes|
[26] https://www.w3.org/2016/09/22-23-wot-minutes.html#day2-item07
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> [27]WoT landing page
[27] https://www.w3.org/WoT/
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 [28]http://webofthings.org/
[28] 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 ]
Summary of Action Items
<trackbot> Created ACTION-78 - Propose tagging and folder
structure for github [on Matthias Kovatsch - due 2016-10-12].
<trackbot> Created ACTION-79 - Prepare and announce kick-off
for scripting [on Johannes Hund - due 2016-10-12].
<trackbot> Created ACTION-80 - Is going to push the security
topic forward [on Michael McCool - due 2016-10-12].
Summary of Resolutions
1. [29]leave charter as-is, add IPSO to liasons wiki, outreach
to the commenter to explain setup
2. [30]we leave the technical work on GitHub
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [31]scribe.perl version
1.144 ([32]CVS log)
$Date: 2016/10/05 13:41:09 $
[31] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[32] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 5 October 2016 13:43:37 UTC