<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I’m not sure what you think is a bad idea or what you mean mean by “already compromised”. Can you elaborate please?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> mei-l [mailto:mei-l-bounces@lists.uni-paderborn.de]
<b>On Behalf Of </b>Raffaele Viglianti<br>
<b>Sent:</b> Monday, November 09, 2015 5:00 PM<br>
<b>To:</b> Music Encoding Initiative<br>
<b>Subject:</b> Re: [MEI-L] list-related changes<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I think this is a bad idea. Whatever target format / platform will display the MEI should be able to access a basic text-styling system that can target, if not the MEI directly, at least a target output. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Text encoding in MEI is already compromised, so we either continue being careless in that matter, or we can avoid making it worse.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Another approach would be adopting a system that would make it easy to embed styling, such as TEI's @<a href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.rendition.html#tei_att.rendition">rendition</a> (and <<a href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-rendition.html">rendition</a>>).
In this way you can have the cake and eat it too.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Raff<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Nov 9, 2015 at 4:31 PM, Roland, Perry D. (pdr4h) <<a href="mailto:pdr4h@eservices.virginia.edu" target="_blank">pdr4h@eservices.virginia.edu</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal"><br>
Putting the mark in the markup --<br>
<br>
[Unicode for bullet] item 1<br>
[Unicode for bullet] item 2<br>
etc.<br>
<br>
denies the opportunity to treat the bullet separately from the item content. Your suggested approach mixes what is presentational with actual content. That's generally a bad idea.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
> -----Original Message-----<br>
> From: mei-l [mailto:<a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a>] On Behalf Of<br>
> Johannes Kepper<br>
> Sent: Monday, November 09, 2015 4:09 PM<br>
> To: Music Encoding Initiative<br>
> Subject: Re: [MEI-L] list-related changes<br>
><br>
> I'm sorry to say, but I see no need to include that in MEI. If I want to be<br>
> descriptive, I can include the mark in the encoding itself. But of course you're<br>
> free to convince me and anyone else who's not convinced yet :-)<br>
><br>
> jo<br>
><br>
> Am 09.11.2015 um 22:03 schrieb Roland, Perry D. (pdr4h)<br>
> <<a href="mailto:pdr4h@eservices.virginia.edu">pdr4h@eservices.virginia.edu</a>>:<br>
><br>
> ><br>
> > I'd like to make it easier to control the formatting of lists from within the<br>
> document markup rather than pushing it off entirely to CSS or othe, external<br>
> formatting procedures.<br>
> ><br>
> > To this end, I plan to remove the current @form attribute and create a new<br>
> att.listrend attribute class containing @mark and @order attributes --<br>
> ><br>
> > <attList><br>
> > <attDef ident="mark" usage="opt"><br>
> > <desc>Contains the character string (usually a single character, such as a<br>
> bullet,<br>
> > box, dash, etc.) that precedes each item in the list.</desc><br>
> > <datatype><br>
> > <rng:data type="string"/><br>
> > </datatype><br>
> > </attDef><br>
> > <attDef ident="order" usage="opt"><br>
> > <desc>Indicates the system used to generate the character string (usually<br>
> a single<br>
> > character) that precedes items in an ordered list.</desc><br>
> > <datatype><br>
> > <rng:data type="NMTOKEN"/><br>
> > </datatype><br>
> > <valList type="semi"><br>
> > <valItem ident="alphalower"><br>
> > <desc>Lower case letters.</desc><br>
> > </valItem><br>
> > <valItem ident="alphaupper"><br>
> > <desc>Upper case letters.</desc><br>
> > </valItem><br>
> > <valItem ident="arabic"><br>
> > <desc>Arabic numerals.</desc><br>
> > </valItem><br>
> > <valItem ident="romanlower"><br>
> > <desc>Lower case Roman numerals.</desc><br>
> > </valItem><br>
> > <valItem ident="romanupper"><br>
> > <desc>Upper case Roman numerals.</desc><br>
> > </valItem><br>
> > </valList><br>
> > </attDef><br>
> > </attList><br>
> ><br>
> > Any list without one of these attributes (a list cannot have both) should be<br>
> assumed to be "simple"; that is, without any mark or order. This is NOT<br>
> procedural markup, just somewhat more descriptive than what used to be<br>
> allowed. J<br>
> ><br>
> > --<br>
> > p.<br>
> > ________________________________<br>
> > Perry Roland<br>
> > University of Virginia<br>
> > P. O. Box 400874<br>
> > Charlottesville, VA, 22904<br>
> > <a href="tel:434-982-2702">434-982-2702</a> (w)<br>
> > pdr4h (at) virginia (dot) edu<br>
> ><br>
> > _______________________________________________<br>
> > mei-l mailing list<br>
> > <a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
> > <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">
https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
<br>
<br>
_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>