12:02:39 RRSAgent has joined #wot-discovery 12:02:43 logging to https://www.w3.org/2024/03/25-wot-discovery-irc 12:03:13 meeting: WoT Discovery 12:03:24 chair: McCool 12:03:26 ktoumura has joined #wot-discovery 12:03:38 present+ Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura 12:04:20 Tomo has joined #wot-discovery 12:05:42 present+ Tomoaki_Mizushima 12:06:54 scribenick: kaz 12:07:11 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#25_March_2024 12:07:16 topic: Minutes 12:07:24 -> https://www.w3.org/2024/03/18-wot-discovery-minutes.html Mar-18 12:07:32 mm: (goes through the minutes) 12:07:47 approved 12:07:54 topic: DID Registry 12:08:27 -> https://github.com/w3c/did-spec-registries/pull/486 did-spec-registries PR 486 - Add WotThing and WotDirectory service types 12:08:32 mm: one pending review 12:08:58 topic: AOB 12:09:16 mm: we had a meeting with the NGSI-LD guys on Friday 12:09:56 ... one thing interesting is there capability to handle geolocation information 12:09:58 q+ 12:10:09 ... the question is what would fit WoT as a use case 12:11:03 ETSI GS CIM 009 V1.1.1 (2019-01) section 4.10 - NGSI-LD geo-query language 12:11:21 https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.01.01_60/gs_CIM009v010101p.pdf 12:12:07 kaz: think we as the WoT WG/IG should think about concrete use cases about how to handle geolocation information 12:13:10 mm: another question is whether we really want to handle geolocation details within WoT or reuse existing mechanism like NGSI-LD 12:13:13 kaz: right 12:13:26 ... that should be discussed as part of the use case discussion 12:13:32 mm: exactly 12:13:39 [adjourned] 12:13:43 rrsagent, make log public 12:13:52 rrsagent, draft minutes 12:13:53 I have made the request to generate https://www.w3.org/2024/03/25-wot-discovery-minutes.html kaz 13:01:04 McCool has left #wot-discovery 14:22:17 Zakim has left #wot-discovery