[climacs-cvs] CVS update: papers/ilc2005/syntax/climacssyntax.tex

[Christophe Rhodes]

Update of /project/climacs/cvsroot/papers/ilc2005/syntax
In directory common-lisp.net:/tmp/cvs-serv522

Modified Files:
	climacssyntax.tex 
Log Message:
Some more small additions

Date: Wed May 18 15:56:46 2005
Author: crhodes

Index: papers/ilc2005/syntax/climacssyntax.tex
diff -u papers/ilc2005/syntax/climacssyntax.tex:1.4 papers/ilc2005/syntax/climacssyntax.tex:1.5
--- papers/ilc2005/syntax/climacssyntax.tex:1.4	Wed May 18 11:51:43 2005
+++ papers/ilc2005/syntax/climacssyntax.tex	Wed May 18 15:56:45 2005
@@ -127,7 +127,10 @@
 Christophe might want to describe the Prolog syntax a bit here. In
 particular any details having to do with the implementation of
 operator precedence as specified in the ISO Prolog standard might be
-interesting.
+interesting.  [ Maybe just the \textit{priority} stuff? I think that's
+the only interesting bit of non-context-freeness; user-defined
+operators is OK because you can't actually define and use a new
+operator in the same directive. ]
 
 The TTCN3 syntax is implemented with a high-level macro which defines
 classes and adds syntax rules using the syntax protocol for each
@@ -160,7 +163,37 @@
   \end{center}
 \end{figure*}
 
-Christophe should describe the tabcode editor here.
+\TabCode\ is a textual format for description of lute tablature.  In
+its simplest form, it is a sequence of whitespace-delimited
+independent words, where each word represents either a set of frets to
+depress and strings to be sounded, or alternatively some element of
+musical notation (such as a barline); figure \ref{fig:besfantlach}
+demonstrates a fragment of manuscript, and its \TabCode encoding.  It
+is also possible to encode more complex elements of lute tablature
+notation in \TabCode: ornaments, beaming, connecting lines and other
+complex elements can all be accommodated.
+
+\TabCode\ has been used to produce scholarly editions of lute works
+\cite{Weiss} and to computer-based musicological studies (as in
+\cite{ecolm-graz} for example).  
+
+\TabCode\ has a rather ad-hoc cobbled together grammar.  Tokenising is
+easy; determining which elements of the notation are best captured is
+not so easy.  Chords, obviously; beams, comments...  Should we try to
+capture a BNF or something?  I suppose it depends how we're doing for
+space.
+
+Need whole-buffer function to present an alternative whole-system view
+on the data.  
+
+Editor is in use for cataloguing European lute music, and supports
+research into more advanced notations (for e.g. editorial comment, or
+manuscript markup)
+
+Efficiency concerns assuaged by typical locality of edit, incremental
+redisplay on the tablature buffer.
+
+MIDI feedback.
 
 \section{Conclusion}