13:03:01 <RRSAgent> RRSAgent has joined #sdw
13:03:01 <RRSAgent> logging to https://www.w3.org/2022/06/23-sdw-irc
13:03:03 <ktoumura> ktoumura has joined #sdw
13:03:08 <kaz> present+ jtandy, ScottSimmos
13:03:57 <kaz> present+ Kaz_Ashimura, Michael_McCool, Joost_van_Uden, Kunihiko_Toumura, Rob_Smith
13:04:56 <kaz> present+ Bert_Bos
13:05:06 <kaz> present+ Christine_Perey
13:05:13 <jvanulde> jvanulde has joined #sdw
13:05:26 <kaz> mm: (gives background)
13:05:54 <kaz> ... WoT wrapping up the spec work
13:06:12 <kaz> ... remaining issues on how to handle geospatial data (for the next version specs)
13:07:16 <kaz> ... did quick survey on OGC specs
13:09:19 <kaz> ss: first step should be identifying smaller topics
13:09:28 <kaz> ... describing geometory, etc.
13:10:38 <kaz> mm: also wanted to say we're also breaking up things into smaller pieces
13:10:43 <kaz> ... and working on use cases
13:10:43 <RobSmith> q+
13:10:52 <kaz> ... e.g., rooms within a building
13:11:07 <kaz> ... may need to involve multiple organizations
13:11:26 <kaz> jt: Scott, you mentioned smaller topics
13:11:39 <kaz> ... ontology/vocabulary we use
13:11:51 <kaz> ... also new OGC API specs
13:12:05 <kaz> ss: kind of ubiquitous
13:12:28 <kaz> mm: connections and relationships with the other standards is important
13:12:47 <kaz> jt: Rob?
13:13:00 <kaz> rs: yes, had a quick look at WoT
13:13:06 <kaz> ... pretty much overlap with our work
13:13:17 <kaz> ... we're defining OGC standards
13:13:22 <kaz> ... including GeoPose
13:13:27 <kaz> ... video map tracks
13:13:46 <jtandy> q?
13:13:50 <kaz> ... synchronizing time meta data and geospatial dat
13:13:55 <jtandy> ack RobSmith
13:13:58 <kaz> s/l dat/l data/
13:14:26 <kaz> ... also Geo Aligning by Immersive Web group as well
13:14:35 <kaz> ... orientation accuracy
13:14:38 <kaz> ... filling in the gaps
13:14:47 <kaz> mm: have reviewed Geo Pose
13:14:55 <kaz> ... solves narrow problems
13:15:00 <kaz> ... viewpoint and origin
13:15:10 <kaz> ... but doesn't handle accuracy
13:15:39 <kaz> ... talking about a use case including velocity of robots
13:15:54 <kaz> ... felt that large number of narrow standards
13:16:03 <kaz> ... unified modular approach
13:16:06 <kaz> ... also tagging data
13:16:17 <kaz> ... leverage of using RDF
13:16:24 <kaz> ... annotate the data
13:16:27 <kaz> q?
13:16:41 <kaz> cp: clarification for Michael's point
13:17:03 <kaz> ... use cases include several groups
13:17:17 <kaz> ... (some of them are) not driven by AR
13:17:32 <kaz> ... our thinking was other standard would have Geo Pose to express velocity
13:17:42 <kaz> ... 8 standards all about time
13:17:51 <kaz> ... velocity is about place and time
13:18:18 <kaz> mm: velocity is a vector of point
13:18:26 <kaz> ... changing the position
13:18:27 <kaz> q?
13:18:29 <kaz> q+
13:18:45 <jtandy> ack kaz
13:19:26 <kaz> kaz: would suggest we split the discussion points
13:19:37 <kaz> ... e.g., vocabulary, data model and API
13:19:50 <kaz> ... think "velocity" is pat of vocabulary
13:19:52 <kaz> mm: right
13:20:03 <kaz> ... let's once go back to there
13:20:27 <kaz> ... our issue is metadata for discovery
13:20:40 <kaz> ... relates to query language
13:20:54 <kaz> ... also maybe around time-series data
13:21:14 <kaz> ... our question is encoding of the data
13:21:33 <jtandy> q?
13:21:37 <kaz> ... Geo Pose does define something close to our points
13:21:49 <kaz> jt: most interesting thing
13:21:54 <kaz> ... encoding geolocation data
13:22:03 <kaz> ... location, velocity, position, etc.
13:22:15 <kaz> mm: our serialization is JSON-LD
13:23:04 <kaz> ... different systems may have different mechanism to handle the data
13:23:20 <kaz> jt: how close are they being able to provide semantic presentation
13:23:26 <kaz> s/on/on?/
13:23:47 <kaz> rs: Geo Pose is a container
13:23:56 <kaz> ... location/position and orientation
13:24:07 <kaz> ... you can choose encoding as you like
13:24:19 <kaz> ... data model rather than a specific syntax
13:24:31 <kaz> mm: technically, WoT TD is something like that
13:24:33 <jtandy> q?
13:24:44 <kaz> present+ CHris_Little
13:24:57 <kaz> present- CHris_Little
13:25:04 <kaz> present+ Chris_Little
13:25:19 <kaz> mm: defining RDF for Geo Pose would not be difficult
13:25:29 <kaz> ... want to look at modular systems
13:25:59 <kaz> jt: here a bunch of properties and would like to add some more
13:26:25 <kaz> mm: would like to specify @context on geolocation data for the WoT Thing Description
13:26:41 <kaz> ... standardized vocabulary using RDF
13:26:49 <kaz> ... to be applied to WoT Discovery
13:26:51 <RobSmith> q+
13:27:01 <kaz> jt: what the vocabulary you need?
13:27:13 <kaz> ... what kind of discovery is needed?
13:27:26 <kaz> ... recently, had an OGC meeting last week
13:27:36 <kaz> ... RDF world and the OGC world
13:27:42 <kaz> ... interesting to revisit
13:27:48 <kaz> ... OGC world to be linked via RDF
13:27:53 <kaz> mm: right
13:28:13 <kaz> ... would be fine if we could refer to that data from WoT TD
13:28:28 <kaz> jt: anybody familiar with Geo SPARQL?
13:28:44 <kaz> ... there is an ontology about whole bunch of things
13:29:05 <kaz> ... includes RDF implementations
13:29:16 <kaz> mm: should look into it more
13:29:23 <kaz> ... searching WoT TD
13:29:50 <kaz> ... we could use Geo SPARQL to get geolocation data
13:29:56 <kaz> ... would be my homework
13:30:02 <kaz> jt: ok
13:30:16 <kaz> ... on top of the existing ontology, standardize properly
13:30:25 <kaz> ... can point you to afterwards
13:30:48 <jtandy> q?
13:30:55 <kaz> mm: also we're discussing I18N
13:31:18 <kaz> ... various types of time expressions
13:31:41 <kaz> cl: hard work on time
13:31:51 <kaz> ... abstract model on time
13:31:58 <kaz> ... ISO for last 40 years
13:32:20 <kaz> ... would take a simpler model
13:32:27 <kaz> ... atomic time, UNIX time, etc.
13:33:19 <kaz> ... established a group with ISO 19
13:33:25 <kaz> ... geographical time coding
13:33:34 <kaz> ... also ISO 601
13:33:42 <kaz> ... 2 different things
13:33:51 <jtandy> s/601/8601/
13:34:14 <kaz> mm: need to come with some consensus
13:34:28 <kaz> ... would be nice to have one specific notation
13:34:39 <kaz> cl: starting to get two things
13:34:54 <kaz> ... if you want to have date/time, etc., that's ok
13:35:03 <kaz> ... and if you don't, can have UNIX time, etc.
13:35:41 <kaz> ... OGC people have not moved to ontology world yet
13:36:00 <kaz> mm: if know the definition in standardized manner
13:36:04 <kaz> ... that's great
13:36:14 <jtandy> ack RobSmith
13:36:16 <kaz> ... what's the data for devices is our question
13:36:53 <kaz> rs: Geo Pose can handle location and orientation
13:37:02 <kaz> ... dynamic aspect of that
13:37:16 <kaz> ... has specific API for query
13:37:36 <kaz> ... probably those two are the key elements
13:37:52 <kaz> ... want to know what time is being looked at
13:38:24 <kaz> ... the areas we're looking at are quite overlapped
13:38:39 <kaz> mm: orthogonal thinking of data and device
13:38:44 <kaz> ... geolocation is part of that
13:38:57 <kaz> ... also defining internal data within a device
13:39:08 <kaz> ... separate deliverable from the WoT spec
13:39:38 <kaz> ... can generalize your approach?
13:39:56 <kaz> rs: looking from an opposite angle
13:40:17 <kaz> ... it's just one big data space to be generalized
13:40:21 <kaz> mm: yeah
13:40:37 <kaz> ... have to go back and look into Geo Pose carefully
13:40:38 <jtandy> q?
13:40:39 <kaz> ... and query language
13:40:41 <jtandy> q+
13:40:50 <kaz> ... wondering about network APIs
13:41:05 <kaz> ... our priority is network APIs
13:41:10 <kaz> rs: yeah
13:41:26 <kaz> ... had a breakout session during TPAC
13:41:31 <kaz> q+
13:41:44 <kaz> mm: average, min, max
13:41:56 <kaz> ... can be a query if you support time data
13:42:13 <kaz> ... radius at some point too
13:42:20 <kaz> ... would see some unified style
13:42:38 <kaz> q+ chris_little
13:43:14 <kaz> ... may also need a bit broader search
13:43:23 <kaz> ... e.g., world-wide search on the Web
13:43:34 <kaz> q- later
13:43:48 <kaz> jt: there is a queue
13:43:53 <jtandy> ack jtandy
13:43:53 <kaz> ... I'm first
13:44:02 <jtandy> https://www.w3.org/TR/sdw-bp/
13:44:12 <kaz> ... have you read the Spatial data Best Practice document?
13:44:19 <kaz> mm: not every detail yet
13:44:21 <kaz> jt: ok
13:44:44 <kaz> ... how to handle geospatial data is described there
13:44:59 <jtandy> q?
13:45:02 <kaz> ... should be a reasonable starting point
13:45:12 <jtandy> ack chris_little
13:45:30 <kaz> cl: one of the APIs is idea retrieval api
13:45:38 <kaz> ... a bit misleading name
13:45:41 <jtandy> s/idea/EDR/
13:45:44 <kaz> ... data retrieval is done
13:45:56 <jtandy> (environmental data retrieval)
13:46:13 <kaz> mm: certainly inline
13:46:21 <jtandy> ack kaz
13:46:32 <McCool> https://www.ogc.org/standards/ogcapi-edr
13:47:31 <McCool> there is also this for BIM: https://brickschema.org/ontology/
13:47:45 <jtandy> q?
13:48:19 <kaz> kaz: would propose a breakout session during TPAC 2022 again after our reading the specs again
13:48:32 <kaz> mm: SDWWG will not meet
13:48:40 <kaz> kaz: maybe a hybrid session then?
13:49:13 <kaz> jt: TPAC is 3 months away
13:49:16 <McCool> https://www.w3.org/TR/owl-time/
13:49:35 <kaz> jt: we need to have info share
13:49:53 <kaz> ... if you can write down something about what you want to use
13:50:02 <kaz> ... RDF vocabulary, serialization, etc.
13:50:12 <kaz> ... would use this vocab and that, etc.
13:50:19 <kaz> ... how would that sound?
13:50:22 <kaz> mm: yeah
13:50:39 <kaz> ... need to collect relevant resources
13:50:46 <kaz> ... but would agree it would be nice
13:50:54 <kaz> q?
13:51:06 <kaz> ... concrete proposal would be useful
13:51:19 <kaz> jt: given the scope of the information you would encode
13:51:32 <kaz> ... and geo folks on our side to see that
13:51:43 <kaz> mm: a couple of steps there
13:51:49 <kaz> ... use cases drive requirements
13:51:53 <kaz> ... then example
13:51:57 <kaz> s/example/examples/
13:52:14 <kaz> ... strawman proposal on vocabulary
13:52:24 <kaz> ... also survey of existing standards
13:52:35 <kaz> ... EDR, etc.
13:53:10 <kaz> jt: information needed to be encoded
13:53:17 <kaz> ... do you think you could build an example?
13:53:55 <kaz> ... we can connect your points to the existing standards
13:54:05 <kaz> q?
13:54:07 <kaz> q+
13:54:21 <kaz> mm: good starting point
13:54:31 <kaz> ... but also think about another problem about metadata
13:54:52 <kaz> ... overall mechanism to handle updates for locations
13:55:04 <McCool> q?
13:55:05 <jtandy> ack kas
13:55:09 <jtandy> ack kaz
13:55:37 <kaz> kaz: ok
13:55:42 <kaz> ... let's think about the first step then
13:56:00 <kaz> mm: look into existing standards again
13:56:10 <kaz> ... generate a concrete example
13:56:26 <kaz> ... in July, we can schedule the next meeting
13:56:37 <kaz> jt: ok
13:56:41 <kaz> ... in terms of what we talked about
13:56:49 <kaz> ... revising your example
13:56:50 <McCool> https://github.com/w3c/wot-discovery/blob/main/proposals/geolocation.md
13:57:15 <kaz> mm: there are bunch of examples within our use cases
13:57:24 <kaz> ... would be a starting point
13:57:27 <kaz> jt: ok
13:57:30 <jtandy> q?
13:57:32 <kaz> ... how long would it take?
13:57:58 <kaz> mm: let's say one month from now
13:58:31 <kaz> jt: we'll have the next plenary call in 4 weeks
13:58:48 <kaz> mm: sounds good
13:59:01 <kaz> ... FYI, we'll talk about the next Charter during TPAC
13:59:27 <kaz> ... 10-20 min presentation during the next SDW call
13:59:36 <kaz> ... can get feedback offline later on GitHub as well
14:00:14 <kaz> ... would update our next Charter based on the discussion
14:00:23 <kaz> jt: we want to nail down the gaps
14:00:24 <jtandy> q?
14:00:24 <kaz> q?
14:00:58 <kaz> kaz: next call on July 28?
14:01:04 <kaz> jt: July 21
14:01:15 <kaz> mm: at this time?
14:01:18 <kaz> jt: yes
14:01:26 <kaz> [adjourned]
14:01:31 <kaz> rrsagent, make log public
14:01:37 <kaz> rrsagent, draft minutes
14:01:37 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/23-sdw-minutes.html kaz
14:02:17 <jtandy> @kaz - thanks for scribing and running the bots for us
16:03:42 <Zakim> Zakim has left #sdw