17:01:27 RRSAgent has joined #auto 17:01:27 logging to http://www.w3.org/2016/12/20-auto-irc 17:08:28 present+ Kaz, Kevin, Mike, Patric_B, Patrick_L, Paul, Peter, Rudi, Song, Urata 17:08:58 urata: would like to start with the testing topic 17:09:54 ... mentioned some concern within my message 17:10:22 ... attached an attachment file 17:10:32 ... to describe how to handle external resources 17:10:47 ... may be going to break the W3C testing policy 17:11:08 -> https://lists.w3.org/Archives/Member/member-automotive/2016Dec/0035.html Urata-san's message (member-only) 17:11:31 urata: the concern is clear 17:11:48 ... if it's OK to refer to external resources, there would be no problem 17:13:46 rstreif has joined #auto 17:14:07 kaz: personally think there should not be problem if all the resources are accessible online 17:14:14 ... can check with PLH 17:15:29 peter: the definition of "testing" is testing specs 17:15:38 ... not the server resources themselves 17:16:01 paul: right 17:16:19 ... don't see how to test our tests without external resources like VSS 17:16:53 kaz: will talk with PLH and clarify the requirements for testing 17:17:02 paul: ok 17:17:13 ... anyway Urata-san has started great work on testing 17:17:56 Present+ Ted 17:18:09 topic: Issues 17:18:20 i/would like/topic: Testing/ 17:18:22 rrsagent, make log public 17:18:35 rrsagent, draft minutes 17:18:35 I have made the request to generate http://www.w3.org/2016/12/20-auto-minutes.html kaz 17:19:11 rudi: shows issues on his screen 17:19:46 -> https://github.com/w3c/automotive/issues/107 Issue-107 17:22:35 rudi: discrepancy between the document title and the shortname 17:23:27 ... would propose we rename the title to "Vehicle Information Service Specification" 17:25:31 kevin: change the title from "Vehicle Signal Server Spec"? 17:26:26 kaz: either is ok 17:26:35 ... it depends on our preference as the whole WG 17:26:59 [vehicle-information-service shortname is what came out of mail thread. i believe we can change the shortname and title if desired] 17:28:57 kaz: so the resolution from this call is changing the document title to "Vehicle Information Service Specification" 17:29:05 ... and use that title for the 2nd WD 17:29:07 ... right? 17:29:12 rudi: yes 17:29:25 urata: so you're suggesting we change the document title? 17:29:42 ... is it OK to change the title of the document? 17:30:03 ... we should ask all the group participants about their opinions as well 17:31:30 ... from my viewpoint, I've been already using the name of "Vehicle Signal Server Specification" in many places within my codes 17:32:15 ... on the other hand, the acronym for "Vehicle Signal Server Spec" is kind of confusing since it's VSSS and similar to VSS 17:32:31 peter: would agree with Rudi's argument 17:32:49 urata: can change the name myself 17:33:00 ... but we should ask others' opinions as well 17:33:08 rudi: yes 17:33:29 ... this issue-107 itself is one of the feedbacks for the FPWD 17:34:07 urata: ok 17:35:59 kaz: in that case, the client-side spec's name would be also "Vehicle Information Client Specification". right? 17:37:00 paul: "Vehicle Information API" would still make sense 17:38:07 kaz: ok 17:38:20 ... we don't have to decide the client spec's name now 17:38:25 ... but at some point, we need to think about that 17:38:27 rudi: ok 17:38:58 paul: that (=using "Vehicle Information API") is my opinion 17:39:01 kaz: ok 17:39:33 ... we should set some deadline to get feedback for this proposal 17:39:50 rudi: would like to publish the 2nd draft with the updated name next year 17:40:26 -> https://github.com/w3c/automotive/issues/99 Issue-99 17:41:05 rudi: JSON Schema instead of WebIDL 17:42:46 kevin: agreeable 17:43:05 patrick: have good experience on JSON Schema 17:43:25 ... all the media is defined using JSON Schema within VW 17:44:06 ... could express the data model easier using JSON Schema than WebIDL 17:46:37 kevin: offer to add JSON Schema notation as well as WebIDL in January 17:46:45 Per Working Group Meeting: consent to accompany the specification with the JSON schema metadata for the API specification; @drkevg and @acrofts84 to add JSON schema and WebIDL definitions in 1/2017 17:47:31 -> https://github.com/w3c/automotive/issues/91 Issue-91 17:47:39 rudi: whole issue list for the server spec 17:47:54 ... generated by Adam 17:48:22 ... would be great if Adam and Kevin could go through the list 17:49:04 rrsagent, draft minutes 17:49:04 I have made the request to generate http://www.w3.org/2016/12/20-auto-minutes.html kaz 17:49:42 #91: Per Working Group Meeting: @drkevg, @acrofts84, and the editors and chairs review the list and clear the remaining items. 17:51:33 kaz: btw, we should change the text for the issue label "Vehicle Signal Server Spec" to "Vehicle Information Service Spec", shouldn't we? 17:51:36 rudi: right 17:51:55 -> https://github.com/w3c/automotive/issues/87 Issue-87 17:52:12 rudi: Deliverable definition 17:53:23 #87: Per Working Group Meeting: addressed at this point with the new charter. Close. 17:54:32 -> https://github.com/w3c/automotive/issues/85 Issue-85 17:58:23 #85: Per Working Group Meeting: ticket stands; Vehicle Information API Specification yet to be created; 17:59:27 topic: Meeting during CES 17:59:54 paul: what would people discuss at CES? 18:00:01 ... WG? BG? 18:01:31 rudi: let's meet in Thursday afternoon 18:01:54 ... 3-5pm 18:02:34 ... myself can't attend CES but Magnus will be there 18:03:09 [ adjourned ] 18:03:42 Meeting: Automotive WG 18:03:53 Chair: Rudi, Paul, Peter 18:04:06 rrsagent, draft minutes 18:04:06 I have made the request to generate http://www.w3.org/2016/12/20-auto-minutes.html kaz 18:04:31 Regarding the test assertion document, it is being created at Hirabayashi-san's site. 18:06:03 yes please. I forgot to mention in the meeting. 18:06:17 arigatougozaimasu 18:07:18 rrsagent, draft minutes 18:07:18 I have made the request to generate http://www.w3.org/2016/12/20-auto-minutes.html kaz 18:09:08 Bye 18:09:44 Yes please.. Thank you! 20:28:14 Zakim has left #auto 20:43:09 ahaller2 has joined #auto 22:19:32 ahaller2 has joined #auto