VODataService 1.3 PR - deprecation of TAPType
Paul Harrison
paul.harrison at manchester.ac.uk
Thu Jul 23 13:21:48 CEST 2026
On 2 Jul 2026, at 13:33, Markus Demleitner via registry <registry at ivoa.net> wrote:
Dear Registry community,
A month ago I have uploaded a proposed recommendation for
VODataService 1.3 to the document repository:
I would like to question the current form that the deprecation of TAPType is taking in the standard. I see how there is an irritating duplication (with different names) of the “obvious” primitive types (int, float etc.) but what about the other more specialist TAP types like TIMESTAMP and POINT - what are providers supposed to do if their TAP service exposes such columns - surely there should be some attempt to unify all VOTableType and TAPType into a single type.
Regards,
Paul.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20260723/a3100e8b/attachment.htm>
More information about the registry
mailing list