Organ Specifications in XML
This is a proposal for a standard format for storing and transmitting organ specifications. There are a number of on-line repositories of organ specifications, including Osiris and the IOF. Each one uses a different format for storing specs, none of which are well optimized for advanced searching or data analysis, often being simply semi-formatted or unformatted text files. This proposed standard will make it feasible to perform data analysis on a level heretofore unattainable.
This effort grew out of the development of the Encyclopedia of Organ Stops. Research for that project included trying to answer questions like:
Tools were built for searching the existing archives, but the relatively unformatted nature of the data necessitated a considerable amount of hand-sifting through data. A better data format would have made these questions, and others, answerable simply by issuing the right database query. The use of such statistics can be used in many areas of organ research.
XML has emerged as a universal meta-format that is well suited for this task, and for which a large body of software exists. Therefore, this proposed standard is based on XML, and consists mainly of an XML DTD (Document Type Definition) and guidelines for its use. An XML Schema is also under development. More information on XML may be found at http://www.w3.org/XML.
Complete documentation on the OrganSpec XML standard may be found here:The Complete Specification (frames version)
The Complete Specification (no frames)
Downloadable Complete Specification (zipped archive, 91k)
Version 0.1 - archive of the original version 0.1 spec, now obsolete.
Software to support the OrganSpec standard is under development. The following software is available:
C# .Net Class Library - a class library for reading and writing OrganSpec files.
OrganSpecEdit - a Microsoft Windows .Net application for creating, editing and viewing OrganSpec files.
Java Class Library - a class library for reading and writing OrganSpec files.
Other tools under development include:
Please send any comments, corrections or suggestions to:
Ed Stauff -Please remove the "SPAM_SUX" spamguard before sending to this address.