Chapter 1: Introduction
The DITA 1.2 specification consists of the following components:
- Document Type Definitions (DTDs) and XML Schemas (XSDs)
- The DTDs and XSDs – along with the catalog files – define DITA markup for the DITA vocabulary modules and DITA document types. While the DTDs and XSDs should define the same DITA elements, the DTDs are normative if there is a discrepancy. If there is a discrepancy between the written specification (this document) and the DTDs, the written specification takes precedence.
- DITA 1.2 written specification
While the DITA 1.2 documentation does contain some introductory information, it is intended neither as an introduction to DITA nor as a users guide. The intended audience of this documentation consists of implementers of the DITA standard, including tool developers and XML architects who develop specializations. The documentation contains several parts:
- Architectural specification
- Language reference
- Conformance statement
The DITA 1.2 written specification is available in the following formats: XHTML, CHM, PDF, and DITA source. The XHTML version is authoritative.
- This word, or the terms "required" or "shall", mean that the definition is an absolute requirement of the specification.
- must not
- This phrase, or the phrase "shall not", means that the definition is an absolute prohibition of the specification.
- This word, or the adjective "recommended", means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
- should not
- This phrase, or the phrase "not recommended", means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
- This word, or the adjective "optional", means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option must be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option must be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides).
1.1.2: Normative references
- [Namespaces in XML 1.0]
- T. Bray, D. Hollander, A. Layman, R. Tobin, and H. S. Thompson, editors, Namespaces in XML 1.0 (Third Edition), http://www.w3.org/TR/2009/REC-xml-names-20091208/, W3C Recommendation, 8 December 2009.
- [Namespaces in XML 1.1]
- T. Bray, D. Hollander, A. Layman, and R. Tobin, editors, Namespaces in XML 1.1 (Second Edition), http://www.w3.org/TR/2006/REC-xml-names11-20060816/, W3C Recommendation, 16 August 2006
- [RFC 2119]
- S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.
- [RFC 3986]
- T. Berners-Lee, R. Fielding, and L. Masinter, Uniform Resource Identifiers (URI): Generic Syntax, http://tools.ietf.org/html/rfc3986, IETF RFC 3986, January 2005.
- [XML 1.0]
- T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, editors, Extensible Markup Language (XML) 1.0 (Fifth Edition), http://www.w3.org/TR/REC-xml/, W3C Recommendation, 26 November 2008.
- [XML 1.1]
- T. Bray, J. Paoli, C.M. Sperberg-McQueen, E. Maler, F.Yergeau, and J. Cowan, editors, Extensible Markup Language (XML) 1.1 (Second Edition),http://www.w3.org/TR/2006/REC-xml11-20060816/, W3C Recommendation, 16 August 2006, edited in place 29 September 2006.
- [XSD 1.0 Structures]
- H. S. Thompson, D. Beech, M. Maloney, and N. Mendelsohn, editors, XML Schema Part 1: Structures Second Edition, http://www.w3.org/TR/xmlschema-1/, W3C Recommendation, 28 October 2004.
- [XSD 1.0 Datatypes]
- P. V. Biron and A. Malhotra, editors, XML Schema Part 2: Datatypes Second Edition, http://www.w3.org/TR/xmlschema-2/, W3C Recommendation, 28 October 2004.
1.1.3: Non-normative references
- IMS-QTI (Kimber)
- Information mapping (Nevin)
- SGML (Nevin) -- no ISO spec available without charge
- Standards reflected in Machine Industry specializations (Kimber)
- XNAL (Kimber)
- [CSS 2.1]
- B. Bos, T. Çelik, I. Hickson, and H.W. Lie, editors, Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification, http://www.w3.org/TR/CSS2/, W3C Candidate Recommendation, 08 September 2009.
- [XHTML 1.0]
- W3C HTML Working Group, XHTML 1.0 The Extensible HyperText Markup Language (Second Edition): A Reformulation of HTML 4 in XML 1.0, http://www.w3.org/TR/xhtml1/, W3C Recommendation, 26 January 2000, revised 1 August 2002.
- [XHTML 1.1]
- M. Altheim and S. McCarron, editors, XHTML 1.1 - Module-based XHTML, http://www.w3.org/TR/xhtml11/, W3C Recommendation, 31 May 2001.
- [XPointer 1.0]
- S. DeRose, E. Maler, and R. Daniel Jr., editors, XML Pointer Language (XPointer) Version 1.0, http://www.w3.org/TR/WD-xptr, W3C Last Call Working Draft, 8 January 2001.
- [XLIFF 1.2]
- OASIS Standard, XLIFF Version 1.2, 1 February 2008, http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html.
- [xml:tm 1.0]
- A. Zydroń, R. Raya, and B. Bogacki, editors, XML Text Memory (xml:tm) 1.0 Specification, http://www.lisa.org/fileadmin/standards/xml-tm.html, The Localization Industry Standards Association (LISA) xml:tm 1.0, 26 February 2007.
- [XQuery 1.0]
- S. Boag, D. Chamberlin, M. F. Fernández, D. Florescu, J. Robie, and J. Siméon, editors, XQuery 1.0: An XML Query Language, http://www.w3.org/TR/xquery/, W3C Recommendation, 23 January 2007.
- [XSL 1.0]
- S. Adler, A. Berglund, J. Caruso, S. Deach, T. Graham, P. Grosso, E. Gutentag, A. Milowski, S. Parnell, J. Richman, and S. Zilles, Extensible Stylesheet Language (XSL) Version 1.0, http://www.w3.org/TR/2001/REC-xsl-20011015/, W3C Recommendation, 15 October 2001.
- [XSL 1.1]
- A. Berglund, editor, Extensible Stylesheet Language (XSL) Version 1.1, http://www.w3.org/TR/xsl11/, W3C Recommendation, 05 December 2006
- [XSLT 1.0]
- J. Clark, editor, XSL Transformations (XSLT) Version 1.0, http://www.w3.org/TR/xslt, W3C Recommendation, 16 November 1999
- [XSLT 2.0]
- M. Kay, editor, XSL Transformations (XSLT) Version 2.0, http://www.w3.org/TR/xslt20/, W3C Recommendation, 23 January 2007
- [XTM 1.0]
- S. Pepper and G. Moore, editors, XML Topic Maps (XTM) 1.0, http://www.topicmaps.org/xtm/index.html, TopicMaps.Org XTM 1.0, 2001.
1.1.4: Formatting conventions in the XHTML version of the specification
The DITA 1.2 specification uses the content of the unique DITA <shortdesc> element to provide link previews for its readers. These link previews are visually highlighted by a border and a colored background. The link previews are not normative; they contain the content of the <shortdesc> element for the child topic, which is normatively rendered as the first paragraph of the child topic; the content is identical in both renditions. The link previews serve as enhanced navigation aids, enabling readers to more easily locate content. This usability enhancement is one of the ways in which the specification illustrates the capabilities of DITA and exemplifies DITA best practices.
The following screen capture illustrates how link previews are displayed in the XHTML version of the specification:
To ease readers in navigating from one topic to another, each XHTML file generated by a DITA topic contains the following navigation links at the bottom:
- Parent topic
- Takes readers to the parent topic, which the topic referenced by the closest topic in the containment hierarchy
- Previous topic
- Takes readers to the previous topic in the reading sequence
- Next topic
- Takes readers to the next topic in the reading sequence
- Return to main page
- Takes readers to the place in the table of contents for the current topic in the reading sequence
The following screen capture illustrates how navigation links are displayed in the XHTML version of the specification: