Tools for Music Information Retrieval and Playing - Intelligent Music Information Systems: Tools and Methodologies - page 130

<!ELEMENTthm _ spine _ refEMPTY>
<!--
Thiselementisneededforgeneralization
ofthemerepresentation,
sincetherecouldbethemessplitindif-
ferentsequencesofnotesbelonging
to the same part or even to different
parts.
-->
<!ATTLISTthm _ spine _ ref

segmentArefIDREF#REQUIRED

segmentBrefIDREF#REQUIRED

transformationref IDREF #RE-

QUIRED
>
<!ELEMENTrelationshipEMPTY>
<!ATTLISTsegment

idID#REQUIRED

>

spine _ start _ refIDREF#REQUIRED <!ELEMENTsegment(segment _ event+)>

<!ELEMENTtransformationEMPTY>
<!ATTLISTtransformation
idID#REQUIRED
descriptionCDATA#REQUIRED
gisCDATA#IMPLIED
>
<!ATTLISTsegment _ event
id _ refIDREF#REQUIRED
>

spine _ end _ refIDREF#REQUIRED

part _ refIDREF#REQUIRED

voice _ refIDREF#REQUIRED

>
<!ELEMENTthm _ desc(#PCDATA)>
<!ELEMENTtranspositionEMPTY>
<!--
Intervalisanintegernumber,indicates
theintervaloftransposition
anditsinterpretationisrelatedtothetype
attribute.Whentypeisrealinterval
indicatesthedistanceinsemitones,oth-
erwise it indicates distance in tonal
scale.
-->
<!ATTLISTtransposition

Those quantities, which depend upon the
structural characteristics, are extremely useful to
deal with musical objects together with all their
possible transformations.

type(real|tonal)#REQUIRED

intervalCDATA#REQUIRED

>
<!ELEMENTinversionEMPTY>
<!--
Staffstepattributemusthavethesamein-
terpretationasthestaff _ step
attributeofnoteheads.
-->
<!ATTLISTinversion

example of a melodic sequence

In Figure 18 there is an example of an MX file and
it is possible to identify the general , structural,
and logic layers.
In the structural layer it is possible to identify
the subelement invariants and its subelements
order , size, and complexity .

type(real|tonal)#REQUIRED

staff _ stepCDATA#REQUIRED

>
<!ELEMENTretrogradationEMPTY>
<--
Invariantsarequantitiesthatrefertoa
themeanddonotvary
evenifthethemeistransformedbycanoni-
caltransformations

the archItecture of a mIr
sYstem

-->

<!ELEMENTtheme(invariants?)>
<!ELEMENTinvariants(order,size,complex-
ity)>
<!ELEMENTorder(#PCDATA)>
<!ELEMENTsize(#PCDATA)>
<!ELEMENTcomplexity(#PCDATA)>
<!--PetriNets-->
<!ELEMENTPNEMPTY>
<!ATTLISTPN

In this section we introduce the architecture of a
MIR system which exploits the MX language in
order to handle different formats of music data.
The most innovative features of this MIR

Figure 17. Example: Notational layer

ile _ nameCDATA#REQUIRED

>
<!--Segments-->
<!ATTLISTrelationship

idID#REQUIRED