[MEI-L] Encoding Square Notation

[Andrew Hankinson, Mr]

Hi Perry,

I'll answer inline below to address some of your questions:

On 2010-06-17, at 6:32 PM, Roland, Perry (pdr4h) wrote:

> Andrew,
> 
> Let me do a little house cleaning in the McGill repo first.  I'm waiting on the results of a little poll of the other members of the technical team, but I should have this done by early next week.  Then we'll talk about where to put the new stuff.
> 
> Yes, RNG and XSD are the targets right now.  We hope that by early next year, the target will switch to ODD, but you don't need to worry about that now.
> 
> My modus operandi has been to work in RNG (because I find it easier to comprehend) and then use Trang from inside oXygen to convert to XSD.  Periodic testing of this conversion is a good idea as there are some things that can't be automagically translated.  But if the conversion doesn't work, then it's a clue that you're being too RNG-centric and you should find another way of writing the schema.
> 
> I think a good starting point would be to modify the neumes module and then the mei-all driver file to include your modified neumes module instead of the original one.  We can take up the possibility of using the current neumes module plus a solesmes module later.

That all sounds good to me. I think a separate Solemnes module is probably the best way to go, given the differences between the variations of neume notation. If we do see some crossover later, we can merge it into a "neumes common" module.

> Regarding episemata:
> 
> Rather than using the values "horizontal", "vertical", "both" --
> 
>>> <syllable>
>>>  <syl>DE_</syl>
>>>  <uneume xml:id="d1e1" name="punctum">
>>>     <note pname="c" oct="4"/>
>>>  </uneume>
>>> </syllable>
>>> <syllable>
>>>  <syl>us</syl>
>>>     <uneume xml:id="d2e1" name="punctum">
>>>        <note pname="c" oct="4" episema="both" />
>>>                **OR**
>>>        <note pname="c" oct="4">
>>>           <episema type="horizontal" />
>>>           <episema type="vertical" />
>>>        </note>
>>>     </uneume>
>>> </syllable>
> 
> I think it would be easier to mesh with any meaning(s) in other repertoires later, if you chose values based on what's being indicated rather than the visual symbol.  For instance --
> 
> <syllable>
>  <syl>DE_</syl>
>  <uneume xml:id="d1e1" name="punctum">
>    <note pname="c" oct="4"/>
>  </uneume>
> </syllable>
> <syllable>
>  <syl>us</syl>
>  <uneume xml:id="d2e1" name="punctum" episema="compoundbeatbeginningandslightlengthening">
>    <!-- OR elements instead of the attribute:
>    <episema value="slightlengthening" />
>    <episema value="compoundbeatbeginning" /> -->
>    <note pname="c" oct="4"/>
>  </uneume>
> </syllable>
> 
> Of course, these particular values are absurd, but you get the point.  A more appropriate value for "compoundbeatbeginning" is "ictus" (if I read the Harvard Dictionary correctly), but I'm less sure about the other ones.  I hope Stefan will suggest values for the others.  Stefan?