FlexDoc/XML XSDDoc Demo
XML Schemas for DITA 1.1


element <steps-unordered>
Namespace:
Type:
anonymous complexType (extension of steps-unordered.class)
Content:
complex, 17 attributes, 1 element
Defined:
globally in taskMod.xsd; see XML source
Includes:
declaration of 1 attribute
Referenced:
Component Diagram
XML Representation Summary
<steps-unordered
   
 = 
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/ul task/steps-unordered "
   
>
   
Content: 
</steps-unordered>
Attributes:
Attribute
Type / Value
Default
Required?
Declared In
Description
xs:string
no
xs:NMTOKEN
no
xs:string
no
xs:string
no
xs:string
no
xs:string
no
xs:string
no
xs:string
no
xs:string
no
xs:string
no
importance-atts.class : ("obsolete" | "deprecated" | "optional" | "default" | "low" | "normal" | "high" | "recommended" | "required" | "urgent" | "-dita-use-conref-target")
no
status-atts.class : ("new" | "changed" | "deleted" | "unchanged" | "-dita-use-conref-target")
no
yesno-att.class : ("yes" | "no" | "-dita-use-conref-target")
no
xs:language
no
In due course, we should install the relevant ISO 2- and 3-letter codes as the enumerated possible values . . .
xs:string
no
xs:string
no
xs:string
"- topic/ul task/steps-unordered "
no
The class attribute supports specialization. »
Content Element Model:
Component
Type / Value
Occurs
Nillable?
Declared In
Description
1..∞
no
The <step> element represents an action that a user must follow to accomplish a task. »
Description
Like the <steps> element, the <steps-unordered> section of a task provides the main content of the task topic, but particularly for cases in which the order of steps may vary from one situation to another. For example, fields of a form can be filled in without particular regard to order as long as the required ones are filled in before submitting the form. One or more steps is required inside the <steps-unordered> section.
Related Components
Referenced By
Anonymous Type Detail
Type Derivation Tree


XML schema documentation generated with FlexDoc/XML 1.15 using FlexDoc/XML XSDDoc 3.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.