...
Monday, April 20 - Vehicle Data
Agenda:
- Data Categories, VSS tree update with EV signals
- Value measurement formats
- Sprint & backlog review
- graphql schema example
- PoC design & implementation
- Webinar & virtual summit workshop content: gathering of topics
- AOB
Participants
Kevin V, Ted, Ulf, Gerald, Guru, Benjamin, Keith, Gunnar, Philippe
Minutes
graphql schema example
Data Categories, VSS tree update with EV signals
Gunnar: I did some polishing of the page Data Categories
- Philippe: what is the status of
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-89 |
---|
|
? - Ulf: I pushed a PR on VSS github repo at vehicle_signal_specification/pull/154 repository, that contains EV signals coming from Geotab doc on EV data access requirements, then this on the maintainer's side now (Daniel Wilms, BMW)
- Philippe: fine with this, we can close the ticket in CCS backlog
Value measurement formats
- Gunnar: goes through the latest modifications he made and through Ulf's comment at the end of the page
- Gerald: it is a side topic maybe, can we discuss in the future the anonymization of the vehicle ID ? in C2C they provide temporary IDs and change it every 5mn
- Gunnar: update the "vehicle identity" definition in the wiki page online
- Philippe: what is the status of
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-93 |
---|
|
? Gunnar: in the value measurement formats we have similar concepts as in CVIM and Sensoris, we need to check what maps to what
Ted: Sensoris is part of the Geospace consortium (OGC.3c work), AFAIK Sensoris is not technically aligned (tbc)
Gunnar: Unknown User (benjamin_klotz) can you help us do the mapping between the value measurement formats and the Sensoris spec ? ideally we should share the same names and perhaps the same content
Benjamin: I can do that both for Sensoris and CVIM as well
CCS-93 commented and changed to in-progress
discussion on Gen 2
Gunnar: I am not sure Gen2 needs to integrate the value measurement formats
Ulf: IMHO most of these should be outside of gen2
Gunnar: shows the "Protocol does not (yet) cover all variations of data exchange" bullet point of the section "Relationship to Protocols" of the wiki page
Ulf: however some data structures shown in the value measurement formats should be added to a gen2 client if the client needs historical data (Ulf Bjorkengren please review here and below)
Ulf: my proposal was that if a node supports historical data you can have metadata in the tree
Ulf: we need to discuss this in the Gen2 group
Ted: how does an application register and sign up to use data (this is related in my opinion to the best practice work in W3C ) ?
Sprint & backlog review
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-88 |
---|
|
reminder for Keith Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-82 |
---|
|
- Gerald: no need to analyze this use case further, sub-task converted to issue and sent back to the backlog
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-73 |
---|
|
- Philippe: browses through the wiki page 5GAA related papers for cloud & connected services
Gunnar: the ones at the top are more relevant that than ones at the bottom, who is interested to read the article of V2X ?
Philippe: will these papers influence our work to some extent ?
Gunnar: it might be interested to look there for the use cases for the demonstrator, so far we have not been so clear on what we want to demonstrate
- sub-task converted to issue and sent back to the backlog
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-62 |
---|
|
done Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-5 |
---|
|
- look at Gunnar's comment above on the use cases for the demonstrator
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-70 |
---|
|
- discussion on what this work item is all about
- Ted: there are some high-level stuff in the Automotive Business Group wiki, look at https://www.w3.org/auto/wg/wiki/Vss_data
- ticket updated on line by Gunnar
- reminder for Benjamin
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-71 |
---|
|
- list of materials to review updated, reminder for Gerald
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-6 |
---|
|
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-83 |
---|
|
- Gunnar: Ulf and I are discussing this topic offline, our thoughts on the access control implementation are not mature yet
- Philippe: I propose to move it as a subtask of
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | CCS-22 |
---|
|
Kevin: my colleague is w
Wednesday, April 15 - Communication Framework
...