Home
Language reference: All-inclusive edition
The language reference portion of the DITA specification contains a topic for each DITA element. The topic defines the element, its inheritance hierarchy, and provides examples of usage. This portion of the DITA specification also includes information about DITA attributes.
Domain elements
General purpose domains are not specific to any type of information, such as the hazard statement domain that provides elements for describing hazardous situations.
Utilities elements
The utilities domain elements represent common features of a language that might not necessarily be semantic, such as image maps.
<coords>
The <coords> element specifies the coordinates of a linkable region in an <imagemap>.

Specification URIs
Notices
Introduction to DITA 1.3
The Darwin Information Typing Architecture (DITA) specification defines a set of document types for authoring and organizing topic-oriented information, as well as a set of mechanisms for combining, extending, and constraining document types.
Architectural specification: All-inclusive edition
The architectural specification portion of the DITA specification outlines the framework of DITA. It contains an overview of DITA markup; addressing; processing; configuration, specialization, generalization, and constraints; as well as information about coding DITA grammar files.
Language reference: All-inclusive edition
The language reference portion of the DITA specification contains a topic for each DITA element. The topic defines the element, its inheritance hierarchy, and provides examples of usage. This portion of the DITA specification also includes information about DITA attributes.
- Element quick reference
  This section contains a listing of DITA elements.
- Topic elements
  The base topic elements include elements that make up the core building blocks of the DITA topic, such as topic, body, and related-links, as well as elements like <p> and <ph> that are used in many topic specializations. Some of these elements are also available inside the <topicmeta> map element.
- Map elements
  Map elements include the core components of DITA maps, such as <topicref> and <reltable>, as well as general purpose map specializations in the map group domain.
- Metadata elements
  Metadata elements include information that is located within the <topicmeta> element (in maps) or <prolog> element (in topics), as well as indexing elements that can be placed in additional locations within topic content.
- Domain elements
  General purpose domains are not specific to any type of information, such as the hazard statement domain that provides elements for describing hazardous situations.
  - Hazard statement elements
    The hazard statement domain elements are used to provide information about product safety hazards. The domain can be included in any topic type or map. Its elements are used to inform readers about potential hazards, consequences, and avoidance strategies.
  - Highlighting elements
    The highlighting elements are used to highlight text with styles (such as bold, italic, and monospace). Never use these elements when a semantically specific element is available. These elements are not intended for use by specializers, and are intended solely for use by authors when no semantically appropriate element is available and a formatting effect is required.
  - Utilities elements
    The utilities domain elements represent common features of a language that might not necessarily be semantic, such as image maps.
    - <area>
      The <area> element describes a linkable area within an <imagemap>. It allows the author to specify a shape within the image, the coordinates of that shape, and a link target for the area.
    - <coords>
      The <coords> element specifies the coordinates of a linkable region in an <imagemap>.
    - <imagemap>
      The <imagemap> element supports the basic functionality of the HTML "client-side" image map markup. <imagemap> allows you to designate a linkable area or region over an image, allowing a link in that region to display another topic.
    - <shape>
      The <shape> element defines the shape of a linkable area in an <imagemap>.
    - <sort-as>
      For elements that are sorted, the <sort-as> element provides text that is combined with the base sort phrase to construct the effective sort phrase. The text can be specified in the content of the <sort-as> element or in the @value attribute on the <sort-as> element. The <sort-as> element is useful for elements where the base sort phrase is inadequate or non-existent, for example, a glossary entry for a Japanese Kanji phrase.
  - DITAVAL reference domain
    The DITAVAL reference domain is used to reference a DITAVAL file that contains conditions that apply only to a subset of a DITA map. It also can be used to replicate a subset of a DITA map for multiple audiences.
- Classification elements
  Classification elements support managing metadata. Those in the subject scheme map are used to define controlled values and to bind the controlled values to DITA attributes as enumerations. Those declared in the classification domain are used in other maps to classify content according to the scheme.
- Specialization elements
  Several DITA elements exist either for architectural reasons or for support of specialized markup yet to be designed. Although there is little need to use these elements unless you are directed to, some of them, such as <state>, can be used if your content makes use of these semantic distinctions. For example, a discussion of signals on a gate of an integrated logic circuit might use the <state> element to represent either on or off conditions of that gate.
- Legacy conversion elements
  Conversion elements exist primarily to aid in the conversion of content to DITA.
- DITAVAL elements
  A conditional processing profile (DITAVAL file) is used to identify which values are to be used for conditional processing during a particular output, build, or some other purpose. The profile should have an extension of .ditaval.
- Technical content elements
  Elements in the technical content section include the original Concept, Task, and Reference specializations, as well as specializations added in later releases. It also includes domains designed primarily for technical content.
- Learning and training elements
  Elements in the learning and training section include specialized topics, maps, content, and metadata elements specially designed to support instructional content.
- Attributes
  This section collects commonly used attributes, with common definitions. If an element uses a different definition, or narrows the scope of, an otherwise common attribute, it will be called out in the topic that defines the element.
Conformance
Conformance to the DITA specification allows documents and document types that are used with different processors or different versions of a processor to produce the same or similar results with little or no reimplementation or modification.
Acknowledgments
(Non-normative) Many members of the OASIS DITA Technical Committee participated in the creation of this specification and are gratefully acknowledged.
Non-normative information
This section contains non-normative information, including topics about new features in DITA 1.3 and migrating from DITA 1.2 to DITA 1.3.
Content models for learning and training package
For each element in the learning and training package, this section presents the content model and a list of parent elements that can contain that element.

`<coords>`

The <coords> element specifies the coordinates of a linkable region in an <imagemap>.

This element contains text data representing coordinate data for image maps. Pixels are the recommended units for describing coordinates. The syntax of the coordinate data depends on the shape described by the coordinates, and is based on the image map definition in HTML. It uses the following data for the appropriate shapes:

Shape: Data format
rect: left-x, top-y, right-x, bottom-y
circle: center-x, center-y, radius
poly: x1, y1, x2, y2, ..., xN, yN. To close the polygon, ensure that the first x and y coordinate pair and the last are the same.

Content models

See appendix for information about this element in OASIS document type shells.

Inheritance

+ topic/ph ut-d/coords

Example

<area>
 <shape>rect</shape>
 <coords>54,1,117,60</coords>
 <xref href="d1-s2.dita"></xref>
</area>

Attributes

The following attributes are available on this element: Universal attribute group (with a narrowed definition of @translate, given below), outputclass, and @keyref.

@translate

Indicates whether the content of the element should be translated or not. For this element the default value is "no". Setting to "yes" will override the default. The DITA architectural specification contains a list of each OASIS DITA element and its common processing default for the translate value; because this element uses an actual default, it will always be treated as translate="no" unless overridden as described. Available values are:

no: The content of this element is not translateable.
yes: The content of this element is translateable.
-dita-use-conref-target: See Using the -dita-use-conref-target value for more information.