- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Thu, 16 May 2019 17:36:34 +0900
- To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:
https://www.w3.org/2019/05/15-wot-minutes.html
also as text below.
Thanks a lot for taking the minutes, Taki!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-IG/WG
15 May 2019
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#15_May_2019
Attendees
Present
Kaz_Ashimura, Michael_McCool, Matthias_Kovatsch,
Takahisa_Suzuki, Taki_Kamiya, Tomoaki_Mizushima,
Ege_Korkan, Kunihiko_Toumura, Victor_Charpenay,
Kathy_Giori, Michael_Lagally, Toru_Kawaguchi,
Tetsushi_Matsuda, Sebastian_Kaebisch, Daniel_Peintner,
Zoltan_Kis
Regrets
Chair
McCool, Matthias
Scribe
TK
Contents
* [3]Topics
1. [4]WoT update to Automotive WG
2. [5]IoT Week
3. [6]Intel IoT Dev Fest
4. [7]IIC
5. [8]GATEKEEPER EU Project
6. [9]CR Transition Confirmation
7. [10]Charter discussion
8. [11]Registration for workshop and f2f
* [12]Summary of Action Items
* [13]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: taki
<scribe> scribe: TK
<kaz> (Taki is fantastic :)
<mlagally> +1
WoT update to Automotive WG
Sebastian: invited to Automotive Update
... I explained WoT Update
... automotive WG wants common data model.
Sebastian: there are OEM problems.
... WoT can help make definitions.
... they want to use protocol binding.
... to describe OEM's protocols.
... I explained we were making transition to CR.
... I pointed to workshop.
... BMW is coming to workshop.
... they may make demo.
... we can discuss next step at workshop.
... Ted is the team contact. He is coming to workshop.
... we can also have joint meeting at TPAC.
Kaz: we had several joint sessions in sapporo, lisbon, etc..
... we should consider further collaboration. how WoT can be
used in automotive. am suggesting we should start discussion on
the WoT Chairs list including a possible joint session during
TPAC 2019 in Fukuoka.
Lagally: regarding demo, it would be most useful if we can
invite them to demo call.
Sebastian: I would do it. But their demo uses real vehicle.
... Kind of isolated demo.
Lagally: But we would like to know overview of what they demo.
Sebastian: I can invite them.
IoT Week
Kaz: Dave sent a message to mailing list.
<kaz> [14]Dave's message
[14] https://lists.w3.org/Archives/Member/member-wot-wg/2019May/0042.html
Kaz: yearly conference. good opportunity to network with IoT
people. Dave considering possible talk and demo.
Ege: June 17, or something like that
<kaz> This year, IoT Week is in Aarhus, Denmark from 17-21
June.
McCool: if interested, please try to join in Denmark.
... I can ping Zoltan.
Intel IoT Dev Fest
McCool: on-line web conference on IoT
... deadline for submission is Friday.
... good opportunity to present WoT
... it will be after workshop.
... I will solicit feedback from WoT WG members before
submitting.
IIC
McCool: I will participate in IIC next week.
... I will plan to talk about WoT.
GATEKEEPER EU Project
McCool: some EU project on healthcare and elderly needs
... meeting in Madrid.
CR Transition Confirmation
McCool: I got feedback from i18n group.
... which requires changes.
... after last week's resolution to request transition.
... it is best to make resolution again.
... for making transition the current document.
<kaz> [15]CR transition approval for TD
[15] https://lists.w3.org/Archives/Member/member-wot-wg/2019May/0044.html
McCool: which also addressed Ralph's comments.
<kaz> [16]CR transition approval for Architecture
[16] https://lists.w3.org/Archives/Member/member-wot-wg/2019May/0043.html
Lagally: Architecture document in current state is ready.
... Ralph mentioned we will need to incorporate security review
and TAG review result before PREC.
... no i18n issue for arch document.
McCool: accessibility comments are all editorials.
Lagally: do we have them?
McCool: Just before the telecon. editorials.
... i18n, JSON-LD, device and sensor reviews are done.
... I want to make a resolution.
McCool is typing a proposal for resolution...
<McCool> proposal: The Web of Things WG resolves that the Web
of Things (WoT) Architecture specification, in its current form
on the master branch of
[17]https://github.com/w3c/wot-architecture, is to be published
as a Candidate Recommendation
[17] https://github.com/w3c/wot-architecture,
McCool: does it look reasonable?
... I do not hear objections.
Kaz: we need to check document using the pubrules checker, etc.
... SOTD section may need slight updates before publishing.
McCool updating the resolution proposal...
<McCool> proposal: The Web of Things WG resolves that the Web
of Things (WoT) Architecture specification, in its current form
on the master branch of
[18]https://github.com/w3c/wot-architecture, is to be published
as a Candidate Recommendation, except for possible editorial
changes to the "Status of this document" section, metadata,
links, and spelling.
[18] https://github.com/w3c/wot-architecture
McCool: does it look better?
... any objections?
<inserted> (no objections)
RESOLUTION: The Web of Things WG resolves that the Web of
Things (WoT) Architecture specification, in its current form on
the master branch of
[19]https://github.com/w3c/wot-architecture, is to be published
as a Candidate Recommendation, except for possible editorial
changes to the "Status of this document" section, metadata,
links, and spelling.
[19] https://github.com/w3c/wot-architecture,
Lagally: Thank you for everyone.
McCool: next one is TD.
<inserted> [20]PR 690
[20] https://github.com/w3c/wot-thing-description/pull/690
McCool: PR #690 addresses Ralph's comment.
... We need to make this in.
... listed Features at risk, and made it searchable.
... I marked each feature with "at-risk" annotation.
... also, there are respec errors.
... I made additions for this.
... I added crEnd metadata.
... 2019-06-18 is the day used for now.
... this should not be too tight.
Matthias: is this a day picked by us or by the process?
<kaz> [21]Milestones calculator
[21] https://w3c.github.io/spec-releases/milestones/?pr=2019-06-27&noFPWD=true
McCool: we cannot go earlier than June 13
... I can make it a couple of days earlier.
... it is about deadline for implementors to report issues etc.
Sebastian: PR is on the editorials-for-ralph-comments branch.
Is this intended?
McCool: When we are done, we are going to merge into master.
... I want to make other PRs #691 and #688, can be merged after
CR.
<inserted> [22]PR 688
[22] https://github.com/w3c/wot-thing-description/pull/688
Victor: PR #688. changes in examples.
... in non-normative parts.
McCool: they are informative. they will not change
implementations.
... question is are those things can we make after CR?
Kaz: we can make it after CR.
McCool: my advice is to worry about this after CR.
... we should discuss this PR in TD call on Friday.
Victor: there is a mistake in example.
... how long will the modification period last?
McCool: We can merge those PRs on Friday.
McCool is marking PR #688 and #691 as editorial...
<kaz> [23]Milestones calculator
[23] https://w3c.github.io/spec-releases/milestones/?pr=2019-06-27&noFPWD=true
Kaz: CR end date. there is a calculator.
... shortest is 4 weeks. June 13 is appropriate.
McCool: crEnd in ReSpec is the date implementors can submit
issues.
Kaz: it means we will not make transition "before that day".
Matthias: so we can change it to 13th.
McCool is making modification online accordingly...
McCool is showing the document changes ...
McCool showing SOTD...
McCool: searchable features at risk.
... note there is exit critetia.
... ideally, there should be producer and consumer for each
feature test.
... however, not necessarily make sense for all test cases/
... I want to hear opinions.
Kaz: Ralph's point makes sense.
... but from WoT viewpoint, we could include manually exposed
TD should be included. we can check architecture terminology.
Lagally: arch doc uses Thing and Consumer.
Matthias: Thing is not required to produce TD.
Sebastian: Please take a look at abstract. there is a good
description there.
... can be hosted by things or externally...
McCool: My suggestion is not to mention this sentence in SOTD.
Matthias: we can say consumer or producer of TD. and also can
say people can produce TD manually.
Kaz: we can explain the detail when making PR transition.
McCool: I worry making those changes complicates things.
Matthias: I would say remove this details and point to
definitions in implementation report.
Sebastian: we can also point to architecture document.
McCool: I suggest to change "if possible" to "if appropriate"
Matthias: can we say "TD producer" instead of producer? and
also consumer to "TD consumer"?
... I would +1, for what you said "when applicable".
McCool: "appropriate" means when it is applicable.
Lagally: +1 for "applicable"
McCool: that works for me.
... any objections?
McCool is pushing the changes to the editorial branch...
Kaz: It would be better to respond to Ralph to wrap-up the
procedure.
... mention that we have updated the draft accordingly.
... after our making resolution.
McCool is showing the changes...
Lagally: I looked at changes, and am not comfortable calling
them editorial.
... I mean, the other ones.
McCool is typing in proposals for a resolution...
<McCool> proposal: The Web of Things WG resolves that the Web
of Things (WoT) Thing Description specification, in its current
form on the editorials-for-ralph-comments branch of
[24]https://github.com/w3c/wot-thing-description, is to be
published as a Candidate Recommendation, except for possible
editorial changes to the "Status of this document" section,
metadata, links, and spelling.
[24] https://github.com/w3c/wot-thing-description
McCool: any comments?
... I would like to make a resolution.
... we can talk about co-editor on Friday.
... We can also review colors based on accessibility WG
comments for architecture doc.
Sebastian: why can't make it now?
Matthias: CR is the one people will look at and comments on.
McCool is taking a look at changes for #691...
McCool: "JSON Schema vocabulary". Is this correct?
... we can make this modification after CR.
<victor>
[25]https://cdn.staticaly.com/gh/vcharpenay/wot-thing-descripti
on/master-uml/index.html?env=dev
[25] https://cdn.staticaly.com/gh/vcharpenay/wot-thing-description/master-uml/index.html?env=dev
McCool is comparing Figure 4 between old and updated...
McCool: no "mandatory" display anymore, instead optional is
[0...1]
Matthias: this is more consistent.
McCool: any questons about this figure?
Victor: you can take a look at the rendered document. It is in
IRC.
McCool is comparing figure 1 old and updated...
Lagally: Interaction affordance is different.
Victor: I fixed a bug.
McCool: Looks better. We should accept this and deals with
small changes later.
McCool going through figure 2, 3...
Matthias: I suggest raplph-comments branch into master first.
<inserted> [26]PR 692
[26] https://github.com/w3c/wot-thing-description/pull/692
McCool is looking at PR #692...
McCool: any comments?
McCool merged PR #692.
<inserted> [27]PR 691
[27] https://github.com/w3c/wot-thing-description/pull/691
McCool: next PR #691.
McCool checking PR #691 diff...
McCool merged PR #691...
Lagally: PR #688 should be reviewed before merging.
McCool: Editoral changes are ok till PREC.
<McCool> proposal: The Web of Things WG resolves that the Web
of Things (WoT) Thing Description specification, in its current
form on the master branch of
[28]https://github.com/w3c/wot-thing-description, is to be
published as a Candidate Recommendation, except for possible
editorial changes to the "Status of this document" section,
metadata, links, and spelling.
[28] https://github.com/w3c/wot-thing-description,
Matthias: we just made editorial changes.
... tomorrow we are going to publish.
... after that, we can change again.
Kaz: Let's change label to "for PREC"
... we should review it precisely.
Lagally: I just suggest to present this in the TD call to allow
reasonable review
Matthias: It is for PREC.
McCool: any objections to making resolution?
<kaz> (no objections for the proposal above)
McCool is typing a resolition...
RESOLUTION: The Web of Things WG resolves that the Web of
Things (WoT) Thing Description specification, in its current
form on the master branch of
[29]https://github.com/w3c/wot-thing-description, is to be
published as a Candidate Recommendation, except for possible
editorial changes to the "Status of this document" section,
metadata, links, and spelling.
[29] https://github.com/w3c/wot-thing-description,
McCool: done.
Sebastian: Thank you!
McCool: next week, we discuss post-CR plans.
Charter discussion
Matthias: we also need to discuss charter before workshop.
<McCool> ... but think about charters
Matthias: please everyone think about this.
<McCool> ... here is our last draft for the IG
[30]https://github.com/w3c/wot/blob/master/charters/wot-ig-2019
.html
[30] https://github.com/w3c/wot/blob/master/charters/wot-ig-2019.html
Matthias: please prepare for next meeting with this.
Registration for workshop and f2f
Kaz: Please get registered for workshop and F2F.
Matthias: where can we find them?
<kaz> [31]workshop registration
[31] https://www.w3.org/2002/09/wbs/1/wotws2-201906/
<kaz> [32]f2f registration
[32] https://www.w3.org/2002/09/wbs/1/WoTF2F201906/
<McCool> [33]F2F logistics page
[33] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_6-7_June_2019,_Munich,_Germany
<kaz> [adjourned]
Summary of Action Items
Summary of Resolutions
1. [34]The Web of Things WG resolves that the Web of Things
(WoT) Architecture specification, in its current form on
the master branch of
https://github.com/w3c/wot-architecture, is to be published
as a Candidate Recommendation, except for possible
editorial changes to the "Status of this document" section,
metadata, links, and spelling.
2. [35]The Web of Things WG resolves that the Web of Things
(WoT) Thing Description specification, in its current form
on the master branch of
https://github.com/w3c/wot-thing-description, is to be
published as a Candidate Recommendation, except for
possible editorial changes to the "Status of this document"
section, metadata, links, and spelling.
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [36]scribe.perl version 1.154 ([37]CVS log)
$Date: 2019/05/16 08:12:49 $
[36] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[37] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 16 May 2019 08:37:36 UTC