Klaus Rettinghaus
Klaus Rettinghaus
This PR allows nesting of `meterSigGrp` elements, and makes `meterSigGrp` a part of `att.enclosingChars` and `att.visibility`. It also removes the schematron assertion rule and makes the rule for needing at...
It seems we reached consensus on possible encodings for split stem notation. This PR offers an implementation with `@stem.split` as part of `att.stems`. Alternatively it could be a direct child...
This PR aligns `att.keySig.anl` with `att.keySigDefault.anl` (as it is supposed to be). Now `key@accid`, `keySig@accid`, `[email protected]`, and `[email protected]` all require a value from `data.ACCIDENTAL.GESTURAL.basic`. closes #590 refers to #1157
Looking into the [bend](https://music-encoding.org/guidelines/dev/elements/bend.html) element, I noticed a problem with the description (or current usage) of the values for "above" and "below". The value "above" in `@curvedir` is described as...
The examples in the Guidelines rendered by Verovio are missing a `figcaption` element. It would be good to have a similar style for all example images.
This is a big step towards purification of our ODD schema. Every step taken here doesn't change the produced RNG at all. Some things can be simplified even more, but...
In reaction to https://github.com/music-encoding/music-encoding/issues/555#issuecomment-1694513365 this remodels `dedicatee` to be in line with `composer`, `funder` and other similar elements, mainly to make it available as child of `work`.
Perhaps I missed something, but I don't understand why `[email protected]` is of `data.ACCIDENTAL.GESTURAL` whereas `keySig@accid` is of `data.ACCIDENTAL.WRITTEN`.
In some cases there are tuplets crossing staves without a beam. To deal with this, `@bracket.place` and `@num.place` should allow the same values as `@beam.place`, i.e. "mixed" is missing. see...
It would be good if the GH action also would keep the build artifacts instead of simply deploying the schema to another repo. Also it would be good, if the...