Adrian has updated pull request #355<\/a>, which is the proposal for how lyrics should be encoded. The change to use a dedicated user-defined key for the lyrics<\/strong> object was more involved, because it required changes to the doc generator tool as well in order to generate the specification and the JSON schema.<\/p>\n\n\n\n Having decided in the last co-chairs’ meeting that we would rename the originally proposed continue<\/strong> object to hyphen<\/strong>, after discussing the issue of Korean text raised by Samuel Bradshaw, we have decided to switch to an enumeration called type<\/strong> with values whole<\/strong>, start<\/strong>, middle<\/strong>, and end<\/strong>, defaulting to whole<\/strong>.<\/p>\n\n\n\n We also discussed renaming lyricLine<\/strong>, which is currently used to identify the individual row of lyrics belonging to an event: we want to use lyricLine<\/strong> to identify the whole line of lyrics, and propose that the existing lyricLine<\/strong> should be renamed eventLyricLine<\/strong>, making clear that it belongs to the lyrics local to that event.<\/p>\n\n\n\n We spent a bit of time discussing some of the notations that are often represented using lyrics in existing music notation software (for example, percussion sticking, harmonic analysis, figured bass, or even chant notation<\/a>) and how these should be encoded in MNX. We had the idea of creating a kind of “kitchen sink” for rows of note-attached text to accommodate these kinds of use cases in the (short- to medium-term) absence of dedicated MNX encodings for these features. We would be interested to hear from the community about this issue, so Adrian will create a discussion on GitHub for feedback.<\/p>\n\n\n\n After we have completed this initial step of encoding lyrics, we’ll move on to lyric metadata, for example, whether a line of lyrics represents verse, chorus, translation, etc. Adrian will prepare a proposal for this after this pull request has been merged.<\/p>\n\n\n\n The next co-chairs’ meeting will be on Thursday 24 October 2024<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" MNX Adrian has updated pull request #355, which is the proposal for how lyrics should be encoded. The change to use a dedicated user-defined key for the lyrics object was more involved, because it required changes to the doc generator … Continue reading Next meeting<\/h2>\n\n\n\n