Re: Measure-free scores

>
> Did I miss a use of measures? I see no musically-justified reason to add
> measures as a container.
>

Respectfully, I think you did miss at least a couple (as have the rest of
those on the thread agitating to get rid of <measure>):

1. Having a <measure> element allow inheritable style properties to be
attached to that element and affect all of its descendants. This makes it
very easy to render an entire measure in a different style by setting a
property in one places -- say, coloring it to highlight a particular
measure in a teaching presentation, would be as easy as applying <measure
style="color: red;">. Without a container, this requires a lot more smarts
from the programmer to determine which run of elements to affect.

2. In a future where musical DOMs support interactivity, a <measure>
element will dispatch events whenever the user interacts with any of its
descendants. Consider a teaching application that asks a student to click
to identify the measure in which some motive occurs.

I feel this discussion has become a bit stuck on encoding compositional
intent. Our use cases for the CG definitely include learning and teaching
music, and live interaction with it, as an important (and "musically
justified") activity.

Note that this applies only to cases where there are actual measures and
barlines in the music -- so please let's not go around on that topic again.
It's been noted that we have to solve the problem of music without
barlines/measures.

...Joe