RegTAP 1.1
Mark Taylor
m.b.taylor at bristol.ac.uk
Fri Jan 19 12:52:32 CET 2018
On Wed, 17 Jan 2018, Markus Demleitner wrote:
> As you write below, the actual VOTable serialisation details should
> rarely matter, and so I'm mapping both char(*) and unicodeChar(*) to
> "string"; but I'm feeling this needs some elaboration, so I put this
> paragraph into the introduction to the table listing:
>
> Many of the columns specified below are defined as haveing a ``string''
> data type. This is to be translated into arrays of \texttt{char} or
> \texttt{unicodeChar} on VOTable output depending on the service
> operators' decisions as to the representation of non-ASCII data in the
> database. For requirements and recommendations regarding national
> characters in RegTAP, see Sect.~\ref{utfreq}. The length of these
> arrays is not defined by this standard, where, obviously, no artificial
> length limits should be posed by implementations. Implementors who have
> to limit the length of strings in their databases are referred to
> appendix~\ref{appBP}.
>
> I'm not 100% happy with this. Better ideas are welcome.
Barring a couple of typos (fixed r4698) it looks fine to me.
Thanks for updates.
--
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/
More information about the registry
mailing list