VSS storage format

*This topic originates from a mail from Tata*

A guy from Tata asked for how to represent large set of data in VSS and how to validate it. We do not have any answers yet. Would it be interesting for COVESA to define a "reference storage format", in CSV, JSON, or whatever? That possibly could be used for data exchange and/or persistence.

This is a bit related to a topic that comes up now and then - if COVESA shall specify/recommend metadata in observations. For example it would be possible for us to define terms like "accuracy" and how to specify/interpret it which possibly also could be included. If COVESA would come up with a format we could possibly also add some (Python) tooling that validates that all data are aligned with the "current" VSS specification, like all signals exist and values are OK for the type.

FYI: @UlfBj @SebastianSchildt @adobekan @slawr @paulboyes

```
Signal, Value, Timestamp
Vehicle.Speed, 123.45, "2023-05-03 12:12:00 UTC"
Vehicle.Speed, 123.67, "2023-05-03 12:12:02 UTC"
```