[September 06, 2000] Several XML DTDs and XML-based authoring tools have been created for use within the Gemini Observatory Project.
The Gemini project "is a multi-national effort to build twin 8.1 meter astronomical telescopes utilizing new technology to produce some of the sharpest views of the universe ever. One telescope will be located atop Hawaii's Mauna Kea and the other atop Chile's Cerro Pachón - together they will provide complete unobstructed coverage of both the Northern and Southern skies. Gemini is an international partnership managed by the Association of Universities for Research in Astronomy under a cooperative agreement with the National Science Foundation."
The Phase1 DTD Distribution includes the main XML DTD and associated DTDs used in the current version of the Gemini Phase 1 Tool to generate Gemini Phase 1 proposals: (1) The 'AstronomyPhase1.dtd' provides the XML Document Type Declaration (DTD) that describes the set of proposals accepted by the Gemini Multi-Observatory Phase 1 Tool. By Kim Gillies, Shane Walker, and Darrell Denlinger (Gemini 8-m Telescopes Project). It allows multiple observatories to add their own information to a proposal while sharing common information. An instance of this DTD is required as part of submitting a proposal to the Gemini 8-m Telescopes Project. (2) The file 'AstronomyPhase1Data.xml' supports the common part of the Phase 1 proposal; included is the set of keywords and keyword categories, along with a list of sites/institutions. (3) The 'Gemini.dtd' file stores an XML DTD for the Gemini 8m Telescope extensions and constraints; it uses the information in the 'AstronomyPhase1.dtd'.
"Each proposal recommended for time is sent by the NTACs/NGOs to Gemini as an XML (eXtensible Markup Language) document consisting of attribute/value pairs that encode the proposal information (e.g. PI name, target co-ordinates, instrument resources, scientific case) and, if required, associated files with figures etc. The Gemini Phase I Tool (PIT) automatically generates the XML file. Partners who have chosen to use their own web-based or other proposal systems must translate their internal formats into the correct XML structures. The XML format is described in a document package and has been defined to be of generic use for observatories other than Gemini."
References:
Description of an XML-based Phase 1 Document. By Kim Gillies, Shane Walker, Darrell Denlinger, and Dayle Kotturi. Gemini High-Level Software Group Report. File: 'ocs.kkg.065-Phase1XMLDTD/05'. 36 pages. Created:September 24, 1998; Modified:September 16, 1999. "This report describes an XML based file format for sharing and processing Phase 1 telescope proposal information. The format was created for use with Gemini telescope proposals, but the authors have tried to make document format flexible and general, making it a good candidate for use at other observatories as well."
The Gemini Phase 1 Document. By Kim Gillies, Shane Walker, Darrell Denlinger, and Dayle Kotturi. Gemini High-Level Programming Group Report. File: 'ocs.kkg.066-GeminiPhase1Doc/03'. 26 pages. Created:September 24, 1998; Modified:September 16, 1999. "This report defines the XML document that Gemini expects to receive from the partner countries during Phase 1 of the telescope time allocation process."
AstronomyPhase1Data.dtd - Data file
XML DTD for the Gemini 8m Telescope extensions and constraints
GeminiData.xml An XML file of data that supports the creation of Gemini Proposals. It contains an example of a Gemini resource list, information about the scheduling period, and information that can be used by authoring tools. For a given semester, this file changes, so be sure and look at the GeminiData.xml file included with PIT for the semester in question."
Example - "A fully developed, valid, well-formed Gemini proposal. It obeys the Gemini DTD and Astronomyphase1 DTD and all external validity constraints. It is compatible with the DTDs in this package."
The Gemini Phase I Proposal Tool. "Each Gemini partner country runs its own Phase I proposal process and may use any mechanism for internal proposal submission and assessment. To ensure that all the National TAC-recommended proposals are transmitted to Gemini Observatory in a common format, XML (extensible markup language) has been adopted for encoding the proposal information. This is a powerful and flexible way of capturing the minimum essential information required by the National Gemini Offices (for their Phase I technical assessment), the National and International TACs (for scientific assessment and scheduling) and for subsequent ingestion into databases at Gemini Observatory (e.g., for Phase II detailed observation definition). The PIT automatically writes proposals in the correct XML format. It is not necessary for proposers to understand this file format but, for those who are interested, a description is available in a document package together with the XML DTD (document type definition) files."
