|
|
| Line 1: |
Line 1: |
| − |
| |
| | == Agenda == | | == Agenda == |
| | | | |
| Line 11: |
Line 10: |
| | == Meetings == | | == Meetings == |
| | | | |
| | + | * [[SIG:Music:Meeting2008|Rreport of meeting: Zadar, Croatia, 12 November 2010]] |
| | + | * [[SIG:Music:Meeting2008|Report of business meeting: Ann Arbor, 14 November 2009]] |
| | + | * [[SIG:Music:Meeting2008|Agenda and report of first meeting: London, 8 November 2008]] |
| | | | |
| − |
| |
| − |
| |
| − | === Business Meeting November 14, 2009, Ann Arbor ===
| |
| − |
| |
| − | The business meeting will take place in the Library Information Technology conference room (room 300, Hatcher Graduate Library North) from 10 a.m. to 12 p.m on saturday, November 14. See http://www.lib.umich.edu/spo/teimeeting09/program.html for the conference program.
| |
| − |
| |
| − | '''Report of the meeting'''
| |
| − |
| |
| − | The focus of this year's meeting was on reporting the aims and the status of ongoing work. In addition to this meeting, these were also topics of informal talks throughout the entire conference.
| |
| − |
| |
| − | The SIG's decision to focus on MEI first led to discussion of the current status of the "ODDification" of MEI and the related question of how to combine MEI and TEI. Whether to subsume MEI into TEI, keep them separate, or adopt a process somewhere between these poles remains an open question. This question was discussed not only in a technical sense of how to combine the schemas and namespaces, but also on a political level with regard to how both the text and music
| |
| − | markup communities can mutually benefit.
| |
| − |
| |
| − | A first step towards documentation of MEI is in progress, too. As part of the DFG/NEH-funded project "Digital Music Notation Data Model and Prototype Delivery System", a list of problems concerning the encoding of music notation alone as well as in combination with text is currently under discussion. Potential solutions to these problems will be documented and illustrative examples will be encoded, which will be helpful for the SIG's work.
| |
| − |
| |
| − | Finally, a significant announcement was made at the meeting. As a sub-part of the German TextGrid project, a music notation editor will be developed. While in-depth TEI support is not on the agenda of this effort, the software's underlaying data format will be MEI, so that hopefully the possibility to create, edit, and display MEI-encoded music will come to fruition soon.
| |
| − |
| |
| − |
| |
| − | === Initial Meeting November 8, 2008, London ===
| |
| − |
| |
| − | '''13/11/2008 - TEI Music SIG: meeting November 8, 2008, London'''
| |
| − |
| |
| − | The first meeting of the Special Interest Group in Music has been held on the 8th of November 2008 within the TEI Members Meeting at King's College London.
| |
| − |
| |
| − | During the meeting, the major pre-existing XML-based encoding formats for music notation have been considered. This includes
| |
| − |
| |
| − | * MEI[http://www.lib.virginia.edu/digital/resndev/mei/], which is currently developed by Perry Roland at the University of Virginia
| |
| − | * MusicXML[http://www.musicxml.org/], which is developed by Recordare LLC (Michael Good)
| |
| − | * MPEG-4 part 23[http://www.interactivemusicnetwork.org/mpeg-ahg/], which was formerly known as Wedelmusic.
| |
| − |
| |
| − |
| |
| − | The SIG will concentrate on MEI first, as it is designed for critical music editions. This decision does not exclude the other formats from further evaluations.
| |
| − |
| |
| − |
| |
| − | '''Long-term agenda:'''
| |
| − |
| |
| − | The SIG has to provide recommendations and examples for the integration of music encoding within TEI. This will start with music examples in Common Western Notation, but shall be extended to other notations as much as possible.
| |
| − |
| |
| − |
| |
| − | The question of integration v collaboration of MEI and TEI was left open until further evaluations: it is not yet sure if the (digital-)musicological community (which is not as large as the TEI community) will accept to definitively incorporate MEI into TEI. This political question will be addressed later.
| |
| − |
| |
| − |
| |
| − | In the long term the SIG will work on determining the actual similarity of the header parts and the textCrit / meiCrit modules.
| |
| − | It would be desirable to allow TEI encodings in a MEI document (at appropriate locations) and vice versa.
| |
| − |
| |
| − | For example, a musical document with text considered worth to be encoded in TEI could be represented as a MEI document with TEI inclusions,
| |
| − |
| |
| − | or it could be represented within TEI, where the <teiHeader> is mandatory and the MEI element <mei:work> could substitute or go alongside with <text> and/or <facsimile>.
| |
| − |
| |
| − | On the other hand, mainly textual document with music embedded could make use of the latter example.
| |
| − |
| |
| − | On order to reach this interoperability, the technical improvement of MEI is a first objective to be reached .
| |
| − |
| |
| − |
| |
| − | For all of these tasks, Johannes Kepper suggested that the SIG might cooperate with the research project called Digital Music Notation Data Model and Prototype Delivery System (conducted by Roland and Kepper). This project will translate MEI from a one-man-show to a community-based project, and will discuss the political issues concerned with the collaboration / integration with TEI.
| |
| − |
| |
| − |
| |
| − | MEI will have to consider to refer in its documentation to the authority lists and controlled values defined by the MPEG4.23 standard wherever appropriate. This has no consequences on the concepts and model of MEI, but helps to standardize the interpretation of certain basic symbols and elements.
| |
| − | For the MPEG4.23 standard documentation please refer to: http://www.interactivemusicnetwork.org/mpeg-ahg/w8632-MPEG-SMR-part-23-rev-public.pdf
| |
| − |
| |
| − |
| |
| − | Furthermore, the development of tools for WYSIWYG generation and dynamic rendering of MEI should be supported by the SIG as much as possible.
| |
| − |
| |
| − |
| |
| − | '''Short-term agenda - first steps:'''
| |
| − |
| |
| − | For the further discussion about MEI's independence it is important to compare the headers. A first question to be addressed is: "is it possible for MEI to use an extended TEI header?"
| |
| − |
| |
| − | A first attempt to answer that question might be to "oddify" MEI, as this allows an easier comparison of individual parts. At the same time, it allows the generation of different schemas as well as DTDs.
| |
| − |
| |
| − | At the same time, the primitive objects and values of MEI shall be compared to their equivalents (if existing) in the MPEG standard.
| |
| − |
| |
| − |
| |
| − | '''16/10/2008 - Agenda for the SIG meeting: London 8th of November 2008.'''
| |
| − |
| |
| − | *2.00 – 2.30: Open discussion (setting SIG agenda)
| |
| − | **music notation as text and music notation in relation with “extra-musical” text
| |
| − | **harmonization of core TEI and music. I.e. using TEI elements for text in the musical notation
| |
| − | **aural common elements between different notation systems
| |
| − | **musical text v layout
| |
| − | **musical text / performance (the case of IEEE 1599)
| |
| − |
| |
| − | *2.30 – 3.00: Open discussion (setting SIG agenda)
| |
| − | **new encoding model or namespace recommendation?
| |
| − | **MusicXML, MEI, IEEE 1599, others
| |
| − | **publishing: what are the possibilities at the moment?
| |
| − |
| |
| − | *3.00 – 3.30: Workshop/Brainstorming
| |
| − | **Perhaps work together on an example
| |
| − | **Defining long-term work of the group
| |
| | | | |
| | | | |
