roy at cacr.caltech.edu
Wed Jan 21 07:06:09 PST 2004
> Taking your v2.txt, we can see the contents of XMLDATA being moved
> separate file, results.xml, say.
No, the XMLDATA stays with the rest of the metadata a la VOtable.
There is, however, a separate file that is a schema for the records of
the table. It says that "magnitude" element is a float and
"constellation" is a string. It says that there is exactly one of
these in each record, and they must come in order in the record. That
is *all* it says about these elements.
This record schema can be kept very simple because most of the
metadata remains in the VOTable as usual. The limits on values (0 < RA
< 360), the units, UCD, etc, are all expressed exactly as before.
> As an example, does an element in a VO record get described as an
> xsi:element construct which we have extended to include attributes
The record schema doesn't mention UCD. The UCDs and other metadata are
in the VOTable FIELD elements as usual. The record schema is
mininal -- just element name and data type. We will however need to
something for table cells that are arrays and groups.
> NONE of this will invalidate VOTable or is meant to replace it.
Precisely. We have just added a new representation XMLDATA to the
exiasting TABLEDATA, BINARY, and FITS representations.
Thank you for your encouragement on this project
More information about the votable