Alberto.Micol at eso.org
Tue Dec 19 09:45:41 PST 2006
Dear Doug and Jonathan,
The paragraph 3.3.6 Query Response Metadata of the SSA0.97 document
that the leading "spectrum." in the UTYPE for a Spectrum data model
should be omitted, the reason being that SSA metadata do not need to
In such case, shouldn't SSA have its own model/name space?
I do not think we want to have UTPYEs not associated to a model, do we?
Then in the Appendices (both A and B) one reads:
<VOTABLE ... xmlns:sdm="http://www.ivoa.net/xml/SpectralDataModel/
<FIELD name="upper/lower bounds of spectral bandwidth"
datatype="float" arraysize="2" ID="boundsSpectral"
(well, the correct utype should be
instead, but that is not the point...)
The point is that the votable declares the SDM name space, but then
the utype used
is not SDM nor SSA compliant, because SDM does not know the "SSA."
and because SSA dictates that the word "Spectrum." should be dropped.
To recap, depending on whether if I follow :
1. the statement in SSA 3.3.6,
2. the SSA Appendix,
3. the SDM v1 rel cand 1 rev 2
I can come up with three (or maybe four) different utypes for
the same field:
which is wrong because sdm wants "Spectrum." and not "SSA."
What is probably meant here is instead:
which means that an SSA name space is to be introduced
but this we know to be wrong: sdm requires "Spectrum."
at this point in time this one seems to me the only
until of course we get the characterisation data model approved.
But in the mean time we have to get the ball rolling...
Could you please clarify?
PS: BTW, I support Randy's comments that the examples given in the
are really important to the developers. It would be so nice to have them
fully thought through, so to act as approved references that one
and adapt to his/her case... It would speed up development!
More information about the dal