Laurent Pugin

It seems that we have a consensus that `` is not really necessary in ``. @pe-ro @fujinaga @kepper @musicEnfanthen

It looks good to me to have `note@size` with percent. However, I would avoid allowing additional symbolic values. Beside the fact that it makes typed implementation such as in Verovio...

> I like `@fioritura`, but not the name. I agree it is not really appropriate. Maybe simply `@small` ? That might seem dull, but maybe a more neutral solution for...

> And what about combinations of `@grace` and `@small?` Or `@cue`? Are they even smaller still? That is something we can prevent with Schematron. At least to prevent `@small` and...

I would still try to avoid `cue-sized` if possible. What about `ornam-sized`? Obviously, any choice need to come with some explanation for what it is meant for. That should include...

And an example of a grace note within a cue 

For [this](https://github.com/music-encoding/music-encoding/issues/700#issuecomment-665834649) example, it would be valuable to reconsider the issue #470 with the idea that you could do ``` /measure /staff (with invisible right barline) /beamSpan /staff (with visible...

@kepper don't you want to have the script for converting the MEI within this repository? I am sure that https://github.com/Edirom/staticVerovioConverter works but then things (e.g., options for the conversions) are...

OK, thanks for the explanation. Sounds fine. I guess if everything runs from a single docker image then having a Python script vs a JavaScript script makes no real difference....

@craigsapp this should discussed in the music encoding repository. I am closing it here.