Lines Matching refs:author

111   * Extensions are named with the syntax `VK_<author>_<name>`.
112   * Layers are named with the syntax `VK_LAYER_<author>_<name>` or
131 [[extensions-naming-author-IDs]]
135 `<author>` above, identifying the author of the extension/layer.
136 This ID is a short, capitalized string identifying an author, such as a
142 can register additional author IDs for that purpose.
145 Details on how to register an author ID are provided below.
146 Layer authors not wishing to register an author ID with Khronos can instead
149 The FQDN should be a domain name owned by the author.
155   ** Khronos-ratified extensions add the reserved author ID `KHR` and use
157   ** The following author IDs are reserved and must not be used:
162   ** Multi-author extensions that have not been ratified by Khronos (those
164      or more registered authors) add the special author ID `EXT` to the base
166   ** Traditional author-specific extensions developed by one author (or one
167      author in cooperation with non-authors) add the author ID to the base
171      Some authors can have additional registered author IDs for special
175      extension - will use the author ID `ANDROID`.
180      registering an author ID.
181      Layer authors that prefer not to register an author ID can instead use
182      a fully-qualified domain name (FQDN) in reverse-order as an author ID,
190 The `KHX` author ID was used for _experimental_ extensions, as described in
209 // Vendor extension name using author ID NV
212 // Vendor layer name using author ID LUNARG
215 // Layer name using the FQDN www.3dxcl.invalid instead of an author ID
232 These objects are given globally unique names by appending the author ID
246 The registry contains reserved author IDs, core and extension interface
257 [[extensions-author-ID]]
268 an author ID with Khronos through the
270 The author ID must be used for any extensions that author registers.
274 To reserve an author ID, propose a merge request against
276 The merge must add a `<tag>` XML tag and fill in the `name`, `author` and
277 `contact` attributes with the requested author ID, the author's formal name
279 The author ID will only be reserved once this merge request is accepted.
281 Please do not try to reserve author IDs which clearly belong to another
284 Khronos may decline to register author IDs that are not requested in good
299 <<extensions-author-ID,author IDs>>.
303 To reserve an Khronos vendor ID, you must first have a Khronos author ID.
310 The `name` attribute must be `VK_VENDOR_ID_<author>`, where `<author>` is
311 the author tag.
355 their author ID and/or FQDNs to that account.
367     how <<extensions-author-ID,author IDs are reserved>>.
370     sequential extension `number`, the `author` and `contact` information
371     (if different than that already specified for the author ID used in the
518     author's discretion.
789 explicit permission from the owner of those values (e.g. from the author of
857 <extension name="VK_AMD_extension_24" number="24" author="AMD" supported="disabled">