VO-DML mapping RFC page
Pierre Fernique
Pierre.Fernique at astro.unistra.fr
Thu Oct 26 17:14:10 CEST 2017
Sorry, sent again for Apps and DAL members.
Pierre
---
Hi DMers,
I have a question concerning the VO-DML mapping RFC document recently
published. At the page 24, we read this constraint (in blue) :
May be I am wrong, but the obligation of removing DM elements of the
MODEL header if there are no relevant data in the VOTable*will imply a
very big constraint on the data provider, notably in the framework of
TAP*. Concretely, it implies that the provider system should be able to
associated to each column of its DB the relevant element of the DM or
DMs associated to and possibly to manage the dependencies with other
columns to know if the DM elements should or should not be inserted in
the response (the list of resulting columns depends of the user query .
For instance, how Simbad database TAP system will be able to generate
the appropriate MODEL elements for this kind of request "/SELECT s_ra
from basic/").
If I am right, I am afraid that the MODEL mapping will be extremely
difficult to implement in the framework of TAP.
Cheers
Pierre
Le 11/10/2017 à 09:30, Laurent Michel a écrit :
> Dear all,
>
> The RFC page for the VO-DML mapping is open now:
>
> http://wiki.ivoa.net/twiki/bin/view/IVOA/VODML-Mapping
>
> Please read, test and comment.
>
> Regards
> DM chair & vice-chair
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20171026/2f719e02/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 50359 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20171026/2f719e02/attachment-0001.png>
More information about the apps
mailing list