Adrian has documented that staves are numbered using a 1-based system (git commit<\/a>).<\/p>\n\n\n\n Adrian has made a change to the specification to remove the micro-syntax for measure location<\/strong>, which was used in six different places in the spec. He has introduced a new object measure rhythmic position<\/strong> that defines the rhythmic position within a particular bar. The git commit<\/a> message specifies the various places where these changes have been made. The specification and examples have also been updated accordingly.<\/p>\n\n\n\n Adrian is next going to work on a pull request for the supports<\/strong> object for accidental visibility (see minutes of previous meeting<\/a>), and will follow up with examples that show how things are encoded with reference to a specific staff (discussion #343<\/a>).<\/p>\n\n\n\n We talked for a while about rich text encoding (with reference to issue #280<\/a>) and discussed how this might look now that we’ve moved to JSON. Daniel agreed to write up an issue capturing some of the discussion as a starting point for further feedback.<\/p>\n\n\n\n The next co-chairs’ meeting is scheduled for Thursday 4 July 2024<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" MNX Adrian has documented that staves are numbered using a 1-based system (git commit). Adrian has made a change to the specification to remove the micro-syntax for measure location, which was used in six different places in the spec. He … Continue reading Next meeting<\/h2>\n\n\n\n