[MEI-L] feature request list (long)

[Joachim Veit]

Hi all,
my God, I can't hardly keep pace with all these discussions...
Perry, many thanks for the "spoken"-text clearification!! If it is
possible to encode that thing which you call a "directive" that's very
fine. I am a bit puzzled by the word "directive" which reminds me only
to "stage directions", "tempo directions" etc. - that's another thing
and perhaps we may have a differentiation later?

Only a few things at the moment:


No. 2 from the list:
data:PLACE: if you take 'above' and 'below' why not "left' and 'right"?
('beside' is neutral and you don't know which side...). It my relatively
often occur within historic notation that some notational elements are
not placed in their "normal" order and that we want to fix this
abnormality. And for special details a renderer may use 'left" with a
default value, depending from - perhaps - dynamics, strokes etc. - So
keep the case open by adding 'left' and 'right'??? (even if some of the
cases might be solved by data.STAFFREL)

No. 3 from the list (see above)
If there is something to fix a "non-sung"/"spoken" text in the sense
which you described with Mo und Larry and you do this momentarily in the
<dir>-element, this would be is fine. Perhaps that possibility should be
added to the description of this element  because nobody might reckon
with this possibilty at the moment???

No. 8
HISTORY:
- It seems to be not easy to find the line between "too easy" and "to
complicated" - I can't decide what seems the best way without thinking
about further examples ...
- Concerning the "@when" or <date> discussions I plea for using <date>
(i.e. Perry's problem with a double usage of "when" would be solved in
this way?)
- Johannes @function: Is it really probably that in an event from the
type "dedication" one has to differentiate between several persons?? And
I just see in Perry's answer that  "role" is already usable for this
(rare) purpose
- Besides: I fully consent with Perry's "it would be very annoying to
encode names in TEI one way and MEI names another" (that should be valid
for other central elements too...)
- Concerning the restriction with provenance would such a strange
description be possible (even if I think that creation is not part of
the provenance):
     <provenance>
         <eventlist><event type="creation">....</event></eventlist>
     <provenance>
(I am only asking this as a question of understanding the restriction)

Yours,
Joachim


-------------- nächster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : veit.vcf
Dateityp    : text/x-vcard
Dateigr??e  : 364 bytes
Beschreibung: nicht verf?gbar
URL         : https://lists.uni-paderborn.de/mailman/private/mei-l/attachments/20100401/3f401ee1/attachment.vcf