element <section> (global)
Namespace: |
|
Type: |
|
Content: |
mixed (allows character data), 18 attributes, 60 elements |
Defined: |
|
Includes: |
|
Used: |
|
XML Representation Summary |
<section |
|
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:NMTOKEN |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string |
|
= |
("obsolete" | "deprecated" | "optional" | "default" | "low" | "normal" | "high" | "recommended" | "required" | "urgent" | "-dita-use-conref-target") |
|
= |
("new" | "changed" | "deleted" | "unchanged" | "-dita-use-conref-target") |
|
= |
("yes" | "no" | "-dita-use-conref-target") |
|
= |
xs:language |
|
= |
xs:string |
|
= |
xs:string |
|
= |
xs:string : "- topic/section " |
|
|
> |
|
|
</section> |
Included in content model of elements (3):
-
Annotation
The <section> element represents an organizational
division in a topic. Sections are used to organize subsets of information
that are directly related to the topic. For example, the titles Reference
Syntax, Example and Properties might represent section-level
discourse within a topic about a command-line process—the content in each
section relates uniquely to the subject of that topic. Multiple sections within
a single topic do not represent a hierarchy, but rather peer divisions of
that topic. Sections cannot be nested. A section may have an optional title.
Type Derivation Tree
complexType
|
XML Source (w/o annotations (1); see within schema source)
<xs:complexType mixed="true">
<xs:complexContent>
<xs:extension base="section.class">
<xs:attribute default="- topic/section " ref="class"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
|
Attribute Detail (all declarations; defined within this component only; 1/18)
-
Type: |
xs:string, predefined
|
Use: |
optional |
Attribute Value
Default: |
"- topic/section " |
XML Source (see within schema source)
<xs:attribute default="- topic/section " ref="class"/>
|