Votlint checks that the XML input is well-formed, and, unless the
valid=false parameter is supplied, that it validates against the
1.0 DTD or 1.1, 1.2, 1.3 or 1.4 schema as appropriate.
Some of the validity checks are also done by
votlint internally, so that some validity-type
errors may give rise to more than one warning.
In general, the program errs on the side of verbosity.
In addition to these checks, the following checks are carried out, and lead to ERROR reports if violations are found:
arraysizeattributes declared in
PARAMvalues incompatible with declared
TDelements with the wrong number of elements
PARAMvalues with the wrong number of elements
TABLEelement different from the number of rows actually in the table
versionattribute is unknown
refattributes without matching
IDelements elsewhere in the document
IDattribute value on multiple elements.
xtypevalues as defined in DALI are checked for formal compliance with DALI requirements.
Additionally, the following conditions, which are not actually forbidden by the VOTable standard, will generate WARNING reports. Some of these may result from harmless constructions, but it is wise at least to take a look at the input which caused them:
TDelements in row of
arraysize- this is a common error which can result in ignoring all but the first character in
TDelements from a column
refattributes which reference other elements by
IDwhere the reference makes no, or questionable sense (e.g.
FIELDin a different table)
FIELDs, though not
INFOs) with the same
TIMESYSelements never referenced.
ucdattribute values are not legal UCD1+ strings (if parameter
unitattribute values are not legal VOUnit strings (if parameter