-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reserved prefixes for names #769
Comments
As noted,
|
The manual now has a subsection for reserved field name suffixes, under the section on Naming Conventions. This content is similar. A brief comment should accompany any prefix to describe its intended use. |
Planning to use a table, alphabetized by prefix, such as:
Note that unless stated explicitly in the meaning, the reservation applies to any upper or lower case form of the prefix. |
As stated in #757 (comment), reference this subsection in the FAQ. |
Also, search through the manual sections for mentions of reserved prefixes (such as |
While perusing ancient NeXus history, interesting to note the idea of naming prefixes was discussed previously. |
Note that in NXentry, the attribute |
|
Restrict |
Additional metadata in EPICS area detector matches the prefix
|
At NIAC2020:
|
Just linking nexusformat/NIAC#80 as that discusses and adds a BLUESKY_ prefix |
NeXus will develop and publish a list of reserved prefixes and avoid standardizing any name (specifically, we are thinking of attribute names) that starts with a reserved prefix. To reserve a prefix, post a GitHub issue to the definitions repository.
Should this be generalized to prefix the names of groups, fields, and links, as well?
Originally posted by @prjemian in #757 (comment)
The text was updated successfully, but these errors were encountered: