IRC log of wot on 2021-10-14
Timestamps are in UTC.
- 00:28:06 [dsr]
- dsr has joined #wot
- 01:29:09 [dsr]
- dsr has joined #wot
- 02:30:15 [dsr]
- dsr has joined #wot
- 03:31:40 [dsr]
- dsr has joined #wot
- 03:56:16 [kaz]
- kaz has joined #wot
- 04:32:22 [dsr]
- dsr has joined #wot
- 05:13:57 [zkis]
- zkis has joined #wot
- 05:33:24 [dsr]
- dsr has joined #wot
- 06:00:22 [dsr]
- dsr has joined #wot
- 07:19:29 [dsr]
- dsr has joined #wot
- 07:37:32 [dsr]
- dsr has joined #wot
- 07:53:40 [dsr]
- dsr has joined #wot
- 08:27:15 [zkis]
- zkis has joined #wot
- 11:10:22 [dsr]
- dsr has joined #wot
- 11:11:05 [zkis]
- zkis has joined #wot
- 11:23:35 [McCool]
- McCool has joined #wot
- 11:32:06 [dsr]
- dsr has joined #wot
- 11:53:19 [dsr]
- dsr has joined #wot
- 11:57:49 [takio]
- takio has joined #wot
- 11:58:00 [kaz]
- rrsagent, bye
- 11:58:00 [RRSAgent]
- I see no action items
- 11:58:10 [RRSAgent]
- RRSAgent has joined #wot
- 11:58:10 [RRSAgent]
- logging to https://www.w3.org/2021/10/14-wot-irc
- 11:58:21 [kaz]
- meeting: WoT Open Day - Day 2
- 11:58:45 [kaz]
- present+ Kaz_Ashimura, Van_Cu_Pham
- 11:59:01 [kaz]
- present+ Takio_Yamaoka, Arturo_Romero
- 11:59:38 [kaz]
- present+ Tetsushi_Matsuda
- 11:59:56 [kaz]
- present+ Hiroshi_Ota
- 12:00:05 [kaz]
- present+ Michael_McCool
- 12:00:34 [kaz]
- present+ Kunihiko_Toumura
- 12:00:39 [ktoumura]
- ktoumura has joined #wot
- 12:02:05 [kaz]
- present+ Gabriel_Romero
- 12:02:11 [kaz]
- present+ Ege_Korkan
- 12:02:26 [kaz]
- present+ Miguel_Romero
- 12:02:32 [Mizushima]
- Mizushima has joined #wot
- 12:02:36 [kaz]
- present+ Michael_Koster, Tomoaki_Mizushima
- 12:02:53 [McCool]
- McCool has joined #wot
- 12:03:02 [mjk]
- mjk has joined #wot
- 12:03:28 [kaz]
- agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2021#Oct_14_-_Open_Day
- 12:03:30 [ota]
- ota has joined #wot
- 12:03:35 [Gabriel_Romero]
- Gabriel_Romero has joined #wot
- 12:03:46 [matsuda]
- matsuda has joined #wot
- 12:04:25 [kaz]
- present+ Andrea_Cimmino, Daniel_Peintner
- 12:04:37 [Pham]
- Pham has joined #wot
- 12:04:38 [Ege]
- Ege has joined #wot
- 12:05:03 [dape]
- dape has joined #wot
- 12:05:46 [kaz]
- topic: Scribe
- 12:05:52 [kaz]
- kaz and tbd
- 12:06:02 [kaz]
- i/kaz/scribenick: kaz/
- 12:06:10 [kaz]
- topic: Agenda
- 12:06:43 [kaz]
- -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2021-10-online-f2f/2021-10-14-WoT-OpenDay-McCool.pdf McCool's slides
- 12:06:57 [kaz]
- mm: (goes though the agenda slides)
- 12:07:22 [kaz]
- ... ECHONET, SDW, brak and Netzo
- 12:07:34 [kaz]
- topic: Guests
- 12:07:50 [kaz]
- -> https://www.w3.org/Consortium/Patent-Policy-20170801/ W3C Patent Policy
- 12:08:02 [kaz]
- mm: please be aware of the W3C Patent Policy above
- 12:08:10 [kaz]
- ... also the minutes will be publicly published
- 12:08:23 [kaz]
- present+ Kotis_K
- 12:08:39 [kaz]
- mm: resources
- 12:08:48 [kaz]
- .. Wiki and Presentations
- 12:09:05 [kaz]
- -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2021 vF2F wiki
- 12:09:21 [kaz]
- -> https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-10-online-f2f presentation area
- 12:09:30 [dsr]
- dsr has joined #wot
- 12:09:31 [kaz]
- mm: please upload your slides there
- 12:09:37 [kaz]
- ... PDF preferred
- 12:10:07 [kaz]
- present+ Philipp_Blum, Sebastian_Kaebisch
- 12:10:18 [kaz]
- present+ Fady_Salama
- 12:10:43 [kaz]
- topic: Self intro
- 12:10:57 [kaz]
- ar: Arturo Romero, CEO of Netzo
- 12:11:12 [kaz]
- s/Self/Guests' self/
- 12:12:07 [kaz]
- ... Miguel and Gabriel also from Netzo
- 12:12:22 [kaz]
- ho: Hiroshi Ota from Yahoo Japan
- 12:13:05 [kaz]
- present+ Konstantinos_Kotis
- 12:13:44 [kaz]
- mm: Van_Cu_Pham from ECHONET
- 12:13:57 [kaz]
- ty: Takio Yamaoka from Yahoo Japan
- 12:14:11 [kaz]
- topic: ECHONET
- 12:14:26 [cris]
- cris has joined #wot
- 12:14:26 [kaz]
- -> @@@slides
- 12:14:53 [kaz]
- tm: tx for giving this opportunity
- 12:15:15 [kaz]
- ... ECHONET Consortium Liaison Activity
- 12:15:18 [kaz]
- ... Agenda
- 12:15:25 [kaz]
- ... liaison acitivities
- 12:15:29 [kaz]
- ... plugfest results
- 12:15:45 [kaz]
- ... mapping ECHONET Device Description
- 12:16:02 [kaz]
- ... starting with Liaison activities
- 12:16:07 [kaz]
- ... Use Case Proposal
- 12:16:16 [kaz]
- ... Leaving and Coming Home
- 12:16:18 [sebastian]
- sebastian has joined #wot
- 12:16:46 [kaz]
- ... (goes through the ECHONET use case which is already included in the Use Cases draft)
- 12:16:49 [kaz]
- ... Plugfest
- 12:17:01 [kaz]
- ... provided four ECHONET Lite devices
- 12:17:06 [kaz]
- ... via intermediary
- 12:17:44 [kaz]
- ... LED, air conditioner, illuminance sensor, temperature sensor
- 12:17:50 [kaz]
- ... developed by Pham-san
- 12:18:00 [kaz]
- ... Plugfest Results (1)
- 12:18:18 [kaz]
- ... Hitachi connected to the Echonet dvices using Nod-RED
- 12:18:30 [kaz]
- ... Fujitsu also connected using their local proxy
- 12:18:34 [kaz]
- ... TUM also
- 12:18:43 [kaz]
- ... Plugfest Results (2)
- 12:18:53 [kaz]
- ... Toumura-san raised some issue
- 12:19:08 [kaz]
- ... on direct access to the ECHONET Lite Web API
- 12:19:18 [kaz]
- present+ Cristiano_Atuzzi
- 12:19:28 [kaz]
- present+ Michael_Lagally
- 12:19:59 [kaz]
- ... for this plugfest, we access ECHONET device via a gateway, though
- 12:20:05 [ryuichi]
- ryuichi has joined #wot
- 12:20:27 [kaz]
- ... by adding the encapsulating object schema, it might be possible to accept it directly
- 12:20:33 [sebastian]
- q+
- 12:20:39 [kaz]
- ... that proposal can be an option
- 12:21:09 [kaz]
- ... however, not sure how to handle the value combination, e.g., "rgb"
- 12:21:39 [kaz]
- ... the real property value is "r" something, "g" something and "b" something
- 12:21:52 [kaz]
- ... Mapping ECHONET Device Description to TD
- 12:22:03 [kaz]
- ... Example: General Lighting (1)
- 12:22:12 [kaz]
- ... DD on the left side and TD on the right side
- 12:22:31 [kaz]
- present+ Ryuichi_Matsukura
- 12:22:38 [kaz]
- rrsagent, make log public
- 12:22:42 [kaz]
- rrsagent, draft minutes
- 12:22:42 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/14-wot-minutes.html kaz
- 12:23:06 [kaz]
- present+ Youngmin_Ji
- 12:23:51 [kaz]
- ... binding template is additionally generated for TD
- 12:24:24 [McCool]
- q+
- 12:24:24 [kaz]
- ... e.g., "op" with "readallproperties"
- 12:24:37 [kaz]
- ... Summary of mapping from DD to TD
- 12:25:01 [kaz]
- ... @context for ECHONET Lite Web API added
- 12:25:25 [kaz]
- ... "id" in TD generated automatically based on "deviceType" and "deviceId"
- 12:25:31 [KiK]
- KiK has joined #wot
- 12:25:41 [kaz]
- ... "title" taken from "deviceType"
- 12:25:56 [kaz]
- ... HTTP message translation
- 12:26:03 [kaz]
- ... Read One Property
- 12:26:32 [Miguel]
- Miguel has joined #wot
- 12:26:44 [kaz]
- .. WoT on the left side and ECHOENT on the right side
- 12:27:04 [kaz]
- ... translate the target path if needed
- 12:27:26 [kaz]
- ... read request, read response
- 12:27:28 [kaz]
- ... then
- 12:27:37 [kaz]
- ... write request, write response
- 12:27:58 [dsr]
- dsr has joined #wot
- 12:27:59 [kaz]
- ... translate the target path if needed
- 12:28:20 [kaz]
- ... translate the HTTP body to property/value pair
- 12:28:43 [kaz]
- ... then return empty HTTP body with code 200 OK
- 12:29:31 [kaz]
- ... ECHONET has updated property, though
- 12:29:42 [kaz]
- ... Summary of the HTTP Message Translation
- 12:29:57 [kaz]
- ... target path of read and write request is translated if needed
- 12:30:15 [kaz]
- ... ECHOENT Lite Web API reads response HTTP message body
- 12:30:21 [kaz]
- ... thanks
- 12:30:23 [kaz]
- q?
- 12:30:40 [McCool]
- q?
- 12:30:47 [kaz]
- sk: tx!
- 12:30:54 [kaz]
- ... question about slide 8
- 12:30:58 [kaz]
- ... payload structure
- 12:31:42 [kaz]
- ... "PlugFest Result (2)"
- 12:32:03 [kaz]
- ... client requests the RGB value
- 12:32:20 [kaz]
- ... and the question is how the payload structure is like
- 12:32:42 [kaz]
- ... similar problem with Philips Hue as well
- 12:32:51 [kaz]
- ... what can we do using TD?
- 12:33:22 [kaz]
- ... subprotocol problem or binding template problem?
- 12:33:27 [mlagally_]
- mlagally_ has joined #wot
- 12:33:31 [kaz]
- ... we need to clarify the situation
- 12:33:38 [kaz]
- ... and then improve the specs
- 12:33:40 [mlagally_]
- q?
- 12:33:52 [mjk]
- q?
- 12:33:53 [kaz]
- tm: personally think it's issue with binding templates
- 12:34:15 [Ege]
- q+
- 12:34:22 [kaz]
- q+
- 12:34:42 [mlagally_]
- q+
- 12:34:49 [kaz]
- ... using sub protocol might be a feasible option, though
- 12:35:23 [kaz]
- ask se
- 12:35:27 [kaz]
- ack se
- 12:35:32 [kaz]
- s/ask se//
- 12:35:56 [kaz]
- mm: agree we definitely need clarification
- 12:36:01 [kaz]
- ... my question is about p9
- 12:36:09 [kaz]
- ... Example: General Lighting (1)
- 12:36:40 [kaz]
- ... issue about the ID
- 12:37:06 [kaz]
- ... this time "echonet" prefix is used
- 12:37:16 [kaz]
- ... need some clean up
- 12:37:23 [kaz]
- tm: tx for your comment
- 12:37:33 [kaz]
- ... I appreciate it
- 12:37:45 [kaz]
- ... no detailed discussion how to generate the ID
- 12:37:53 [kaz]
- ... so this is just an example
- 12:37:54 [mjk]
- I'm confused by the payload issue. Why is { "r": 20, "g": 200, "b"10 } acceptable where { "brightness": 80 } is not
- 12:38:26 [kaz]
- q+ mjk
- 12:38:57 [kaz]
- mm: my second point is, should the "id" be always a URL?
- 12:39:19 [kaz]
- ... that's rather a question to myself
- 12:39:24 [kaz]
- q?
- 12:39:26 [kaz]
- ack mc
- 12:39:30 [kaz]
- ack ege
- 12:39:34 [kaz]
- ek: tx
- 12:39:37 [kaz]
- ... very detailed
- 12:39:58 [kaz]
- ... payload on p7
- 12:40:04 [kaz]
- ... schema problem?
- 12:40:08 [dsr]
- dsr has joined #wot
- 12:40:15 [kaz]
- tm: this was proposal from Toumura-san
- 12:40:20 [ark_]
- ark_ has joined #wot
- 12:40:40 [arturo_romero_netzo]
- arturo_romero_netzo has joined #wot
- 12:41:23 [kaz]
- ek: highly indesirable for an intermediary to process the conversion
- 12:41:36 [kaz]
- ... counter requirement for interoperability
- 12:41:51 [kaz]
- ... put the full schema
- 12:42:08 [kaz]
- ... for consumer to consider
- 12:42:10 [kaz]
- q?
- 12:42:18 [cris]
- +1
- 12:42:26 [kaz]
- tm: yeah, that's right
- 12:43:20 [kaz]
- ... ECHONET Lite Web API's Device Description describes {"r": 20, "g": 255, "b": 0}
- 12:43:44 [kaz]
- ek: what part of the properties to be converted is handled by the Binding
- 12:44:00 [kaz]
- tm: thanks to Toumura-san, we've noticed this issue
- 12:44:15 [McCool]
- ack k
- 12:46:15 [kaz]
- kaz: we should continue to think about variety of property structure from existing standards
- 12:46:21 [McCool]
- ack ml
- 12:46:35 [kaz]
- ... should look into exsiting mechanisms and then think about how to solve the problem
- 12:46:50 [kaz]
- ml: Oracle Cloud IoT platform
- 12:47:03 [kaz]
- ... also handled RGB mapping
- 12:47:17 [kaz]
- ... encoding the structure into property combination
- 12:47:29 [kaz]
- ... so this is my second time to see this issue
- 12:47:36 [kaz]
- s/exsiting/existing/
- 12:48:03 [kaz]
- ... we should this as one of the specific examples to solve the issues
- 12:48:16 [kaz]
- ... would agree we need to solve this issue for TD
- 12:48:18 [kaz]
- q?
- 12:48:46 [kaz]
- mjk: tx for ECHONET to participate first :)
- 12:48:52 [kaz]
- ... potential endpoint for WoT
- 12:49:00 [kaz]
- ... great presentation
- 12:49:10 [kaz]
- ... need discussion for this issue
- 12:49:25 [kaz]
- ... my assumption is data schema part of TD is on the wire
- 12:49:42 [kaz]
- ... agree the problem is a long-standing one
- 12:49:44 [mlagally_]
- ./property combination/property combination: rgb_r, rgb_g, rgb_b/
- 12:49:49 [mlagally_]
- s/property combination/property combination: rgb_r, rgb_g, rgb_b/
- 12:50:06 [kaz]
- ... information model
- 12:50:24 [kaz]
- ... we do need to have a sort of abstract data schema
- 12:50:27 [kaz]
- ... unbound way
- 12:50:37 [kaz]
- ... and another wired schema
- 12:50:49 [mlagally_]
- s/solve this issue for TD/solve this specific issue of encoding a rgb color in the TD/
- 12:50:58 [kaz]
- ... maybe protocol binding used for the conversion
- 12:51:03 [mjk]
- ack mjk
- 12:51:12 [McCool]
- q?
- 12:51:19 [kaz]
- tm: thank YOU for your comment
- 12:51:28 [kaz]
- ... defining schema in abstract format?
- 12:51:52 [Ege]
- q+
- 12:52:01 [kaz]
- ... and another wire data schema
- 12:52:15 [kaz]
- ... that is the purpose of the binding. right?
- 12:52:26 [kaz]
- mjk: data schema was part of binding originally
- 12:52:34 [kaz]
- ... but getting another view
- 12:52:58 [kaz]
- ... semantic schema never changes but protocol schema could change
- 12:53:03 [kaz]
- tm: I see
- 12:53:06 [kaz]
- q?
- 12:53:12 [kaz]
- ack e
- 12:53:33 [kaz]
- ek: ECHONET can write a binding template?
- 12:53:35 [cris]
- I like mjk proposed solution. +1 we already have schemas on forms with additionalExpectedResponses
- 12:53:43 [kaz]
- tm: can't answer right now
- 12:54:01 [kaz]
- ... need discussion on the ECHONET side
- 12:54:09 [kaz]
- ... and would like to continue via the liaison
- 12:54:10 [kaz]
- q_
- 12:54:12 [kaz]
- q+
- 12:54:16 [kaz]
- s/q_//
- 12:55:37 [McCool]
- q?
- 12:55:46 [kaz]
- kaz: we should simply ask matsuda san and ECHONET to work with us to improve the Binding Template Note
- 12:55:49 [kaz]
- ek: ok
- 12:56:25 [kaz]
- tm: let's continue the discussion offline
- 12:56:28 [kaz]
- kaz: ok
- 12:56:36 [kaz]
- mm: should wrap up
- 12:57:11 [kaz]
- ... seems SDW group has issue on WebEx connection
- 12:57:23 [kaz]
- ... so would suggest we take break earlier
- 12:57:48 [kaz]
- [10-min break]
- 12:57:54 [kaz]
- rrsagent, draft minutes
- 12:57:54 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/14-wot-minutes.html kaz
- 13:05:02 [ScottSimmons]
- ScottSimmons has joined #wot
- 13:05:14 [PeterRushforth]
- PeterRushforth has joined #wot
- 13:05:23 [jtandy]
- jtandy has joined #wot
- 13:05:37 [RobSmith]
- RobSmith has joined #wot
- 13:05:38 [Linda_van_den_Brink]
- Linda_van_den_Brink has joined #wot
- 13:05:38 [jtandy]
- present+ jtandy
- 13:05:42 [ScottSimmons]
- present+ ScottSimmons
- 13:06:17 [Linda_van_den_Brink]
- present+ Linda_van_den_Brink
- 13:06:24 [PeterRushforth]
- present+
- 13:06:36 [RobSmith]
- present+ RobSmith
- 13:08:36 [kaz]
- topic: Preliminary for the SDW collaboration
- 13:09:00 [kaz]
- topic: TD issue based on ECHONET discussion
- 13:09:05 [kaz]
- s/topic: Preliminary for the SDW collaboration//
- 13:09:24 [kaz]
- ek: would create a TD issue unless somebody else would
- 13:09:33 [kaz]
- mm: go ahead and put the URL here on the IRC
- 13:09:44 [kaz]
- topic: SDW collaboration
- 13:10:09 [kaz]
- jt: Jeremy Tandy, the Chair of the SDW group (co-Chair is Linda)
- 13:10:23 [kaz]
- ... collaborating with OGC
- 13:10:41 [kaz]
- ... Scott and Linda also here
- 13:11:23 [kaz]
- linda: Linda van den Brink from Geonovum
- 13:11:29 [kaz]
- ... member of W3C and also OGC
- 13:11:45 [kaz]
- ... chairing the SDW group with Scott
- 13:11:52 [kaz]
- s/Scott/Jeremy/
- 13:12:06 [kaz]
- ... Scott, you can also introduce yourself
- 13:12:18 [kaz]
- Scott: Scott Simmons from OGC
- 13:12:54 [kaz]
- jt: a few more people from SDW
- 13:13:07 [kaz]
- br: Bill Roberts
- 13:13:18 [kaz]
- ... very interested to here
- 13:13:26 [kaz]
- pr: Peter Rushforth
- 13:13:27 [sebastian]
- sebastian has joined #wot
- 13:13:51 [kaz]
- rs: Rob Smith
- 13:14:45 [kaz]
- roba: Rob @@@ from OGC
- 13:15:16 [kaz]
- jvu: Joost van Ulden
- 13:15:43 [kaz]
- topic: Note for guests
- 13:15:55 [kaz]
- mm: please be aware of the W3C Patent Policy
- 13:16:05 [kaz]
- topic: Spatial Data on the Web and WoT Geolocation
- 13:16:15 [kaz]
- mm: (shows the slides)
- 13:16:33 [kaz]
- i|shows|-> https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-10-online-f2f McCool's slides|
- 13:16:40 [kaz]
- ... WoT working on discovery as well
- 13:16:49 [kaz]
- ... including geospatial discovery
- 13:17:01 [kaz]
- ... want to integrate with the existing standards
- 13:17:08 [kaz]
- ... and include best practices
- 13:17:28 [kaz]
- ... use cases are smart cities, smart homes, automotives, etc.
- 13:17:45 [kaz]
- ... geolocation data to cover various use cases
- 13:18:07 [kaz]
- ... include data description or getting that from the device (or both)
- 13:18:16 [kaz]
- ... Geolocation Project Report
- 13:18:39 [kaz]
- ... geolocation requirements have been discussed
- 13:18:49 [kaz]
- ... also issue with query
- 13:19:07 [kaz]
- s/also/encoding of geolocation data. also/
- 13:19:18 [kaz]
- ... creating a group Note
- 13:19:34 [kaz]
- ... how to encode and use geolocation data for WoT purposes
- 13:19:42 [kaz]
- ... develop a working document
- 13:20:02 [kaz]
- ... presentation on Monday, Oct 11 about smart building
- 13:20:18 [kaz]
- ... also requirements from Singapore
- 13:20:27 [kaz]
- ... we need to collaborate (with SDW)
- 13:20:39 [kaz]
- ... Collaborations Needed
- 13:20:59 [kaz]
- ... concrete set of recommendations needed
- 13:21:23 [kaz]
- ... Next Steps
- 13:21:30 [kaz]
- ... some proposals myself
- 13:21:42 [kaz]
- ... but would ask the SDW group for advice
- 13:22:03 [kaz]
- jt: bring the people working on the topic into the loop
- 13:22:21 [kaz]
- ... key initiative in the geolocation area is MGCTI API
- 13:22:31 [kaz]
- s/MGCTI/OGC/
- 13:22:39 [kaz]
- ... how to interact with geospatial data
- 13:23:01 [kaz]
- ... covers query
- 13:23:13 [kaz]
- ... common features and records
- 13:23:20 [kaz]
- ... are you aware of that work?
- 13:23:22 [kaz]
- mm: yes
- 13:23:39 [kaz]
- ... the question is we have our own discovery spec
- 13:23:56 [kaz]
- ... which part to be reused/imported?
- 13:24:10 [kaz]
- ... we need to capture the plan
- 13:24:45 [kaz]
- ... my hope is basic discovery for WoT first during this charter period
- 13:25:10 [kaz]
- ... and the question is do we need informative thing first?
- 13:25:24 [kaz]
- ... other things also going on
- 13:25:28 [kaz]
- ... and wanted to ask you
- 13:26:09 [kaz]
- ... in addition to OGC, IEEE P287 working on geolocation, time series data, interval queries, etc.
- 13:26:13 [kaz]
- jt: yes
- 13:26:22 [kaz]
- ... time and space together
- 13:27:04 [kaz]
- mm: acceleration, velocity, etc., are not well handled for robotics, etc.
- 13:27:22 [kaz]
- ... alignment with the existing W3C specs would be good
- 13:27:40 [kaz]
- jt: Scott, you've been involved in IEEE, ISO, etc.
- 13:27:52 [kaz]
- ... any other touch points?
- 13:28:19 [kaz]
- ... identifying some common patterns both in WoT doing and OGC is doing
- 13:28:27 [kaz]
- ... aim converge at some point
- 13:28:37 [kaz]
- ... thinking about same query, etc.
- 13:28:46 [kaz]
- ... any ideas from SDW?
- 13:29:02 [kaz]
- ss: OGC APIs and the features
- 13:29:10 [kaz]
- ... convenient API to handle data
- 13:29:30 [kaz]
- ... but if there is some existing work on the WoT side
- 13:29:40 [kaz]
- ... would see that
- 13:30:04 [kaz]
- ... bigger convenient API may or may not be usable
- 13:30:29 [kaz]
- ... would see the intersections
- 13:31:43 [kaz]
- mm: we have discussion on descriptive vs prescriptive
- 13:32:09 [kaz]
- ... big problem with IoT is out-of-box interoperability
- 13:32:23 [kaz]
- ... would have recommended practices
- 13:32:39 [kaz]
- ... but what are those recommended practices
- 13:33:09 [kaz]
- ra: Rob Atkinson
- 13:33:29 [kaz]
- ... bunch of different pints
- 13:33:46 [kaz]
- ... different aspects of interoperability
- 13:34:21 [kaz]
- ... distinction among methods for bunch of stuff
- 13:34:51 [kaz]
- ... exact same sensors should work the same, but what if put in different locations?
- 13:35:03 [kaz]
- ... collaboration with WoT, starting with the data
- 13:35:42 [kaz]
- ... another aspect
- 13:36:00 [kaz]
- ... commonality of implementation
- 13:36:40 [kaz]
- ... a profile of SSN for WoT purpose may be useful
- 13:36:49 [kaz]
- ... and finally
- 13:37:00 [kaz]
- ... where the touch point is?
- 13:37:40 [kaz]
- ... have to work on interoperability across different platforms
- 13:37:43 [kaz]
- mm: yeah
- 13:37:51 [kaz]
- ... might have particular use cases
- 13:38:03 [kaz]
- ... and put some common one
- 13:38:18 [kaz]
- ... on the other hand, would get a bigger picture for the next step
- 13:38:44 [kaz]
- ... we're looking at JSON-LD for vocabulary extension
- 13:38:58 [kaz]
- ... also experimental extension for JSON
- 13:39:26 [kaz]
- ... would figure out some compromise
- 13:39:42 [kaz]
- ... issue of encoding for the short term
- 13:39:52 [kaz]
- ... and then privacy concern
- 13:40:05 [kaz]
- ... need to figure out possible solutions
- 13:40:30 [kaz]
- jt: we have a group preparing for a Note
- 13:40:48 [kaz]
- ... bunch of work in hand
- 13:40:53 [kaz]
- ... looking at privacy issues
- 13:41:02 [kaz]
- ... in terms of starting with small part
- 13:41:19 [kaz]
- ... encoding geolocation data using JSON-LD?
- 13:41:24 [kaz]
- mm: yes, JSON-LD
- 13:41:35 [kaz]
- ... specifically WoT Thing Description based on JSON-LD
- 13:41:50 [kaz]
- ... data schema for actual definition
- 13:41:58 [kaz]
- ... how to unify the things for queries
- 13:42:03 [kaz]
- ... struggling with that
- 13:42:05 [RobSmith]
- Responsible Use of Spatial Data: https://w3c.github.io/sdw/responsible-use/
- 13:42:08 [kaz]
- ... still a proposal
- 13:42:19 [kaz]
- jt: query pattern
- 13:42:22 [kaz]
- ... you're using
- 13:42:33 [kaz]
- ... smaller part of the building block
- 13:42:48 [kaz]
- ... about semantic alignment of WoT and Spatial world
- 13:43:52 [kaz]
- ... wondering if Rob can give description on his work about GeoPse
- 13:44:07 [kaz]
- mm: we need a structure
- 13:44:15 [kaz]
- ... how to address the problem
- 13:44:28 [kaz]
- ... (shows an example TD)
- 13:44:45 [kaz]
- ... responding with position property
- 13:45:01 [kaz]
- ... longitude, latitude, accuracy and accuracyUnit
- 13:45:20 [kaz]
- s/longi/including longi/
- 13:45:28 [kaz]
- ... making things modular
- 13:45:38 [kaz]
- ... and pieces to be combined
- 13:45:57 [kaz]
- jt: something Rob Atkinson is also working on
- 13:46:19 [kaz]
- mm: @context has geolocation vocabulary
- 13:46:49 [kaz]
- roba: we might want to use the context of DCAT
- 13:47:08 [kaz]
- ... scalability issues there?
- 13:47:49 [kaz]
- mm: you could have other sub namespaces for geolocation ontology
- 13:48:50 [kaz]
- roba: schema.org, etc. changes everyday
- 13:48:58 [kaz]
- s/etc./etc.,
- 13:49:31 [kaz]
- mm: we'd like to find some ontology to be imported
- 13:49:55 [kaz]
- q?
- 13:50:00 [kaz]
- q-
- 13:50:16 [kaz]
- ... that's the theory of @context within TD
- 13:50:28 [kaz]
- ... there is also privacy issues
- 13:50:39 [kaz]
- ... when geolocation is exposed
- 13:50:59 [kaz]
- roba: would imagine semantic annotation to be added
- 13:51:37 [kaz]
- mm: downstream implementation should assume fixed items
- 13:51:57 [kaz]
- ... still need to spend time to see the OGC specs
- 13:52:06 [kaz]
- ... also WoT to capture their use cases
- 13:52:22 [kaz]
- ... and see requirements for geospatial data
- 13:52:34 [kaz]
- ... we (WoT WG) have to write an updated Charter
- 13:52:48 [kaz]
- ... actually, we have both WoT-WG and WoT-IG
- 13:53:05 [kaz]
- ... our WG recharter may request a 6mo extension
- 13:53:22 [kaz]
- q+
- 13:53:58 [kaz]
- jt: what's the right way then?
- 13:54:11 [kaz]
- ... normative recommendation on this topic?
- 13:54:19 [kaz]
- ... what's the risk and impact?
- 13:55:11 [kaz]
- ... identifying one or two key SDW communities would make sense?
- 13:55:47 [kaz]
- ... any thoughts from SDW?
- 13:56:04 [kaz]
- linda: OGC experimentation would be useful
- 13:56:22 [kaz]
- ... collaboration on some specific topic
- 13:56:32 [kaz]
- ... joint session between WoT and OGC
- 13:57:00 [kaz]
- mm: due to COVID situation, our F2F schedule has been changed
- 13:57:09 [kaz]
- ... purpose of project is clarifying the issues
- 13:57:24 [kaz]
- ... use the concrete example for further discussion
- 13:57:42 [kaz]
- ... map for territory, etc.
- 13:57:48 [kaz]
- q?
- 13:58:15 [kaz]
- jt: an opportunity to leverage WoT machinery using Plugfest and OGC?
- 13:58:33 [kaz]
- mm: make sense for IoT geolocation
- 13:59:01 [kaz]
- ... what would be the next meeting?
- 13:59:32 [kaz]
- ... maybe early next year?
- 13:59:40 [kaz]
- ... e.g., February
- 13:59:45 [kaz]
- ... for the sprint dash
- 13:59:53 [kaz]
- ... let me reach out by email
- 14:00:31 [jtandy]
- q?
- 14:01:28 [kaz]
- kaz: for the next step, I'd suggest we define one specific core use case
- 14:01:54 [kaz]
- ... smart city is OK, but some concrete core use case would be useful
- 14:02:09 [kaz]
- ... and think about our identifies issues based on that use case
- 14:02:27 [kaz]
- ... also we should learn our generated specs with each other
- 14:03:02 [kaz]
- mm: would capture the points on the GitHub issue as well
- 14:03:18 [kaz]
- jt: can share my notes as well
- 14:03:46 [kaz]
- ... let me ask if anybody in the OGC space have any other points
- 14:03:49 [kaz]
- ack k
- 14:03:54 [kaz]
- (none)
- 14:04:04 [kaz]
- jt: linda, what about you?
- 14:04:07 [kaz]
- linda: nothing
- 14:04:39 [kaz]
- mm: who is the right person as the contact point?
- 14:04:52 [kaz]
- jt: Scott with Linda and myself
- 14:04:56 [kaz]
- mm: ok
- 14:05:54 [kaz]
- ... thanks a lot for joining this call!
- 14:06:12 [McCool]
- q?
- 14:06:22 [kaz]
- i|can share|-> https://github.com/w3c/wot/issues/981 Joint call with SDW #981|
- 14:06:28 [kaz]
- (SDW guys leave)
- 14:07:33 [RobSmith]
- OGC GeoPose seems relevant to location with orientation issues for WoT: https://www.ogc.org/projects/groups/geoposeswg
- 14:07:44 [kaz]
- topic: Netzo
- 14:07:55 [Fady]
- Fady has joined #wot
- 14:08:16 [Fady]
- Ege: Introducing Netzo
- 14:08:27 [kaz]
- i/Ege/scribenick: Fady/
- 14:09:06 [Fady]
- Arturo Romero: Introducing Netzo
- 14:09:35 [kaz]
- s/Arturo Romero:/Arturo_Romero:/
- 14:09:46 [Fady]
- ... We are three brothers
- 14:10:06 [Fady]
- ... from mexico
- 14:10:15 [Fady]
- ... We moved to Munich
- 14:10:41 [sebastian_]
- sebastian_ has joined #wot
- 14:10:43 [Fady]
- ... studied in Germany
- 14:11:34 [Fady]
- ... The problem of IoT today is that it is fragmanted with not interoperability.
- 14:12:02 [Fady]
- ... current solution are siloed, lacking unified interface
- 14:12:35 [Fady]
- ... or are very expensive
- 14:12:48 [Fady]
- ... How does Netzo solve this?
- 14:13:19 [Fady]
- It does this by unfiying IoT of software level
- 14:14:10 [Fady]
- ... We now introduce the Netzo Platform
- 14:14:50 [Fady]
- ... It is an application enablement platform
- 14:15:53 [Fady]
- ... Getting started with Netzo is easy
- 14:16:26 [Fady]
- ... It allows adding things
- 14:16:46 [Fady]
- ... or simulating them just by having their TD
- 14:17:23 [kaz]
- rrsagent, draft minutes
- 14:17:23 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/14-wot-minutes.html kaz
- 14:17:49 [kaz]
- Chair: McCool/Sebastian
- 14:17:50 [kaz]
- rrsagent, draft minutes
- 14:17:50 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/14-wot-minutes.html kaz
- 14:17:57 [Fady]
- ... A TD can be added either by writing it from scratch, by creating them from TMs, importing them or discovering them
- 14:18:57 [Fady]
- ... Netzo creates multi-Thing Dashboard, allow sharing and more
- 14:19:16 [Fady]
- ... How does Netzo look like?
- 14:19:36 [Fady]
- We offer an IDE
- 14:20:08 [Fady]
- ... drag and drop widgets for value visulaization
- 14:20:38 [Fady]
- ... viewing the WoT API etc.
- 14:21:01 [Fady]
- ... Our roadmap:
- 14:21:09 [Fady]
- ... enroll early adopters
- 14:21:18 [Fady]
- ... aquire beta testers
- 14:21:31 [Fady]
- ... create a community
- 14:21:42 [Fady]
- ... then promote
- 14:22:27 [Fady]
- ... we will begin with a private beta in November
- 14:22:51 [Fady]
- ... we ask you to apply with the link we will provide
- 14:23:27 [Fady]
- ... early adopters are forerunners and gain a say in Netzo
- 14:23:56 [Fady]
- ... and therefore get an advantage
- 14:24:04 [kaz]
- q
- 14:24:13 [Fady]
- ... We reached the end of the presentation
- 14:24:30 [kaz]
- q+
- 14:24:37 [dape]
- q?
- 14:24:50 [sebastian]
- sebastian has joined #wot
- 14:24:53 [sebastian]
- q?
- 14:24:59 [gabriel]
- gabriel has joined #wot
- 14:24:59 [Fady]
- ... For applying to beta test please visit https://netzo.io/private-beta-signup
- 14:25:27 [kaz]
- q?
- 14:25:28 [dape]
- q?
- 14:25:37 [Fady]
- Ege: Thank you for presentation Arturo
- 14:25:42 [McCool]
- q+
- 14:26:20 [kaz]
- ack k
- 14:26:46 [Fady]
- Kaz: Thank you for presentation. Do you have trouble with v1 standard?
- 14:26:55 [cris]
- q+
- 14:27:24 [dape]
- q+
- 14:27:45 [Fady]
- Miguel: To understand your question correctly, are we having trouble with the context?
- 14:27:59 [kaz]
- s/v1 standard/WoT standards, either v1 standard or v1.1 draft/
- 14:28:36 [Fady]
- Kaz: I mean did you have any problem understanding v1 standard?
- 14:29:00 [kaz]
- q?
- 14:29:03 [kaz]
- ack mc
- 14:29:30 [Fady]
- Miguel: We do not have problems with understanding the standard
- 14:29:56 [Fady]
- Mccool: Do you implement the WoT Discovery spec?
- 14:30:22 [Fady]
- Miguel: We still did not implement it.
- 14:30:46 [kaz]
- s/1 standard/1 standard when you implemented your implementation/
- 14:31:06 [Fady]
- Mccool: What was your open source strategy?
- 14:31:13 [kaz]
- q?
- 14:31:17 [kaz]
- q+
- 14:32:03 [takio]
- q+
- 14:32:24 [Fady]
- Miguel: The marketplace now has 3 types of plugins, and more can be added and can be monetized
- 14:33:47 [Fady]
- McCool: There are no orchestration plugins. Do you intend to implement orchestration plugin?
- 14:34:12 [McCool]
- q?
- 14:34:36 [Fady]
- Miguel: We intend to implement something like this, we call it scripting
- 14:35:37 [Fady]
- Christiano: I was wondering, how much of this is ready to be tried in the beta?
- 14:36:20 [Ege]
- q+
- 14:36:27 [McCool]
- ack c
- 14:36:32 [Fady]
- Miguel: All the things that you saw in the screenshots are already implemented. You can expect everything to we presented in beta state by the middle of November
- 14:37:48 [Fady]
- Daniel: Is the basis for some of the things in Netzo in node-wot? Are you contributing to node-wot?
- 14:38:01 [McCool]
- ack d
- 14:38:04 [dape]
- ack dape
- 14:38:14 [Fady]
- Miguel: We use it internally, yes and fully embrace it
- 14:38:36 [Fady]
- Ege: What kind of limitations do you see in node-wot?
- 14:39:09 [Fady]
- Miguel: We see node-wot lagging a bit behind in features
- 14:40:02 [Fady]
- Kaz: Your system is like an emergant platform. What types of devices be used with it?
- 14:40:20 [kaz]
- s/emergant/emulation/
- 14:40:42 [sebastian]
- q+
- 14:40:46 [McCool]
- q?
- 14:40:46 [kaz]
- ack k
- 14:41:03 [kaz]
- ack takio
- 14:41:12 [Fady]
- Miguel: Any device that can use the protocols in node-wot can be emulated
- 14:41:47 [kaz]
- kaz: in that case, would suggest you join the Plugfest next time :)
- 14:41:54 [kaz]
- Miguel: happy to :)
- 14:42:05 [kaz]
- takio: why did you choose WoT as your platform
- 14:42:09 [kaz]
- s/form/form?/
- 14:42:43 [kaz]
- i/in that/scribenick: kaz/
- 14:42:44 [McCool]
- q?
- 14:43:07 [Fady]
- Takio: We tried many things, but we heard about WoT we knew it was going to solve the problem we want to solve
- 14:43:45 [Fady]
- Ege: Is it possible to do a live demo?
- 14:43:58 [kaz]
- s/Takio:/Miguel:/
- 14:44:09 [Fady]
- Miguel: We are not prepared to do it now.
- 14:44:39 [Fady]
- Ege: For me it is fine, but I thought it would be nice to show the others
- 14:44:53 [Fady]
- McCool: We can schedule a live demo
- 14:45:10 [Fady]
- Miguel: We would love to do that
- 14:45:21 [McCool]
- q?
- 14:45:28 [McCool]
- ack e
- 14:45:29 [Ege]
- ack e
- 14:45:39 [Fady]
- McCool: We can schedule a meeting, let's discuss this offline
- 14:45:47 [McCool]
- q+
- 14:46:11 [Fady]
- Sebastian: Thank you for presentation and it's nice to see what we WoT can be
- 14:46:35 [Fady]
- ... Please join our plugfest so we can test your system
- 14:46:43 [kaz]
- s/we WoT/WoT/
- 14:47:13 [Fady]
- Arturo: We are reaching our release date, that's why we want to hear your feedback
- 14:47:24 [Fady]
- ... and start a joined collaboration
- 14:47:58 [Fady]
- McCool: What is your first feature you want to finish?
- 14:48:36 [kaz]
- s/joined/joint/
- 14:48:39 [Fady]
- ... Arturo: Bring data to the platform, to see them in the platform
- 14:48:52 [Fady]
- McCool: you mean live data?
- 14:49:33 [kaz]
- s/... Ar/Ar/
- 14:49:33 [Fady]
- Miguel: Yes. And fill a dashboad with widgets with live data
- 14:49:37 [kaz]
- q?
- 14:49:37 [McCool]
- q?
- 14:49:40 [kaz]
- ack s
- 14:49:43 [McCool]
- ack m
- 14:49:57 [Fady]
- McCool: The queue is empty
- 14:50:12 [Fady]
- ... you have a contact already, Ege
- 14:50:22 [Fady]
- ... you should continue working
- 14:50:32 [Fady]
- ... and tell us about any issues you encounter
- 14:50:39 [Fady]
- ... so that we can address it
- 14:51:01 [McCool]
- q?
- 14:51:10 [Fady]
- ... anyone else has further comments?
- 14:51:22 [Fady]
- ... I see no one else in the queue
- 14:51:40 [Fady]
- ... next week there are two breakouts
- 14:52:03 [Fady]
- The edge-computing breakout is new and is on Friday
- 14:52:38 [kaz]
- s/The/... The/
- 14:52:39 [Fady]
- ... I am trying to figure out my schedule for next week
- 14:53:03 [kaz]
- i/edge/... Smart Cities organized by Kaz/
- 14:53:05 [Fady]
- ... we are going to cancel architecture and profiles
- 14:53:25 [Fady]
- we should track down the breakouts next week
- 14:53:47 [Fady]
- ... Kaz, do you have an update regarding breakout?
- 14:53:58 [Fady]
- Kaz: let me see
- 14:54:08 [kaz]
- breakout session on Oct 18 at 15UTC and Oct 21 14UTC.
- 14:54:42 [kaz]
- s/breakout/Smart Cities breakout/
- 14:54:45 [Fady]
- McCool: Are there any other breakouts?
- 14:55:43 [Fady]
- ... Kaz, do you know when the voice interactions one is?
- 14:55:50 [Fady]
- ... I will look it out
- 14:57:35 [Fady]
- Kaz: Is it ok to put the link in wiki even when it is protected by password?
- 14:58:28 [Fady]
- McCool: It should be working
- 14:59:18 [Fady]
- McCool: Next week will have to wing it. Are there any organization matters for next week?
- 14:59:58 [kaz]
- i|Next|kaz: my point is so far the W3C Event Team has not put the actual CVent link on the public pages, so maybe we should also avoid putting that on our public wiki|
- 15:00:08 [Fady]
- McCool: Let's assume the editor's call we happen as planned (6 am eastern)
- 15:01:54 [kaz]
- s/we/will/
- 15:02:18 [kaz]
- kaz: will distribute a doodle poll to find a better slot soon.
- 15:02:20 [kaz]
- [adjourned]
- 15:02:26 [kaz]
- rrsagent, draft minutes
- 15:02:26 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/14-wot-minutes.html kaz
- 16:49:06 [dsr]
- dsr has joined #wot
- 16:59:51 [Zakim]
- Zakim has left #wot
- 17:06:10 [zkis]
- zkis has joined #wot
- 17:07:40 [dsr]
- dsr has joined #wot
- 17:25:11 [dsr]
- dsr has joined #wot
- 17:25:48 [dsr]
- dsr has joined #wot
- 17:50:12 [dsr]
- dsr has joined #wot
- 18:09:20 [dsr]
- dsr has joined #wot
- 18:52:29 [dsr]
- dsr has joined #wot
- 19:25:16 [dsr]
- dsr has joined #wot
- 19:44:16 [zkis]
- zkis has joined #wot
- 19:54:53 [dsr]
- dsr has joined #wot
- 20:27:10 [dsr]
- dsr has joined #wot
- 20:46:14 [dsr]
- dsr has joined #wot
- 21:03:07 [dsr]
- dsr has joined #wot
- 22:02:57 [dsr]
- dsr has joined #wot
- 22:09:07 [zkis]
- zkis has joined #wot
- 23:03:58 [dsr]
- dsr has joined #wot