Lines Matching refs:XML
32 This document describes the Khronos OpenGL API Registry XML schema, and provides
34 C header files. The underlying XML files and scripts, as well as headers
35 generated from the current authoritative copy of the XML files, can be
49 The registry uses an XML representation of the API and a set of Python 3
50 scripts to manipulate the XML, based on the lxml Python bindings. It comes
51 with an XML schema and validator. Outside users are welcome to submit pull
52 requests on github, although the XML schema itself is mature and unlikely to
55 Other APIs defined by Khronos, such as Vulkan and OpenXR, use a similar XML
58 Some groups outside Khronos have their own XML based API descriptions,
112 the C types and definitions in the XML to something appropriate to their
117 Actual XML registry processing is done in \code{reg.py}, which contains
125 \section{XML Registry Schema}
128 The format of an XML registry is a top level \tag{registry} tag
132 schema file, \code{registry.rnc}, against which the XML registry files
453 Eventually all \tag{group} tags will be removed from the XML
879 \subsection{Stability of the XML Database and Schema}
883 to feedback and to Khronos' own wishlist. This means the XML schema is
885 to adding attributes to existing tags. The XML databases such as
888 canonicalization of the XML or sorting of \tag{command} and
897 There are lots of tools and additional tags that would make the XML format
914 The initial releases of the XML Registry did not include type annotation
918 been added to the XML, in the form of \tag{group} tags (see
1024 reflect this not being the only Khronos XML API schema in use, and
1040 groups of \tag{extension} tags, to ease XML transformations such