W3C

– DRAFT –
VSSo

17 October 2022

Attendees

Present
Daniel_Alvarez, Felix_Loesch, Nick_Russel, Ted_Guild
Regrets
-
Chair
DanielA, Felix
Scribe
ted

Meeting minutes

Welcome back

Congratulations to Daniel Alvarez and welcome back from paternity leave

Results of build

Ted: as we advanced VSS, I wanted to look towards creating updated VSSo and VSSo Core specs. Core built whereas VSSo threw an error around SKOS object.
… I will address namespace, markup and other issues so we can generate publishable W3C specs automatically as VSS gets released. There may be times we want to pause that while addressing design decisions

Felix: we also need to encourage others from more companies (Ford and Mercedes for example) to re-engage

DanielA inquires about issues during build

---> 11 out_concept['definition'] = g.value(concept, SKOS.definition).toPython()

Ted: Carine and I made a number of manual tweaks to pass W3C Pubrules and I will work to get those into underlying Python

DanielA: another comment regarding VSSo development, we should keep focus on having the Core module in a stable state
… there are other decisions to be made but Core should be stable. That should be our initial focus

Felix: agree

DanielA: regarding increasing participation from partners. I reached out and made counter proposals but feel we need to address one at a time

Felix: I do not want to exclude anyone but unless people are showing up to actually contribute, it is difficult to accept counter proposals
… re-activating this group is important. after reaching a stable state for the Core, we should reach out more broadly

DanielA: a stable version, concensus on Core from attendees and trying to engage are good goals for the rest of the year
… not only having the model but demo with real or mock data would be very useful for understanding how this ontology can help

Ted: need to get a body of data, might be able to get help from a NSF project
… could probably host SPARQL or other at W3C

https://github.com/commaai/comma2k19

DanielA: this body of data is potentially useful but there seems to be limitation on uses

Ted: I think Bosch has some open data
… the COVESA Ford EV crowdsourcing project could be great to demo around, perhaps attract some of the NSF PIVOT researchers I mentioned who are looking at EV issues

https://wiki.covesa.global/display/WIK4/EV+Charging+and+Energy+Services+Proposal#EVChargingandEnergyServicesProposal-DraftCharter

Ted: effort is to leverage SAREF4Auto and VSSo

DanielA: the hard part is trying to convince people to use ontologies to begin with
… simple queries are not enough, combining disparate sources is what makes it valuable
… same with showing cross-OEM uses with data

Next steps:

* Tooling, Ted to share VSS tools build issue with Daniel

* All to try to identify data sets for demo, Ted to try for Ford EV project at AMM this week

* Felix to prioritize issues, centering on Core first

Issues

https://github.com/w3c/vsso/issues

[reviewed open issues assigning #vss-core tag to prioritize]

* Attendees encouraged to contribute to issues tagged as vsso-core

Felix: we can find some that we can resolve readily, assign ones that will take more work

DanielA: I would recommend larger, more impactful such as instances vs sub-classes as a priority

Felix: agree

https://github.com/w3c/vsso/issues/22

Felix: we will discuss that one next time

DanielA: that is a tricky issue, will consume a fair amount of time and should select another
… we can also bring forward a list of competency questions to make sure ontology can answer

Felix: makes sense too

<ted> Next Meeting: 24 October, cancel 31 October

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).

Diagnostics

Succeeded: s/@@congrats to Daniel/Congratulations to Daniel Alvarez and welcome back from paternity leave/

Succeeded: s/@@automate/Ted: as we advanced VSS, I wanted to look towards creating updated VSSo and VSSo Core specs. Core built whereas VSSo threw an error around SKOS object./

Succeeded: s/@@designdecisions/… I will address namespace, markup and other issues so we can generate publishable W3C specs automatically as VSS gets released. There may be times we want to pause that while addressing design decisions/

Succeeded: s/@@html_namespace_markup_etc/Ted: Carine and I made a number of manual tweaks to pass W3C Pubrules and I will work to get those into underlying Python/

Succeeded: s/@@ford_ev/… the COVESA Ford EV crowdsourcing project could be great to demo around, perhaps attract some of the NSF PIVOT researchers I mentioned who are looking at EV issues/

Succeeded: s/@@vsso-core_tage/[reviewed open issues assigning #vss-core tag to prioritize]/

Found 'Next meeting:' not followed by a URL: '24 October, cancel 31 October'.

Maybe present: DanielA, Felix, Ted