<kaz> scribenick: taki
<scribe> scribe: TK
<kaz> (Taki is fantastic :)
<mlagally> +1
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.
Kaz: Dave sent a message to mailing list.
<kaz> Dave's message
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.
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.
McCool: I will participate in IIC
next week.
... I will plan to talk about WoT.
McCool: some EU project on
healthcare and elderly needs
... meeting in Madrid.
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> CR transition approval for TD
McCool: which also addressed Ralph's comments.
<kaz> CR transition approval for Architecture
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 https://github.com/w3c/wot-architecture, is to be published as a Candidate Recommendation
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 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.
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 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.
Lagally: Thank you for everyone.
McCool: next one is TD.
<inserted> PR 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> Milestones calculator
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> PR 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> Milestones calculator
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 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.
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> 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> PR 692
McCool is looking at PR #692...
McCool: any comments?
McCool merged PR #692.
<inserted> PR 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 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.
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 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.
McCool: done.
Sebastian: Thank you!
McCool: next week, we discuss post-CR plans.
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 https://github.com/w3c/wot/blob/master/charters/wot-ig-2019.html
Matthias: please prepare for next meeting with this.
Kaz: Please get registered for workshop and F2F.
Matthias: where can we find them?
<kaz> workshop registration
<kaz> f2f registration
<McCool> F2F logistics page
<kaz> [adjourned]