- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 07 Apr 2020 19:12:38 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/03/30-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Zoltan!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Discovery
30 Mar 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#30_Mar_2020
Attendees
Present
Kaz_Ashimura, Michael_McCool, Kevin_Olotu, Zoltan_Kis,
Chritian_Glomb, Kunihiko_Toumura, Michael_Koster,
Andrea_Cimmino
Regrets
Chair
McCool
Scribe
zkis
Contents
* [3]Topics
1. [4]Agenda
2. [5]Previous minutes
3. [6]Pull request #4
4. [7]Use cases
5. [8]Issue#7
6. [9]New issue about whether could a directory service
support content negotiation and return metadata in
different formats, e.g. Vorto, OpenAPI, WoT TD.
7. [10]Check prvious actions again
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: zkis
Agenda
<McCool>
agenda:[13]https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebC
onf#30_Mar_2020
[13] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#30_Mar_2020
MMc editing WG WoT Discovery wiki, guests: Kevin Olotu (Bosch)
McCool: any objection against Kevin as guest?
no objections
McCool: today would like to follow up on the issues
Previous minutes
[14]Mar-23 minutes
[14] https://www.w3.org/2020/03/23-wot-discovery-minutes.html
McCool: any objections on publishing the Agenda
[no objections]
Pull request #4
[15]https://github.com/w3c/wot-discovery/pull/4
[15] https://github.com/w3c/wot-discovery/pull/4
McCool: I think we should limit the scope to metadata
... otherwise we could merge it
Christian: so the proposal is to split the content to multiple
files and link them?
McCool: yes
... and then a README
... we could do that later, for now we can merge it
Christian: I just proposed a template and tried to put the use
cases in that
... nothing was changed, just reorganized
McCool: any objections for merging?
[no objections]
Merged with a comment on how to follow up.
Use cases
[16]https://github.com/w3c/wot-discovery/tree/master/USE-CASES
[16] https://github.com/w3c/wot-discovery/tree/master/USE-CASES
MMc editing, adding Scope
McCool: limit discovery to metadata discovery
MMc made PR #12
[17]https://github.com/w3c/wot-discovery/pull/12
[17] https://github.com/w3c/wot-discovery/pull/12
McCool: will leave it open for a week for comments
Issue#7
[18]https://github.com/w3c/wot-discovery/issues/7
[18] https://github.com/w3c/wot-discovery/issues/7
Kevin: two kinds of work, alignment of semantic terminology and
how to do interoperability
McCool: there is too much things for one issue.
... let's keep this issue for the first, i.e. alignment of
semantic terminology and move the rest to a new issue
Andrea: maybe we could explore automatic translation
... into a TD
Koster: take things that are described by Vorto, define those
in TD and add protocol bindings
Andrea: but we don't have that translation today, right?
Koster: we could create a TD template and add the protocol
binding information
... there are 2 things, the information model and bindings
Andrea: finding the translation is the challenge
McCool: bidirectional translation, even
MMc is creating a new issue for Vorto interoperability
[19]https://github.com/w3c/wot-discovery/issues/13
[19] https://github.com/w3c/wot-discovery/issues/13
McCool: assigning issue#7 to Kevin
... this is more like a TD issue
... didn't work, assigning it to Michael Koster
New issue about whether could a directory service support content
negotiation and return metadata in different formats, e.g. Vorto,
OpenAPI, WoT TD.
[20]https://github.com/w3c/wot-discovery/issues/14
[20] https://github.com/w3c/wot-discovery/issues/14
Koster: the question is how are we going to use it for
discovery searches
McCool: is this suitable scope for you Kevin?
Kevin: yes
Check previous actions again
<kaz> [21]Mar23 minutes
[21] https://www.w3.org/2020/03/23-wot-discovery-minutes.html
McCool: capturing issues from past minutes
... creating a docker container for node-wot, could we create
an issue in node-wot?
... Kaz, please fix the typo for doc->docker
Koster: for management API, we could define a TD
<kaz> [fixed]
<McCool> mm: "doc" should be "docker" in minutes
McCool: CG please create an issue in node-wot
[adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [22]scribe.perl version 1.154 ([23]CVS log)
$Date: 2020/04/01 09:39:40 $
[22] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[23] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 7 April 2020 10:12:39 UTC