1、IEEE Std 1599-2008IEEE Recommended Practice forDefining a Commonly AcceptableMusical Application Using XML IEEE3 Park Avenue New York, NY 10016-5997, USA26 September 2008IEEE Computer SocietySponsored by theStandards Activities Board1599TMIEEE Std 1599-2008 IEEE Recommended Practice for Defining a C
2、ommonly Acceptable Musical Application Using XML Sponsor Standards Activities Board of the IEEE Computer Society Approved 12 June 2008 IEEE-SA Standards Board IEEE 1599 DTD reprinted with permission from Prof. Goffredo Haus 2008. Abstract: This recommended practice develops an XML application defini
3、ng a standard language for symbolic music representation. The language is a meta-representation of music information for describing and processing said music information within a multi-layered environment, for achieving integration among structural, score, Musical Instrument Digital Interface (MIDI)
4、, and digital sound levels of representation. Furthermore, the recommended practice integrates music representation with already defined and accepted common standards. This recommended practice will be accepted by any kind of software dealing with music information, e.g., score editing, optical musi
5、c recognition (OMR) systems, music performance, musical databases, and composition and musicological applications. Keywords: description, multimedia, music, synchronization, XML The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2008 by
6、the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 26 September 2008. Printed in the United States of America. IEEE and POSIX are registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educatio
7、nal classroom use can also be obtained through the Copyright Clearance Center. iv Copyright 2008 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std 1599-2008, IEEE Recommended Practice for Defining a Commonly Acceptable Musical Application Using XML. This introduction
8、provides some background on the rationale used to develop this recommended practice. It is meant to aid in the understanding and usage of this document. This recommended practice can be considered a first collective step toward the improvement of both sub-symbolic and symbolic music coding and proce
9、ssing, music communication, and capabilities of individuals and companies in the following areas: Music processing and delivering, at multiple levels of representation Modeling for music analysis and synthesis Definition and implementations of tools for automatic music understanding, for composing a
10、nd for performing music, for music browsing on the Web Topics of major interest for the definition of this proposal are as follows: Realization of tools, test, demonstrations Support of existing applications and formats Semantics of music notation, compatibility with Common Western Notation (CWN) Gr
11、aphical notation, representation, interleaving for real-time interaction Orientation to networks Integration of symbolic notation, audio, visual, metadata, representation Possibility of splitting: fragmentation, segmentation Orientation to musicology and/or performances Brief history of this project
12、 and relationship to the Intelligent Manufacturing Systems financial support The Project Authorization Request (PAR) to define a new recommended practice was submitted to the IEEE Computer Society (CS) Standards Activity Board (SAB) and accepted in September 2001. The abstract was submitted to the I
13、ntelligent Manufacturing Systems (IMS) secretariats and accepted in August 2002 (second version). IMS is a global fund consisting of seven regions: U.S., Canada, Australia, Japan, Korea, Switzerland, and the European Union. A project must have partners from at least three different regions and must
14、be accepted by all secretariats.aThe IEEE Conference MAX 2002: Musical Applications Using XML took place in Milan, Italy, on September 1920, 2002, organized by the IEEE CS Working Group of P1599.bDuring development, MX was the internal code for the project that became IEEE Std 1599 (see 1.5). Variou
15、s meetings of the IEEE CS SAB were attended from 2002 through 2006. Slides were presented regarding the progress of the project at every meeting. Denis Baggi, Working Group Chair and one of the authors of this recommended practice, became a member of the SAB, functioning as liaison to the aSee the I
16、MS Web site: http:/www.ims.org. bThe P before 1599 indicates an IEEE authorized standards project that was not approved by the IEEE-SA Standards Board at the time the Working Group was formed. v Copyright 2008 IEEE. All rights reserved. Technical Activity Board (TAB), of which he was already a membe
17、r. The IEEE CS put an additional Web page for the project on its site, which was linked to the IMS Web page. The proposal for a feasibility study, “Music XML Lite,” was accepted by the Swiss IMS Secretariat, and the project ran from February through November of 2004. This included a trip to the U.S.
18、, Australia, and Japan to meet potential project partners. An intermediate report was delivered in September 2004 that outlined the past, present, and future of the project. Various talks were given and leaflets distributed about the project, e.g., at the IMS Forum in Cernobbio, Italy, on May 14, 20
19、04. In particular, two talks were given at an IMS meeting in Gold Coast, Australia, on November 9, 2004. IMS endorsed the project in 2006, and the Commission for Technological Innovation of the Department of Public Economy of the Swiss Federal Government accepted a proposal for financing in 2006. Th
20、e project consisted of completion of the standard definition as well as realizing applications for the Radio Televisione della Svizzera Italianacand for the jazz festival Jazz AsconaNew Orleans and Classics,dincluding its sponsored programs to help the victims of the Katrina hurricane. Notice to use
21、rs Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the app
22、licable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variet
23、y of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private user
24、s, the IEEE does not waive any rights in copyright to this document. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigend
25、a, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance
26、of amendments, corrigenda, or errata, visit the IEEE Standards Association Web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEE
27、E-SA Web site at http:/standards.ieee.org. cSee the RTSI Web site: http:/www.rtsi.ch. dSee http:/ vi Copyright 2008 IEEE. All rights reserved. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/updates/errata/index.html
28、. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at the following URL:http:/standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called to the possibility that implementation of this recommended practice may
29、 require use of subject matter covered by patent rights. By publication of this recommended practice, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE is not responsible for identifying Essential Patent Claims for which a license m
30、ay be required, for conducting inquiries into the legal validity or scope of Patents Claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of
31、this recommended practice are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Participants At the time this recommend
32、ed practice was submitted to the IEEE-SA Standards Board for approval, the IEEE P1599 Working Group had the following membership: Denis L. Baggi, Chair Goffredo Haus, Official Reporter Antonello DAguanno Adriano Barat Lazlo Belady Michael Cohen Loretta Diana Federico Flueckiger Tosiyasu L. Kunii Mau
33、rizio Longari Luca A. Ludovico Damian McGuckin Tony Milosz Kalpdrum Passi Alberto Pinto Perry Roland Elisa Russo Donald Sloan Lorenzo Sommaruga Paolo Tagliolato Giancarlo Vercellesi Working Group members who contributed in the past include the following: Liz Armstrong Jrme Barthlmy France Champagne
34、Gustavo Frederico Michael Good Charl Jeannot Markus Lepper Yashuo Mishiro Marco Mattavelli Dan Nagy Jacques Steyn Tony Strasser Guy Tremblay Ruo-hua Zhou Giorgio Zoia vii Copyright 2008 IEEE. All rights reserved. The following members of the individual balloting committee voted on this recommended p
35、ractice. Balloters may have voted for approval, disapproval, or abstention. Juan Carreon James Case Clint Chaplin Keith Chow John Cole Tommy Cooper Thomas Dineen Paul Eastman Thomas Gauntner Michael Geipel Randall Groves Werner Hoelzl Mark Jaeger Piotr Karocki Mark Knight Susan Land William Lumpkins
36、 Gary Michel Michael S. Newman Charles Ngethe Jose Puthenkulam Bartien Sayogo Richard Schrenker David J. Schultz John Sheppard John Vergis P. Wolfgang Oren Yuen When the IEEE-SA Standards Board approved this recommended practice on 12 June 2008, it had the following membership: Robert M. Grow, Chair
37、 Thomas Prevost, Vice Chair Steve M. Mills, Past Chair Judith Gorman, Secretary Victor Berman Richard DeBlasio Andy Drozd Mark Epstein Alexander Gelman William R. Goldbach Arnold M. Greenspan Kenneth S. Hanus Jim Hughes Richard H. Hulett Young Kyun Kim Joseph L. Koepfinger* John Kulick David J. Law
38、Glenn Parsons Ronald C. Petersen Chuck Powers Narayanan Ramachandran Jon Walter Rosdahl Anne-Marie Sahazizian Malcolm V. Thaden Howard L. Wolfman Don Wright *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Satish K. Aggarwal, NRC Representative Michael H.
39、Kelley, NIST Representative Malia Zaman IEEE Standards Program Manager, Document Development Lorraine Patsco IEEE Standards Program Manager, Technical Program Development viii Copyright 2008 IEEE. All rights reserved. Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 1.3 Benefits 2 1.4 Official Web
40、 site 2 1.5 Registration object. 2 2. Normative references 2 3. Acronyms and abbreviations 2 4. Conventions 3 5. Representation of music information through XML 3 6. IEEE 1599 layers 4 6.1 General 6 6.2 Logic 11 6.3 Structural . 73 6.4 Notational 79 6.5 Performance. 82 6.6 Audio . 89 Annex A (inform
41、ative) Bibliography . 93 Annex B (informative) IEEE 1599 DTD 94 Annex C (informative) Running applications to demonstrate IEEE 1599 110 1 Copyright 2008 IEEE. All rights reserved. IEEE Recommended Practice for Defining a Commonly Acceptable Musical Application Using XML IMPORTANT NOTICE: This standa
42、rd is not intended to assure safety, security, health, or environmental protection in all circumstances. Implementers of the standard are responsible for determining appropriate safety, security, environmental, and health practices or regulatory requirements. This IEEE document is made available for
43、 use subject to important notices and legal disclaimers. These notices and disclaimers appear in all publications containing this document and may be found under the heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from
44、 IEEE or viewed at http:/standards.ieee.org/IPR/ disclaimers.html. 1. Overview 1.1 Scope This recommended practice will develop an XML application defining a standard language for symbolic music representation. The language will be a meta-representation of music information for describing and proces
45、sing said music information within a multi-layered environment, for achieving integration among structural, score, Musical Instrument Digital Interface (MIDI), and digital sound levels of representation. Furthermore, the recommended practice should integrate music representation with already defined
46、 and accepted common standards. The recommended practice will be accepted by any kind of software dealing with music information, e.g., score editing, optical music recognition (OMR) systems, music performance, musical databases, and composition and musicological applications. 1.2 Purpose There is c
47、urrently no defined, independent standard for representing music information that can describe and process all the different layers that characterize music information. For each layer of music information, there is one or more accepted standard e.g., MIDI for performances, Notation Interchange File
48、Format (NIFF) for notation, and so on and/or one or more proprietary formats. None of these can be suitably applied to other layers. This recommended practice will make easier the integration, interchange, and translation from one layer to another of music information across different applications a
49、nd even for different users. IEEE Std 1599-2008 IEEE Recommended Practice for Defining a Commonly Acceptable Musical Application Using XML 2 Copyright 2008 IEEE. All rights reserved. 1.3 Benefits There are many advantages in this recommended practice. Musicians could benefit because they would be able to handle each representation of a music piece as a unique entityfor example, by simultaneously watching a score and listening to the music of a particular audio recording. Music analysts would have the complete con