kepper

Well, you certainly don't need to hear from me – but thanks for asking ;-) I'm not sure I really get the point of this discussion, but I totally agree...

All that is generated automatically on commit. However, the code in there is quite old, and has been adjusted several times to different needs (it's been generating the starting point...

just a brief update – I'm working on this (including #46, #59, #35 and potentially #28), and hope to have something ready for review soon. No need for someone else...

that's the code I kept ;-) > Am 05.12.2018 um 13:03 schrieb Klaus Rettinghaus : > > HTML errors/warnings > > • still div within code > • div does...

Well, using `@resp` to identify the editor responsible for identifying the writer is consistent with other uses of `@resp` and should stay like that. But: Don't we lack a mechanism...

@doerners will take it to the Metadata IG…

I think this is still necessary, yes. However, I'm working on some bigger changes to be proposed with a later version of MEI (surely more MEI 6 than MEI 5.x),...

I think the main argument for `//bTrem/note/@slash` was (and still is) that an OMR application (or a human transcriber) may recognize that slash _visually_, but not necessarily the _logical_ meaning....

ping @lpugin if this should go in earlier than someday…

What I would like to see here, in addition to the change in the specs, is some more documentation, maybe along the lines of https://music-encoding.org/guidelines/dev/content/metadata.html#headerRelatedItemVsFRBR. We should ideally give example(s)...