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.
144 separate author IDs.
149 <tag name="ANDROID"  author="Google LLC" contact="contactperson @githubusername"/>
150 <tag name="CHROMIUM" author="Google LLC" contact="contactperson @githubusername"/>
153 In the above example, `Google LLC` is the author for two author IDs
156 Details on how to register an author ID are provided below.
157 Layer authors not wishing to register an author ID with Khronos can instead
160 The FQDN should be a domain name owned by the author.
164 specific to a single registered author or platform (e.g. Android).
166 Typically, they are only implemented by the registered author or by
169 Khronos has registered some author IDs for specific uses:
179 The `KHX` author ID was used for _experimental_ extensions, as described in
186 The following author IDs are reserved and must _not_ be used:
197   * Khronos-ratified extensions add the reserved author ID `KHR` and use the
199   * Multi-vendor extensions add the special author ID `EXT` to the base
201   * Vendor extensions add the author ID to the base prefix.
208     registering an author ID.
209     Layer authors that prefer not to register an author ID can instead use a
210     fully-qualified domain name (FQDN) in reverse-order as an author ID,
228 // Vendor extension name using author ID NV
231 // Vendor layer name using author ID LUNARG
234 // Layer name using the FQDN www.3dxcl.invalid instead of an author ID
251 These objects are given globally unique names by appending the author ID
265 The registry contains reserved author IDs, core and extension interface
276 [[extensions-author-ID]]
287 an author ID with Khronos through the
289 The author ID must be used for any extensions that author registers.
293 To reserve an author ID, propose a merge request against
295 The merge must add a `<tag>` XML tag and fill in the `name`, `author` and
296 `contact` attributes with the requested author ID, the author's formal name
298 The author ID will only be reserved once this merge request is accepted.
300 Please do not try to reserve author IDs which clearly belong to another
303 Khronos may decline to register author IDs that are not requested in good
318 <<extensions-author-ID,author IDs>>.
322 To reserve an Khronos vendor ID, you must first have a Khronos author ID.
329 The `name` attribute must be `VK_VENDOR_ID_<author>`, where `<author>` is
330 the author tag.
374 their author ID and/or FQDNs to that account.
386     how <<extensions-author-ID,author IDs are reserved>>.
389     sequential extension `number`, the `author` and `contact` information
390     (if different than that already specified for the author ID used in the
537     author's discretion.
805 explicit permission from the owner of those values (e.g. from the author of
878 <extension name="VK_AMD_extension_24" number="24" author="AMD" supported="disabled">