guidelines
guidelines copied to clipboard
music-encoding
:scroll: The Music Encoding Initiative Guidelines
For example, it would be nice to link to the `@enclose` attribute on ``. There are likely two parts to this -- 1: including an `id` on the HTML element...
It would be a nice feature to link any occurrence of an element from its descriptions in the tag library.
In v4.0.0 `` underwent heavy changes that are not reflected in the documentation. This leads to confusion (cf. https://github.com/music-encoding/music-encoding/issues/579) and should be fixed
The *Declaration* fields in the guidelines, that present the ODD snippet, are invalid, because `` is not allowed within ``. Example: http://music-encoding.org/guidelines/dev/data-types/data.uneumename.html
data.DURATION.gestural and data.DURATION both refer to data.DURATION.cmn (and data.DURATION.mensural). That restricts the values of `@dur.ges` to the same as those for `@dur`, which doesn't make sense, does it?
As pointed to in https://github.com/music-encoding/music-encoding/issues/602 @key.sig.mixed is no longer available in MEI v4. A way of encoding mixed key signatures should be provided in the guidelines.
I'd like to improve and expand the pedal section in chapter 04. But I'm not quite shure how to encode piano pedal lines. AFAICS there are different possibilities (refers to...
This issue can be used to discuss chapter 7 of the guidelines.
The key element: https://music-encoding.org/guidelines/v4/elements/key.html Is currently allowed to be contained in these element: It was originally designed to be a header-specific description of the key for the work. However, it...
`[email protected]` (and `[email protected]`) can have the value `above` or `below`. What exactly does this mean? The documentation says that it is in relation to the noteheads: `@place` in other cases...
Metadata
Owner
Metadata
:scroll: The Music Encoding Initiative Guidelines