...

Meeting Minutes

15 April 2025

• • VSS meta data extensions
    • sampling: and other related metadata can be overloaded, different meaning depending on situtational understanding
      • On-board API reporting data broker broadcast capabilities, useful for third party apps running on-board (encryption: authentication: access_control:) and API
      • Prescriptive in how it wants data collected cf https://github.com/COVESA/commercial-vehicles/blob/main/tmp/convert-spreadsheet/insurance-output.yaml
      • Descriptive in how the data was collected
    • Use of declared constants, some should be part of profile definitions
    • Privacy - Suggest bringing to EU Data Act project call
      • privacy_domain: [VehicleData, DriverData, LocationData, other?] use CONSTANTS, namespace or YAML declarations
      • data_collection:
        • sampling_rate: "100 ms" (need more than just frequency, event, conditional and calculation. may have fallback preferences in collection request - issue 7)
        • retention_policy: "30 days"
        • data_privacy: "anonymized" (defined constants, aggregate, sensitive, consent - would need more details)
      • network_serialization:
        • cycle_time: "10ms"
        • message_priority: "high" (timeliness of data can be highly important to third party, curve logging and other sampling conventions can help)
        • transmission_mode: "Periodotic"
    • Calculations and conditionals - issue 4
      • operational_conditions: "Normal operation, not during engine startup" - rewrite as a calculation based on other signals
      • dependencies: Vehicle.Powertrain.EngineCoolant.Level Vehicle.Powertrain.EngineCoolant.Pressure
      • minimum_send_interval: 
      • platform_system: motion_plus - this an on-board API and Supplier or OEM identifier? of interest to third party, example insurance using data in forensic evidence after an accident

...