Re: Upcoming MusicXML 3.1 issues

1-2) Sound good.

3) I would vote *not* to add a new direction-type for the "do not copy"
symbols and would prefer that they be specified with the other-direction
semantics.

4) I added a comment on github.

5) Sounds good.

.mjb


On Mon, Feb 6, 2017 at 10:09 AM, Michael Good <mgood@makemusic.com> wrote:

> Hello all,
>
> Here are some of the outstanding MusicXML 3.1 issues I would like to
> address next, starting this week. If you have comments or suggestions on
> the proposed implementations, please share them soon - either on this list
> or in GitHub.
>
> 1) Mixing musical symbols with text in directions and credits. This
> involves adding <symbol> and <credit-symbol> elements whose text is a SMuFL
> canonical glyph name. (https://github.com/w3c/musicxml/issues/163)
>
> 2) Add more comprehensive piano pedal indications, supporting the
> sostenuto pedal symbol and the abbreviated damper and sostenuto symbols
> present in SMuFL. This involves adding a sostenuto type and two new
> attributes (abbreviated and number) to the pedal element. (
> https://github.com/w3c/musicxml/issues/102)
>
> 3) Add the complete SMuFL miscellaneous symbols range. This involves
> adding an optional metronome-arrows element to the metronome element. There
> are also two “do not copy” glyphs. Should we add a new direction type for
> these, or just rely on the other-direction element being able to specify an
> arbitrary SMuFL glyph? (https://github.com/w3c/musicxml/issues/93)
>
> 4) Allow grace cue notes. This includes adding a new grace cue symbol
> size, and explicitly documenting that the cue element indicates a silent
> note. (https://github.com/w3c/musicxml/issues/68 and https:/
> /github.com/w3c/musicxml/issues/67)
>
> 5) Add the complete SMuFL lyrics range by specifying SMuFL glyphs for
> elisions in addition to the descriptive names already present. (
> https://github.com/w3c/musicxml/issues/101)
>
> I also plan to prepare a specific proposal for adding more unique element
> IDs early this week (https://github.com/w3c/musicxml/issues/145).
>
> Best regards,
>
> Michael Good
> VP of MusicXML Technologies
> MakeMusic, Inc.
>
>