Matt Gough Blog [closed]: review / overview
Saturday, Apr 10 2004, 03:08
lets break it down;
we have the scripting and the scripting notation [with hand written and machine readable formats of both]. the implementation of the score is the scripting, the xml based syntax the notation.
scripting:
michael klein proposed that multiple choreographers random scribbles could be examined to develop a common scripting language to develop and plan dance works. although written on paper in a left to right format the intention was to get away from linear scores that potentially prevented the scripting of complex / emergent works.
my personal belief is that complexity is in the eye of the beholder. as much as it is possible to illustrate complex systems the act itself renders them simple. the more simple 'looking' the system the greater the potential complexity.
in order to create emergent or non linear works we must be able to define multiple systems in the single work, both open and closed. however it is only in the reading / performance of the score that the emergent / non linear properties may be revealed. interpretation can be everything, at some level there must be open instruction in reading of these scores in general. the dancers should be as capable and confident as a musician or actors sight reading new scores and scripts. remaining true to the 'intention' of the work yet bringing their unique interpretation and innovation as and where required.
notation:
I make no claims to be the first to suggest an xml based dance notation system. as far I am aware the only existing system in [limited] use is for morris / country dancing and is used drive a basic java visualisation of set dances. systems for concert dance have be proposed but not developed.
this particular project differs from other proposals in two areas. firstly a clearly defined intention / need rather than just being a technical exercise. secondly the system is being designed for both human and software implementation to encourage usage.
from hand to machine:
professional notators are expensive, documenting a work for archival can be a involved process. apart from the new form being simple to notate by hand [and create hand written archives], it should also be convertable to machine readable format with a minimum of knowledge and equipment. ideally a crib sheet of the document format and syntax, a basic text editor and a web browser to view the document tree.
the absence of dedicated software for doing 'something' with these files may put some artists off from creating machine readable scores. however with most dance and technology artists making their own software for performances i envisage software becoming quickly available. in addition to this the advantages of this system to smooth dance and technology collaborations cannot be under estimated.
some thoughts:
it has always been my belief that the system should be free to use and well documented. rather than being the property of a particular group it should be of benefit to the dance community as a whole. that said the project should be lead with vision, insight and clarity and i think that michael is the person to do that.
it has alway been a struggle to get dancers / choreographers to embrace new methodologies. although this notation is less complex than laban or benish we should remember that both these forms have a low take up. if our approach is based on solid theory and practical knowledge with a simple, capable implementation i think that those who take the time to experiment with the system will use it on a regular basis.
matt
i'm away from my usual terminal at the moment so please excuse the double posting
Filed by Article19 at 3:08 PM | 
Stumble It!