TAP-1.1 PR is now available

Patrick Dowler pdowler.cadc at gmail.com
Mon Sep 11 20:57:03 CEST 2017

As for requiring VOTable-1.3 -- I think we do want to do that so that
when someone implements all the table serialisation formats they'll
implement BINARY2; we already de facto accept the treatment of nulls
that is specified in 1.3 because people did it that way anyway.

I assume clients had to be able to accept VOTable-1.3 documents for
some time now and services can change the output version without much

Are we missing an exolicit 1.3 or later and just implyin 1.3 by reference?


PS-The point about BINARY2 is a dig vs myself since I have yet to
implement support for it :-)

On 11 September 2017 at 11:48, Patrick Dowler <pdowler.cadc at gmail.com> wrote:
> I agree that it would be nice for citations in the text to have a nice
> short name and I guess I could just manually type it before the
> \citep... maybe that's what I am supposed to do. Markus? And I could
> reduce the number of times I use \citep to 1 per major section (the
> first).
> Pat
> On 8 September 2017 at 04:04, Mark Taylor <m.b.taylor at bristol.ac.uk> wrote:
>> A couple more comments on PR-TAP-1.1-2017-08-30:
>> First, in section 4.3 the indexed, principal and std columns have
>> now been changed to integer rather than boolean values following
>> my earlier comments - thanks.  However, the text does not explain
>> how these integers are to be interpreted as flags.  Somewhere it
>> should make explicit that these columns must have values 1/0 to
>> indicate true/false.
>> Second, I already commented on TAP-1.1-20170707-WD:
>> On Wed, 19 Jul 2017, Mark Taylor wrote:
>>> Reference style:
>>>    The text has quite a few references like "As required by
>>>    (Dowler and Demleitner et al., 2013)".  It would be a bit more
>>>    readable to see "As required by DALI 1.0" (possibly followed by
>>>    a reference).  I'm not sure if that's something that can be
>>>    handled at that ivoatex level?  Anyway not essential.
>> and I don't think these have been changed.  To the extent that's
>> a stylistic decision, fair enough.
>> However in some cases this is more than an annoyance.
>> For instance at the start of Section 3 of the PR:
>>    "The (Ochsenbein and Williams et al., 2013) format is the standard
>>     format for output (query results) and input (table upload) ..."
>> is more difficult to understand than
>>    "The VOTable format is the standard format ..."
>> but it also seems to suggest that version 1.3 of the VOTable standard
>> is mandated.  I don't think that's intended - is it?
>> There are some other places in the text where similar comments apply.
>> Mark
>> On Fri, 1 Sep 2017, Marco Molinaro wrote:
>>> Dear all,
>>> this is to inform you that the
>>> TAP-1.1 Proposed Recommendation
>>> has been uploaded on the IVOA
>>> Documents repository, see
>>> http://www.ivoa.net/documents/TAP/20170830/
>>> Please review and comment it (or continue to do so)
>>> in view of the RFC period that should start in the
>>> second half of September.
>>> Cheers,
>>>      François, Marco, Pat
>> --
>> Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
>> m.b.taylor at bris.ac.uk +44-117-9288776  http://www.star.bris.ac.uk/~mbt/
> --
> Patrick Dowler
> Canadian Astronomy Data Centre
> Victoria, BC, Canada

Patrick Dowler
Canadian Astronomy Data Centre
Victoria, BC, Canada

More information about the dal mailing list