Meetings: InterOpMay2011Registry Relational Registry DMThis page describes efforts towards creating a "relational" Registry DM that will express the same data model that is implicit within the resource XML schema, in order that the new DM definition could be used with a next generation Registry interface which might be more TAP-like. One of the most desirable features of a relational DM is that it contain a few tables as possible to make querying it easier. I have tried to model the VOResource schema (only) to achieve this aim and the result is shown below. As can be seen this still involves the creation of 13 tables if the current element multiplicities that are in the XML schema are to be fully supported, and note that this number will increase when other schema are included. The methodology for mapping the XML to relational schema involved the following transformations.
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | A Java library of objects that represent the Registry metadata models along with standard XML schema mapping (via JAXB) and the above relational mapping (via JPA) is available at http://software.astrogrid.org/doc/ivoa-objects/ | |||||||
-- PaulHarrison - 13 Jun 2011 <--
|
Meetings: InterOpMay2011Registry Relational Registry DMThis page describes efforts towards creating a "relational" Registry DM that will express the same data model that is implicit within the resource XML schema, in order that the new DM definition could be used with a next generation Registry interface which might be more TAP-like. One of the most desirable features of a relational DM is that it contain a few tables as possible to make querying it easier. I have tried to model the VOResource schema (only) to achieve this aim and the result is shown below. As can be seen this still involves the creation of 13 tables if the current element multiplicities that are in the XML schema are to be fully supported, and note that this number will increase when other schema are included. The methodology for mapping the XML to relational schema involved the following transformations.
-- PaulHarrison - 13 Jun 2011 <--
|