Change log for November 21, 2024 Vulkan 1.3.302 spec update:

Github Issues

  * Add a NOTE clarifying that VkImageLayout VK_IMAGE_LAYOUT_GENERAL cannot
    support all device uses in all cases (public issue 2430).
  * Update and cross-reference descriptions of dispatching commands in the
    glossary and the introduction of the <<dispatch, Dispatching Commands>>
    and <<shaders-compute, Compute Shader>> sections, so that instead of a
    list, they are defined by the contents of the Dispatching Commands
    chapter (public issue 2457).

Internal Issues

  * Make descriptions of framebuffer coordinates consistent with the rest of
    the specification for `FragCoord` VkSubpassDescription, and in the
    <<primsrast-depthbias-computation, Depth Bias Computation>> and
    <<vertexpostproc-viewport, Controlling the Viewport>> sections (internal
    issue 962).
  * Replace uses of "`currently bound`" with "`bound`" and add a CI check
    enforcing the existing rule in the style guide (internal issue 993).
  * Clarify that <<fragops-shader-termination, termination and demotion>>
    discard samples, not fragments (internal issue 2125).
  * Add common draw vertex binding VU for setting
    VK_PRIMITIVE_TOPOLOGY_PATCH_LIST (internal issue 4073).
  * Add CI check that an instance extension does not have a dependency on a
    device extension (internal issue 2385).
  * Remove "`on the device`" when referring to feature enables (internal
    issue 4056).
  * Add a new 'featurelink' attribute to feature struct members that
    indicates the link name for a Boolean API feature when it differs from
    the feature name (internal issues 4042, 4057).
  * Use "`enumerant *specifies*`" wording consistently, per the style guide,
    and add a CI check for it (internal issue 4077).
  * Clarify the <<introduction>> chapter in descriptions of how the
    specification expresses requirements, fix minor issues, and reorder the
    chapter for increased readability (internal issue 3921).
  * Add missing <feature> tags to several extensions, a `nofeatures`
    attribute attribute for extensions to explicitly indicate they don't
    require any features, and added CI to check that every extension either
    requires at least one feature, or sets the `nofeatures` tag to true
    (internal issues 3946, 3951).
  * Add a NOTE to the VK_EXT_host_image_copy command descriptions that host
    image copy to / from an image is not internally synchronized (internal
    issue 4040).
  * Use consistent phrasing to describe links to feature names (internal
    issue 4056).
  * Fix XML tagging for VkSwapchainPresentFenceInfoEXT::pFences to
    accommodate array elements which can optionally be VK_NULL_HANDLE
    (internal issue 4067).
  * XML workaround so that APIs that should not appear in Vulkan SC
    generated artifacts are treated correctly (internal issue 4074).
  * Remove use of "`recommended`" as a normative term, and replace the
    couple of places it was used in that fashion. Add a new "`Use the Active
    Voice`" section of the style guide and apply its recommendations
    (internal issue 4085).
  * Clarify descriptor buffer binding limits for
    vkCmdBindDescriptorBuffersEXT and the
    <<limits-maxDescriptorBufferBindings, maxDescriptorBufferBindings>> and
    <<limits-maxSamplerDescriptorBufferBindings,
    maxSamplerDescriptorBufferBindings>> limits (internal issue 4086).
  * Clarify that the taskShader feature is mandatory in the
    VK_EXT_mesh_shader proposal document (internal issue 4088).
  * Remove overzealous `protectedNoFault` VUs from vkCmdDecodeVideoKHR and
    vkCmdEncodeVideoKHR (internal MR 6994).
  * Update VK_NVX_binary_import and VK_NVX_image_view_handle for 64-bit
    handles (internal MR 6995).
  * Remove stale references to `tg_start` and `tg_end` in the
    <<decode-av1-picture-info, Std Picture Information>> definition
    (internal MR 6996).
  * Add a VkDeviceCreateInfo VU for robustBufferAccessUpdateAfterBind
    (internal MR 7008).
  * Reorder ci to catch schema errors validation errors before spec
    generation, for more intelligible error messages (internal MR 7013).
  * Remove VkValidationFeaturesEXT VU 02968, as the validation layers no
    longer have the corresponding restriction (internal MR 7016).
  * Remove redundant vkCreateShadersEXT VU 09669 (internal MR 7021).
  * Update proposal documents to link into the right specification page in
    docs.vulkan.org instead of into the independent reference pages in the
    registry (internal MR 7026)

New Extensions

  * VK_EXT_vertex_attribute_robustness
  * VK_KHR_video_encode_av1
  * VK_KHR_video_encode_quantization_map
  * VK_NV_display_stereo

.github/workflows/CI.yml

@@ -29,8 +29,8 @@ jobs:
       - name: REUSE license checker
         run: reuse lint
 
-  terminology-check:
-    name: Run various checker scripts on the spec and XML sources
+  consistency-check:
+    name: Run consistency checks on the spec and XML sources
     runs-on: ubuntu-latest
     container: khronosgroup/docker-images@sha256:089687083ceb36483a3917389e4278718ab19c594099634f5dd80e22540c960f
 
@@ -70,13 +70,14 @@ jobs:
 
     steps:
       - uses: actions/checkout@v4
+      - name: Validate the XML before building anything using it
+        run: make -C xml validate
       - name: Build the actual spec (both chunked and single-page HTML), and other common targets
         run: ./makeSpec -clean -spec all QUIET= -j${nproc} -Otarget manhtmlpages validusage styleguide registry chunked html
       - name: Check consistency of internal xrefs and anchors in the output, now that an HTML output is available
         run: make check-xrefs
       - name: Build headers, for use by all later stages
-        run: make validate install test
-        working-directory: xml
+        run: make -C xml install codec_headers test vtest
       - name: Package generated spec
         # https://github.com/actions/upload-artifact#limitations
         # upload-artifact would upload all of almost 10k files individually

.gitlab-ci.yml

@@ -23,9 +23,9 @@ license-check:
     - reuse lint
   allow_failure: false
 
-# Run various checker scripts on the spec and XML sources
+# Run consistency checks on the spec and XML sources
 # Separate from the generate step to set allow_failure: false
-terminology_check:
+consistency-check:
   stage: build
   script:
     # Internal self-test of the check_spec_links script
@@ -64,6 +64,8 @@ spec-generate:
   script:
     - NODE_PATH="/usr/lib/node_modules"
     - export NODE_PATH
+    # Validate the XML before building anything using it
+    - make -C xml validate
     # Build the core-only spec, to catch some incorrect ifdef errors
     - ./makeSpec -clean -spec core -genpath gencore QUIET= -j${nproc} -Otarget html manhtmlpages
     # Build the HTML/chunked spec and other common targets.
@@ -89,7 +91,7 @@ spec-generate:
     # Check consistency of internal xrefs and anchors in the HTML output
     - make check-xrefs
     # Build headers, for use by all later stages
-    - ( cd xml && make validate install test vtest )
+    - make -C xml install codec_headers test vtest
   artifacts:
     when: always
     paths:

ChangeLog.adoc

@@ -14,6 +14,96 @@ appears frequently in the change log.
 
 '''
 
+Change log for November 21, 2024 Vulkan 1.3.302 spec update:
+
+Github Issues
+
+  * Add a NOTE clarifying that VkImageLayout VK_IMAGE_LAYOUT_GENERAL cannot
+    support all device uses in all cases (public issue 2430).
+  * Update and cross-reference descriptions of dispatching commands in the
+    glossary and the introduction of the <<dispatch, Dispatching Commands>>
+    and <<shaders-compute, Compute Shader>> sections, so that instead of a
+    list, they are defined by the contents of the Dispatching Commands
+    chapter (public issue 2457).
+
+Internal Issues
+
+  * Make descriptions of framebuffer coordinates consistent with the rest of
+    the specification for `FragCoord` VkSubpassDescription, and in the
+    <<primsrast-depthbias-computation, Depth Bias Computation>> and
+    <<vertexpostproc-viewport, Controlling the Viewport>> sections (internal
+    issue 962).
+  * Replace uses of "`currently bound`" with "`bound`" and add a CI check
+    enforcing the existing rule in the style guide (internal issue 993).
+  * Clarify that <<fragops-shader-termination, termination and demotion>>
+    discard samples, not fragments (internal issue 2125).
+  * Add common draw vertex binding VU for setting
+    VK_PRIMITIVE_TOPOLOGY_PATCH_LIST (internal issue 4073).
+  * Add CI check that an instance extension does not have a dependency on a
+    device extension (internal issue 2385).
+  * Remove "`on the device`" when referring to feature enables (internal
+    issue 4056).
+  * Add a new 'featurelink' attribute to feature struct members that
+    indicates the link name for a Boolean API feature when it differs from
+    the feature name (internal issues 4042, 4057).
+  * Use "`enumerant *specifies*`" wording consistently, per the style guide,
+    and add a CI check for it (internal issue 4077).
+  * Clarify the <<introduction>> chapter in descriptions of how the
+    specification expresses requirements, fix minor issues, and reorder the
+    chapter for increased readability (internal issue 3921).
+  * Add missing <feature> tags to several extensions, a `nofeatures`
+    attribute attribute for extensions to explicitly indicate they don't
+    require any features, and added CI to check that every extension either
+    requires at least one feature, or sets the `nofeatures` tag to true
+    (internal issues 3946, 3951).
+  * Add a NOTE to the VK_EXT_host_image_copy command descriptions that host
+    image copy to / from an image is not internally synchronized (internal
+    issue 4040).
+  * Use consistent phrasing to describe links to feature names (internal
+    issue 4056).
+  * Fix XML tagging for VkSwapchainPresentFenceInfoEXT::pFences to
+    accommodate array elements which can optionally be VK_NULL_HANDLE
+    (internal issue 4067).
+  * XML workaround so that APIs that should not appear in Vulkan SC
+    generated artifacts are treated correctly (internal issue 4074).
+  * Remove use of "`recommended`" as a normative term, and replace the
+    couple of places it was used in that fashion. Add a new "`Use the Active
+    Voice`" section of the style guide and apply its recommendations
+    (internal issue 4085).
+  * Clarify descriptor buffer binding limits for
+    vkCmdBindDescriptorBuffersEXT and the
+    <<limits-maxDescriptorBufferBindings, maxDescriptorBufferBindings>> and
+    <<limits-maxSamplerDescriptorBufferBindings,
+    maxSamplerDescriptorBufferBindings>> limits (internal issue 4086).
+  * Clarify that the taskShader feature is mandatory in the
+    VK_EXT_mesh_shader proposal document (internal issue 4088).
+  * Remove overzealous `protectedNoFault` VUs from vkCmdDecodeVideoKHR and
+    vkCmdEncodeVideoKHR (internal MR 6994).
+  * Update VK_NVX_binary_import and VK_NVX_image_view_handle for 64-bit
+    handles (internal MR 6995).
+  * Remove stale references to `tg_start` and `tg_end` in the
+    <<decode-av1-picture-info, Std Picture Information>> definition
+    (internal MR 6996).
+  * Add a VkDeviceCreateInfo VU for robustBufferAccessUpdateAfterBind
+    (internal MR 7008).
+  * Reorder ci to catch schema errors validation errors before spec
+    generation, for more intelligible error messages (internal MR 7013).
+  * Remove VkValidationFeaturesEXT VU 02968, as the validation layers no
+    longer have the corresponding restriction (internal MR 7016).
+  * Remove redundant vkCreateShadersEXT VU 09669 (internal MR 7021).
+  * Update proposal documents to link into the right specification page in
+    docs.vulkan.org instead of into the independent reference pages in the
+    registry (internal MR 7026)
+
+New Extensions
+
+  * VK_EXT_vertex_attribute_robustness
+  * VK_KHR_video_encode_av1
+  * VK_KHR_video_encode_quantization_map
+  * VK_NV_display_stereo
+
+'''
+
 Change log for November 1, 2024 Vulkan 1.3.301 spec update:
 
 Github Issues
@@ -11188,7 +11278,7 @@ Internal Issues:
   * Resolve contradictions and use of undefined "`per-sample shading`" term
     in the <<primsrast-sampleshading, Sample Shading>> and
     <<shaders-fragment-execution, Fragment Shader Execution>> sections; for
-    the <<features-features-sampleRateShading, sampleRateShading feature>>;
+    the <<features-features-sampleRateShading, sampleRateShading>> feature;
     for code:FragCoord, code:SampleId, and code:SamplePosition; and for
     slink:sname:VkPipelineMultisampleStateCreateInfo (internal issue 1134).
   * Clarify the meaning of the ptext:maxDescriptorSet* limits in footnote 8
@@ -11428,7 +11518,7 @@ GitHub Issues:
     aliasing in flink:vkBindMemory2 - the new rules are true regardless
     (public issue 317).
   * Clarified the <<features-features-samplerAnisotropy,
-    pname:samplerAnisotropy feature>> to only affect the
+    pname:samplerAnisotropy>> feature to only affect the
     slink:VkSamplerCreateInfo::pname:anisotropyEnable value, and that
     pname:maxAnisotropy is ignored when pname:anisotropyEnable is VK_FALSE
     (public issue 503).

Makefile

@@ -148,7 +148,7 @@ VERBOSE =
 # ADOCOPTS options for asciidoc->HTML5 output
 
 NOTEOPTS     = -a editing-notes -a implementation-guide
-PATCHVERSION = 301
+PATCHVERSION = 302
 BASEOPTS     =
 
 ifneq (,$(findstring VKSC_VERSION_1_0,$(VERSIONS)))
@@ -283,6 +283,7 @@ SPECFILES = $(wildcard $(SPECDIR)/chapters/[A-Za-z]*.adoc $(SPECDIR)/chapters/*/
 # Shorthand for where different types generated files go.
 # All can be relocated by overriding GENERATED in the make invocation.
 GENERATED      = $(CURDIR)/gen
+GENERATED_DIR  = $(notdir $(GENERATED))
 REFPATH        = $(GENERATED)/refpage
 APIPATH        = $(GENERATED)/api
 VALIDITYPATH   = $(GENERATED)/validity
@@ -536,12 +537,18 @@ check-undefined:
 # Look for use of custom macros in the proposals and other
 # non-Specification document (except for the ChangeLog*.adoc) markup
 CHECK_CUSTOM_MACROS = git grep -n -E -f $(ROOTDIR)/config/CI/custom-macros [A-Z][A-Z]*.adoc proposals/
+CHECK_REFPAGE_ATTRIBUTES = git grep -n -E -f $(ROOTDIR)/config/CI/refpage-attributes proposals/
 check-custom-macros:
 	if test `$(CHECK_CUSTOM_MACROS) | wc -l` != 0 ; then \
 	    echo "Found use of specification macros in proposal or repository metadocumentation, where they are not allowed. Please use straight asciidoc markup like *must* for fixes:" ; \
 	    $(CHECK_CUSTOM_MACROS) ; \
 	    exit 1 ; \
 	fi
+	if test `$(CHECK_REFPAGE_ATTRIBUTES) | wc -l` != 0 ; then \
+	    echo "Found use of {refpage} attribute in proposals, which has been replaced by {docs} and {extensions}. See proposals/template.adoc for the current link markup style:" ; \
+	    $(CHECK_REFPAGE_ATTRIBUTES) ; \
+	    exit 1 ; \
+	fi
 
 # Look for '.txt' and '.asciidoc' files, which should almost all be .adoc now
 CHECK_TXTFILES = find . -name '*.txt' -o -name '*.asciidoc' | egrep -v -E -f $(ROOTDIR)/config/CI/txt-files-allowed
@@ -797,7 +804,7 @@ ANTORA_EXTRAFILES = \
 
 # The pagemap is copied, separately since the rewrite script creates it.
 setup_spec_antora pagemap $(JSPAGEMAP) $(PYPAGEMAP): xrefmaps $(JSAPIMAP)
-	$(QUIET)find ./gen ./chapters ./appendices -name '[A-Za-z]*.adoc' | \
+	$(QUIET)find $(GENERATED) ./chapters ./appendices -name '[A-Za-z]*.adoc' | \
 	    grep -v /vulkanscdeviations.adoc > $(ANTORA_FILELIST)
 	$(QUIET)ls -1 $(ANTORA_EXTRAFILES) >> $(ANTORA_FILELIST)
 	$(QUIET)$(PYTHON) $(SCRIPTS)/antora-prep.py \
@@ -808,7 +815,7 @@ setup_spec_antora pagemap $(JSPAGEMAP) $(PYPAGEMAP): xrefmaps $(JSAPIMAP)
 	    -jspagemap $(JSPAGEMAP) \
 	    -pypagemap $(PYPAGEMAP) \
 	    -filelist $(ANTORA_FILELIST)
-	$(QUIET)$(CP) $(JSPAGEMAP) $(ANTORA_SPECMODULE)/partials/gen/
+	$(QUIET)$(CP) $(JSPAGEMAP) $(ANTORA_SPECMODULE)/partials/$(GENERATED_DIR)
 
 # Generate Antora features module content by rewriting feature sources
 # No additional pageHeaders required.
@@ -904,7 +911,7 @@ CLEAN_ANTORA_PATHS = \
 	antora/spec/modules/ROOT/pages/appendices \
 	antora/spec/modules/ROOT/pages/chapters \
 	antora/spec/modules/ROOT/pages/partials \
-	antora/spec/modules/ROOT/pages/gen \
+	antora/spec/modules/ROOT/pages/$(GENERATED_DIR) \
 	antora/spec/modules/ROOT/partials \
 	antora/features/modules/features/pages/proposals \
 	antora/features/modules/features/partials \

appendices/VK_AMD_shader_early_and_late_fragment_tests.adoc

@@ -22,9 +22,9 @@ _and_ late fragment tests with the code:EarlyAndLateFragmentTestsAMD
 execution mode.
 
 ifdef::VK_EXT_shader_stencil_export[]
-If `apiext:VK_EXT_shader_stencil_export` is supported, additional execution
-modes allowing early depth tests similar to code:DepthUnchanged,
-code:DepthLess, and code:DepthGreater are provided.
+If the `apiext:VK_EXT_shader_stencil_export` extension is supported,
+additional execution modes allowing early depth tests similar to
+code:DepthUnchanged, code:DepthLess, and code:DepthGreater are provided.
 endif::VK_EXT_shader_stencil_export[]
 
 include::{generated}/interfaces/VK_AMD_shader_early_and_late_fragment_tests.adoc[]

appendices/VK_EXT_inline_uniform_block.adoc

@@ -83,8 +83,9 @@ refer to individual offsets within the uniform block (see issue #2).
 However, this extension does introduce new features/properties about the
 level of support for update-after-bind inline uniform blocks.
 
-5) Is the pname:descriptorBindingVariableDescriptorCount feature introduced
-by `VK_EXT_descriptor_indexing` supported for inline uniform blocks?
+5) Is the <<features-descriptorBindingVariableDescriptorCount,
+pname:descriptorBindingVariableDescriptorCount>> feature introduced by
+`VK_EXT_descriptor_indexing` supported for inline uniform blocks?
 
 *RESOLVED*: Yes, as long as other inline uniform block specific limits are
 respected.

appendices/VK_EXT_shader_viewport_index_layer.adoc

@@ -14,8 +14,10 @@ include::{generated}/meta/{refprefix}VK_EXT_shader_viewport_index_layer.adoc[]
     {GLregistry}/AMD/AMD_vertex_shader_layer.txt[`GL_AMD_vertex_shader_layer`],
     {GLregistry}/AMD/AMD_vertex_shader_viewport_index.txt[`GL_AMD_vertex_shader_viewport_index`],
     and {GLregistry}/NV/NV_viewport_array2.txt[`GL_NV_viewport_array2`]
-  - This extension requires the pname:multiViewport feature.
-  - This extension interacts with the pname:tessellationShader feature.
+  - This extension requires the <<features-multiViewport,
+    pname:multiViewport>> feature.
+  - This extension interacts with the <<features-tessellationShader,
+    pname:tessellationShader>> feature.
 *Contributors*::
   - Piers Daniell, NVIDIA
   - Jeff Bolz, NVIDIA

appendices/VK_EXT_vertex_attribute_robustness.adoc

@@ -0,0 +1,35 @@
+// Copyright 2024 The Khronos Group Inc.
+//
+// SPDX-License-Identifier: CC-BY-4.0
+
+include::{generated}/meta/{refprefix}VK_EXT_vertex_attribute_robustness.adoc[]
+
+=== Other Extension Metadata
+
+*Last Modified Date*::
+    2024-11-01
+*IP Status*::
+    No known IP claims.
+*Contributors*::
+  - Daniel Story, Nintendo
+
+=== Description
+
+It can be detrimental to performance for applications to have to define fake
+vertex attribute locations and buffer bindings for vertex shaders that may
+reference attribute locations for which there is no vertex data.
+
+This extension allows applications to not have to specify fake vertex
+attribute locations, and if the vertex shader reads those attributes it will
+read (0,0,0,0) or (0,0,0,1).
+
+include::{generated}/interfaces/VK_EXT_vertex_attribute_robustness.adoc[]
+
+=== Issues
+
+None
+
+=== Version History
+
+  * Revision 1, 2024-11-01 (Piers Daniell)
+  ** Internal revisions

appendices/VK_KHR_format_feature_flags2.adoc

@@ -35,13 +35,12 @@ On top of replicating all the bits from elink:VkFormatFeatureFlagBits,
 elink:VkFormatFeatureFlagBits2KHR adds the following bits :
 
   * ename:VK_FORMAT_FEATURE_2_STORAGE_READ_WITHOUT_FORMAT_BIT_KHR and
-    ename:VK_FORMAT_FEATURE_2_STORAGE_WRITE_WITHOUT_FORMAT_BIT_KHR indicate
-    that an implementation supports respectively reading and writing a given
-    elink:VkFormat through storage operations without specifying the format
-    in the shader.
-
+    ename:VK_FORMAT_FEATURE_2_STORAGE_WRITE_WITHOUT_FORMAT_BIT_KHR specify
+    that an implementation supports reading and writing, respectively, a
+    given elink:VkFormat through storage operations without specifying the
+    format in the shader.
   * ename:VK_FORMAT_FEATURE_2_SAMPLED_IMAGE_DEPTH_COMPARISON_BIT_KHR
-    indicates that an implementation supports depth comparison performed by
+    specifies that an implementation supports depth comparison performed by
     code:OpImage*Dref* instructions on a given elink:VkFormat.
     Previously the result of executing a code:OpImage*Dref* instruction on
     an image view, where the pname:format was not one of the depth/stencil

appendices/VK_KHR_fragment_shader_barycentric.adoc

@@ -80,9 +80,9 @@ code:BaryCoordNoPerspKHR interpolated?
 code:BaryCoordNoPerspKHR may: also be decorated with the code:Centroid or
 code:Sample qualifiers to specify interpolation, like any other fragment
 shader input.
-If <<features-shaderSampleRateInterpolationFunctions,
-pname:shaderSampleRateInterpolationFunctions>> is enabled, the extended
-instructions InterpolateAtCentroid, InterpolateAtOffset, and
+If the <<features-shaderSampleRateInterpolationFunctions,
+pname:shaderSampleRateInterpolationFunctions>> feature is enabled, the
+extended instructions InterpolateAtCentroid, InterpolateAtOffset, and
 InterpolateAtSample from the GLSL.std.450 may: also be used with inputs
 decorated with code:BaryCoordKHR or code:BaryCoordNoPerspKHR.
 

appendices/VK_KHR_ray_tracing_pipeline.adoc

@@ -320,9 +320,10 @@ There are two main reasons for the difference here:
 required dependency, particularly when the "`Feature Requirements`" section
 says it is required to be supported anyhow?
 --
-*RESOLVED*: If `apiext:VK_KHR_pipeline_library` were a required extension
-dependency, then every application would need to enable the extension
-whether or not they actually want to use the pipeline library functionality.
+*RESOLVED*: If the `apiext:VK_KHR_pipeline_library` extensino were a
+required dependency, then every application would need to enable the
+extension whether or not they actually want to use the pipeline library
+functionality.
 Developers found this to be annoying and unfriendly behavior.
 We do wish to require all *implementations* to support it though, and thus
 it is listed in the feature requirements section.

appendices/VK_KHR_video_encode_av1.adoc

@@ -0,0 +1,40 @@
+// Copyright 2023-2024 The Khronos Group Inc.
+//
+// SPDX-License-Identifier: CC-BY-4.0
+
+include::{generated}/meta/{refprefix}VK_KHR_video_encode_av1.adoc[]
+
+=== Other Extension Metadata
+
+*Last Modified Date*::
+    2024-09-23
+*IP Status*::
+    No known IP claims.
+*Contributors*::
+  - Ahmed Abdelkhalek, AMD
+  - Benjamin Cheng, AMD
+  - Ho Hin Lau, AMD
+  - Lynne Iribarren, Independent
+  - David Airlie, Red Hat, Inc.
+  - Ping Liu, Intel
+  - Srinath Kumarapuram, NVIDIA
+  - Vassili Nikolaev, NVIDIA
+  - Tony Zlatinski, NVIDIA
+  - Konda Raju, NVIDIA
+  - Charlie Turner, Igalia
+  - Daniel Almeida, Collabora
+  - Nicolas Dufresne, Collabora
+  - Daniel Rakos, RasterGrid
+
+=== Description
+
+This extension builds upon the `apiext:VK_KHR_video_encode_queue` extension
+by adding support for encoding elementary video stream sequences compliant
+with the AV1 video compression standard.
+
+include::{generated}/interfaces/VK_KHR_video_encode_av1.adoc[]
+
+=== Version History
+
+  * Revision 1, 2024-09-23 (Daniel Rakos)
+  ** Internal revisions