> > While thinking about verse, I would also like to sneak in a new > > element which should have been there all along: <rhyme>. This > > will be a phrase level element used to delimit the rhyming word/s > > of a line. It will have an attribute LABEL to identify which bit > > of the rhyme scheme (e.g. the a or b) this rhyming word > > instantiates and possibly TYPE to indicate what sort of a rhyme > > this is (e.g. full, partial, etc) Overall I'm in favor, but I'm a bit concerned that we'd be rushing ahead without thinking this through. E.g., what about markup to indicate stress (particularly important in old Russian poetry, IIRC from David & David's presentation at Extreme a few years ago), scansion, etc.? Do we really need a label=, or will n= do? Is type= sufficient for indicating a true rhyme vs a near rhyme, or are near rhymes ineligible? E.g. And all through the *house* Not a creature was stirring, Not even a *mouse*. vs ... syllables into a *line*, It sounds more ethnic if it ain't good English, And it don't even gotta *rhyme*. > Would such an element also need some sort of identifier to > differentiate it from other <rhyme label="b"> elements in a given > document? After all, when detailing rhyme schemes on different > poems, one conventionally always starts with "a," yet the "a" sound > of one poem bears no relation to the "a" sound of another. Good point, but my gut instinct is that we could rely on position in the hierarchy to differentiate one <rhyme label="a"> from another. However, one does wonder if one <rhyme n="a"> should point to its corresponding <rhyme n="a">, and vice-versa.