...
- Prioritized Topics:
- Capabilities - create a list of common vehicle capabilities/function to be expose via api
- IFEX (Interface Exchange) - a general interface description and transformation technology
- uServices - definition of common vehicle services usimg protobuf as the interface definition language
- Vehicle Signal Specification over Data Distributiion Service
- Vehical Information Service Specification (VISS) - a service for accessing vehicle information, signals from sensors on control units within a vehicle's network. It exposes this information using COVESA Vehicle Signal Specification (VSS).
- Vehicle API - will expose vehicle data as defined and described by COVESA's Vehicle Signal Specification to a variety of agreed upon touch-points in and out of the vehicle
- Hierarchical Information Model (HIM)
- Interface Blueprint
Agenda 2024-03-19
- Pick up where we left off last week.
- Walk through nascent backlog
Agenda 2024-03-12
- Contribute Commodity Catalog Call for Submission
- Start with submissions on seating, cabin climate from BMW, Mercedes, BMW, Ford, GM
- Signal discovery at interface level
- Stronger Agenda - Potential Comments
- Signal discovery at interface level
- Blueprints
- e.g. Errors. Ford has common errors
- Commodity Service
- never compared to VHAL
- BMW - Connected VHAL properties
- Start with Seating and HVAC
- Action Item: Provide Seating HVAC - Try to get Seating capabilities
- Ping Gunnar about commits
- Getting this offline and readiness
- IFEX - Overlay for AUTOSAR for ARXML VHAL/SOMEIP
- Actoin Item: Help Halim
- HIM Rule setAgree on cap
- User Identity
- ActionItem: What work can we work on as a group, key fob related to vehicle signals and how related to user identity
- Extension for key fob on VSS
- Authentication
- Some requests have OBD / Emmisions regulations
- How is this handled in VISS and Kuksa
- Very specific topics like IFEX <> uServices
- Backlog in GitHub
...
{"serverDuration": 139, "requestCorrelationId": "6c20686e1e8f12db"}