<list> List

Sequence of two or more items, which may or may not be ordered.

Usage/Remarks

Attribute usage
  • The @list-type attribute specifies whether there should be a prefix preceding each item and determines the prefix type (such as bullet or number). A “simple” list takes no prefix character.
  • The @prefix-word attribute can be used to prepend a word such as “Step”, “Method”, or “Procedure” to a list item, in addition to, typically, a number (thus “Step 1.”).
  • If the @list-type specifies a bulleted style (“@list-type="bullet"”), the @style-detail attribute may be used to name the preferred prefix character, for example, a “dash”, “hollow-bullet”, or “square”. If no @style-detail is given, the processing system will choose what character to display.
Attributes

Base Attributes

Models and Context
May be contained in
Description
The following, in order:
Content Model
<!ELEMENT  list         %list-model;                                 >
Expanded Content Model

(label?, title?, (list-item | x)+)

Tagged Samples
Ordered list
Arabic numbers will be automatically generated
...
<p>The Tag Suite is the complete set of elements and attributes 
described in the standard. Along with these descriptions, the 
standard includes two discrete standards models or Tag Sets:
 <list list-type="order">
  <list-item>
   <p>The Interchange Tag Set (in MathML 2.0 and MathML 3.0 
    variants)</p></list-item>
  <list-item>
   <p>The Extended Tag Set (in MathML 2.0 and MathML 3.0 
    variants)</p></list-item>
 </list>
</p>
...
Bulleted list (unordered)
...
<p>The Tag Suite is the complete set of elements and attributes 
described in the standard. Along with these descriptions, the 
standard includes two discrete standards models or Tag Sets:
 <list list-type="bullet">
  <list-item>
   <p>The Interchange Tag Set (in MathML 2.0 and MathML 3.0 
    variants)</p></list-item>
  <list-item>
   <p>The Extended Tag Set (in MathML 2.0 and MathML 3.0 
    variants)</p></list-item>
 </list>
</p>
...
Unordered list with character set by @style-detail
...
<p>... To assist standards developers to define accessibility 
requirements and recommendations, the Guide presents:
 <list list-type="bullet" style-detail="dash">
  <list-item>
   <p>a summary of current terminology relating to accessibility;</p></list-item>
  <list-item>
   <p>issues to consider in support of accessibility in the standards 
    development process;</p></list-item>
  <list-item>
   <p>a set of accessibility goals (used to identify user accessibility 
    needs);</p></list-item>
  <list-item>
   <p>descriptions of (and design considerations for) human abilities 
    and characteristics;</p></list-item>
  <list-item>
   <p>strategies for addressing user accessibility needs and design 
    considerations in standards.</p></list-item>
 </list>
</p>
...
List items explicitly numbered using <label>
...
<p>Entries can fail HTG processing because of three
 types of problems:
 <list>
  <list-item id="bid.1-1">
   <label>1</label>
   <p>Formatting: submissions are not in the proper
    Seq-submit format.</p>
  </list-item>
  <list-item id="bid.1-2a">
   <label>2-a</label>
   <p>Identification: submissions may be missing the
    genome center tag, sequence name, or Accession
    number, or this information is incorrect.</p>
  </list-item>
  <list-item id="bid.1-2b">
   <label>2-b</label>
   <p>Identification: submissions may be missing the
    genome center tag, sequence name, or Accession
    number, or this information is incorrect.</p>
  </list-item>
  <list-item id="bid.13">
   <label>3</label>
   <p>Data: submissions have problems with the data
    and therefore fail the validator checks.</p>
  </list-item>
 </list>
</p>
...
Related Resources