- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 21 Jul 2020 18:06:11 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/07/13-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Farshid!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Discovery
13 Jul 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#13_July_2020
Attendees
Present
Kaz_Ashimura, Michael_McCool, Andrea_Cimmino,
Kunihiko_Toumura, Farshid_Tavakolizadeh,
Christian_Glomb, Tomoaki_Mizushima
Regrets
Chair
McCool
Scribe
FarshidT
Contents
* [3]Topics
1. [4]Minutes
2. [5]PRs
3. [6]Next PR, LinkSmart directory
4. [7]PR: TD for thing directory
5. [8]PR: fujitsu's directory
6. [9]PR 35 again
7. [10]Next week's agenda
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: FarshidT
Minutes
[13]https://www.w3.org/2020/07/06-wot-discovery-minutes.html
[13] https://www.w3.org/2020/07/06-wot-discovery-minutes.html
McCool: @kaz, please create an issue to document the manifests
related RFC
<kaz> ACTION: kaz to generate a GitHub issue for the expected
resources on manifests IETF RFCs discussed on July 6
no objections to publishing the minutes
PRs
McCool: three PRs related to directory APIs
... another PR is the draft of directory specs, will start with
that
... list of editors, scheduling
[14]https://github.com/w3c/wot-discovery/pull/35
[14] https://github.com/w3c/wot-discovery/pull/35
McCool: architecture section
... intro may have different sections for each type of
introduction service
... exploration: supported/types of exploration services.
... directory services, may be a subsection of exploration
... information model: the data model of the service, a TD as
specification
... registration, management, notification, search (query)
Andrea: add subsection describing different response formats
McCool: can have a link in TD (directory's specs) with a link
to sparql query endpoint
Farshid: also include openapi specs because TD currently
doesn't allow specifying response headers and codes
McCool: we add extensions to TD. We better avoid having
parallel specs, will be difficult to maintain.
... additional exploration types
... decide what introduction types should be part of the specs
Andrea: RDF summaries, for when having links and TDs together
in the information model
... have some material on this topic, to be discussed next
week.
Farshid: what about security requirements for exploration API?
McCool: what introduction types we want to include? direct url,
dns-sd, core-rd, did document.
... every link can point to a TD, and the TD may have a type to
specify if it is a thing or directory
Farshid: what about a section for listing? Search is applied to
lists.
<inserted> [15]McCool's comment for Issue 35
[15] https://github.com/w3c/wot-discovery/pull/35#issuecomment-657594588
McCool: any volunteers for additional editors?
Andrea: yes
Farshid: yes
<McCool> proposal: add Farshid Tavakolizadeh, Kunihiko Toumura,
and Andrea Cimmino as co-editors
Toumura: yes, for introduction section
RESOLUTION: add Farshid Tavakolizadeh, Kunihiko Toumura, and
Andrea Cimmino as co-editors
<inserted> [16]comment on additional co-Editors
[16] https://github.com/w3c/wot-discovery/pull/35#issuecomment-657596491
Next PR, LinkSmart directory
<kaz> [17]PR 36
[17] https://github.com/w3c/wot-discovery/pull/36
Farshid: reviewed by ben and made modifications.
McCool: merged, goes to prior work. To be further improved
PR: TD for thing directory
[18]PR 31
[18] https://github.com/w3c/wot-discovery/pull/31
McCool: being added to proposals.
Farshid: TDs are added as links
McCool: doesn't include full TD specs. Will merge for
discussion purposes and consider it along with linksmart's TD.
... will probably take linksmart's TD as basis, for a TD inside
the specs.
... added comment on the PR and merged
PR: fujitsu's directory
[19]PR 33
[19] https://github.com/w3c/wot-discovery/pull/33
McCool: sequence diagrams, nice to have for the specs document
... not TD specs, but has a readme
... for specs, will restructure to have a TD and sequence
diagrams from PRs. And will try to make them consistent
afterwards.
Toumura: this was created for plugfest.
McCool: automatically created UML diagrams, may use the same
tooling in specs
scribenick: kaz
Kaz: Fujitsu's old work should be included in the WoT discovery
draft at least as part of "best practices"
<kaz> [20]PR 33 merged
[20] https://github.com/w3c/wot-discovery/pull/33
scribenik: FarshidT
McCool: added co-editors as reviewers to PR 35. Please add more
comments. Will discuss next week and merge.
PR 35 again
<kaz> [21]PR 35
[21] https://github.com/w3c/wot-discovery/pull/35
McCool: please review PR 35 and the draft outline
Next week's agenda
McCool: specs draft outline, RDF summaries
<kaz> [adjourned]
Summary of Action Items
[NEW] ACTION: kaz to generate a GitHub issue for the expected
resources on manifests IETF RFCs discussed on July 6
Summary of Resolutions
1. [22]add Farshid Tavakolizadeh, Kunihiko Toumura, and Andrea
Cimmino as co-editors
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [23]scribe.perl version ([24]CVS log)
$Date: 2020/07/14 09:14:58 $
[23] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[24] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 21 July 2020 09:04:51 UTC