<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 15, 2013 at 12:02 PM, Andrew Hankinson <span dir="ltr"><<a href="mailto:andrew.hankinson@mail.mcgill.ca" target="_blank">andrew.hankinson@mail.mcgill.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
application/vnd.mei+xml .xml -> Mapping .xml to the MEI mime type seems like a big problem.<br>
<br>
application/vnd.mei+xml .mei -> Seems like the best solution, yes?<br></blockquote><div><br></div><div>As far as I know mimetype is orthogonal to file extension, so even if we secure a mimetype application/mei+xml it won't matter if your file has .xml or .mei extension.</div>
<div><br></div><div>I personally don't see an issue with file extension at all. What's the problem with using either .mei or .xml? In a web context all that matters is the mimetype, in a OS context, using .xml is generally going to make things easier, but it's not eventually not a big deal.</div>
<div><br></div><div>Raf</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
(the MEI mime type I give is just an example).<br>
<br>
-Andrew<br>
<br>
<br>
On 2013-08-15, at 5:47 PM, Sigfrid Lundberg <<a href="mailto:slu@kb.dk">slu@kb.dk</a>><br>
<div class="im"> wrote:<br>
<br>
> .txt is a poor choice. Most web servers will deliver that as text/plain which is not what you want. In apache web server there is a file mime-types which connects extensions to mime types, which then interacts with users web clients and plug-ins and helper applications<br>
><br>
</div><div class="im">> Sigfrid<br>
> ________________________________________<br>
> Fra: <a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a> [<a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a>] på vegne af Andrew Hankinson [<a href="mailto:andrew.hankinson@mail.mcgill.ca">andrew.hankinson@mail.mcgill.ca</a>]<br>
</div>> Sendt: 15. august 2013 17:23<br>
<div class=""><div class="h5">> Til: Music Encoding Initiative<br>
> Emne: Re: [MEI-L] File extensions<br>
><br>
> You can sign me up too.<br>
><br>
> Personally, I like .mei. XML could also be thought of as plain text, so I would argue that we should go with the most specific usage, rather than the most general. We could just go with .txt and be just as correct as .xml.<br>
><br>
> Either way, though, I think this is an appropriate topic for putting some guidance in the Guidelines. I'll volunteer to write it, but I would like some way of getting a consensus.<br>
><br>
> Any ideas? An online poll?<br>
><br>
> -Andrew<br>
><br>
> On 2013-08-15, at 5:09 PM, "Roland, Perry (pdr4h)" <<a href="mailto:pdr4h@eservices.virginia.edu">pdr4h@eservices.virginia.edu</a>><br>
> wrote:<br>
><br>
>><br>
>> Sigge,<br>
>><br>
>> Thanks for being so gracious in your acceptance of my effort to "volunteer" you.<br>
>><br>
>> There's no rush on this. After Christmas/beginning of 2014 is fine. I'm sure you'll find willing volunteers to help you write the proposal. You can "volunteer" me in return. :-)<br>
>><br>
>> Anyone who wants to participate, please contact Sigge. I hear he's starting a list. :-)<br>
>><br>
>> Thanks again,<br>
>><br>
>> --<br>
>> p.<br>
>><br>
>><br>
>> __________________________<br>
>> Perry Roland<br>
>> Music Library<br>
>> University of Virginia<br>
>> P. O. Box 400175<br>
>> Charlottesville, VA 22904<br>
>> <a href="tel:434-982-2702" value="+14349822702">434-982-2702</a> (w)<br>
>> pdr4h (at) virginia (dot) edu<br>
>> ________________________________________<br>
>> From: mei-l-bounces+pdr4h=<a href="mailto:virginia.edu@lists.uni-paderborn.de">virginia.edu@lists.uni-paderborn.de</a> [mei-l-bounces+pdr4h=<a href="mailto:virginia.edu@lists.uni-paderborn.de">virginia.edu@lists.uni-paderborn.de</a>] on behalf of Sigfrid Lundberg [<a href="mailto:slu@kb.dk">slu@kb.dk</a>]<br>
>> Sent: Thursday, August 15, 2013 10:49 AM<br>
>> To: Music Encoding Initiative<br>
>> Subject: Re: [MEI-L] File extensions<br>
>><br>
>> My keyboard is too fast.<br>
>><br>
>> Cannot promise to write it alone and have to discuss it here in Copenhagen. Not before Christmas, that's for sure<br>
>><br>
>> S<br>
>> ________________________________________<br>
>> Fra: <a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a> [<a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a>] på vegne af Roland, Perry (pdr4h) [<a href="mailto:pdr4h@eservices.virginia.edu">pdr4h@eservices.virginia.edu</a>]<br>
>> Sendt: 15. august 2013 16:44<br>
>> Til: Music Encoding Initiative<br>
>> Emne: Re: [MEI-L] File extensions<br>
>><br>
>> Hi Sigfrid,<br>
>><br>
>> Sounds like we have a volunteer to lead the way to registering an MEI mimetype. :-)<br>
>><br>
>> --<br>
>> p.<br>
>><br>
>><br>
>> __________________________<br>
>> Perry Roland<br>
>> Music Library<br>
>> University of Virginia<br>
>> P. O. Box 400175<br>
>> Charlottesville, VA 22904<br>
>> <a href="tel:434-982-2702" value="+14349822702">434-982-2702</a> (w)<br>
>> pdr4h (at) virginia (dot) edu<br>
>> ________________________________________<br>
>> From: <a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a> [<a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a>] on behalf of Sigfrid Lundberg [<a href="mailto:slu@kb.dk">slu@kb.dk</a>]<br>
>> Sent: Thursday, August 15, 2013 10:39 AM<br>
>> To: Music Encoding Initiative<br>
>> Subject: Re: [MEI-L] File extensions<br>
>><br>
>> Hi,<br>
>><br>
>> I'm using .xml as suffix. Don't really care.<br>
>><br>
>> As I'm a coauthor of RFC6129 (<a href="http://tools.ietf.org/html/rfc6129" target="_blank">http://tools.ietf.org/html/rfc6129</a>) I have strong opinions on your "by the way" question. Yes, we should register a mime type, and it should be application/mei+xml. Since it is in the application hierarchy it requires an RFC and some negotiations with IESG and IETF before one get a line in the appropriate IANA document.<br>
>><br>
>> Cheers<br>
>><br>
>> Sigfrid<br>
>><br>
>> ________________________________________<br>
>> Fra: <a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a> [<a href="mailto:mei-l-bounces@lists.uni-paderborn.de">mei-l-bounces@lists.uni-paderborn.de</a>] på vegne af Andrew Hankinson [<a href="mailto:andrew.hankinson@mail.mcgill.ca">andrew.hankinson@mail.mcgill.ca</a>]<br>
>> Sendt: 15. august 2013 16:12<br>
>> Til: Music Encoding Initiative<br>
>> Emne: [MEI-L] File extensions<br>
>><br>
>> Hi all,<br>
>><br>
>> Is there a common understanding of what the proper file extension for MEI files should be?<br>
>><br>
>> I've been assuming .mei is the "standard", but a counter-example of .xml was recently brought to my attention. So, I thought I'd poll the collected wisdom and see what others were doing. Are you using .xml, .mei, or some other variation on these?<br>
>><br>
>> -Andrew<br>
>><br>
>> ====<br>
>> Related:<br>
>> -- Should we register an actual mimetype? Maybe: application/vnd.music-encoding+xml ?<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><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>
>> 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>
>> 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>
>> 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><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><br>
</div></div></blockquote></div><br></div></div>