RE: Joint Spatial Data on the Web (SDW) and Web of Things (WoT) Working Group session 23-Jun-2022, 13-14.00UTC

Hi.

Meeting details including joining instructions are here: https://www.w3.org/events/meetings/54fb3c39-8826-418b-bcac-46e112f08535/20220623T090000

Attached is an introductory presentation on WoT and geolocation discovery.

For more information on Web of Things, see: https://www.w3.org/WoT/

@michael - please can you forward this invitation to your WG members if the team-wot@w3.org<mailto:team-wot@w3.org> doesn't include everyone you need

Best regards, Jeremy

From: Tandy, Jeremy
Sent: 21 June 2022 09:59
To: public-sdw-wg@w3.org
Cc: Linda van den Brink <l.vandenbrink@geonovum.nl>
Subject: Joint Spatial Data on the Web (SDW) and Web of Things (WoT) Working Group session 23-Jun-2022, 13-14.00UTC


Joint Spatial Data on the Web (SDW) and Web of Things (WoT) Working Group session.

Thursday 23-June2022, 13:00-14:00 UTC



Hi SDW-ers. We are meeting with the WoT folk for a joint session on our regular monthly slot on Thursday. Details below. WoT-WG will benefit from your insight and experience around geospatial. They want to re-use what exists already (or is already under development). We need to help them connect their requirements to those standards.



Session objective:

(a) Define the geolocation deliverables for next WoT WG charter (2023 onwards). A starting list is here [1]. Use cases will guide what _kind_ of geolocation data we might need.

... Do we need velocity? Maybe, the use case is transportation or robotics.

... Do we need to identify topology? Maybe, if we are talking Building Information Management systems.

... Do we need to worry about visibility from given viewpoints?  Maybe, if the use case is AR.

...

(b) Agree schedule for routine checkpoint joint sessions and date of next meeting. Ongoing coordination is needed to ensure that WoT leverage existing geospatial standards and avoid creating new - especially around vocabularies/ontologies.



WoT gaps and future work are listed here [2].



WoT WG view is that GeoPose (limited to orientation?) and GeoSPARQL (missing a wat to access actual geolocation data in a consistent way?) don't cover all the use cases.



Looking forward to seeing you. Jeremy and Linda

(SDW-WG co-chairs)



...



[1]: Geospatial deliverables _may_ include the following

  1.  Geospatial discovery mechanisms (e.g. finding Things near a certain location)
  2.  Geospatial data encoding standards, for both metadata (Thing Descriptions) and dynamic data (here is a proposal, but it is only an outline): https://github.com/w3c/wot-discovery/blob/main/proposals/geolocation.md<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwot-discovery%2Fblob%2Fmain%2Fproposals%2Fgeolocation.md&data=05%7C01%7Cjeremy.tandy%40metoffice.gov.uk%7C0c3992f442ae4208714808da53096bf9%7C17f1816120d7474687fd50fe3e3b6619%7C0%7C0%7C637913597562466976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aio%2BYdr0PYpU21cmnR%2F%2Fq6NYK4cejvvDn4E1xFS53B8%3D&reserved=0>; may be necessary to enable 1.
  3.  Geospatial use cases (e.g. logistics, Smart City infrastructure management, etc.).  We have a set of use cases here, https://github.com/w3c/wot-usecases<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwot-usecases&data=05%7C01%7Cjeremy.tandy%40metoffice.gov.uk%7C0c3992f442ae4208714808da53096bf9%7C17f1816120d7474687fd50fe3e3b6619%7C0%7C0%7C637913597562466976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r7XqYMab8d9Ezdc9Xx%2FMzY8JeSjaqbCUSpENj%2BD5cIg%3D&reserved=0>, and recently did a review of gaps here, https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwot-usecases%2Fblob%2Fmain%2FUSE-CASES%2Fcoverage.csv&data=05%7C01%7Cjeremy.tandy%40metoffice.gov.uk%7C0c3992f442ae4208714808da53096bf9%7C17f1816120d7474687fd50fe3e3b6619%7C0%7C0%7C637913597562466976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z31fSGyJ2sHXAJETgOoJqYYJgvkajb%2BsnPzYV%2Bq8%2BJc%3D&reserved=0>, and it was clear that accounting for location is one of our biggest gaps.



[2]: Gaps and Future Work:

  *   GIS Integration
     *   Geospatial data and discovery
  *   Data Management
     *   Digital Twins and shadows
     *   Event notifications
     *   Historical data
  *   Security
     *   Key provisioning and onboarding
     *   Secure LAN access
     *   Proxy services
     *   Access control and ad-hoc sharing
     *   MUDS
  *   Accessibility
     *   Sensory modality mapping
     *   Textual/descriptive interfaces
     *   Service location
     *   Mobility services
  *   Advanced Use Cases
     *   Transportation
     *   Logistics
     *   Distributed energy management
     *   AR visualization
     *   Analytics integration e.g. for health and safety monitoring