<div dir="ltr">Hi Walter, all,<div>I think you're correct.</div><div>I leave the final answer to the editor and authors.</div><div><br></div><div>I think the adql: prefix should disappear also in 1.0 </div><div>services, if possible, while datatype=char is not </div><div>wrong, but may be misleading.</div><div><br></div><div>Cheers,</div><div> Marco<br><div class="gmail_extra"><br><div class="gmail_quote">2017-10-09 21:04 GMT+02:00 Walter Landry <span dir="ltr"><<a href="mailto:wlandry@caltech.edu" target="_blank">wlandry@caltech.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Everyone,<br>
<br>
In surveying how existing TAP providers set the datatype for a<br>
timestamp column in TAP_SCHEMA.columns, I have seen all of<br>
<br>
datatype=timestamp<br>
datatype=adql::TIMESTAMP<br>
datatype=char<br>
<br>
As I understand it, in TAP 1.1, the correct way to represent it is<br>
something like<br>
<br>
datatype = char<br>
arraysize = *<br>
xtype = timestamp<br>
<br>
Is that correct?<br>
<br>
Thanks,<br>
Walter Landry<br>
</blockquote></div><br></div></div></div>