VOTable RESOURCE and TABLE number

[molinaro-m]

ConeSearch currently fixes to 1 RESOURCE with 1 TABLE response.
Should this be relaxed?

[Zarquan]

Is there a science case for extending this ?

[molinaro-m]

The reason to relax this is that, while a single "results" table is fine, the wording in the REC-1.03

There must be a single RESOURCE in the VOTable, and that contains a single TABLE.

prevents other RESOURCES even if they were not results one. This blocks the ability to add DataLink service descriptors.

So, it's not to encourage multi-table result sets but to allow RESOURCEs or TABLEs with other goals.
A change in the wording describing this would suffice, in my opinion.

[molinaro-m]

Pull request #56, that would be available after #55 refactoring, is supposed to fix this

[molinaro-m]

fixed by #56