search

w3c / mnx

Music Notation CG next-generation music markup proposal.
179 stars 18 forks source link

Octave shift camelCase vs kebab-case incostintencies #344

Closed GeorgeTailor closed 3 months ago

GeorgeTailor commented 6 months ago

https://w3c.github.io/mnx/docs/mnx-reference/objects/octave-shift/

The type property should be in camelCase to be consistent with other places in MNX

mscuthbert commented 6 months ago

The "value" should also change -- the example gives another micro-format as a string to parse while the spec says that "octave shift amount" is a number. Neither fits the current direction MNX transposition or placement specifications are going towards.

Never mind, will make a new issue.

adrianholovaty commented 3 months ago

I've just fixed what I believe is the last case of kebab-case: the "octave-shift" string. See aa7e24cd.

With that, I believe this issue can be closed!