Adrian has created an initial pull request (#355<\/a>) to propose the beginnings of an encoding for lyrics (issue #354<\/a>).<\/p>\n\n\n\n We spent the bulk of the meeting discussing some aspects of the existing approach, resulting in the decision to change the name of the continues<\/strong> object to hyphen<\/strong> to make it clearer, and agreeing that rather than handling gaps in lines of lyrics using a kind of “sparse array” approach (where a line of lyrics that should not include a lyric for a particular note would need an empty object in an array) we would use an object where lyrics are identified by a string-based key, with the lyric text stored as the value for that key at each position. Adrian will update the pull request to reflect these changes.<\/p>\n\n\n\n We also discussed how extender lines for melismas might be encoded, but did not settle on a specific approach in the course of our discussions.<\/p>\n\n\n\n We welcome further community feedback on the proposal as it stands in the pull request, and expect to merge this pull request ahead of the next co-chairs’ meeting in two weeks.<\/p>\n\n\n\n The next co-chairs’ meeting is scheduled for Thursday 10 October 2024<\/strong>.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" MNX Adrian has created an initial pull request (#355) to propose the beginnings of an encoding for lyrics (issue #354). We spent the bulk of the meeting discussing some aspects of the existing approach, resulting in the decision to change … Continue reading Next meeting<\/h2>\n\n\n\n