Hi Markus -
Thanks for looking at the SSAP response and commenting; that is why we are doing this.
Another issue to look at is the usage of GROUP. To keep it simple, I used only one level deep groups, and the UTYPEs are fully specified. I don't see any need to make it more complex than that, but others may disagree.
On Fri, 26 Jan 2007, Markus Dolensky wrote:
> Thanks a lot for putting this out! What about a more explicit utype namespace
> definition such as
>
> <VOTABLE
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://www.ivoa.net/xml/VOTable/v1.1"
> xmlns:ssa="http://www.ivoa.net/xml/SSA/ssa-v1.0.xsd"
> xmlns:sdm="http://www.ivoa.net/xml/SpectrumDM/sdm-v1.0.xsd"
> xmlns:stc="http://www.ivoa.net/xml/STC/stc-v1.30.xsd"
> xmlns:char="urn:vo-characterization"
Beware, if you look at the query respone in a Web browser it may not display the XML header info fully (firefox doesn't).
Here is what we actually have for the namespaces currently in the SSAP query response:
<VOTABLE
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="xmlns:http://.../xml/VOTable/VOTable-1.1.xsd"
xmlns:ssa="http:www.ivoa.net/xml/DalSsap/v1.0"
version="1.1">
SSAP is a single name space, so the others are not needed.
For a Spectrum dataset, the SSAP namespace is replaced by Spectrum: xmlns:spec="http:www.ivoa.net/xml/SpectrumModel/v1.0"
Additional namespaces would be defined if those elements are present in the content.
So I think it is correct.