Laurent Pugin

I left `tab.string` with the idea that this could go into an MEI 5.1. However, since we are now looking at having this for version 6.0, then it can be...

Yes, I realized that there was a problem with my proposal. I do find the semantics of `` problematic and would prefer a more neutral element. At the same time,...

Yes, I think we are. This makes sense. However, I think I would go one step further and **remove** `att.horizontalAlign` and `att.verticalAlign` from `rend`. If you want to do what...

Not quite. See https://github.com/music-encoding/music-encoding/issues/1189#issuecomment-1572054858 and a few more of our comments. I think we still need `att.horizontalAlign` and `att.verticalAlign` to be added to ``, or to `` but to ``...

> [...] can be "the same" as another rest, but with a different layout. Then it is not the same... I think that is a case where you would use...

One example where I think it is useful to use `@sameas` for specifying the it is the same element at the same location at the same time can be when...

It seems that there is more work needed here: * It would be better to have the attribute describing size to be call `size` and not `fontsize`. That way it...

Regarding the question of the beat and compound meter, one solution I imagined was to specify it with an additional attribute (e.g `@beat`) that would specify how many `meter.unit` a...

I can personally live with `meterSig` but I agree too the `timeSig` would be better. Does it need to be a 4.0.0 version? Wouldn't 3.1 be OK? Looking at `@beatDef`...

I am not convinced that `@tstamp.ges` is really the right option for context-less timestamps. My understanding of `*.ges` attributes is for them to be provided when the gestural domain information...