VO-DML <-> database schema

[Gerard Lemson]

Short follow up:
Would be nice to represent the mapping as a votable with empty tables, annotated with the data model.
But there are some substantial complications with a relational mapping caused by freedoms allowed in VO-DML wrt VO-URP.
Such as data type inheritance and attributes/references with cardinalities > 1.

> -----Original Message-----
> From: dm-bounces at ivoa.net <dm-bounces at ivoa.net> On Behalf Of Gerard
> Lemson
> Sent: Thursday, May 14, 2020 9:24
> To: Paul Harrison <paul.harrison at manchester.ac.uk>; dm at ivoa.net
> Subject: RE: VO-DML <-> database schema
> 
> Hi Paul
> With Laurent Bourges I wrote a VO-DML -> relational schema mapping (well,
> VO-URP really), which I can find for you and which basically implements B.2 in
> Appendix B of the BVO-DML spec.
> It includes filling in TAP_SCHEMA tables. Note that it does make use of some
> restrictions in VO-URP and has a particular implementation of how to map
> inheritance hierarchies.
> In SciServer we are using this for our implementation of the resource access
> control data model.
> 
> Have to run for 5 meetings now, but will look it up later.
> 
> Cheers
> Gerard
> 
> 
> > -----Original Message-----
> > From: dm-bounces at ivoa.net <dm-bounces at ivoa.net> On Behalf Of Paul
> > Harrison
> > Sent: Thursday, May 14, 2020 8:27
> > To: dm at ivoa.net
> > Subject: VO-DML <-> database schema
> >
> > Hi,
> >
> > does anyone have some code for translating from VO-DML -> TAP schema
> > before I do it myself? Also code going in the other direction would be
> > useful - from db schema to VO-DML?
> >
> > Cheers,
> > 	Paul.
> >
> > p.s. - Ideally I was looking for something fairly self contained like XSLT...