SSAmples

[Markus Dolensky]

> I guess I don't really see the point. If it's constant, use a PARAM within
> the group. If it's a column, use a FIELDref within the group.

Ah, a mixed approach: Since VOTable allows this it's ok, of course.
I tend to use FIELD(ref) and PARAM(ref) symmetric, but that's a just a personal 
convention and I don't want to impose this on anybody else.

Clarified.

> Another comment on Target: the whole first table giving the global info,
> including Target, is only a table because you're not allowed to have
> GROUP elements directly under RESOURCE. It would be cleaner if you could
> just eliminate the first <TABLE> and </TABLE> and have those PARAM and
> GROUP values directly under RESOURCE. Is the reason VOTable doesn't
> allow this that GROUPs could potentially include FIELDS?

In future versions we might have FIELD elements also in the global section. So, 
for the sake of extensibility I don't mind wrapping global parameters into a TABLE.

Markus