subdivision-model

Complex type information

Content

• Sequence [1..1]
  from group start-of-structure
  enum [0..1]The enumerator associated with a subdivision or level (e.g., 1. for sections, (a) for subsections). Note: When an enumerator appears as two enumerator (e.g., (a)(2)), the structure is produced with two levels where the second level has an attribute of display-inline="yes-display-inline"
  header [0..1]The header is the structure, often proceeded by an enum element that represents the "bold" text or heading of a subdivision or level. For example: the words “Short Title” in the phrase “Section 1. Short Title.” The text of headers is typed in sentence style casing (upper and lower case) so that the table of contents entries can be extracted from the body of the document. Display mechanisms (both print and on-line) will need to transform the casing of headers based on their legislative structure. Section headers display uppercased. Subsection headers display in a caps and small caps casing style where the first letter of the header is always uppercased; characters originally typed using uppercasing are caps and all other words are initial capped, except for the following words: a, an, and, as, at, but, by, for, in, of, on, or, the, and to. Levels below the subsection level are cased using caps and small caps, but maintain sentence style casing. For all other structural levels (e.g., division, title, subtitle, part, subpart, etc.), the casing is transformed to uppercase. In addition, any necessary punctuation and spaces following the header will be generated for display or printing. For example, when certain structures, e.g., Titles, Subtitles, Chapters, etc., follow OLC style, the display or print system will generate a centered header with no subsequent punctuation. For sections using OLC style, a generated period will follow the header, and for structures below the section level, a generated period followed by an em-dash will follow the header.
  toc [0..1]The table of contents for a measure or portion of a measure. The attributes of the toc element are used for regeneration of the toc within the authoring environment. There are essentially two toc sub-models (toc-entries or multi-column-toc-entries). Both models are non-hierarchial in that the legislative structure is defined in an attribute rather in the structure of the toc itself. The toc-entries sub-model, the most common, is sequence of enumerators and headers from the measure's source using PCDATA. There is no distrinction between the enumerator and header elements within the toc-entry elements. The multi-column-toc-entries sub-model contain up to three columns of data per entry (toc-enum, level-header, and target or page-num). Both sub-models also support quoted-entry elements (ie.g., toc-quoted-entry and multi-column-toc-quoted-entry respectively).
  Choice [0..*]
  • appropriations-major
  • appropriations-intermediate
  • appropriations-small
  • sectionA hierarchical structure of a measure. This is usually the top level contained with the legislative body. Levels contained within sections are subsections, paragraphs, subparagraphs, clauses, subclauses, items, and subitems. Sections are normally enumerated with a numeric value followed by a period (e.g., 1.). The formatting of a section (structure of legislation) will be according to the rules of the style (such as OLC style or United States Code Style) in effect. The style will control such display issues as the fonts and highlighting used, the margins, and the indentation levels. The style (and the numerical order of the section (structure of legislation) within its containing structure) will also control generation of text, for example, the word “Section”, “Sec.”, or “§” before the enumerator and any punctuation or spacing surrounding or following the enumerator. In so doing, the style will ensure that a period always follows the abbreviation “Sec”, but not the word “Section”, and that the appropriate punctuation follows the enumerator. Accordingly, such punctuation will not be keyed and will not be part of the data. Any necessary punctuation and spaces following the header will also be generated for display or printing. For example, when a section (structure of legislation) follows OLC style, a generated period will follow the header.
  1. title [0..*]A hierarchical structure of a measure, frequently the top-level hierarchical structure inside the body of the measure, or second only to the division (structure of legislation) level. Titles (structure of legislation) and sections (structure of legislation) are the main building blocks of legislation. The formatting of a title (structure of legislation) will be according to the rules of the style (such as OLC style or United States Code Style) in effect. The style will control such display issues as the casing, fonts and highlighting used, the margins, and the indentation levels. The style will also control generation of text, for example, the word “Title ” before the enumerator and any punctuation or spacing surrounding or following the enumerator. Any necessary casing, punctuation, and spacing following the header will also be generated for display or printing. For example, when a title (structure of legislation) follows OLC style, the display or print system will generate a uppercased centered header with no punctuation following. Note: An appropriations account is generally described by a title (structure of legislation), but in some instances the account (structure of legislation) element should be used, e.g., when several accounts are grouped together within “General Provisions” which is considered the title (structure of legislation). Note: In these DTDs, a <title> does not refer to a subcaption or heading. The element <title> is a very specific subdivision of a legislative measure. The element header and subheader should be used to describe a headings or subcaptions.

Attributes

None

Used in

• Element subdivision   via derived anonymous type

Type inheritance chain

• subdivision-model
  • extended by Anonymous type of element subdivision