- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 27 Apr 2020 13:11:56 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at: https://www.w3.org/2020/04/07-govtech-minutes.html also as text below. Thanks, Kazuyuki --- [1]W3C [1] http://www.w3.org/ - DRAFT - Govtech collab 07 Apr 2020 Attendees Present Kaz_Ashimura, Michael_McCool, Jennifer_Lin, Ege_Korkan, Kunihiko_Toumura Regrets Chair McCool Scribe kaz Contents * [2]Topics 1. [3]Changing the time? 2. [4]Agenda 3. [5]Prev minutes 4. [6]Use cases 5. [7]Next call * [8]Summary of Action Items * [9]Summary of Resolutions __________________________________________________________ Changing the time? proposal: move the time one hour earlier, check with Sebastian Agenda McCool: use cases discussion on fleet management, etc. Jennifer: once we get approval, we can describe the details McCool: np, for example, node-wot is not our standard itself ... we can still capture the use case itself Kaz: right. our focus is generating use case descriptions based on the needs, so implementation details don't need to be described ... getting feedback from your engineers would be helpful for improving use case descriptions, though McCool: (mentions some research work from Intel as well) Prev minutes [10]Mar-24 minutes [10] https://www.w3.org/2020/03/24-govtech-minutes.html McCool: (goes through the minutes) ... btw, we've been holding discussion on lifecycle ... during the architecture call Jennifer: missed the call last week McCool: also there is discussion on node-wot as well ... Philip Tran's name to be capitalized ... also the last part recorded by Kaz should have the same style Kaz: will fix it McCool: seems ok to me ... how about you? ... accurate and can be publicly published? Jennifer: don't think particularly sensitive McCool: you can review the minutes offline to make sure Jennifer: ok McCool: (mentions discussion on IETF Anima, etc., about onboarding) Jennifer: for us, onboarding is either sensors, etc., are installed by detected McCool: there are 3 different levels of keys ... the problem is some devices don't have embedded keys ... Oliver from Siemens is working on the discussion ... governmental keys, manufacturer keys and application keys ... we're still discussing that (during the WoT Security call) ... and time for node-wot here ... 3 issues here ... session is open to people at the moment ... developer support ... developer outreach might be done by Eclipse foundation, though ... then manage the process, and tutorials ... we'll discuss those points during the wot marketing call (after the discussion on the press release) Use cases <inserted> mm: would like make progress on use cases Jennifer: that is the only agenda item in my mind McCool: there are some like more generic like smart cities ... (mv old "govtech-gps-module.md" to "smartcity-localization.md") ... (mv old "govtech-health-monitor.md" to "smartcity-health-monitor.md") ... then ... (open "smartcity-health-monitor.md") (discussion based on the MD file) <McCool> [11]https://en.wikipedia.org/wiki/K-means_clustering [11] https://en.wikipedia.org/wiki/K-means_clustering McCool: will lead you some article on clustering (above) Jennifer: tx McCool: maybe useful for face detection ... and feature extraction Jennifer: btw, I don't mind providing this information itself ... Singapore is doing what US, etc., are doing ... maybe there are some clusters there ... detecting crowds to avoid people's getting too closely McCool: (updates the description) ... determine the number of people in an area and send a notification f crowded conditions are detected Jennifer: another use case for WoT might be face detection using cameras McCool: adds a note about that to the "Description" section Kaz: will you make a PR for this use case later? McCool: yes ... (puts Jennifer's name as the submitter of the use case) Jennifer: how does the location service detect location of PCs? McCool: using wifi hotspot information, etc. ... also people can be detected using camera's and the position can be reused ... senor fusion ... note necessarily GPS Jennifer: thermal sensor can be another possibility [12]https://www.w3.org/TR/geolocation-API/ [12] https://www.w3.org/TR/geolocation-API/ Kaz: e.g., geolocation api tries all the possible methods and will give geolocation information based on the sensors available McCool: (adds information about that) Kaz: note that the work was taken over by the Device and Sensors WG (as part of the generic sensor API) McCool: ok ... (refers to OGC's work as well) Kaz: thought Michael Lagally was also working on a geolocation-related use case McCool: that one and this use case should be merged in some way Jennifer: altitude is used to identify the floor of buildings? Kaz: altitude might be useful to identify overlapping highways, roads, railways and subways McCool: that's a good point ... (adds the concept on 2D location vs 3D location) Next call McCool: in 2 weeks Kaz: will allocate a new webex if it's ok by Sebastian [adjourned] Summary of Action Items Summary of Resolutions [End of minutes] __________________________________________________________ Minutes manually created (not a transcript), formatted by David Booth's [13]scribe.perl version 1.154 ([14]CVS log) $Date: 2020/04/27 04:10:35 $ [13] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [14] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 27 April 2020 04:11:46 UTC