Skip to content
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

Closed
prjemian opened this issue Apr 24, 2020 · 12 comments · Fixed by #808
Closed

reserved prefixes for names #769

prjemian opened this issue Apr 24, 2020 · 12 comments · Fixed by #808
Assignees
Labels
enhancement NIAC should review The NIAC should review/discuss
Milestone

Comments

@prjemian
Copy link
Contributor

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)

@prjemian
Copy link
Contributor Author

As noted,

Also suggest that prefixes be easily recognizable, such as capitalized with underscore after, such as PRJ_.

@prjemian
Copy link
Contributor Author

prjemian commented Jun 4, 2020

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.

@prjemian
Copy link
Contributor Author

prjemian commented Jun 4, 2020

Planning to use a table, alphabetized by prefix, such as:

prefix use meaning URL
IDF_ attributes reserved for use by ISIS Muon Facility www.isis.stfc.ac.uk
NX NXDL class For the class names used with NeXus groups www.nexusformat.org
NX_ attributes reserved for use by NeXus www.nexusformat.org
PDBX_ attributes reserved for the US protein data bank www.rcsb.org
SAS_ attributes reserved for use by canSAS www.cansas.org/
SILX_ attributes reserved for use by silx www.silx.org

Note that unless stated explicitly in the meaning, the reservation applies to any upper or lower case form of the prefix.

@prjemian
Copy link
Contributor Author

prjemian commented Jun 4, 2020

As stated in #757 (comment), reference this subsection in the FAQ.

@prjemian
Copy link
Contributor Author

prjemian commented Jun 4, 2020

Also, search through the manual sections for mentions of reserved prefixes (such as NX reserved for NXDL class names) and create references to this new subsection where appropriate.

@prjemian
Copy link
Contributor Author

prjemian commented Jun 4, 2020

While perusing ancient NeXus history, interesting to note the idea of naming prefixes was discussed previously.

@prjemian
Copy link
Contributor Author

Note that in NXentry, the attribute IDF_Version is ISIS Muon IDF_Version. Add IDF_ to the list.

@prjemian
Copy link
Contributor Author

@prjemian
Copy link
Contributor Author

Restrict AD to upper case (since address exists).

@prjemian
Copy link
Contributor Author

Additional metadata in EPICS area detector matches the prefix NDAttr, for example:

        @NDAttrName = Sample_XTranslation
        @NDAttrDescription = Sample XTranslation [mm]
        @NDAttrSourceType = NDAttrSourceEPICSPV
        @NDAttrSource = 9idcSample:XTranslation
        @NDAttrName = UserName
        @NDAttrDescription = user name listed as GUP PI
        @NDAttrSourceType = NDAttrSourceEPICSPV
        @NDAttrSource = 9idcLAX:UserName
        @NDAttrName = GUPNumber
        @NDAttrDescription = GUP proposal number
        @NDAttrSourceType = NDAttrSourceEPICSPV
        @NDAttrSource = 9idcLAX:GUPNumber

prjemian added a commit that referenced this issue Oct 13, 2020
prjemian added a commit that referenced this issue Oct 13, 2020
prjemian added a commit that referenced this issue Oct 14, 2020
@prjemian
Copy link
Contributor Author

At NIAC2020:

Prefixes should follow a naming scheme of uppercase letters followed by an underscore, but exceptions will be made for cases already in wide use.

prjemian added a commit that referenced this issue Oct 26, 2020
@stuartcampbell
Copy link
Member

Just linking nexusformat/NIAC#80 as that discusses and adds a BLUESKY_ prefix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement NIAC should review The NIAC should review/discuss
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants