pe-ro

This may start a cascade of allowing `@rend` on lots of block-level elements -- `` for sure, but also other text-y elements like ``, ``, `` and all its derivatives,...

Just a thought: we can think of `` as another kind of incipit and therefore allow it to contain score-level markup. Perhaps this allows too much leeway, but it relieves...

@efreja, I'm not sure I understand your comment about rendering. I assume you mean that given content of "Dm7/G" in the `` element, you want to render the "Dm7" part...

The universe of documents that MEI aims to represent is much larger than what Music21 will allow, so limiting chord labels to a set of so-called "standard names" probably won't...

@gregchapman-dev, MEI provides the `@class` attribute for such situations. `@class` holds a reference to a `` element, stored in the header, which in turn records a term in a taxonomy....

`@class` is a more restrictive version of `@type` since it requires one to provide a taxonomy of types/classes. Alternatively, `@type` is a freer version of `@class` as it allows one...

Can you provide a more concrete example of what you're describing? Just make up some markup and we can discuss it. Here's an example of the use of `@class`. Step...

"jazz" as an element name seems overly broad to me. I haven't looked at the **jazz interpretation, but I presume it implements a particular harmonic labeling system.

@gregchapman-dev, your proposal is simple -- in this particular case. The problem is that, despite your short list of chord labeling systems, the number of elements needed to accommodate everyone's...

I'm inclined to stick with adding `@normal`, although perhaps a better name would be `@pitches`, `@pitchcontent`, etc. As long as a place is provided to record the pitch content, I...