refer to TAPSchemaDM

[pahjbo]

In the spirit of regularising data model descriptions in VO-DML - I have created https://ivoa.github.io/TAPSchemaDM/ perhaps this could be mentioned in an appendix

[pdowler]

The tap_schema is part of the TAP spec so the VO-DML description could live in this repository...

Normal practice is that a "data model" standard includes serialisation (xsd, json-schema) except in this case were talking primary about a database implementation. Aspects are serialised (more or less completely in xml using the VODataService xsd (imported by VOSI tables). That's a fairly tangled web of dependencies.

I think the use case for having tap_schema in VO-DML is code generation (in which I am including programmatic code and database schema/DDLs) -- is that right? Is there another reason/use that makes the VO-DML valuable that I'm missing?