16:20:03 <RRSAgent> RRSAgent has joined #auto
16:20:03 <RRSAgent> logging to http://www.w3.org/2017/04/18-auto-irc
16:20:05 <trackbot> RRSAgent, make logs public
16:20:05 <Zakim> Zakim has joined #auto
16:20:07 <trackbot> Zakim, this will be
16:20:07 <Zakim> I don't understand 'this will be', trackbot
16:20:08 <trackbot> Meeting: Automotive Working Group Teleconference
16:20:08 <trackbot> Date: 18 April 2017
16:21:29 <ted> Rudi: still 10 issues that need to be addressed for VISS
16:21:41 <ted> … plenty of discussion but some lacking resolution
16:22:05 <ted> … we need our editors to see if they can wrap them up so we can bring the doc to CR
16:22:32 <ted> … Urata, from your testing can you say that from your perspective it works?
16:23:26 <ted> Urata: basically the remaining issues are very detailed and not major obstacles
16:23:50 <ted> Rudi: we want to publish VIAS as FPWD. there are not too many issues
16:24:09 <ted> Urata: I have been focused on VIAS the last two weeks, solved 5 github issues
16:24:20 <ted> … you can see them from the closed issues page
16:24:44 <ted> https://github.com/w3c/automotive/issues?q=is%3Aissue+is%3Aclosed
16:24:56 <ted> Urata: there are two remaining issues for VIAS at present
16:25:10 <ted> … one is rather big, write WebIDL for VIAS
16:25:32 <ted> … I haven't received review for my change but merged it myself
16:25:40 <urata_access> https://w3c.github.io/automotive/vehicle_information_api/vehicle_information_api_specification.html
16:26:13 <ted> Urata: I added WebIDL definition on this document
16:26:27 <ted> … Hashimoto commented on the security and privacy considerations
16:26:38 <ted> … there are some other minor issues that have been addressed
16:26:54 <ted> … another rather big github issue is 156
16:27:07 <ted> https://github.com/w3c/automotive/issues/156
16:27:16 <ted> [[Whether VIAS is high level API or Websocket based APIs?]]
16:29:28 <ted> Urata: if this as a high level API then it should be more abstract
16:30:02 <ted> … Rudi's comment was that VIAS is a counterpart to VISS and should be described concretely, using web socket
16:31:16 <ted> Gunnar: agree we do not need to mention explicitly the Javascript library and that is consistent with your WebIDL definitions
16:31:46 <ted> Urata: if it is a library definition then it would be considered an application
16:31:58 <ted> Peter: I do not see how it would be defined as an application
16:32:05 <ted> … a library is not an application
16:32:18 <ted> … I agree it should not be defined as a JS library
16:32:45 <ted> Urata: yes, it can be implemented as a JS library but the spec does not define how it should be implemented
16:33:09 <ted> … we should remove the phrases in the spec that call it a JS library
16:33:22 <ted> Gunnar: isn't it possible to check what is normally done in W3C?
16:33:55 <ted> Peter: usually it would be WebIDL at W3C but we are also not the usual group
16:34:56 <ted> Rudi: correct, it would be a definition of an extension or to be implemented directly in a browser. we have not received support from browser vendors and took a different route
16:35:07 <ted> (service/sockets)
16:36:07 <ted> Rudi: agree we should remove JS library and I am OK with removing the direct correlation with VISS and sockets
16:36:50 <ted> … a VIAS compliant client would most likely need to implement against VISS but it does not need to be explicit
16:38:28 <ted> … presently we only have 1 server definition, VISS
16:38:47 <ted> Urata: in the current VIAS document there are connect and disconnect methods
16:39:21 <ted> … if the underlying connection is something other than web sockets it might be a stateless service without a persistent connection
16:39:52 <ted> Rudi: we can clarify connection-less protocol option
16:40:25 <ted> Urata: that is a good solution
16:40:52 <ted> … I will address 156
16:41:19 <ted> … we also have issue 164
16:41:40 <ted> https://github.com/w3c/automotive/issues/164
16:42:36 <ted> Urata: VIAS already has this in mind
16:45:49 <ted> … publishing FPWD should be possible after addressing the remaining issues
16:54:56 <ted> [discussion on VIAS implementations. most likely will be a JS library but can also be done directly in a browser or browser extension]
16:55:26 <ted> Urata: my concern is whether VIAS will be accepted as a W3C specification
16:56:11 <ted> Rudi: we will find out when we get to FPWD what the feedback will be from the broader community, receive their comments and pushback
16:56:45 <ted> … I wanted to touch base on demos at AMM
16:56:47 <ted> q+
16:58:44 <ted> Ted: we have a table and demos planned by Peter and Wonsuk
16:59:06 <ted> … I would like to see Urata demo too if he is interested
16:59:31 <ted> … I will have a W3C banner of sorts and some printed materials on W3C. if you are doing demos you may want to have some materials as well for possible follow up
16:59:49 <ted> Urata: I have a demo but the UI is a bit rough and the data is not realistic
17:00:19 <ted> … if it is necessary I can bring it but think Peter-san's demo will be better
17:01:14 <ted> Ted: do not feel pressured but encouraged :)
17:01:18 <ted> Peter: I think the test suite is very useful as it is
17:01:37 <ted> … we will be opening OpenDS for signals
17:03:03 <ted> … hopefully I can have that available in time, some other priorities are competing for resources
17:03:21 <ted> Gunnar: keep in touch, we might be able to find some resources to help fix it up
17:03:39 <ted> Peter: hope is to run this on Genivi development platform and not on a PC
17:05:32 <ted> … on our github there is a report in progress
17:06:07 <RRSAgent> I have made the request to generate http://www.w3.org/2017/04/18-auto-minutes.html ted
17:07:58 <ted> Gunnar: the normal showcase is only one day, Genivi development platform will be open the entire week
17:10:44 <RRSAgent> I have made the request to generate http://www.w3.org/2017/04/18-auto-minutes.html ted
17:11:42 <gunnarx> gunnarx has left #auto