Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Mention original contributing companies.  No known extension / application of results however.

Metadata & policies

...

This section describes the metadata used and its openness.

Metadata can be available (pdf documentation), structured, on open formats. It can additionally use ad hoc semantics (e.g. a fixed list of properties), reuse standard semantics (e.g. format properties, units) or be fully linked (e.g. reuse URIs as identifiers between connected entities).


Vehicle Signal Specification (Gunnar Andersson ) (see the documentation)

Non-formal metadata is within VSS with a given set of properties (label, comment, min, max…), provided in various open formats. VSS comes with an extension mechanism to create or update branches, signals or attributes.

There are policies in VSS in regard to its units: they should follow first automotive standards, or at least be SI. They are explicitly defined in the documentation.

SensorIS (Unknown User (gururaja.n) )

SensorIS uses different serialization open formats for its data, but the current release only has its metadata in protobuf. Units are standard are explicitly defined (e.g. deg_c for Celsius degrees)

There is a policy for extensions (new properties of signals)

Unknown User (benjamin_klotz) - please clarify what this means

Vehicle Signal Specification (Gunnar Andersson )

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

This specification does not define a data model.

The specification has requirement to data formats (JSON, XML Schema), uses URIs and some best practices that candidate data models should followTBA.

CVIM (Unknown User (benjamin_klotz) )

Measurement data comes in packages through data channels. The packages are provided in JSON (open format). Non-formal metadata is supposed to be provided in JSON too but so far only examples are available in the pdf documentation. Data package metadata is composed of a fixed list of properties.

There are no policies to create new properties or standard unitsTBA.

Table comparison (if applicable) (Unknown User (benjamin_klotz) To Be Confirmed)

...