...

Tooling that supports the generation of DB DDL for the creation of schemas for the VSS data-model and any other model using the vspec notation.

Inputs / Feedback

1) API spec as input (Daniel Alvarez Nov 2024)

Thread with Daniel on Slack summarized here as it will disappear after 90 days. He suggested that if an API can be used as an input it would likely provide hints as to what is needed for the output:

"I thought that if you have the api specification given, one can select the concepts of interest from the specification and generate the schema for the database that matches exactly that. In your case, I’m assuming that the database can be set from scratch up. So, no dependencies or constraints are given. Wouldn’t be easier then to make the database compliant to the api specification?"

Stephen Lawrence : I agree with Daniel's idea that if an API spec for a function + meta-data is available then that should be helpful for generating a schema. That could be an enhancement. We also have the use-case where a DB is used as a data store, with no API available or multiple possible accessors and a straight forward VSS representation is required, e.g. a starting point in the COVESA Central Data Service Playground where VSS data can immediately be stored.