[wot-usecases][AR] minutes - 19 January 2021

available at:
  https://www.w3.org/2021/01/19-wot-uc-minutes.html

also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

      [1] https://www.w3.org/

                        Discovery + AR Use Cases

19 January 2021

   [2]Agenda. [3]IRC log.

      [2] https://github.com/w3c/wot/issues/955
      [3] https://www.w3.org/2021/01/19-wot-uc-irc

Attendees

   Present
          Christine_Perey, Colin_Steinmann, James_Jackson,
          Jan-Erik_Vinje, Joshue_O_Connor, Kaz_Ashimura,
          Kunihiko_Toumura, Linda_van_den_Brink, Michael_Koster,
          Michel_McCool, Nazih_Fino, Rob_Smith, Ted_Guild,
          Tomoaki_Mizushima, Tony_Hodgson, Vladimir_Ufnarovsky

   Regrets
          Sebastian

   Chair
          McCool

   Scribe
          kaz

Contents

    1. [4]Background
    2. [5]Intro
    3. [6]Open AR Cloud
    4. [7]Next steps

Meeting minutes

  Background

   Christine: (provides the background so far)
   … discovery is the key
   … to have broader discussion on discovery for AR today

   McCool: (provides logistics notes)
   … the minutes will be public
   … holding as an IG meeting under the use case TF
   … (introduction of McCool himself as the co-Chair for the WoT
   WG/IG)

   (and the others also introduce themselves)

   Christine

   Tony

   Linda

   Rob

   Joshua

   Ted

   Joshue

   Kaz

   Jan-Erik

  Intro

   McCool: this meeting is specifically discovery for AR
   … focus on AR use cases
   … and identify what the next steps would be
   … would provide technical background information
   … any comments before that?

   (none)

   McCool: (shows the TPAC breakout slides)

   [8]WoT Breakout slides

      [8] https://www.w3.org/2020/10/27-wot-breakout/2020-10-WoT-Breakout.pdf

   McCool: [WoT Goal and Use Cases]
   … [Current Work Items]
   … have published several specs
   … working on a new Charter
   … Discovery is a process to access metadata
   … not just local area broadcasting but also internet search
   … considering multi-process approach
   … including geospatial awareness
   … finding out where the related sensors are, etc.
   … [Thing Description]
   … describes information on devices
   … including metadata
   … one of the metadata is location
   … might be static but could be dynamic
   … e.g., if the device is a vehicle
   … also not just position but acceleration, direction, etc., can
   be included
   … [Geolocation]
   … did some prototyping
   … quickly shows them

   [9]geolocation-related issues

      [9] https://github.com/w3c/wot-testing/labels/Geolocation

   McCool: (shows example TDs)
   … longitude, latitude, etc.
   … accuracy and heading
   … might have property to distinguish the positions
   … links to associate entities
   … need to have some method to handle this

   [10]example TDs

     [10] https://github.com/w3c/wot-testing/tree/master/events/2020.09.Online/TDs/Intel

   Christine: discussion for now?

   McCool: let's have discussion during the second half
   … 24mins past now

   Christine: introducing open AR cloud would make sense

  Open AR Cloud

   Jan-Erik: (starts to share the screen)
   … AR-Cloud, Spatial Discovery & WoT
   … open AR cloud is a young non-profit
   … 60+ partners and 300+ members
   … big picture here
   … new convergence
   … real world spatial computing including IoT
   … what is the AR cloud?
   … realtime 3D/spatial map of the world
   … (Ori Inbar)
   … exciting concept
   … (4 books on the slides)
   … Open AR Clouds, AR Convergence, Welcome to Mirror World, ...
   … Layers of the Spatial Web
   … thematic layers and reality capture layers
   … IoT, Art, Entertainment, Commerce, etc.
   … currently not good interoperability there
   … The Open Web Platform - Web@30
   … standards, protocols, services, clients
   … we should let James Jackson give the through story
   … jj: interesting comparison with the Web
   … Open Spatial Computing Platform (OSCP)
   … provides core building blocks
   … we provide reference implementations
   … high-level view of the experience
   … various phases here
   … first thing to do is discovery
   … spatial service discovery
   … it's sort of hierarchy
   … it's mapping of coverage polygon
   … services themselves will be smaller geo area named geo zone
   … determine accurate position in the real world
   … and secondly determine it in geopost
   … determine the precise position where you're within the real
   world

   Jan-Erik: geo post is a standard by OGC
   … also we have the CEO of a company who provide it
   … small steps to the goals

   McCool: we need to move along

   James: ok
   … once you determine the position
   … you can think of democritizing the position
   … anyone can discover it
   … content itself is not our standardization target
   … the other key aspect is digital twin
   … static layer and dynamic layer
   … discover a content which is available to me
   … e.g., a building in front of me
   … spatial discovery is one of our use cases
   … you could discover other elements

   McCool: a lot of points packed here
   … any additional materials before discussion?

   (none)

   McCool: is there any liaison with W3C?

   Jan-Erik: happy to establish one
   … indirectly connected via ETSI, etc.

   Christine: can work with Kaz for the procedure

   Kaz: yes

   McCool: two points here
   … 1. information model
   … what information to be included here?
   … 2. discovery process
   … very loose structure here
   … onboarding, contact model, etc., to be described
   … we don't have to just have a mDNS approach
   … and would like to know how your model works

   Jan-Erik: would follow it up
   … we ourselves work on the geospatial aspects

   McCool: semantic discovery and network-relevant discovery are
   also of our interest
   … also last year we started to work on several use cases
   … Rob Smith submitted one
   … e.g., geospatial query needs to include position of view

   Rob: regarding location
   … are you interested in trajectory, i.e., history of location,
   as well?

   McCool: historical data in general
   … relates to time-series data
   … time stamp is also
   … not only spatial aspect

   Rob: video aspect is in my scope

   McCool: Kaz is also involved in the MEIG

   Rob: yes

   Jan-Erik: interesting aspect about time domain
   … different time series structure to be considered here
   … note that it's highly sensitive
   … if you have very local access, the data might be aggregated

   McCool: yeah
   … could be several use cases like factory automation
   … sometimes privacy control could be less weighted

  Next steps

   McCool: capturing use cases and requirements
   … we're holding use cases call bi-weekly
   … having a couple of you would be helpful
   … do a project to dig into the issues

   Christine: Linda, any ideas from the Spatial group viewpoint?

   Linda: what McCool mentioned makes sense
   … functional requirements would be helpful
   … and thinking about geo pose

   Christine: dig into some complete package

   McCool: follow-up actions here
   … (updates the agenda issue)

   [11]agenda issue

     [11] https://github.com/w3c/wot/issues/955

   McCool: 1. spatial experts participating in WoT use cases calls
   and contributing use cases
   … 2. discuss liaisons between WoT and geospatial SDOs
   … 3. WoT to review and summaze relevant spatial data standards
   … 4. review of ongoing standards activitis
   … 5. proposals and prototypes from WoT to b reviewed by spatial
   experts
   … the question is what/where the spatial data comes from
   … having a service that is responsive for some specific area?

   Kaz: completely agree with the approach
   … and would like to extract horizontal requirements as well as
   vertical requirements from the use cases at the bullet point 1

   McCool: (adds note to the bullet point 1, use case)

   Rob: spatial on the Web producing responsible use of spatial
   data
   … would like to post the information

   Editor's draft

   <RobSmith> [12]https://w3c.github.io/sdw/responsible-use/

     [12] https://w3c.github.io/sdw/responsible-use/

   McCool: tx

   published draft

   <brinkwoman> Actually just published at [13]https://www.w3.org/
   TR/responsible-use-spatial/

     [13] https://www.w3.org/TR/responsible-use-spatial/

   [14]https://lists.w3.org/Archives/Member/member-wot-wg/2020Dec/
   0002.html

     [14] https://lists.w3.org/Archives/Member/member-wot-wg/2020Dec/0002.html

   <McCool> [15]https://github.com/w3c/wot-testing/blob/master/
   events/2020.09.Online/TDs/Intel/intel-camera.jsonld

     [15] https://github.com/w3c/wot-testing/blob/master/events/2020.09.Online/TDs/Intel/intel-camera.jsonld

   <McCool> [16]https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf

     [16] https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf

   McCool: the next WoT Use Cases call will be held on Jan-26

   [17]times at your timezone :)

     [17] https://www.w3.org/WoT/IG/wiki/Main_Page#WebConf_Meetings

   McCool: people interested are encouraged to join that call

   Kaz: if you're interested but don't have access to the webex
   coordinate, please let me know

   [adjourned]


    Minutes manually created (not a transcript), formatted by
    [18]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

     [18] https://w3c.github.io/scribe2/scribedoc.html

Received on Wednesday, 3 March 2021 08:40:30 UTC