<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Last January, I raised an issue about Tick-based Timing in the
W3C Music Notation Community Group's MNX Repository [1], but it
was closed in February without my being satisfied that it had been
sufficiently discussed.</p>
<p>I had the feeling that something important was being glossed
over, so have been thinking hard about the subject over the past
few weeks, and have now uploaded an article about it to my website
[2].<br>
</p>
<p>My conclusions are that Tick-based Timing<br>
</p>
<ul>
<li> has to do with the difference between absolute (mechanical,
physical) time and performance practice,</li>
<li>is relevant to the encoding of <i><b>all</b></i> the world's
event-based music notations, not just CWMN1900.</li>
<li> needs to be considered for the next generation of music
encoding formats<br>
</li>
</ul>
<p>I would especially like to get some feedback from those working
on non-western notations, so am posting this not only to the W3C
MNCG's public mailing list, but also to MEI's.</p>
<p>All the best,<br>
James Ingram<br>
(notator)<br>
</p>
<p>[1] MNX Issue #217: <a class="moz-txt-link-freetext"
href="https://github.com/w3c/mnx/issues/217">https://github.com/w3c/mnx/issues/217</a><br>
[2]
<a class="moz-txt-link-freetext"
href="https://james-ingram-act-two.de/writings/TickBasedTiming/tickBasedTiming.html">https://james-ingram-act-two.de/writings/TickBasedTiming/tickBasedTiming.html</a></p>
<br>
<div class="moz-signature">-- <br>
<p><a class="moz-txt-link-freetext"
href="https://james-ingram-act-two.de">https://james-ingram-act-two.de</a><br>
<a class="moz-txt-link-freetext"
href="https://github.com/notator">https://github.com/notator</a></p>
</div>
<div class="moz-signature">
<title>email signature</title>
<meta charset="utf-8">
<style type="text/css">p
{
margin-bottom: 2px;
font-family:'Arial, sans-serif';
font-size: 13px;
</style> </div>
</body>
</html>