Re: MusicXML issue

Hi
differences are annoying but can also staff music in itself has not an
unique form for representation: in this direction I liked the MIDIxml
efforts, as the format could be used IMHO to cross-check the manual
annotations inserted in musicxml, to try solve some points of an ambiguous
notations

All existing sheet-music-editors have inconsequences in their
> musicxml-exports. However, lot’s of the time it’s not the problem of the
> editing-software itself, it’s the person who is using the software in a
> wrong way to input his content. When this “engraver" is using a “text”-tool
> while he/she should have been using the “fingering”-tool, nobody can do
> anything about it until somebody invents an unambiguous UX-toolbox for
> common mistakes like this :-)
>

Not only IMHO, it's not only a problem of representation in itself, but
also a problem with processing data to create an automatic
"representation". I suppose something could be done with some kind of
machine learning to create "patterns" for representing snippets in a way
which may sound reasonable, but this is not an easy task, and does not
resolve human differences you cited. However maybe trying approaching the
problem (in the export/procesing phase) from several parallel point of view
may help?



> If you like to try it yourself, please visit
> http://www.musicxmlsanitizer.io. It actually is our first step for
> importing a musicxml-file into neoScores. It is in continuous development
> so please come back regularly. It’s our intention to expand this “service”
> to become some kind of musicxml-validator like the w3c Markup Validation
> Service https://validator.w3.org/
>

 this could be a great service! :-)