PatrickL: we may have a couple people from SiriusXM on work they are doing in CCC
PatrickL: we are seeking to be as
generic as possible for transmitting data and following the
roadmap we set out over the course of the last year
... supporting everything in VISS and general RESTful
methods
https://github.com/w3c/automotive/pull/298
[recap of discussion on this pull request]
Ulf: I think we should go with VSS
PatrickL: I am proposing the
separation as only part of this group has influence on how VSS
looks like
... proposal is to move forward for the pull request
Joakim: politics should not have a bearing on how standards form
Daniel: I had to leave early last time and do not want to go that direction
Magnus: there wasn't resolution last week
PatrickL: no, just a proposal to carry forward as we didn't
Ted: @@proxy
PatrickL: has the VSS gen2 been discussed as well over at Genivi?
Daniel: yes
PatrickL: we did not set out to
rework the data model and enhace VSS
... we focused on features in the WG for this new gen2
protocol
Ulf: I propose we have a vote and settle this topic
Laurent: we are not trying to
replace VSS, but want something more
... I am not sure there is that much of a disconnect
... we could do something more generic and think of other use
cases
Ted: @@core_issue
Laurent: sensor and actuator
being one issue
... that translates to read and write
Ulf: it can be ignored but might be helpful for some so I think it is a non-issue
Laurent: already seems ignored in VSS2
Ted: @@acls
Daniel: at the end you have key
value pairs, we are trying to add more via metadata when
available
... we had a presentation on graphql which is facilitated by
strong schemas and the common data model
... having in the spec the notion that VSS is a prime data
model we support but you can use something else has limited
value
PatrickL: I do not want to
replace VSS
... instead of two sides to it we will have three
... we want to have a way to transfer data from a service in a
restful manner, core thing we want to achieve
... to do so with multiple transport protocols we need a common
truth and that is what gen2 is about
... VSS brings the structure, the skeleton
Ted proposal
@@VSS1 and 2, future - neither work. option to deviate, restrict commitment
Ulf: the snapshot is way to go forward for sure
PatrickL: what are the benefits for VSS2?
Ulf: in what sense?
Ted: several and will let Ulf and other contributors go first
<PatrickLue> https://raw.githack.com/w3c/automotive/gh-pages/spec/Gen2_Core.html
Ulf: I do not see any needs that
can't be met by VSS for something undefined
... it has a track record and recognition in the industry
PatrickL: keeping what to be precise
Ted: VSSo, numeric identifiers which would be really helpful for offboarding, @@
Daniel: Benjamin did extensive
search before getting started on ontology front and VSS was the
most comprehensive and supporting a huge set of use cases with
no blockers in using it across protocols
... basically any transportation layer, big benefit is knowing
the data being sent. nothing else is comparable
... my perspective is that is only advantage in staying aligned
with VSS. we can discuss and try to handle any blockers as they
arise
... snapshot is a last resort
... yes the separation of organizations is suboptimal in some
regards but also benefits of an additional wide audience
... not sure why we are stuck on this, all arguments are on
table
PatrickL: what role does Gen2 place in VSS world?
Ulf: well Gen2 is hopefully more
advanced version over VISS beyond just adding HTTP but a more
advanced data model
... we start with VISS and outcome of our function
conversations
PatrickL: what is the issue with
the pull request?
... I see the simplifications as a benefit
... making it simplier to implement has a great benefit
Ulf: should we keep VSS as a data model or go with your proposal
PatrickL: what does it take away from VSS?
Ulf: the question then are we going with a subset?
Ted will reiterate his questions in email
PatrickL: encourage those with thoughts on what that question could be answered
Daniel: would like your pull request split so we can free the other issues
PatrickL: that helps
... I would appreciate help in how to separate
Laurent: in VSS the spec goes to parser and generates JSON, there could be one for how it is transported on the wire
PatrickL: suggest switching to email for ballot question discussion
Ted: I have some thoughts and will start
[adjourned]
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: Don Ted Daniel Harjot Glenn Laurent PatrickL Ulf Magnus Joakim Peter No ScribeNick specified. Guessing ScribeNick: ted Inferring Scribes: ted WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 26 Mar 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]