pe-ro

In my opinion, when `@sameas` is used, it's the elements that are the same thing. Some, but probably not all, attributes may vary depending on context.

It's there because I copied the content model from an RNG schema I was using to test the changes.

Partially addresses issue #1351

I don't think Pure ODD supports the concept of interleave. This is a stumbling block to adopting Pure ODD in my opinion. Perhaps Pure ODD supports interleave in a way...

It's used in the content model of `` and in the modifications to ``, ``, ``, and `` I recently suggested. I suppose the reason it's not supported in ODD...

The time signature-based scheme is designed for human encoders who aren't usually very good at calculating tick offsets. :-) Treating all time signatures as indications of simple meter means that...

> If we do not want to do this, we can still specify it in the beatRpt itself (with a duration?). For > timestamp, then we should probably clarify in...

I think `@tstamp.ges` should be redefined as "pulses/clicks elapsed since the start of the score or part" and `@tstamp2.ges` (with the same datatype) added for those elements that already have...

Assuming that `@tstamp.ges` is sufficient to record event onset times in units other than musical ones, i.e., so-called "beats", I'm contemplating adding a new attribute, `@tstamp.ges.origin` to indicate whether the...

I should have been more precise about the intended values for `@tstamp.ges.origin`. The idea was that it may take the values 'score' and 'measure' to indicate whether the numeric values...