Register STANDRT OpenXR author ID

[StanD4rt]

Register the STANDRT OpenXR author ID for StanD4rt.

Contact: StanD4rt@hotmail.com

This updates the fragmented registry source and regenerated xr.xml.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ foundationqa
❌ StanD4rt
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[rpavlik-bot]

An issue (number 2804) has been filed to correspond to this pull request in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#2804 ), to facilitate working group processes.

This GitHub pull request will continue to be the main site of discussion.

[rpavlik]

Do you have a link or more information on the work you're doing with OpenXR? If you are wanting to just create a layer, you can use a reverse domain name instead of a registered author tag. If you are creating an extension as well, I would suggest waiting to submit this until the spec for the extension is ready to submit. We prefer to see some evidence of use before registering an author tag to keep the XML clean.

Additionally, the working group is concerned about the naming here, that it might imply standardization or endorsement. You will need to choose a more-abbreviated or otherwise less-confusing tag if you eventually do need this merged.

[StanD4rt]

Thank you for the clarification.

This work is a custom OpenXR runtime implementation for Windows, rather than an API layer or an extension proposal.

Our immediate need is to return a standards-compliant value in XrSystemProperties.vendorId. We do not have an applicable physical-device USB vendor ID, and we want to follow the official Khronos process rather than inventing an identifier or reusing one assigned to another organization.

Our understanding is that, for this case, we should first register an author ID/tag and then submit a separate Khronos vendor-ID registration using that author ID. Could you please confirm that this is the correct process?

We also understand the concern regarding STANDRT potentially implying standardization or endorsement. We will replace it with a shorter, neutral, non-confusing tag before proceeding. If there are any additional naming constraints or preferences beyond the published author-ID rules, please let us know.

We can provide additional technical information about the runtime if needed.