12:59:18 <RRSAgent> RRSAgent has joined #wot-uc
12:59:18 <RRSAgent> logging to https://www.w3.org/2022/01/25-wot-uc-irc
12:59:24 <kaz> meeting: WoT Use Cases
13:00:58 <Antonio_Virdis_UniPI> Antonio_Virdis_UniPI has joined #wot-uc
13:02:44 <cperey> cperey has joined #wot-uc
13:03:10 <mlagally_> mlagally_ has joined #wot-uc
13:03:58 <CarloPuliafito> CarloPuliafito has joined #wot-uc
13:04:17 <cperey> present+ christine_perey
13:04:49 <McCool> McCool has joined #wot-uc
13:05:37 <Mizushima> Mizushima has joined #wot-uc
13:08:44 <cris_> cris_ has joined #wot-uc
13:09:35 <kaz> present+ Kaz_Ashimura, Antonio_Virdis_UniPisa, Carlo_Puliafito, Christine_Perey
13:10:17 <kaz> -> @@@
13:11:05 <kaz> s|https://www.w3.org/Consortium/Patent-Policy-20170801/ W3C Patent Policy|
13:11:34 <kaz> present+ Cristiano_Aguzzi, Enzo_Mingozzi, Michael_McCool, Tomoaki_Mizushima
13:12:05 <kaz> i/https/topic: Guests/
13:12:21 <kaz> rrsagent, make log public
13:12:31 <kaz> rrsagent, draft minutes
13:12:31 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz
13:12:50 <kaz> scribenick: cris_
13:13:16 <cris_> topic: document status
13:13:35 <kaz> present+ Ryuichi_Matsukura
13:13:47 <cris_> mc: we should check hyperlinks and identifies if they are references
13:14:08 <cris_> ml: ok should I assign you to this task?
13:14:10 <cris_> mc: fine
13:14:22 <cris_> ... it is a clean up activity
13:14:25 <cris_> ... not super critical
13:14:46 <kaz> -> https://github.com/w3c/wot-usecases/issues/178 Issue 178 - Check hyperlinks and convert to references if necessary
13:14:51 <cris_> ml: there's a minor issue in PR 175
13:15:30 <cris_> mc: not worry about it I fixed the reference to the real standard in other PR
13:16:43 <kaz> chair: Lagally
13:16:57 <kaz> rrsagent, draft miutes
13:16:57 <RRSAgent> I'm logging. I don't understand 'draft miutes', kaz.  Try /msg RRSAgent help
13:17:08 <kaz> s/rrsagent, draft miutes//
13:17:11 <kaz> rrsagent, draft minutes
13:17:11 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz
13:17:38 <cris_> ml: good work references seems good
13:17:52 <cris_> ... I think if there're smaller issues we can update later
13:18:03 <kaz> present+ Lorenzo_Gigli
13:18:05 <kaz> rrsagent, draft minutes
13:18:05 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz
13:18:32 <kaz> present+ Michael_McCool
13:18:32 <hyperloris> hyperloris has joined #wot-uc
13:18:34 <kaz> rrsagent, draft minutes
13:18:34 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz
13:18:57 <cris_> ml: line 8582 contains changes what have you done there
13:19:09 <cris_> mc: I re-organized the references
13:19:23 <cris_> ... and split them in categories
13:19:30 <cris_> ... added also comments
13:19:38 <kaz> i|line 8582|-> https://github.com/w3c/wot-usecases/pull/177 PR 177 - Update References|
13:20:07 <cris_> ml: no conflicts right?
13:20:08 <cris_> mc: no
13:20:21 <cris_> ml: ok I propose merging
13:20:26 <cris_> ... merged
13:21:07 <kaz> i|PR 175|-> https://github.com/w3c/wot-usecases/pull/175 PR 175 - Update Health Privacy Section|
13:21:26 <cris_> topic: Guests
13:22:09 <cris_> ml: Oracle, working on cloud technologies
13:22:17 <cris_> mc: co-chair of wot WG
13:22:35 <kaz> topic: Self introduction
13:22:43 <kaz> s/topic: Self introduction//
13:23:08 <kaz> i/Oracle/(WoT guys introduce themselves)/
13:23:22 <cris_> kaz: w3c team contact
13:23:54 <cris_> cris: IE, unibo research fellow working on WoT and IoT
13:25:03 <cris_> Carlo: research fellow University of Pisa invited for presenting a conference research work
13:25:16 <kaz> rrsagent, draft minutes
13:25:16 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz
13:25:22 <cris_> Matsukura: co-editor of use-case document
13:25:32 <kaz> s/Matsukura/Mizushima/
13:26:07 <cris_> virdis: Associate professor of University of Pisa
13:26:29 <cris_> Christine: Interoperability and geospatial expert
13:27:18 <cris_> lorenzo: Phd student, interested in wot and blockchain technologies
13:27:41 <cris_> topic: Carlo presentation
13:27:55 <cris_> s/Carlo/Carlo's/
13:27:57 <kaz> -> slides tbd@@@
13:28:22 <cris_> carlo: the work was done in the context of the Arrowhead tool project
13:28:35 <kaz> present+ Michael_Lagally
13:28:50 <cris_> ... we used standard WoT technologies: servients and scripting apis
13:29:05 <cris_> ... today I present you an use case in edge computing
13:29:38 <cris_> ... in the use case we have a patient with health sensors
13:30:13 <kaz> rrsagent, draft minutes
13:30:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz
13:30:27 <cris_> ... there are two software agents: a servient hosted in wearable devices and one in a gateway
13:31:28 <cris_> ... when the patient moves to the hospital the servient hosted on the gateway should move to a new node in the hospital
13:31:50 <cris_> ... where it can preserve its quality of service requirements
13:32:54 <kaz> q+ to discuss state management (later)
13:32:55 <cris_> ... now the problems are: state managment and addressing
13:33:54 <cris_> ... stateful migration can be transparent to the final wot application (preferable) or explicit
13:34:16 <cris_> ... when the servent migrate addresses need also to be updated
13:34:49 <cris_> Carlo showing a UML flow diagram about migration process
13:36:34 <cris_> carlo: when the exposer detect a migration it emit an event to the consumers
13:37:29 <McCool> q+
13:38:17 <cris_> ... on the other end if the consumer detects an ip change re observe/subscribe
13:38:24 <cris_> ... to all the affordances
13:38:37 <kaz> q- later
13:39:02 <cris_> mc: one note: webhooks and other protocols have the problem that when the ip changes the connection is broken
13:39:16 <cris_> Carlo showing the expiremental setup
13:40:19 <McCool> (still have some followup comment, pls leave me on the q)
13:40:37 <cris_> carlo: there are some executing time costs for the consumer side
13:41:06 <kaz> q+ to ask about the concrete scenario and device/network setting (e.g., HTTP, long polling, websocket, ...)
13:41:10 <cris_> ... we also measured the container downtime
13:41:21 <cris_> q+
13:41:57 <cris_> ... most of the downtime is due to the container migration time
13:42:33 <kaz> q?
13:42:35 <cris_> carlo: that's was all
13:42:38 <kaz> q- later
13:42:42 <cris_> ml: thank you, very interesting
13:42:55 <cris_> ... did you see any gaps?
13:43:08 <cris_> s/gaps/gaps in the specification/
13:43:21 <cris_> carlo: addressing might be a problem
13:43:32 <cris_> ... in wot adresses are considered to be static
13:44:46 <cris_> ... there are might be some security concerns when you migrate a container, how should those be handled?
13:44:51 <mlagally_> q?
13:45:03 <cris_> ml: thank you, we can talk about it offline
13:45:29 <cris_> mc: follow up, we are working on this problem also in the network working group
13:45:41 <cris_> ... I agree to have a follow up call
13:45:55 <cris_> ml: what about an use case description ?
13:47:24 <cris_> cris: how are you able to sent the onMigration event?
13:47:36 <cris_> carlo: we are using a reactive approach
13:48:08 <cris_> ... the servient detects a migration
13:48:15 <cris_> and event an event
13:48:44 <cris_> s/event an event/emits an event/
13:50:29 <kaz> q?
13:50:34 <kaz> ac mc
13:50:38 <kaz> ack cr
13:50:40 <cris_> ... we are using coap
13:50:46 <kaz> ack mc
13:50:50 <cris_> q+
13:50:52 <kaz> s/ac mc//
13:50:59 <kaz> q- later
13:51:25 <cris_> cris: thank you got it
13:51:37 <cris_> ml: the conversation is running long
13:51:48 <cris_> ... I think we should move to another call
13:52:03 <mlagally_> q?
13:52:23 <kaz> ack c
13:52:24 <kaz> ack k
13:52:24 <Zakim> kaz, you wanted to discuss state management (later) and to ask about the concrete scenario and device/network setting (e.g., HTTP, long polling, websocket, ...)
13:52:50 <McCool> (time check, we need to move onto Christine's topic)
13:53:13 <cris_> kaz: state management can be done in xml exchange manager
13:53:34 <kaz> -> https://www.w3.org/TR/scxml/ SCXML
13:53:35 <kaz> -> https://www.w3.org/TR/mmi-arch/ MMI Architecture
13:53:57 <cris_> ... plus a detailed use case description should be defined
13:54:25 <cris_> ... like data model, flow and protocols
13:54:29 <kaz> s|xml exchange manager|SCXML-based Interaction Manager, but we should have further discussion next time./
13:54:55 <cris_> topic: Geospatial community
13:55:06 <kaz> s/description should be defined/scenarios should be described./
13:55:14 <cris_> christine: there's a new standard wg in the IEEE
13:55:21 <cris_> ... they are working in the spatial web
13:55:38 <cris_> ... on December they approved the first internal draft
13:55:42 <McCool> https://sagroups.ieee.org/2874/
13:55:54 <cris_> ... it is highly relvevant to connected things
13:56:13 <cris_> ... the second item is the open geospatial consortium
13:56:33 <kaz> s/https/-> https/
13:56:42 <cris_> ... THE most popular work  in the geospatial communty come from OGC
13:56:43 <kaz> s|2874/|2874/
13:56:43 <kaz> IEEE P2874 Spatial Web, Architecture and Governance Working Group|
13:56:58 <kaz> s/it is hi/chrstine: it is hi/
13:57:05 <cris_> ... on relevant work is geo posting
13:57:15 <cris_> ... it contains information also about orientation
13:57:30 <cris_> ... it uses also time
13:58:15 <cris_> ... the spec is trying to prevent the creation of different formats for indicating an orientation (i.e. in the context of building enviroments/ smart vehicles)
13:58:34 <cris_> ml: I read the standard, a follow up meeting would be good about this topic
13:58:54 <cperey> https://github.com/opengeospatial/GeoPose/blob/main/standard/pdf/geopose_standard.pdf
13:58:57 <cris_> ... we need more time to collect ides and how it can be used inside wot
13:59:09 <kaz> i/geo psting/geo posing/
13:59:21 <kaz> s/geo posing/geopose/
13:59:38 <cris_> ml: in general geo posing does not really fit all our use cases
13:59:49 <cris_> ... we need to integrate with other solutions
14:00:08 <cris_> christine: ogc would be glad to ear any limits of the standard
14:00:18 <cperey> IEEE P2874 WG   2:55  PM https://sagroups.ieee.org/2874/
14:00:24 <cris_> ... and understand how it can be integrated with other solutions
14:00:52 <cris_> ml: we are at the hour, can we continue in the next use case call
14:00:53 <cperey> Thank you for letting me know when to have an interim meeting, one week from today, I can also invite others
14:00:54 <cris_> mc: good
14:00:58 <cris_> ml: aob ?
14:01:42 <cris_> adjourned
14:01:52 <kaz> rrsagent, draft minutes
14:01:52 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/25-wot-uc-minutes.html kaz