Long term VSS source format

Today we use "vspec" - Yaml with some extra semantics for include. This is sometimes criticized as we have no "formal" schema/ruleset to describe "correct" VSS. Some have proposed that a schema shall be created for JSON, but that then require that we first convert/expand to JSON.

But now we have ontologies getting more interest. Is vspec a viable long term format, or would something else be better. Possibly based on some ontology format (RDF? Owl?). Something that still "easily" can be converted to existing JSON/Yaml so that whoever wants to work with current tooling can reuse it. Like `RDF->Yaml->Protobuf`? Might allow a more expressive model.