W3C

Automotive and Transportation Breakout

23 Mar 2020

Agenda

Remote meeting minutes

Attendees

Present
Regrets
Chair
Peter, Ulf, Megan, Ken
Scribe
Megan

Contents


Agenda: https://www.w3.org/auto/wg/wiki/Auto-f2f-mar-2020

TOCC

Clemens: unless Linda appears, I can give an overview of Spatial Data on the Web Best Practices

Clemens: maybe a brief overview of OGC, Open Geospatial Consortium mix of companies, universities, governments
... works with ISO TC211 Geospatial
...2014 joint workshop to discuss how geospatial standards could be improved (broader access): OGC W3C joint working group

Clemens: in 2014 started to run into need to develop standards for the web and came together with W3C to form SDWIG
...key output: spatial data on the web best practices
...complimentary to W3C's "data on the web best practices" with specific things for spatial data

Mark: some various OGC players keep us in SmartCities appraised of their work

Clement: routing APIs attempt at implementing some of the best practices

Ted: idea of this session ...everyone understand where we're coming from, come to an agreement on the vision of how the ontologies should be architected
...how to start organizing and structuring this

Ken: smart cities, ITS, OGC

Ted: accessibility representatives may be looped in later

...accessibility-aware engineers...W3C web accessibility initiative
...people using ontologies to assist with mapping for persons in wheelchairs, or assistance for persons with visibility requirements
...a consideration for routing
...hopefully will be involved in an ongoing basis; TBD whether it belongs in the core or as a complementary modular piece

Ted: review of different groups' perspectives...next steps - agreeing on how things should be structured

Linda: GeoSPARQL contains a small ontology for representation of locations and geometries
...SSN ontology via spatial data on the web working group
...SSN modular structure: SOSA core, simple taxonomy; SSN more extensive axioms...
...Routing work that will be covered tomorrow; OGC setting up standards working group for routing; draft charter (not publicly available)
...purpose is to develop and maintain a routing conceptual model, a routing ontology, and a route exchange model, and to develop and maintain an OGC API about open routing and maybe extensions to the API
...ontology work not certain, mostly focused on API and exchange model

Clement: will be talking about some of this tomorrow...there are 2 general groups: one with a focus on ontologies and the semantic web, the other more focused on web APIs, json stuff, where semantics don't play as much of a role
...routing work so far not so much on the ontology end
...need to see what other groups are doing and how we can reduce overlap and make it fit together

Linda: GeoSPARQL has been around for a while; used and implemented but not a huge success; but there are now more and more change requests coming in to OGC; implementers now who are interested in developing it further and working on it
...looking into maybe creating a working group for that in the future
...if it's of interest it may be good to coordinate

Ken: what is our actual goal? to start developing an ontology with a vehicle focus?
...need to consider 3 big things: (1) how do we govern development of the ontology? (2) how does our ontology relate to other work? data on the web, applications, APIs, (3) how do we actually document it?
...once we have those parameters in mind, then we can start delegating the workload to different groups

Linda: which other ontologies will we have some relationship with?
...SSN, GeoSPARQL

Clemens: owl time

Ken: OGC observations and measurements abstract specification

Clement: a precursor of SOSA
...revision ongoing to bring it closer with SOSA and SSN
...UML model vs SSN/SOSA owl models

Ken: start documenting what's out there

Clemens: start small and see if it gets picked up and you can extend it

Ken: agree; aware of multiple different independent groups that are interested in this topic
...group in TC204 interested in parking

Clemens: risk of underlying repository is different groups use different language

Ken:...need to abstract things into a format that clearly maps one representation to another

Clemens: need clear mechanisms so as not to block other activities

Ken: do we agree that we need to establish the three baseline requirements?

Megan and Clemens agree

Ken: presentation
...ITS data model framework
...need for combined top-down and bottom-up approach
...smart city proposal, aligned with structure proposed by ISO JTC1 WG 11 (smart cities): custom, cooperative and core components
...3d view of the intersection of the models
...propose use of GitHub to facilitate coordination

<Ken> Ken to send slides to Ted

thanks

<Ken> We need to pick a small topic to investigate

<Ken> What are the scope of comments that we need to be looking at? (from Megan)

<Ken> ... We need to coordinate and identify all of the overlaps

discussion about use of GitHub, openness and ISO acceptance of approach

Carlos: how would you propose to select a small scope to begin with?

Ken: suggest (from the ITS side) to start with one service package
...from the architecture

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/04/13 18:37:59 $