BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20220623T002957Z
BEGIN:VTIMEZONE
TZID:America/New_York
X-MICROSOFT-CDO-TZID:10
BEGIN:STANDARD
DTSTART:20211107T060000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:STANDARD
DTSTART:20221106T060000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20220313T070000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:54fb3c39-8826-418b-bcac-46e112f08535
DTSTAMP:20220623T002957Z
SUMMARY:Joint SDW-WoT WG session
DTSTART;TZID=America/New_York:20220623T090000
DTEND;TZID=America/New_York:20220623T100000
DESCRIPTION:https://www.w3.org/events/meetings/54fb3c39-8826-418b-bcac-46e1
 12f08535/20220623T090000/\n\nSession objectives: \n(a) Define the geolocat
 ion deliverables for next WoT WG charter (2023 onwards). A starting list i
 s here [1]. Use cases will guide what _kind_ of geolocation data we might 
 need. \n… Do we need velocity? Maybe\, the use case is transportation or
  robotics.\n… Do we need to identify topology? Maybe\, if we are talking
  Building Information Management systems.\n… Do we need to worry about v
 isibility from given viewpoints?  Maybe\, if the use case is AR.\n…\n(b)
  Agree schedule for routine checkpoint joint sessions and date of next mee
 ting. Ongoing coordination is needed to ensure that WoT leverage existing 
 geospatial standards and avoid creating new - especially around vocabulari
 es/ontologies.\n \nWoT gaps and future work are listed here [2].\n \nWoT W
 G view is that GeoPose (limited to orientation?) and GeoSPARQL (missing a 
 wat to access actual geolocation data in a consistent way?) don't cover al
 l the use cases.\n\nLooking forward to seeing you. Jeremy and Linda \n(SDW
 -WG co-chairs)\n\n…\n \n[1]: Geospatial deliverables _may_ include the f
 ollowing\n1.	Geospatial discovery mechanisms (e.g. finding Things near a c
 ertain location)\n2.	Geospatial data encoding standards\, for both metadat
 a (Thing Descriptions) and dynamic data (here is a proposal\, but it is on
 ly an outline): https://github.com/w3c/wot-discovery/blob/main/proposals/g
 eolocation.md\; may be necessary to enable 1.\n3.	Geospatial use cases (e.
 g. logistics\, Smart City infrastructure management\, etc.).  We have a se
 t of use cases here\, https://github.com/w3c/wot-usecases\, and recently d
 id a review of gaps here\, https://github.com/w3c/wot-usecases/blob/main/U
 SE-CASES/coverage.csv\, and it was clear that accounting for location is o
 ne of our biggest gaps.\n \n[2]: Gaps and Future Work:\n•	GIS Integratio
 n\no	Geospatial data and discovery\n•	Data Management\no	Digital Twins a
 nd shadows\no	Event notifications\no	Historical data\n•	Security\no	Key 
 provisioning and onboarding\no	Secure LAN access\no	Proxy services\no	Acce
 ss control and ad-hoc sharing\no	MUDS\n•	Accessibility\no	Sensory modali
 ty mapping\no	Textual/descriptive interfaces\no	Service location\no	Mobili
 ty services\n•	Advanced Use Cases\no	Transportation\no	Logistics\no	Dist
 ributed energy management\no	AR visualization\no	Analytics integration e.g
 . for health and safety monitoring\n\nAgenda\n\nThe meeting focuses on a d
 iscussion starter about how the SDW-WG and Web of Things WG might collabor
 ate for WoT Geospatial\n\nAgenda: \n- Introduction of WoT Geospatial plans
  by Michael McCool\n- Discussion\n- Planning for inter-WG coordination\n- 
 AoB
STATUS:CONFIRMED
CREATED:20220610T065538Z
LAST-MODIFIED:20220623T002957Z
SEQUENCE:0
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Spatio-temporal Da
 ta on the Web Working Group:mailto:public-sdw-wg@w3.org
RECURRENCE-ID;TZID=America/New_York:20220623T090000
END:VEVENT
END:VCALENDAR