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

unifying/improving spelling of names within the PaNET ontology #55

Closed
kara-mela opened this issue Jun 5, 2024 · 5 comments
Closed

unifying/improving spelling of names within the PaNET ontology #55

kara-mela opened this issue Jun 5, 2024 · 5 comments

Comments

@kara-mela
Copy link

I recognized that the terminology in PaNET is already widely unified, however I discovered some exceptions. It would be great if you could have a look at it:

  1. ‘spin echo scattering’ -> space
  2. 'high resolution' is spelled without dash in almost all cases, except for 'high resolution neutron imaging'
  3. some few names with abbreviations, please avoid
  • EUV -> extreme ultra violet, UV -> ultra violet, VUV -> vacuum ultra violet
  • 'IR photon probe' is the only case where IR is used instead of infrared
  • 'time of flight' is the generally used spelling, exceptions are 'pulsed neutron TOF probe' and 'time-of-flight spectrometry'
  • XMCD -> 'x-ray magnetic circular dichroism'
@kara-mela
Copy link
Author

I just recognized, that my intention with point 1. is not visible: there is an additional space between 'echo' and 'scattering' that should be deleted.

@spc93
Copy link

spc93 commented Jun 6, 2024

Some comments:

  • Names are copied from existing sources wherever possible.
  • Adopted style is lower-case except for acronyms
  • We assume the names are not case-sensitive in order to avoid a proliferation of terms using different case.
  • We assume that there is no significant preference for label over alt-label, i.e. all labels have the same importance.
  • Abbreviations and acronyms are treated as any other label/alt-label
  • There are some mistakes!

@paulmillar
Copy link

We should probably capture this "style guide" in the PaNET SOP document --- I don't think it's there currently.

@paulmillar
Copy link

So, based on the above comments, should @kara-mela open a pull-request to resolve this issue?

@paulmillar
Copy link

Some comments:

@spc93 Just to let you know, I've taken your comments and put them in the Standard Operating Procedure document as a starting point for a naming convention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants