With the build system for the documentation site and the test system now firmly in place, it is possible to achieve good velocity with actual work towards the next MusicXML 4.1 release https:\/\/github.com\/w3c-cg\/ – Closed: <harmonic> misses a number attribute https:\/\/github.com\/ – Closed: Make part-symbol repeatable https:\/\/github.com\/ – Closed: Support multiple accidentals https:\/\/github.com\/w3c-cg\/ – Closed: Barline only takes single coda https:\/\/github.com\/w3c- – In progress: Clarify fan attribute usage for multi-level beams https:\/\/github.com\/w3c-cg\/ To keep the schema, documentation site, tests, release notes, etc. in sync, I am following a list of steps that I keep refining as I go: https:\/\/github.com\/w3c-cg\/ Other than roadmap items, the following topics received recent attention:<\/p>\n\n\n\n – The question of encoding ties and slurs across repeat sections started as a simple-sounding discussion at https:\/\/github.com\/w3c-cg\/ – Many discussion topics and issues have arisen around clarifying the documentation, removing ambiguity, addressing edge cases for the sake of application developers. Thanks to @lemzwerg, @rpatters1 and others for bringing these issues forward – once I feel they reach a place of clarity and mutual understanding, we can consider adding them to the roadmap.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" ROADMAP PROGRESS With the build system for the documentation site and the test system now firmly in place, it is possible to achieve good velocity with actual work towards the next MusicXML 4.1 release https:\/\/github.com\/w3c-cg\/musicxml\/milestone\/3. Here are the items that have … Continue reading ONGOING TOPICS<\/h2>\n\n\n\n