Additions to TAP Implementation Notes
Marco Molinaro
molinaro at oats.inaf.it
Tue May 6 03:37:01 PDT 2014
Hi everybody,
thanks to Dave's reminder I added too a small section about TAP_SCHEMA
schema having a custom name.
I put it just after the TAP_SCHEMA optional section.
I agree on letting TAP_SCHEMA be an optional component of a TAP service.
TAP services I'm working on actually use it to provide data to the tables
endpoint, but otherwise it would have been only a duplication of that
endpoint's information.
Cheers,
Marco
2014-04-30 2:48 GMT+02:00 Dave Morris <dave.morris at metagrid.co.uk>:
> I would like to draw your attention to some new proposals we have added to
> the TAP Implementation Notes.
>
> Hopefully, the first three will be fairly harmless.
>
> Explanation of optional features
> http://volute.googlecode.com/svn/trunk/projects/dal/
> TAPNotes/TAPNotes-fmt.html#ac-geo-opt
>
> Modulo operator
> http://volute.googlecode.com/svn/trunk/projects/dal/
> TAPNotes/TAPNotes-fmt.html#af-modulo
>
> Bitwise operators
> http://volute.googlecode.com/svn/trunk/projects/dal/
> TAPNotes/TAPNotes-fmt.html#af-bitwise
>
> The last two will need further discussion.
>
> Making TAP-SCHEMA optional
> http://volute.googlecode.com/svn/trunk/projects/dal/
> TAPNotes/TAPNotes-fmt.html#tf-tapschema-opt
>
> Dynamic metadata and TimeToLive
> http://volute.googlecode.com/svn/trunk/projects/dal/
> TAPNotes/TAPNotes-fmt.html#tf-meta-dyn
>
> I look forward to hearing your thoughts,
> Dave
>
> --------
> Dave Morris
> Software Developer
> Wide Field Astronomy Unit
> Institute for Astronomy
> University of Edinburgh
> --------
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dal/attachments/20140506/bf5ad780/attachment.html>
More information about the dal
mailing list