% Improved Vulkan XML format
This project is an attempt to improve the Vulkan XML registry file. The design goals for the new format, in roughly priority order:
-
Ensure that 100% of the current information in
vk.xmlis captured in the new format. Transformation back and forth should be lossless. -
Make it easier to generate bindings for non-C languages. Extracting information from the current registry requires being able to parse C type declarations. This should be avoided where possible.
-
Make the RelaxNG schema actually verify the basic integrity of the document. The current
registry.rncdoesn't provide much verification, even of the basic structure of the registry. For example, according to the schema, the<type category="basetype">element can include struct<member>child elements, even though such a thing has no meaning and cannot be correctly processed by tools. -
Make the format more consistent. For example, the name of a
typeelement sometimes appears in an attribute and sometimes in a<name>sub-element within the element. This makes processing such declarations more difficult. However, do note that improving consistency can sometimes lead to information being in two places. -
Make the format more logically structured. For example, the current schema allows the content model of an element to radically change because of an attribute being set to a certain value.
The various
<type category="whatever">elements are really completely different elements, and in many cases have entirely different conceptual content models. Yet they still claim to betypeelements. This requires processing code to be radically different for the same element, based on the presence or absence of an attribute. -
Minimize changes needed to the existing processing infrastructure, where they do not conflict with the above. If the existing infrastructure is going to be able to process the new format, it will have to change somewhat. But using different element names is typically an easy fix. By contrast, using a completely different structural layout is not. The latter should be avoided unless there is a genuine need.
-
Layout the RelaxNG schema in a way that makes it easier to extend via RelaxNG's own extension/inclusion mechanisms. This also makes it easier to extend when adding new kinds of data. It should be possible to search for where an attribute or element is defined just by knowing the attribute/element's name.
-
Make the format amenable to transformation to and processing in non-XML formats like JSON. This means avoiding lots of "markup"-style formatting.
Generating the new format requires the use of Lua 5.1 or later. It requires no other dependencies than this; any files needed for XML processing are provided.
Executing lua.exe ConvertToNewFmt.lua from this directory will generate vk_new.xml, which is a file that stores the vk.xml data in the new format. No other parameters are needed for this process. Though if you want to provide a filename, you can via lua.exe ConvertToNewFmt.lua <filename>.
Executing lua.exe ConvertFromNewFmt.lua from this directory will generate vk_old.xml from vk_new.xml. The main purpose of this tool is to ensure that the generated XML contains all of the same data as the original file.
new_registry.rnc contains the RelaxNG compact schema that defines the new XML format. new_registr.rng is a non-compact version of the schema (it may be out of date, since I primarily edit the compact version).
The old registry schema and vk.xml files are in the src directory.
All of the .lua files are tools for converting between the old and new formats.
reading_the_schema.md explains some of the decisions behind the way the schema is defined, as well as providing the conventions used in its authoring.