Page History

...

Expand

Backlog

Android Compatibility Definition Document
Software architectural task force : Vehicle Data architecture for Android
Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs
question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing
Signal to service translation
Secure access control in Some/IP

Participants

Apologies

Agenda

Minutes

Permission enforcement implementation

Outcome of call with OpenDS

Gunnar: I have not succeeded to work with opends yet, I tried to build on ubuntu, no show stopper for the timebeing, nothing changed so far, on it

Feature content for MS3

Maria: will Android R11 be used for the demo
Stephen: There is R9 and R10 on R-Car. Android 11 would need to check more from Google agreement perspective.
Gunnar: We will use R10 for the demo
Philippe: invite Bosch to do some implementation tasks, e.g. on the application layer
Stefan: shows the block diagram in External Data Server Proof-Of-Concept - Work Breakdown Structure
Philippe: explains what the team has implemented, will implement for MS3 and which tasks are to be assigned (app development)
Stefan: explained which vehicle properties are available in the demo (look at
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key AASIG-58
)
Maria and his developer will look at it and provide feedback
Stefan indicates that Tieto has agreed to make their VHAL code available, it will be under MPL 2.0, look at
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key AASIG-116
)

Participants

...

Page tree