Paul: Ted created a F2F registration and Wonsuk started a draft agenda
<Paul> https://www.w3.org/auto/wg/wiki/Auto-f2f-april-2018
Wonsuk: I will continue to update based on input from today's
https://www.w3.org/2002/09/wbs/61259/April2018F2F/
Paul: I created an issue with W3C
Technical Architecture Group (TAG)
... it is now in their issue list
Ted: we had a partial review from them as part of wwwivi issue
<Paul> https://github.com/w3ctag/design-reviews/issues/234
Wonsuk: any sense of the timeline
Ted: I will ask Yves, the Team Contact for TAG, when they will take it up and point out we want to move forward toward PR
Paul: who is up for being editors on RSI
Ted: I have talked to a number of people during F2F and subsequently my understand is the following:
Ted: PatrickL, PatrickB, Adam,
Joakim, Guru, Mike, asked Urata but haven't heard back
... trying to recall others will look at my notes
... we need to figure out who is on what
... we should take to email and wiki since only a few are
here
... W3C Management approved our recharter today, we can start
forming in advance of Advisory Commitee review
... Kevin less available
PatrickL: definitely signals and framework is a priority
Ted: I suspect Guru on media
Joakim: I can contribute on the common data model and have heard from Gunnar about sensors
Gunnar: yes a data ontology
... extending the signaling
... vehicle data in general
... analysis on quality, reliability of the data. there is some
research around that
... you also have some past media experience at W3C?
Joakim: yes, that too - the media annotations
https://www.w3.org/wiki/GAO_Community_Charter#Dependencies_or_Liaison
[[Data warehousing, Extended Vehicle/Neutral Server
from ISO20078,9&80, Neutral Vehicle, Industry 4.0 (W3C EU project) discussions]]
https://www.w3.org/wiki/GAO_Community_Charter#Dependencies_or_Liaison
Ted: we have been hearing from iso group, neutral vehicle, fleet managers, oems, tier 1s, regulators, aaa, sensoris and others interest in using w3c auto specs to perform data sampling and relay to data silos in the cloud. i also am talking with dave raggettmy uk colleague some of you know from web of things. he is participating from in industry 4.0 EU project that wants to focus on automotive first and we are involving our colleague who leads privacy at w3c
Gunnar: we need to coordinate between Genivi and W3C on this
Ted: Marty and I just got off a two week european tour. we visited JLR, Valeo, Continental, PSA, Intempura, Volvo, NEVS, BMW, Caruso, Bosch, HERE/Sensoris plus Melco and Genivi, dinner with Magnus and Gunnar in Gothenberg. Major topics we hear were data warehousing, personal profiles, our spec work, scope of rechartering group. Point of the trip is to promote our activity as adoption is essential for standards to succeed. Hopefully
Joakim: I agree outreach and ensuring this gets widely adopted is very important
Paul: we need to encourage the early adopters to speak up
Gunnar: there are additional adopters that are not making their work known
Joakim: really great that there are implementations but have there been third party developers involved?
Ted: we had Roadrules and Vin.li, that startup under JLR incubator that does preventative diagnostics based on signals, vibration and other sensors, DAV.network, starting to attract fleet managers but yes we need more and them to be engaged
Paul: the crux to adoption is making sure it is pertinent to developers
Hira: can you tell us who has implemented VISS
Ted: as Gunnar mentioned you won't hear of some. RFQ are confidential. Melco, ETRI and Samsung in OCF, ACCESS, JLR either themselves or a partner, it is in the GDP development platform, available in android, etc. Volvo is perhaps doing something themselves or another company
<joakim> no comment
Hira: when do we think we can get to PR
<joakim> I have contact with them
Ted: we already have the requirements of implementations, encourage more to produce reports and the test suite. we will get more input before PR but pending issues we can potentially publish as PR later this month.
Paul: we don't have much time remaining for the next Business Group focuses in more depth
Ted: data warehousing clearly a big interest, we should switch to mail threads and start sketching out on wiki while we continue to try to align stakeholders
Paul: what about sensoris?
Ted: yes, Prokop is interest in doing some mapping exercises with our spec and has some tools that might help not only with that but in comparing existing VSS model with VW's.
Joakim: what about the use cases
we started?
... in media annotation we had tooling to make sure the spec
addressed all the use cases
Ted: PatrickL was a big proponent and we started some. We agreed it would be a good regular exercise and should ensure we align with spec features. more 3rd party developers would be helpful for their perspective
Joakim: we found it really
useful
... Wonsuk do you remember what we used to mark use cases with
features in the spec?
Wonsuk: roughly, goal was to
access a bunch of different metadata on different types such as
mpeg3 in dublin core
... a developer needs to understand before they can implement
and we were trying to make a common api
... I'll look for it and relay a link
Joakim: the use cases were written in the spec itself or maybe a separate document
Wonsuk: I will check and send to the mailing list
Paul: next call
We have an Auto Working Group call at Tuesday at 0000 EDT, 0500 GMT,
0600 CET, 1030 IST, 1300 CST, 1400 JST/KST, 2100 PDT (Monday night**).
Ted: regrets from me as I will be in a plane then
<wonsuk> Use Cases and Requirements for Ontology and API for Media Object 1.0: https://www.w3.org/TR/2009/WD-media-annot-reqs-20090604/
<joakim> +1
<wonsuk> This is the use case doc from media annotation wg
Paul: it will be great to sketch out the editors in more detail next week and can also delve further into next BG topics
Gunnar: possible regrets from me as well
[adjourned]
who leads privacy at w3c/
we will get some engineers and perspective from some of these organization. Marty worked with Paul Hansen on an article about W3C Auto in the latest (February) Hansen Report./