VOTable is meant to serialize tabular documents in the context of Virtual Observatory applications. This schema corresponds to the VOTable document available from http://www.ivoa.net/Documents/latest/VOT.html Accept UCD1+ Accept also old UCD1 (but not / + %) including SIAP convention (with :) content-role was previsouly restricted as: ]]>; is now a token. Deprecated in Version 1.2 Deprecated in Version 1.1 MUST be provided if the PARAM is part of a GROUP that has a VO-DML element. The VO-DML annotation MUST in that case identify a VO-DML Role (be it as attribute or as element). For other possible rules see the "mapping document". MUST be provided if the FIELDref is part of a GROUP that has a VO-DML element. The VO-DML annotation MUST in that case identify a VO-DML Role (be it as attribute or as element). For other possible rules see the "mapping document". MUST be provided if the PARAMref is part of a GROUP that has a VO-DML element. The VO-DML annotation MUST in that case identify a VO-DML Role (be it as attribute or as element). For other possible rules see the "mapping document". Added in Version 1.2: INFO for diagnostics The 'encoding' attribute is added here to avoid problems of code generators which do not properly interpret the TR/TD structures. 'encoding' was chosen because it appears in appendix A.5 The ID attribute is added here to the TR tag to avoid problems of code generators which do not properly interpret the TR/TD structures Added in Version 1.2: INFO for diagnostics Added in Version 1.2: INFO for diagnostics in several places The valid format of a reference to a VO-DML element. (Used to be 'UTYPE'). MUST have a prefix that elsewhere in the VOTable is defined to correspond to a VO-DML model defining the referenced element. See "mapping document", https://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/doc/MappingDMtoVOTable-v1.0-201607xx.docx. Suffix, separated from the prefix by a ':', MUST correspond to the vodml-id of the referenced element in the VO-DML/XML representation of that model. Allows one to map particular values defined in a VALUES/OPTION list to enumeration literals in the VO-DML model or to a concept in a SKOS vocabulary. The VOTable OPTION value that is being maped to enum literal or semantic concept. TBD anyURI as an identifier of concepts made sense for SKOS vocabularies. How about general semantic vocabularies? I.e. is it ok for the type be xs:string iso xs:anyURI? MUST be provided on annotations of FIELDref and PARAMref and, if contained in a VO-DML annotated GROUP or PARAM. If not provided on a root GROUP, indicates that it represents a stand-alone object. MUST reference the exact VO-DML type of the instance represented by the container of the annotation element. Q: should we make minOccurs="1"? A: no, but add sentences on what SHOULD/MAY/MUST be done in text. MUST: if no ROLE or if structured type. Also Reference serializations MUST have TYPE? SHOULD: primitive types Allows one to map OPTION values in VOTABLE to either EnumLiterals in data model (if TYPE identifies VO-DML/ Enumeration), or SKOSConcept in external SKOS vocabulary (if ROLE is a VO-DML/Attribute containing a skosconcept declaration). NB: IF the datatype of the ROLE is an Enumeration, and there is NO optionmapping it implies that the values ARE the enum literals, or the concepts.