 |
FlexDoc/XML XSDDoc Demo |
XML Schemas for DITA 1.1 |
|
FlexDoc/XML XSDDoc Demo |
XML Schemas for DITA 1.1 |
Namespace: |
|
Content: |
|
Defined: |
globally in commonElementMod.xsd; see XML source |
Includes: |
declarations of 3 attributes |
Referenced: |
by 1 location |
XML Representation Summary |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<... |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
</...> |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Attribute |
Type / Value |
Default |
Required? |
Declared In |
Description |
|
xs:string
|
no |
||||
|
scale-atts.class : (50 | 60 | 70 | 80 | 90 | 100 | 110 | 120 | 140 | 160 | 180 | 200 | "-dita-use-conref-target")
|
no |
||||
|
frame-att.class : ("top" | "bottom" | "topbot" | "all" | "sides" | "none" | "-dita-use-conref-target")
|
no |
||||
|
expanse-att.class : ("page" | "column" | "textline" | "-dita-use-conref-target")
|
no |
||||
|
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 . . .
|
|||
|
anonymous : ("default" | "preserve")
|
"preserve" |
no |
|||
|
xs:string
|
no |
||||
|
xs:string
|
no |
Component |
Type / Value |
Occurs |
Nillable? |
Declared In |
Description |
|
{text} × |
character data |
may appear between child elements |
||||
0..∞ |
||||||
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). »
|
|||
1..1 |
no |
The code phrase (<codeph>) element represents a snippet of code within the main flow of text. »
|
||||
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. »
|
||||
1..1 |
no |
The superscript (<sup>) element indicates that text should be superscripted, or vertically raised in relationship to the surrounding text. »
|
||||
1..1 |
no |
A subscript (<sub>) indicates that text should be subscripted, or placed lower in relationship to the surrounding text. »
|
||||
1..1 |
no |
The teletype (<tt>) element is used to apply monospaced highlighting to the content of the element. »
|
||||
1..1 |
no |
The bold (<b>) element is used to apply bold highlighting to the content of the element. »
|
||||
1..1 |
no |
The underline (<u>) element is used to apply underline highlighting to the content of the element. »
|
||||
1..1 |
no |
The italic (<i>) element is used to apply italic highlighting to the content of the element. »
|
||||
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 |
The <term> element identifies words that represent extended definitions or explanations. »
|
||||
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. »
|
||||
1..1 |
no |
The <cite> element is used when you need a bibliographic citation that refers to a book or article. »
|
||||
1..1 |
no |
A quotation element (<q>) indicates content quoted from another source. »
|
||||
1..1 |
no |
The <state> element specifies a name/value pair whenever it is necessary to represent a named state that has a variable value. »
|
||||
1..1 |
no |
( Deprecated ) - The <boolean> element is used to express one of two opposite values, such as yes or no, on or off, true or false, high or low, and so forth. »
|
||||
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).
|
|||
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. »
|
||||
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. »
|
||||
1..1 |
no |
The trademark (<tm>) element in DITA is used to markup and identify a term or phrase that is trademarked. »
|
||||
1..1 |
no |
The <draft-comment> element allows simple review and discussion of topic contents within the marked-up content. »
|
||||
1..1 |
no |
A <required-cleanup> element is used as a placeholder for migrated elements that cannot be appropriately tagged without manual intervention. »
|
||||
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.
|
||||
1..1 |
no |
An <indextermref> is a reference to an index entry in a lookup table used by the indexing process. »
|
||||
1..1 |
no |
An <indexterm> is an index entry. »
|
||||
1..1 |
no |
The <data> element represents a property within a DITA topic or map. »
|
||||
1..1 |
no |
The <data-about> element identifies the subject of a property when the subject isn't associated with the context in which the property is specified. »
|
||||
1..1 |
no |
The <foreign> element is an open extension that allows information architects to incorporate existing standard vocabularies for non-textual content. like MathML and SVG, as inline objects. »
|
||||
1..1 |
no |
The <unknown> element is an open extension that allows information architects to incorporate xml fragments that does not necessarily fit into an exisitng DITA use case. »
|
||||
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. |