W3C

- DRAFT -

WoT PoC

07 Jul 2020

Attendees

Present
Kaz_Ashimura, Jennifer_Lin, Michael_McCool, Kunihiko_Toumura, Tomoaki_Mizushima
Regrets
Chair
McCool
Scribe
kaz

Contents


<McCool> todo - robotics followup, use cases for remote sensing, water management

Quick update

<jennifer> SPOTON were featured in this OECD spotlight article: https://trends.oecd-opsi.org/trend-reports/innovative-covid-19-solutions/

<jennifer> If you click on the "Download" button and search for "SPOTON" in the pdf.

<jennifer> https://trends.oecd-opsi.org/wp-content/uploads/2020/07/OECD_2020-Report-Book-v2.pdf (Or here)

<jennifer> SPOTON is GovTech's intended PoC for WoT.

<jennifer> SPOTON already is in production, but it doesn't fully support WoT yet

Prev minutes

June-9

Jennifer: wondering about the geolocation information

McCool: put updates on geolocation to the use cases
... anyway, ok with the minutes themselves?

Jennifer: nothing sensitive or anything

McCool: accepted

geolocation

<McCool> https://github.com/w3c/wot-architecture/issues/456

McCool: there was general discussion on geolocation
... also accuracy of geolocation information
... SSN standard defines accuracy, precision and resolution

SSN

McCool: also Basic Geo Vocabulary by Dan Brickley

Basic Geo Vocabulary

McCool: and World Geodetic System

World Geodetic System - Wikipedia

<McCool> https://www.w3.org/TR/geolocation-API/#coordinates_interface

McCool: Coordinates interface definition from the Geolocation API Spec 2nd Edition
... we have an API definition for geolocation here
... however, need to talk with the DAS WG guys

https://w3c.github.io/geolocation-sensor/#geolocationsensor-interface Generic Sensor API - Geolocation sensor

ISO119-2:2016 Geographic information

Kaz: some updates about geolocation api (by DASWG) and geolocation information accuracy (by ISO) above

McCool: ok

<McCool> https://w3c.github.io/hr-time/#dom-domhighrestimestamp

Issue 456

McCool: possible issue on high resolution time stamp

Kaz: yeah, related issue on who would manage the clock

McCool: (adds comments to Issue 456)

comment 1

comment 2

comment 3

comment 4

McCool: good to have joint discussion with the DASWG during TPAC

Kaz: definitely

McCool: would like to polish the geolocation use case description
... will create a separate use case about time and accuracy
... note that the goal here is not re-inventing the wheel
... geolocation information itself, time, accuracy and SSN
... SSN is kind of complicated and need to think about how to use it
... also how to map the geolocation information from the geolocation api with the smart city dashboard

Jennifer: yeah

McCool: another use case I'm interested is the mapping
... even for static sensor for measurement as well

Kaz: we need to think about "Web browser as a WoT Servient" for that purpose as well

McCool: yeah
... let's discuss mapping during the next meeting

Jennifer: the eventual goal should include reusing the existing map services like Google Maps as well

McCool: ok, let's defer that to the next meeting
... data visualization is another viewpoint
... also what the possible limitation with iotschema, etc.

[adjourned]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/07/07 13:28:20 $