TAP-1.1 and adql: prefixes in TAP_SCHEMA.columns

[Patrick Dowler]

I don't recall anything definitive, but is it the consensus that 
prefixes are out for TAP-1.1? That would make the values of datatype in 
the tap_schema exactly consistent with the values in VOSI-tables... I'm 
fine with that.

Question: how does one describe/expose/prototype usage of new datatypes 
that go beyond the base set available in VODataService and/or ADQL?

Answer: short names are really short for:

ivo://ivoa.netnet/std/VODataService#VARCHAR

using the same logic as short DataLink vocabulary and I think we need to 
state that to be clear which short names are allowed.

I suppose that means someone could have a fully qualified datatype/xtype 
like:

http://example.com/newtypes#new-fangled-thing

but in the VOSI tables they would likely be reduced to describing it as 
a base type only and losing the extra info (which VOTable xtype can carry).

Pat

On 02/07/14 07:09 AM, Markus Demleitner wrote:
> Ha... so, there's still the things we have xtypes for, which are
> prefixed with adql: and, as xtypes will remain so.
> This, as far as I can see, concerns:
>
> * TIMESTAMP
> * BLOB
> * CLOB
> * REGION
> * POINT
>
> My vote: no prefixes on any of them.  And a strong vote against
> prefixing TIMESTAMP.

-- 

Patrick Dowler
Canadian Astronomy Data Centre
National Research Council Canada
5071 West Saanich Road
Victoria, BC V9E 2E7

250-363-0044 (office) 250-363-0045 (fax)