Notes on Samples for XML Authority
Welcome
Thank you for your interest in XML Authoritytm, the most comprehensive XML schema authoring and conversion tool available. We are committed to your success with XML and schemas. If we can do a better job please let us know.
The following Samples are provided so that you can immediately use XML Authority on authentic DTD files. Each section lists a directory or file name and description, followed by a description of the DTD itself.
CML.DTD
Chemical Markup Language - This DTD is fully described in Journal of Chemical Information and Computer Science.
DDML.DTD
A means for XML developers to describe their XML document structures using XML document syntax.
opentag.dtd
OpenTag Format Specifications (http://www.opentag.org/otspecs.htm).
quicktour.dtd
DTD used in Quicktour.
xbel-1.0.dtd
XML Bookmarks Exchange Language, version 1.0.
Handy Entities
Useful entity definitions (Latin and other Unicode characters and symbols). XMLlat1, XMLspecial, and XMLsymbol DTDs.
Import-ables
Sample import files.
AML - Astronomical Markup Language
"We are currently defining a new XML language called AML, 'Astronomical Markup Language', aimed at being a standard exchange format for metadata in astronomy. AML now supports the following objects (in the object-oriented sense): astronomical object, article, table, set of tables, image, person. This means that all these objects can be described with the same language, allowing easier establishing of links between them, and the creation of programs handling all these objects with the same user interface. The following databases can already be queried in AML: Simbad, NED, ADS, and the Benn&Martin people database. A java AML browser can be used to retrieve AML documents and browse them with a common user interface. The creation of this language is a prerequisite for further work on information retrieval in astronomy, and it will allow the use of the same information by both humans and intelligent agents: the intelligent agents can use AML with an XML parser, while a browser for AML documents will be used to create an associated user interface." See: http://www.infm.ulst.ac.uk/~damien/these/AML.dtd
CIM
The industry organization Distributed Management Task Force, Inc. (DMTF) is developing CIM as "a conceptual information model for describing management that is not bound to a particular implementation. This allows for the interchange of management information between management systems and applications. This can be either 'agent to manager' and 'manager to manager' communications which provides for Distributed System Management. There are two parts to CIM: The CIM Specification and the CIM Schema. The CIM Specification describes the language, naming, Meta Schema and mapping techniques to other management models such as SNMP MIBs, and DMTF MIFs etc. The Meta Schema is a formal definition of the model. It defines the terms used to express the model and their usage and semantics. The elements of the Meta Schema are Classes, Properties, and Methods. The Meta Schema also supports Indications and Associations as types of Classes and References as types of Properties. The CIM Schema provides the actual model descriptions. The CIM Schema supplies a set of classes with properties and associations that provide a well-understood conceptual framework within which it is possible to organize the available information about the managed environment." [from the FAQ at http://www.dmtf.org/cim/cim_xml/]
DocBk-Simple
For more information on DocBook and Simplified DocBook see: http://www.oasis-open.org/cover/xml.html#docBook
GCAPapers - Graphic Communications Association - GCA 'Paper' DTD
For several years, the Graphic Communications Association (GCA) has requested (or required) that papers for GCA conferences be prepared according to guidelines in SGML/XML DTDs. Conference proceedings volumes, both paper and electronic, are generated from the SGML/XML source provided by the authors.
GedML
GedML is "a way of encoding genealogical data sets in XML. It combines the well-established GEDCOM data model with the new XML standard for encoding complex information. The result is a representation that can easily be converted to and from GEDCOM, but can be manipulated much more easily using standard tools."
iCalendar
"The iCalendar XML DTD" is described in an IETF Network Working Group Internet Draft (draft-dawson-ical-xml-dtd-01.txt), written by Frank Dawson of Lotus. The memo "defines a XML Document Type Definition (DTD) that corresponds to the iCalendar, calendaring and scheduling core object format defined by RFC 2445. This DTD provides equivalent functionality to the standard format defined by RFC 2445. Documents structured in accordance with this DTD may also be know as 'XML iCalendar' documents. . .The iCalendar DTD promotes a number of iCalendar properties into attributes on the 'iCal' element. This has been done to express these properties as 'global attributes' for the iCalendar object, as a whole. For example, the CALSCALE, METHOD, VERSION and PRODID properties have been 'mapped' into attributes on the iCalendar object."
ICE - Information and Content Exchange
"The Information and Content Exchange protocol is for use by content syndicators and their subscribers. The ICE protocol defines the roles and responsibilities of syndicators and subscribers, defines the format and method of content exchange, and provides support for management and control of syndication relationships. We expect ICE to be useful in automating content exchange and reuse, both in traditional publishing contexts and in business-to-business relationships. ICE is built as an application of XML, and also makes use of HTTP. ICE can leverage a number of other emerging W3C efforts." The ICE authoring team "has identified two areas of special interest for future work: 1) How to define a constraints mechanism that will meet the needs of ICE and possibly leverage other emerging W3C schema efforts such as XML-Data, DCD, XSchema, etc.; 2) How to define a usage data model that will allow businesses to exchange information about how the syndicated content is being used." See also the announcement and W3C Staff Comment. Communiques regarding the submission may be directed to Brad Husick (Vignette). See http://www.w3.org/TR/1998/NOTE-ice-19981026 for more information.
PIF-XML - Process Interchange Format XML
On June 12, 1998, Jeffrey Ricker posted an announcement for an initial design of PIF-XML (Process Interchange Format XML). PIF is "an interchange format designed to help automatically exchange process descriptions among a wide variety of business process modeling and support system such as workflow software, flow charting tools, process simulation systems, and process repositories." PIF itself "is based on the Knowledge Interchange Format (KIF), which is in turn based on LiSP. Since both LiSP and XML are text-based and nested trees, the translation is relatively straightforward. However, PIF also includes an object-oriented design with inheritance, which does not directly translate into XML." The initial work attempts a direct translation of PIF version 1.2, and is not optimized for economy in XML; a provisional DTD and example encoded PIF-XML document are available.
RFCs
Writing I-Ds and RFCs using XML was published as an IETF Network Working Group Internet-Draft (draft-mrose-writing-rfcs-00.txt) in the 'informational' category. Date: February 1999, Expires: August 02, 1999. The author is Marshall T. Rose (Invisible Worlds, Inc.). The memo "describes how to write a document for the I-D and RFC series using the Extensible Markup Language (XML). The memo has three goals: 1) To describe a simple XML Document Type Definition (DTD) that is powerful enough to handle the simple formatting requirements of RFC-like documents whilst allowing for meaningful markup of descriptive qualities.; 2) To describe software that processes XML source files, including a tool that produces documents conforming to RFC 2223, HTML format, and so on.; 3) To provide the proof-of-concept for the first two goals (this memo was written using this DTD and produced using that software)."
SMIL
The Synchronized Multimedia Integration Language (SMIL, pronounced 'smile'). SMIL allows integrating a set of independent multimedia objects into a synchronized multimedia presentation. Using SMIL, presentations such as a slide show synchronized with audio comments or a video synchronized with a text stream can be described [. . .] SMIL documents are well-formed XML documents in the sense of the XML 1.0 draft. For describing the syntax of SMILE documents, this specification uses two notations: (1) an augmented Backus-Naur form (BNF) similar to the one defined for HTTP 1.1, and (2) an XML Document Type Definition (DTD)."
TMX - Translation Memory eXchange
"The purpose of the TMX format is to provide a standard method to describe translation memory data that is being exchanged among tools and/or translation vendors, while introducing little or no loss of critical data during the process. TMX is XML-compliant. It also uses various ISO standards for date/time, language codes, and country codes." OSCAR (Open Standards for Container/Content Allowing Re-use) is the LISA Special Interest Group responsible for the definition of TMX.