Klaus Rettinghaus

Thanks for the reminder! Obviously I need to resolve those conflicts. And I'd like to have some feedback on the changes in the XSLTs from @kepper. Or we split things...

Conflicts resolved.

Well you could do that, but then it applies also to every specified element name and attribute value. But values like "adlib" and "sprech" are not English. Do we want...

Thanks. The only other place we use a dot as separator in attribute values is in `data.NOTATIONTYPE` specifying a subtype. All other cases use a dash. Maybe use `above-below` and...

Maybe @ahankinson could add his thoughts here, because some of the proposed improvements for LibMEI could/should go upstream?

Sorry, I see a tie in the upper voice.

You want to treat an accidental like a free floating glyph, but it is always connected to a pitch event, so from my point of view it should be (always...

A current problem I see is that [model.syllablePart](https://music-encoding.org/guidelines/dev/model-classes/model.syllablePart.html) is member of [model.eventLike](https://music-encoding.org/guidelines/dev/model-classes/model.eventLike.html), allowing as syllable children: * [barLine](https://music-encoding.org/guidelines/dev/elements/barLine.html) * [chord](https://music-encoding.org/guidelines/dev/elements/chord.html) * [clef](https://music-encoding.org/guidelines/dev/elements/clef.html) * [clefGrp](https://music-encoding.org/guidelines/dev/elements/clefGrp.html) * [custos](https://music-encoding.org/guidelines/dev/elements/custos.html) * [note](https://music-encoding.org/guidelines/dev/elements/note.html) * [pad](https://music-encoding.org/guidelines/dev/elements/pad.html)...

@bwbohl Did you have a look?

In latest develop `@tstamp2` is available (though `@tstamp2.ges` and `@tstamp2.real` are not). What needs to be done here?