Introductions for Gary Wallace
Gary: Public policy for Sirius on business side, been involved in automotive data from emergency response perspective for last decade
Ulf: I have been working towards
resolution on wildcards issue with Daniel and feel we are
almost there
... wildcards do not add more to the functionality for common
uses with the change of position at the end of the tree
path
... we have some small implementation dependent issues but
pretty sure we will come up with a final solution and we would
no longer need wildcards
Daniel: theoretically it is
basically resolved and worked on an implementation that needs
to be refined so haven't issued a pull request
... we can do the release during our F2F meeting
... that release can be the baseline for Gen2 work
PatrickL: can you hint to the solution for example for all closed doors?
Daniel: you can go through doors
path and get all doors back if you don't specify the position
or if you want can use query parameters
... leaving position off will return all doors
Ulf: my understanding is we
introduce one more branch type, position based pbranch and used
by tools to generation information on positioning
information
... we still need to see if it works
Daniel: that is right, question
whether pbranch is needed or position is an attribute. I was
wondering if it would be useful for tooling but that is
something not finally discussed
... for CSV I created them for review and will work on final
solution
Laurent: pbranch isn't something we can look at presently, correct?
<PatrickLue> https://github.com/GENIVI/vehicle_signal_specification/issues/81
Ted: Gunnar was going to let us know
if we can have meeting space at GENIVI AMM, I will reach out to
him and Karin Hanson to confirm but may also be worth looking at
alternatives since it is not that far away
...previously we had identified VW and BMW as potential fallback
hosts
PatrickL: I can look but our office in Munich is smaller
Daniel: I will check
... I would also like a colleague in the WoT group who can
present on protocol abstraction that they are working on
... not sure they have more but would be worth seeing what they
are working on as applicable for Gen2
... they are close to a release candidate
PatrickL: Ted, perhaps you can see if there is substantive progress to include
Ted: will do and put both Patrick and Daniel in cc to Gunnar and Karin re F2F space
PatrickL: I have not received feedback on what elements should be in a Gen2 from a pure description standpoint and will create a pull request
Ulf: Ted sent a set of questions we could use to poll the group and would propose we do that to help further a resolution sooner than later
PatrickL: I had seen the questions as well but not discussion around them so gathered they might not be as easy to understand as hoped
https://lists.w3.org/Archives/Public/public-automotive/2019Mar/0008.html
https://github.com/w3c/automotive/issues/300
Ted: based on previous discussions there may be aspects of new VSS work that would not necessarily belong in Gen2, some attributes we may deem optional features etc in the interest of keeping scope for implementers reasonable. questions were formed to help make that clearer and see how people feel
Ulf: I think you managed to come up with a set of questions that would lead the group to a common understanding and where majority wants to go
Daniel: Second that, questions are clear and would let us go further
<magnus> +1
Daniel: from there we can divide what are data and protocol issues
Action Ted to create survey
<trackbot> Created ACTION-30 - Create survey [on Ted Guild - due 2019-04-09].
Ulf: we have a framework level
with html+js example client start
... we do no address access restrictions yet but we have server
core and registration. we only have dummy data being sent
back
<magnus> https://github.com/MEAE-GOT/W3C_VehicleSignalInterfaceImpl
Daniel: quick question, would the poll be binding for a resolution?
Ted: the questions are more
survey and will hopefully produce a common understanding we can
agree upon
... if we have opposing views at the end and two or more
proposals we can put those to a formal vote per W3C process
[generally we are encouraged to endeavor to work out a mutually
agreeable solution]