pe-ro

@craigsapp, In MEI, `@ppq` must always contain an integer value. In other words, MEI enforces your so-called "optimal solution" regarding the capture of note duration. MEI allows one to choose...

I don't know for sure, but I believe that once upon a time, `att.barLine.vis/@place` used a different datatype (as did all the barline-related attributes); hence, the different textual explanation. Somewhere...

To maintain backward compatibility, @rettinghaus is correct. We should keep the datatype for data.STAFFLOC and get rid of the description at `att.barLine.vis/@place`. Bringing in `data.CLEFLINE` is a red herring; however....

Calling it an "addressing" or a "coordinate" system is a distinction without a difference. The point is to be able to reliably identify the line or space where something is...

@riedde, I have not checked for any effects in the Guidelines. I'll do so in the next couple of days.

I just realized that the backward compatibility problem with my last proposal can be eliminated by a model for `` consisting of -- ```xml ``` This will continue to allow...

@bwbohl, the objective is to ensure that `` allows only the following possibilities each time it is used: - one or more `` elements followed by one or more "name-like"...

@riedde, following up on your question > Have you checked if this has side-effects to the guidelines? Is there documentation that has to be changed? The short answer is, yes,...

The idea of a responsibility statement comes from the notion of transcribing that part of a bibliographic item's title that says who's responsible for its content. The most common form...

The removal of `` from [model.textPhraseLike.limited](https://music-encoding.org/guidelines/dev/model-classes/model.textPhraseLike.limited.html) will also need to be addressed in the ~~MEI 4 -> MEI 5~~ MEI 5 -> MEI 6 [EDITED by @bwbohl ] XSLT.