[MEI-L] feature request list (long)

[Roland, Perry (pdr4h)]

Blocks of text between staves should be marked using <div> or <anchoredtext>.

--
p.

__________________________
Perry Roland
Digital Curation Services
University of Virginia Library
P. O. Box 400155
Charlottesville, VA 22904-4155
434-982-2702 (w)
pdr4h at virginia.edu
________________________________
From: mei-l-bounces+pdr4h=virginia.edu at lists.uni-paderborn.de [mei-l-bounces+pdr4h=virginia.edu at lists.uni-paderborn.de] On Behalf Of Raffaele Viglianti [raffaeleviglianti at gmail.com]
Sent: Wednesday, March 31, 2010 1:18 PM
To: Music Encoding Initiative
Subject: Re: [MEI-L] feature request list (long)


On 31 March 2010 15:21, Roland, Perry (pdr4h) <pdr4h at eservices.virginia.edu<mailto:pdr4h at eservices.virginia.edu>> wrote:

> So what about a <mei:spoken> element? (I'm sure someone in the list could propose a more appropriate name for non-sung text) For now, it could be in the text module and could live between measures (i.e. in model.sectionPart or model.measureLike) and just contain <p>. What do people think?

Actually, I'd be more inclined to create a specialized form of the <dir> element.  It would be in the controleventLike class and could occur anywhere other elements in that class, such as dir, dynam, phrase, tempo, hairpin, octave, reh, slur, tie, etc., could occur.  In other words, <spoken> would be attached to a staff and it's time location would be specified just like these other elements, i.e., with @tstamp or @startid.


<dir> is not allowed between measures, right? (please correct me if I'm wrong)
I am thinking of situations where a portion of text is added in between staves, for example at the end of a section and before the start of a new one. I guess it would still be representable with <dir> but it would be semantically attached to the first following staff. I think that expanding <dir> is still a good idea, but could it be worthwhile to allow this customised element also in between sections?

Raffaele