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

"Note Codes" vs. "Note Names" #74

Closed
ahankinson opened this issue May 16, 2024 · 1 comment
Closed

"Note Codes" vs. "Note Names" #74

ahankinson opened this issue May 16, 2024 · 1 comment
Labels
Type: Spec Clarification Clarifications to existing content in the spec

Comments

@ahankinson
Copy link
Contributor

Decide on the standard terminology for notes.

From #67

@ahankinson ahankinson added the Type: Spec Clarification Clarifications to existing content in the spec label May 16, 2024
@ahankinson
Copy link
Contributor Author

I have been considering this issue.

I think it's implicit that all the sections give the "code"; that is, you could apply the terminology "Accidental codes" or "Octave codes" to the other section. I think "Notes" on its own is not sufficient, because all the parameters combine to give a "note code" (octave, accidental, name), so this section is actually "Note name codes", since it specifically refers to the part of the note code that provides the note name. (To be more specific, this is actually "Pitch class codes" but I think "Note names" is clearer to a general audience.)

In the spirit of optimizing the terminology, "Accidental codes" -> "Accidentals", "Octave codes" -> "Octaves", and "Note name codes" -> "Note names".

So I think for now I would prefer to keep it as "Note names", since this section is specifically about naming the pitch class, not the whole "Note code".

Please re-open with any differing opinions.

ahankinson added a commit that referenced this issue May 21, 2024
Makes note names required. Also moves the section to the beginning of the Musical Notation section, since all examples that follow it require the use of note names.

Fixes #13
Refs #74
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Spec Clarification Clarifications to existing content in the spec
Projects
None yet
Development

No branches or pull requests

1 participant