- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 18 Feb 2020 23:13:56 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/02/10-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Daniel!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-Discovery
10 Feb 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#10_Feb_2020
Attendees
Present
Andrea_Cimmino, Kaz_Ashimura, Michael_McCool,
Christian_Glomb, Christopher_Ambler, Daniel_Peintner,
Ege_Korkan, Kunihiko_Toumura, Taki_Kamiya,
Tomoaki_Mizushima
Regrets
Michael_Koster
Chair
McCool
Scribe
dape
Contents
* [3]Topics
1. [4]Introduction
2. [5]Organizational logistics
3. [6]Planning
* [7]Summary of Action Items
* [8]Summary of Resolutions
__________________________________________________________
<kaz> scibenick: dape
Introduction
<kaz> mm: we have guests from GoDaddy today
Christopher: GoDaddy technical side
Andrea: Technical University of Madrid, a W3C Member and
participating in the WoT WG
... working on discovery mechanism based on WoT
McCool: Andrea, could you post links to project and paper.
Would be useful
<Cimmino>
Papers:
* [9]https://www.mdpi.com/1424-8220/20/3/822
https://www.mdpi.com/1424-8220/20/3/822
* [10]https://ieeexplore.ieee.org/abstract/document/8804825
https://ieeexplore.ieee.org/abstract/document/8804825
*
[11]https://link.springer.com/chapter/10.1007/978-3-319-74433-9
_2
Projects:
https://link.springer.com/chapter/10.1007/978-3-319-74433-9_2
* VICINTIY ([12]https://vicinity.bavenir.eu/#/home)
https://vicinity.bavenir.eu/#/home
* DELTA ([13]https://www.delta-h2020.eu/)
[13] https://www.delta-h2020.eu/
McCool: GoDaddy is not a W3C Member but quest participation for
today is possible
... Note: minutes are going to be public after 1 week review
period
<kaz> [14]W3C Patent Policy
[14] https://www.w3.org/Consortium/Patent-Policy/
<kaz> [15]W3C Patent Policy FAQ 13
[15] https://www.w3.org/2003/12/22-pp-faq.html#guest
<kaz> [16]W3C Patent Policy FAQ 6
[16] https://www.w3.org/2003/12/22-pp-faq.html#non-participants
Kaz: guest invitation for today's meeting is fine given we
won't have any concrete technical discussion on our normative
specs today
... please be aware of the W3C patent policy and also the
patent policy FAQ above
Organizational logistics
McCool: 1 hour weekly call
... start in 5 minutes at the latest
... chair picks scribe
Planning
McCool: Kaz, no wot-discovery repo yet?
<McCool_> ACTION: kaz to create wot-discovery github repo
Kaz: have created a wiki but no repo yet
McCool: Resource on the Web&Networks IG
<McCool_> [17]https://www.w3.org/wiki/Networks
[17] https://www.w3.org/wiki/Networks
McCool: Other events for Agenda are T2TRG workshop and F2F in
helsinki
<McCool_>
[18]https://www.w3.org/WoT/IG/wiki/F2F_meeting,_6-11_June_2020,
_Helsinki
[18] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_6-11_June_2020,_Helsinki
<McCool_>
[19]https://github.com/w3c/wot/blob/master/proposals/wot-discov
ery.md
[19] https://github.com/w3c/wot/blob/master/proposals/wot-discovery.md
McCool: We have material in WoT repo. Propose to move it over
to new repo
... content should turn into W3C draft style
... prefer to collect use-cases/analyzes first
... at the moment is is *raw* material
... "Use cases" section is empty so far
... there are design options (at the moment 1 out of several)
... need to look into related standards, e.g. CORE resource
directory
... we have material but some parts are 2 years old
... suggest to break up single md file in multiple md files
... we look at end-user use-cases
... need to identify user
Ege: human user or also things discovering "other" things as
well?
McCool: Usually human user
Ege: Suggest making this clear (end-user focus)
Andrea: What is the range of the discovery?
McCool: Should grow out of requirements
... assumed multiple scales (peer-to-peer, local network,
global, ...)
... end-goal of discovery is discovering TDs
... need to have section in Architecture saying what is
discovery for
Andrea/McCool: disscovery should at least return TDs, .. might
be more, or parts
McCool: Did work in last few years on various forms... should
have a write-up for it, kind of a history
Kaz: agree, should clarify uses cases first
... as part of WoT architecture we have been working on uses
cases. need to think about how to work with Architecture task
force
McCool: Propose brainstorming first and maybe push use-cases
also to architecture
... I think we should follow architecture template
Kaz: and possibly could update the template for discovery
purposes
<McCool_>
[20]https://github.com/w3c/wot-architecture/blob/master/USE-CAS
ES/use-case-template.md
[20] https://github.com/w3c/wot-architecture/blob/master/USE-CASES/use-case-template.md
McCool: Some use-cases taken from MMI work
... suggest creating similar directory "USE-CASES" as in
wot-architecture
... "good" use-cases touch more (building blocks) than just
discovery
... please create PR for updates/changes
<McCool_> [21]https://github.com/w3c/wot
[21] https://github.com/w3c/wot
Kaz: Note, I've just created wot-discovery repo in the
meanwhile
<kaz> [22]wot-discovery repo
[22] https://github.com/w3c/wot-discovery
<McCool_> ACTION: McCool to copy over context from
wot/proposals/wot-discovery.md and break up into sections
<McCool_> ACTION: McCool to create directory for USE-CASES
<McCool_> ACTION: McCool to generate README.md in wot-discovery
for PR process, explanation of structure, etc
(some audio problem with McCool's line, and Daniel types in)
Daniel: w.r.t. to last action I suggest pointing to wot repo
and imrpove it if necessary
<McCool_> agree, will do pointer rather than a copy for PR
process
McCool: If people have uses cases in mind please create
sketches or issues
... next time we can discuss the issues (use-cases)
... Schedule, link for charter?
<kaz> [23]official charter
[23] https://www.w3.org/2020/01/wot-wg-charter.html
<kaz> [24]WG page also updated for that
[24] https://www.w3.org/WoT/WG/
McCool: charter speaks about goal ... local and global et
cetera
... if we feel we want to update the charter we can do so...
but needs formal procedure
... Discovery is on REC track
... completion expected for Q1 2021
<McCool_> ACTION: McCool to create revised schedule in the wiki
NOTE: We had further discussion about the publication schedule
during the main call on Feb 12, and decided we'll update the
[25]WoT main wiki to manage the publication schedule for all
the WoT deliverables.
[25] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Schedule
McCool: CR be end of the year 2020
... rather optimistic
... will update schedule for next week call
... If you encounter other groups doing discovery please bring
it up
... lets talk about upcoming events also next week
... plase add "future topics" to Agenda
Christopher: best entry point?
McCool: Suggest the wiki page
[26]WoT Discovery wiki
[26] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf
<kaz> [adjourned]
Summary of Action Items
[NEW] ACTION: kaz to create wot-discovery github repo
[NEW] ACTION: McCool to copy over context from
wot/proposals/wot-discovery.md and break up into sections
[NEW] ACTION: McCool to create directory for USE-CASES
[NEW] ACTION: McCool to create revised schedule in the wiki
[NEW] ACTION: McCool to generate README.md in wot-discovery for
PR process, explanation of structure, etc
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [27]scribe.perl version 1.154 ([28]CVS log)
$Date: 2020/02/18 14:12:07 $
[27] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[28] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 18 February 2020 14:14:04 UTC