<scribe> scribenick: ted

<scribe> Scribe: Ted

WG meeting schedule

Peter: this is 2pm PST and 11pm CEST and might be better earlier in the day
... for the west coast, 9am onward start is reasonable

Glenn: that would be noon for us on east coast and 6pm for Europe

Peter: obviously not enough to decide

Ted: I can start a doodle and propose the different times, starting as early as 8 or 9am PST?

Peter: it cuts into when people tend to head home

Ulf: yes but that would be much better than at present, even an hour earlier (10pm CEST) would be better

Gunnar: depending on the day, I might not be able to do five

Ted: sounds like 5 optimal hours and question of which day. suggest we avoid Mondays due to holidays and Fridays as it may interfere with European weekend plans

Peter: we'll see what people think and aim for a single time instead of alternating

Open source project to promote VSS data model

https://docs.google.com/document/d/1ACoHvQZQTgJF41gIvM48RfoG695O58AUjdvGATGBB6k/edit -> Project writeup

Peter: this aligns well with Joakim's work in Graph

Glenn: if we narrow the use cases, that would make it easier to remap sample data
... I would prefer those aimed for the public good, for instance harsh braking with location for mapping hazardous intersections
... we can also use ABS brakes for evaluating road conditions

Peter: that is more tangible with clear use cases like this, doesn't have to be many just a couple

Glenn: agree, most minimum viable project

Ulf: those are good proposals, we could perhaps come up with a few more. I'm reminded of some of our colleague Amir's recent presentations
... micro-weather was very interesting
... predictive maintenance such as based on cranking voltage another
... we can figure out what signals to bring from stakeholders

Peter: having use cases can help

Glenn: agree it is useful to include use cases on the document and then we can go to our design engineers and see which are more readily feasible

Ted: when the document settles I'll move it to a wiki, @@sample, @@

Gen2 editors

Peter: I guess we have Ulf who expressed interest in continuing as an editor but from Geotab instead of Volvo
... PatrickB isn't on the call

Ted: I will be speaking with Colin Lee from JLR tomorrow@@

Daniel: expect Adnan, I or someone else from BMW to as well

Ted: I expect PatrickL to kick in when his schedule settles and to pull in pieces from ViWi protocol such as Registry so we can move more quickly than we have been

VSS status

Peter: I noticed we have an outstanding pull request and wondering what the timeline is and how we should work with it

Daniel: much of our energy has gone into discussions around taxonomy, updating documentation etc
... Benjamin finished his thesis and Adnan is taking over, we will settle and get back to it

Ted: CharIN, IEC@@ on EV
... ADAS, diagnostics

Daniel: yes, I want to get others to jump in
... the spec files aren't that legible and we probably want to leverage some open source tools for representing the tree

Gunnar: for visualizing the tree and...?

Daniel: yes and to be able to zoom in on certain branches, I am hearing this from my colleagues as well starting to look at this

Gunnar: yes, that would be helpful for clarifying - we can also use plantUML but that only gives the tree structure

Ted: if we publish a JSON view from tree spec there are tools

Gen2 reference implementation update

Peter: Mitsubishi and Volvo started this Gen2 implementation and hopefully Ulf will continue from Geotab
... this ties into the Graph project

Ted: yes and at the f2f @@use cases sockets

Ulf: at a later stage, yes tie together
... worth mentioning the latest step we are talking about, building this implementation onto a server that can be remotely accessed
... bootstrap install is rather involved whereas an instance running somewhere then people can play with it more readily

Gunnar suggests https://jsonviewer.stack.hu or https://jsonviewer.stack/

Ulf: people can then start playing with client apps and we can have a few simple example ones available
... should only take a week or two

Peter: do we have a place we can deploy it?

Ulf: Ted thought it might be possible at W3C

Peter: maybe a docker image would be useful too

Ted: yes, I know the policy for WG 'labs' as will send an email on details, if you are inclined to contribute to debugging, administration etc send me your ssh key

https://cytoscape.org/

Ted: I have pet peeves about Docker unless we are willing to commit to being diligent maintainers wrt security updates etc

VSSo status and location

Gunnar: I would prefer to work on github infrastructure to include Travis or some other continuous integration

Ulf: I will talk to you about it

Peter: there is increased interest in VSSo and wonder where that will end up? is that in W3C WoT?
... there is considerable interest about it within Volvo

Ted: Raphael@@ ws...

Daniel: Benjamin was the main editor, please involve me in the discussion with him and Raphael

@@mark fox, process

Ted: I will take the action...

Peter: any other business?

http://automotive.eurecom.fr/vsso

[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: Ted Glenn Ulf Peter Don Gunnar Harjot Daniel
Regrets: Adnan
Found ScribeNick: ted
Found Scribe: Ted
Inferring ScribeNick: ted
Found Date: 24 Sep 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.)