concept

The <concept> element is the top-level element for a topic that answers the question "what is?" Concepts provide background information that users must know before they can successfully work with a product or interface. Often, a concept is an extended definition of a major abstraction such as a process or function. It might also have an example or a graphic, but generally the structure of a concept is fairly simple.

Contains

(title then (titlealts) (optional) then (shortdesc) (optional) then (prolog) (optional) then (conbody) (optional) then (related-links) (optional) then (topic or concept or task or reference) (any number) )

Contained by

dita, topic, concept, task, reference

Inheritance

topic/topic, concept/concept

Attributes

Name Description Data Type Default Value Required?
id An anchor point. This ID is the target for references by href and conref attributes, and for external applications that refer to DITA content. ID #IMPLIED No
conref This attribute is used to reference an ID on a topic that can be reused. For example, you could create a series of topics in a compound (dita) or nested context for authoring convenience and then reference each topic individually into a new target location. During output processing, a lookup process will pull the contents of the first topic into the calling topic markup that has the conref attribute.

The conref value follows the same conventions as HTML for normal file links. To refer to target content in a different file, put the full URL of that topic before the # character.

Target elsewhere in the same file: 
  conref="#topicid"
First topic in different file: 
  conref="filename.xml"
Specific topic in different file: 
  conref="filename.xml#topicid"
CDATA #IMPLIED No
%select-atts; (platform, product, audience, otherprops, importance, rev, status) A set of related attributes, described at %select-atts; parameter entity PE not applicable Not applicable
xml:lang Specifies the language of the element content. When no xml:lang value is supplied, the default value of English is assumed. For example, if there is a note element with the attribute xml:lang set to the value "es-es," then the label on the note, which is normally output as "Note" is now output in Spanish as "Nota." The allowed xml:lang values are based on ISO-3166 Country Codes and RFC 3066 Language Codes (see W3C: Language tagging in HTML and XML). NMTOKEN #IMPLIED No
DITAArchVersion Designates the version of the architecture that is in use. CDATA "1.0" (version dependent; will increase) Yes
domains Indicates the specialized domains that are included in the DTD. CDATA ui-d hi-d pr-d sw-d No
%global-atts; (xtrf, xtrc) A set of related attributes, described at %global-atts; parameter entity PE not applicable Not applicable
class, outputclass Common attributes described in Other common DITA attributes

Example

<concept id="concept">
 <title>Introduction to Bird Calling</title>
 <shortdesc>If you wish to attract more birds to your Acme Bird Feeder,
learn the art of bird calling. Bird calling is an efficient way
to alert more birds to the presence of your bird feeder.</shortdesc>
 <conbody>
   <p>Bird calling requires learning:</p>
   <ul>
    <li>Popular and classical bird songs</li>
    <li>How to whistle like a bird</li>
   </ul>
 </conbody>
</concept>