General inputs

Steve input:

• First/early 'next steps'
  • How to organise project during its creation phase?
    • Move discussion to 24/7 online where possible for faster pace than weekly calls
    • Top level phases?
    • Record and comment on work breakdown.
    • Project management: where, what, how
  • Take a breath - are we aligned on top level goals and what/who/how? Who will be active? What are their interests?
  • Implementation
    • Check state of VISS Docker support
    • Confirm project setup for upstreams, e.g VISS, DBs
      • Can be considered part of early wider socialisation of project.
    • Planning for additional DBs, e.g. Apache IoTDB, Realm
  • Determine early Use Cases to be 'guided' by
  • Look at connection to MongoDB/BMW work. What is common?
  • Feeder link

Use cases to be explored

tbd

VISS Protocol Servers

Notes on known OSS VISS Servers:

• WAII
  • W3C reference implementation for the VISS standard.
  • Hosted by W3C as part of the W3C and Covesa cooperation agreement
  • Has support for historical (persistent) data
  • Has backend abstraction for VSS data stores
  • Architecture supports connecting southbound data feeders to a data store
• Kuksa.val
  • Project hosted in Eclipse.
  • Historically inconsistent support for VISS (see Detroit AMM presentation and mentioned PR discussion)
  • Architecturally live 'last value' data only. No current support for historical or persistent data.
    • Assumption is that persistence is left to northbound clients?
• Aos Edge
  • The Aos Edge orchestration platform provides a VISS Server as part of the Aos Edge Core embedded part of the platform to provide secure, abstracted data to services orchestrated by the system. Implementation hosted at the Aos Edge Core product site.
  • VISS support equates more to VISS v1, with access control provided by the Service definition controls in Aos Edge, rather than using the access control specified in VISS v2.
• Other earlier implementations
  • During the early development of VISS (e.g. v1) various groups created implementations.
  • It appears they are no longer maintained but they are mentioned here for completeness.

VSS Data Store / Embedded DBs

WAII VISS server currently supports the following DBs as data store backends:

• SQLite
• Redis

Notes on OSS DB candidates to be added (this does not represent their complete feature lists):

• Apache IoTDB
  • Column orientated time-series DB designed for embedded IoT (high ingestation rate, low latency query etc.)
  • User Defined Functions for data processing at the Edge
  • Wide support for Apache eco-system, e.g. Flink, Hadoop, Spark in the cloud.
  • Wide range of API bindings + MQTT broker
  • Some sync functionality between instances
• MongoDB Realm
  • Object DB initially developed for mobile.
  • Wide range of mobile API bindings + C#. C++ binding in Beta.
  • Advanced support for automated sync between instances. Also sync between Realm and Atlas (MongoDB Cloud DB) in the cloud.