FlexDoc/XML XSDDoc Demo
XML Schemas for DITA 1.1


complexType "figgroup.class"
Namespace:
Content:
complex, 16 attributes, 27 elements
Defined:
Includes:
declaration of 1 attribute
Referenced:
Component Diagram
XML Representation Summary
<...
   
 = 
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
   
>
   
Content: 
</...>
Attributes:
Attribute
Type / Value
Default
Required?
Declared In
Description
outputclass
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
Content Element Model:
Component
Type / Value
Occurs
Nillable?
Declared In
Description
1..1
0..1
no
The <title> element contains a heading or label for the main parts of a document such as <topic>, <section>, and <example> and for the display elements such as figure (<fig>) and <table>.
0..∞
1..1
no
The <figgroup> element is used only for specialization at this time. »
  xref
1..1
no
Use the cross-reference (<xref>) element to link to a different location within the current topic, or a different topic within the same help system or DITA document. »
  fn
1..1
no
Use footnote (<fn>) to annotate text with notes that are not appropriate for inclusion in line or to indicate the source for facts or other material used in the text.
  ph
1..1
no
ph (ver 1)
The phrase (<ph>) element is used to organize content for reuse or conditional processing (for example, when part of a paragraph applies to a particular audience). »
  codeph
1..1
no
The code phrase (<codeph>) element represents a snippet of code within the main flow of text. »
  synph
1..1
no
The syntax phrase (<synph>) element is a container for syntax definition elements. »
1..1
no
The user interface control (<uicontrol>) element represents a button, entry field, menu item, or other object that allows the user to control the interface. »
1..1
no
The <menucascade> element is used to document a series of menu choices, or to show any choice on a menu from which the user needs to choose. »
  sup
1..1
no
The superscript (<sup>) element indicates that text should be superscripted, or vertically raised in relationship to the surrounding text. »
  sub
1..1
no
A subscript (<sub>) indicates that text should be subscripted, or placed lower in relationship to the surrounding text. »
  tt
1..1
no
The teletype (<tt>) element is used to apply monospaced highlighting to the content of the element. »
  b
1..1
no
The bold (<b>) element is used to apply bold highlighting to the content of the element. »
  u
1..1
no
The underline (<u>) element is used to apply underline highlighting to the content of the element. »
  i
1..1
no
The italic (<i>) element is used to apply italic highlighting to the content of the element. »
  msgph
1..1
no
The message phrase (<msgph>) element contains the text content of a message produced by an application or program. »
1..1
no
The <filepath> element indicates the name and optionally the location of a referenced file by specifying the directory containing the file, and other directories that may precede it in the system hierarchy. »
1..1
no
The user input (<userinput>) element represens the text a user should input in response to a program or system prompt. »
1..1
no
The system output (<systemoutput>) element represents computer output or responses to a command or situation. »
1..1
no
keyword (ver 1)
The <keyword> element identifies a keyword or token, such as a single value from an enumerated list, the name of a command or parameter, or a lookup key for a message (contrast with term).
  option
1..1
no
The <option> element describes an option that can be used to modify a command (or something else, like a configuration). »
1..1
no
When referencing the name of an application programming interface parameter within the text flow of your topic, use the parameter name (<parmname>) element to markup the parameter. »
1..1
no
The <apiname> element provides the name of an application programming interface (API) such as a Java class name or method name. »
1..1
no
The window title <wintitle> element represents the title text that appears at the top of a window or dialog, and applies to wizard titles, wizard page titles, and pane titles. »
  msgnum
1..1
no
The message number (<msgnum>) element contains the number of a message produced by an application or program. »
1..1
no
The variable name (<varname>) element defines a variable that must be supplied to a software application. »
1..1
no
The command name (<cmdname>) element specifies the name of a command when it is part of a software discussion. »
Related Components
Referenced By


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.