accountNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure used within appropriations legislation.

An account (structure of legislation) is a rarely used element, as most appropriations accounts are tagged as titles (structure of legislation). However, when several accounts are grouped under a general heading, (e.g., “Related Accounts” or “General Provisions”), the general heading is tagged as a title (structure of legislation), and the individual accounts contained within are tagged as accounts (structure of legislation). When used, an account (structure of legislation) is typically comprised of one or more subaccounts (structure of legislation). The formatting of an account (structure of legislation) will be according to the rules of the appropriation style.

The style will control such display issues as the fonts and highlighting used, centering of headings, the margins, and the indentation levels. The style will also control generation of text, as well as any punctuation or spacing surrounding or following the header. Accordingly, such punctuation will not be keyed and will not be part of the data.

action–dateNOBillsCommitteeConferenceHearingResolutionThe date or dates on which a particular floor action occurred.

There may be two dates associated with an action, the regular calendar date and the legislative day. Sometimes the textual descriptions of these dates do not divide neatly into two parts, for example, the full date may be written as “February 3 (legislative day, January 30), 1995”. Therefore, the ACTION DATE is just data characters, to be entered in any fashion necessary.

For purposes of searching and for date comparisons, the real values of the date and the Legislative Day may be stored in the attributes for this element: date and legis-day in the machine-readable “YYYYMMDD” format. The year is the first four digits, followed by the 2-digit month, followed by the 2-digit day. For the month and day, zero fill as necessary to produce two digits. Formerly, the *I46 locator code.

action-descNOBillsCommitteeConferenceHearingResolutionDescription of the floor action taking place (i.e., introduction, committee referral, committee action, committee reporting, calendar placement).Formerly, the *I47 locator code.

action-instructionNOBillsCommitteeConferenceHearingResolutionInstruction related to the action. For example,“[Strike out all after the resolving clause and insert the part printed in italic]”.

actionNOBillsCommitteeConferenceHearingResolutionContainer for all information pertaining to a floor action for a measure or Amendment, i.e., the actual description of the floor action and the date on which the action occurred.

added-phraseNOAmendmentBillsCommitteeConferenceHearingRamseyerResolutionUS CodeNewly added or inserted material. This material is usually shown in italic.

There are two ways material may be marked as new or deleted. If an entire structure such as a <title> or <section> has been added or deleted, the changed attribute on the structure could be set to “added” or “deleted.” If only a small portion of a structure has been added or deleted, perhaps a few words or a single letter, the <added-phrase> and <deleted-phrase> elements are used to mark those small additions and deletions.

Note: This is not the element to be used in an amendment to insert text. This is the element used in a bill or resolution to indicate that text has been added. In an amendment, the text to be inserted is contained within a <text-to-insert> element.

after-quoted-blockNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe text appearing after the closing quotemarks in a <quoted-block>. This is usually a period, but could be “;”, or “; and”, or anything else. The closing double quotemarks need to be generated by downstream display systems.

appropriations-paraNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeSpecific paragraph form used in appropriation legislation which may contain one or more provisos.

associated-docNOBillsCommitteeConferenceHearingResolutionIdentification of another documents that have an association with the current document such as reports, companion bills, identical bills, amendments, etc.. Used in the form element.

attestation-dateNOBillsCommitteeConferenceHearingResolutionUS CodeContainer for the date (legislative and/or calendar) on which a measure is passed and the chamber that passed it. Since this text take various forms, the attributes record the date and chamber values for searching.

attestation-groupNOBillsCommitteeConferenceHearingResolutionUS CodeContainer for information related to an attestation, e.g., a legislative measure's passage and certification of authenticity for a particular chamber. An attestation may (and usually does) begin with the date of the attestation, which is generated. This date represents the date (legislative and/or calendar) on which a measure is passed and the chamber that passed it and can be generated from the chamber and a system date.

attestationNOBillsCommitteeConferenceHearingResolutionUS CodeContainer for information indicating passage of a measure and certification by the Clerk of the House of Representatives or the Secretary of the Senate (or their representatives) that a document is genuine. The text of the printed attestation will be generated from this information.

attestorNOBillsCommitteeConferenceHearingResolutionUS CodeName of a person who certifies that a document is genuine.

author-noteNOBillsCommitteeConferenceHearingRamseyerResolutionAn author-note is an internal metadata element for including notes from the author of the document.

billNOBillsCommitteeConferenceHearingThe top level container element that contains all the text and markup for an entire bill or Act. This element encompasses the bill's form (metadata which is the information about the Bill such as the official title), and the legis-body (the actual words that comprise the content of the bill).

Note: An Engrossed Amendment is still just an Amendment, not a Bill; it has not been incorporated, it has merely been passed.

boldNOAmendmentBillsCommitteeConferenceHearingResolutionWords displayed in bold for emphasis or other purposes primarily.

calendarNOBillsCommitteeConferenceHearingResolutionLegislative calendar name and number. In the House, examples are Consent Calendar No. 4, Union Calendar No. 3, House Calendar No. 12, Private Calendar No. 1, Corrections Calendar No. 6, Discharge Calendar No. 1. In the Senate, examples are Executive Calendar No. 1 or Legislative Calendar No. 3. Formerly, the *I35 locator code.

chapterNOAmendmentBillsCommitteeCompilationsConferenceHearingRamyserResolutionUS CodeA hierarchical structure of a measure.

The formatting of a chapter (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 will also control generation of text, for example, the word “Chapter ” before the enumerator and any punctuation or spacing surrounding or following the enumerator. For example, a chapter (structure of legislation) in OLC style will have a generated em-dash following 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 chapter (structure of legislation) follows OLC style, the display or print system will generate a centered header with no punctuation following.

clauseNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is contained directly with subparagraphs. Levels contained within clauses are subclauses, items, and subitems. Clauses are normally enumerated with lowercased roman-numeral values within parentheses (e.g., (ii)).

colspecNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeCALS Open Table Model.

committee-appointment-paragraphNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeResolving-clauses can contain additional paragraphs structurally within the clauses themselves but displayed as separate paragraphs without enumerators. This is commonly used in the resolution to appoint Members to committees (see 106 HRes 6) Note: the first subsection within a resolving clause is displayed inline within the resolving clause

committee-nameNOBillsCommitteeCompilationsConferenceHearingRamseyerResolutionThe name of a working subdivision of a chamber, which prepares legislation or conducts investigations.

congressNOAmendmentBillsCommitteeCompilationsConferenceHearingResolutionThe number of the Congress, e.g., “101st Congress” or “The One Hundred and First Congress.”

constitution–articleNOBillsResolutionA hierarchical structure of a measure. This structure contains text to amend the Constitution of the United States.

continuation-textNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeTextual material belonging to a level, the text follows the sub-level

cosponsorNOBillsCommitteeConferenceHearingResolutionIdentification information for a congressional member who has signed onto a measure, signifying his/her support; usually just the name but sometimes including additional information such as the state represented.

current-chamberNOAmendmentBillsCommitteeConferenceHearingResolutionIdentifies the chamber currently having control of the legislation (e.g., “In the House of Representatives” or “In the Senate of the United States”) Formerly, the *I45 locator code.

definitionNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe meaning of a term; may include other terms the definitions which are referenced elsewhere.

deleted-phraseNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeWords or phrases which have been stricken or which show strike-through.

Material that has been deleted from a bill or resolution is printed and displayed as typographically distinct, to indicate that it has been removed. In current measures, this material is usually shown with a line through it as to indicate that it has been stricken.

There are two ways material may be marked as new or deleted. If an entire structure such as a <title> or <section> has been added or deleted, the changed attribute on the structure could be set to “added” or “deleted.” If only a small portion of a structure has been added or deleted, perhaps a few words or a single letter, the <added-phrase> and <deleted-phrase> elements are used to mark those small additions and deletions.

Note: This is not the element used in an amendment to strike text. This is the element used in a bill or resolution to indicate text that has been stricken. The instructions in an amendment to indicate that text is to be stricken are marked with the <text-to-strike-out> element.

distribution-codeNOBillsCommitteeConferenceHearingResolutionUsed by the Government Printing Office to distribute paper copies of a measure to congressional and other governmental offices. Indicates the stage or type of measure, but is used to tell GPO to whom measures should be distributed. The values are as follows: I: Public Bills Introduced or Referred in the House, IA: Joint Resolutions Introduced or Referred in the House, IB: Public Bills and Joint Resolutions Reported in the House, II: Public Bills and Joint Resolutions Introduced or Reported in the Senate, IIA: Public Bills and Joint Resolutions Referred in the Senate, III: Simple and Concurrent Resolutions in the Senate, IIIA: Amendments in the Senate, IV: Simple and Concurrent Resolutions in the House, V: Private Bills Introduced in the House, VI: Private Bills Introduced in the Senate, VII: Private Bills Reported or Referred in the House, VIII: Private Bills Reported or Referred in the Senate, IX: Reprint Bills for House Document Room, and X: Reprint Bills for Senate Document Room. Formerly, the *I60 locator code.

divisionNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. If present, usually the top-level hierarchical structure, containing titles (structure of legislation) within it.

The formatting of a division (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 will also control generation of text, for example, the word “Division ” before the enumerator and any punctuation or spacing surrounding or following the enumerator or the header. Accordingly, such punctuation will not be keyed and will not be part of the data.

editorialNOAmendmentBillsCommitteeConferenceHearingRamseyerResolutionIs an element in the text-model. Its intended use is to reference opinion.

effective-dateNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeDate on which a measure or portion of a measure takes effect or is repealed.

Note: this is only used to identify dates that are explicitly specified in the text, (e.g. May 5, 1998) not dates that are implicitly specified (e.g., on or after the 15th day after the date of the enactment of this Act”).

endorsementNOBillsCommitteeConferenceHearingResolutionUsed to create the endorsement structure that is on the “back” of a measure; the endorsement typically includes information about the measure's title, number, the chamber in which it is being considered, its calendar number, etc.

Endorsements are created by either the GPO or the Clerks. GPO creates endorsements on calendar bills (reported bills), while the Enrolling Clerks create endorsements on engrossments. It should be noted that a simple resolution reported has an endorsement, but engrossed simple resolutions do not have endorsements.

enrolled-datelineYESBillsUsed for enrolled bills, verbage contains the date for the first day of the session in which the bill is enrolled. entryNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeCALS Open Table Model cell entry.

enum-in-headerNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeIdentifies enumerators within header elements so that they can be cased appropriately on output, but typed within the document as lowercased.

enumNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe 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"

external-xrefNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodePointer, or cross reference, to material outside the document.

first-page-dateNOBillsCommitteeConferenceHearingRamseyerResolutionThe first-page-date element is used within the Bill metadata to describe the date on the first page.

first-page-descNOBillsCommitteeConferenceHearingRamseyerResolutionThe first-page-desc element is used within the Bill metadata as a description used on the first page.

first-page-headerNOBillsCommitteeConferenceHearingRamseyerResolutionThe first-page-header element is used within the Bill metadata to describe the header on the first page.

footnote-refNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeAn element used to reference a footnote used for a note of reference, explanation, or comment.

footnoteNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeAn element used for a note of reference, explanation, or comment.

formNOBillsCommitteeConferenceHearingResolutionContainer element for those portions of a measure that are typically identified as metadata for the measure and displayed on the first page of the measure before the legislative language of the bill or resolution. Some of the elements contained within the form are also displayed in the endorsement (back cover) of the measure when applicable. The content model is: distribution-code?, calendar?, congress, session, legis-num, associated-doc*, current-chamber, action*, legis-type, official-title

formulaNOAmendmentBillsCommitteeCompilationsConferenceUS CodeHearingRamseyerResolutionContainer for a graphic element representing a scientific or mathematical equation.

fractionNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA fraction expression that displays or prints inline with regular text (e.g., 2/5).

graphicNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA pointer to a file containing a graphic and information about the graphic.

The <graphic> element uses attributes that point to an external graphic file such as a photograph of a person or a drawing of a warning symbol. The attributes and their values have been modeled on GPO attributes. The actual graphic is usually stored in an external file and merely named by the attributes of this element. The element itself would be empty, but it is used to contain a brief description of the graphic (See element <graphic-description>). This description can be used for searching, to display in place of the graphic in an online system, or to be read by a voice synthesis device for the visually-impaired who cannot see the graphic.

header-in-textNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeElement for headers that appear in the text. The casing for these headers must be transformed appropriate to their level as described in the <header> element section.

headerNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe 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.

holc-attorneyNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-attorney" is Bill metadata that describes the HOLC attorney drafting the legislation.

holc-contact-phoneNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-contact-phone" is Bill metadata that describes the phone number for the HOLC contact.

holc-contactNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-contact" is Bill metadata that describes the HOLC contact concerning the legislation.

holc-creation-dateNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-creation-date" is Bill metadata that describes the date the legislation was drafted at HOLC.

holc-creatorNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-creator" is Bill metadata that describes the HOLC person who drafted the legislation.

holc-doc-numberNOBillsCommitteeConferenceHearingRamseyerResolution

holc-filenameNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-filename" is Bill metadata that describes the physical filename of the file.

holc-job-numberNOBillsCommitteeConferenceHearingRamseyerResolution

holc-last-authorNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-last-author" is Bill metadata that describes the last author of the file.

holc-last-savedNOBillsCommitteeConferenceHearingRamseyerResolutionThe "holc-last-saved" is Bill metadata that describes the last date the file was saved.

inline-commentNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeAn inline-comment element defines an inline-comment from the author. This element is not displayed on output.

instructive-paraNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeDescriptive paragraph at the beginning of a table of contents.

internal-xrefNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodePointer, or cross reference, to another portion of the current document.

italicNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeWords displayed in italic for emphasis or to indicate a book title or ship name or other purposes primarily within text or header elements. Note: This is not used to indicate inserted, instead the added-phrase element is used to indicate inserted text.

itemNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is contained directly with subclauses. Levels contained within items are subitems. Items are normally enumerated with lowercased double characters within parentheses (e.g., (aa)). Once reaching (zz), items are enumerated as (aaa), (bbb), etc..

legis-bodyNOBillsCommitteeCompilationsConferenceHearingRamseyerContainer for the textual content of a legislative measure. This may include such material as proposed law and changes to existing law. This element does not contain the enacting clause, but the enacting clause is generated on output before the legis-body is displayed.

legis-commentNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe legis-comment element defines a comment to the legislative language.

legis-counselNOBillsCommitteeConferenceHearingRamseyerResolutionThe legis-counsel element defines the legislative counsel. This information is available in the <preform> and is not displayed on output.

legis-numNOBillsCommitteeCompilationsConferenceHearingRamseyerResolutionThe “legis-num” is the legislation's official identifier e.g., “H.R. 1514” or “S.J. RES. 42” The first “word” indicates the chamber creating the legislation and the type of legislation. Values are: H.R. for House Bill, S. for Senate Bill, H.J. RES. for House Joint Resolution, S.J. RES. for Senate Joint Resolution, H.CON. RES. for House Concurrent Resolution, S.CON. RES. for Senate Concurrent Resolution, H. RES. for House Simple Resolution, and S. RES. Senate Simple Resolution. Formerly, the *I43 locator code.

legis-typeNOBillsCommitteeCompilationsConferenceHearingRamseyerResolutionContainer for whether the document is “A BILL” or “AN ACT” or “AMENDMENT.”

level-headerNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeHeader used within multi-column-toc-entry to represent the header of the section or big level.

linebreakNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeUsed to force a newline in the output. Should be used very rarely.

list-itemNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeContains one component of a list.

listNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA container element for a sequence of list-items organized as a list. The list can be non-numbered, numbered, or lettered.

meta-houseNOBillsCommitteeConferenceHearingRamseyerResolutionThe meta-house element is a container element for the metadata for the House of Representatives.

meta-senateNOBillsCommitteeConferenceHearingResolutionThe meta-house element is a container element for the metadata for the Senate

multi-column-toc-entryNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeContainer for multiple column table of contents entry. These are table of contents entries that typically contain a page number or target location.

multi-column-toc-quoted-entryNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeContainer used when a quoted toc entry has more than 2 columns as seen most often in the U.S. Code. The container includes an optional toc-enum and level-header followed by the page number or alternate target.

nonsponsorNOBillsCommitteeConferenceHearingResolutionIdentification information for a legislator who has signed onto the measure, but not a sponsor or cosponsor; usually just the name but sometimes including additional information such as the state represented.

notedNOBillsCommitteeConferenceHearingResolutionThe noted element defines a metadata note.

official-titleNOBillsCommitteeCompilationsConferenceHearingRamseyerResolutionThe official title of a measure or portion of a measure. A measure typically has both an official title and one or more short titles (element <short-title>).

omitted-textNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeUsed to indicate that a span of copy is not present in the document. This element may be used to tag a few missing characters (horizontal missing text) or any number of missing lines (vertical missing text). Use of this element will result in a line of “stars” (asterisks) being printed or displayed where copy is missing. This line typically consists of three or seven “stars” (asterisks). The Ramseyer portion of Committee Reports also uses three and seven “stars” (asterisks).

page-numNOAmendmentBillsCommitteeCompilationsConferenceHearingResolutionUS CodeThe page number where this entry begins in the printed representation.

pagebreakNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeUsed to force a new page in the output. Should be used very rarely.

paragraphNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is contained directly with subsections. Levels contained within paragraphs are subparagraphs, clauses, subclauses, items, and subitems. Subparagraphs are normally enumerated with a numeric values within parentheses (e.g., (1)).

partNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure.

The formatting of a part (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 will also control generation of text, for example, the word “Part ” before the enumerator and any punctuation or spacing surrounding or following the enumerator. Accordingly, such text will not be keyed and will not be part of the data.

Any necessary casing and spacing following the header will also be generated for display or printing. For example, when a part (structure of legislation) follows OLC style, the display or print system will generate a centered header with no punctuation following.

pre-formNOBillsCommitteeConferenceHearingRamseyerResolutionThe pre-form element is a metadata element that defines information about the bill or resolution.

provisoNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeConditional language under which an appropriation is made. The first Proviso within a structure begins with the generated text “Provided, ” and ends with a generated colon. Subsequent Provisos within the same structure begin with the generated text “Provided further, ” and end with a generated period. No punctuation should be keyed as the final punctuation symbol for any proviso as this punctuation will be provided by the output specification.

proxyNOBillsCommitteeConferenceHearingResolutionUS CodeThe proxy element defines a proxy for an attestation within a bill.

quoteNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeWords displayed in quotation marks for emphasis or to indicate a speech or other purposes primarily within text or header elements. This represents the inline quote element.

quoted-blockNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeTextual matter used to amend current law. Quoted block is so named because it is printed or displayed with quotation marks in front of each structural and non-structural level. (These quotation marks are generated for print or display; they are not part of the data.) The name “quoted block” is not meant to imply that the words within this element exist somewhere else and are being quoted. Rather, they signify text to be used to amend current law.

In print or display, quoted material usually takes on the style (margins, enumeration style, typographic style, etc.) of the document which is being amended. Thus, a bill in OLC style that is intended to modify United States Code, would put text that was to be inserted into the United States Code inside the quoted block (structure of legislation) and the words would print in USC style, with a quotation mark preceding each level. Other rules that apply to the specific style associated with the quoted-block also need to be applied. For example, when using USC style, section enumerators are preceded by a section symbol and a thin space rather than the word “Sec.”.

Note: Words displayed in quotation marks for emphasis or to indicate a speech are not considered to be quoted-block.

reintroduction-codeNOBillsCommitteeConferenceHearingRamseyerResolutionThe reintroduction-code element is metadata that defines the reintroduction code used by the legislative counsel.

roleNOBillsCommitteeConferenceHearingResolutionUS CodeAn official title or position held by a person such as “Secretary.”

rowNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeCALS Open Table Model.

running-headerNOBillsCommitteeConferenceHearingRamseyerResolutionThe running-header element defines the running header that should be used in printed output. This element should not be used for non-page oriented output.

sectionNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA 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.

sessionNOAmendmentBillsCommitteeCompilationsConferenceHearingResolutionThe session, or meeting, of Congress, e.g., “1st Session”, “2d Session”, “3d Session”, “4th Session”, etc. Formerly, the *I42 locator code.

short-titleNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe abbreviated or shortened name of a measure or portion of a measure.

The short title is used in two senses: (1) the abbreviated or shortened name of an entire measure, used as an alternative to the long title when speaking of the measure; and (2) the abbreviated or shortened name of a portion of a measure, such as a title or a division.

Unlike most metadata which must appear in the form of a document, a short title may appear almost anywhere within the text of a measure. Therefore, the short-titles will likely be implemented using text-entities.

signature-lineNOBillsCommitteeConferenceHearingRamseyerResolutionThe signature-line is a metadata element that defines the line where are signitures are included on the pre-form.

sponsorNOBillsCommitteeConferenceHearingResolutionIdentification information for the congressional member who introduced a legislative measure, for himself/herself, another member (noted in the Senate with “by request”), or for the administration; usually just the name but sometimes including additional information such as the state represented. (Note: a measure can only have one sponsor).

subaccountNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure used within appropriations legislation immediately below the level of an account.

An 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”. An account (structure of legislation) is typically comprised of one or more subaccounts (structure of legislation).

The formatting of a subaccount (structure of legislation) will be according to the rules of the appropriation style. The style will control such display issues as the fonts and highlighting used, centering of headings, the margins, and the indentation levels. The style will also control generation of text, as well as any punctuation or spacing surrounding or following the header. Accordingly, such punctuation will not be keyed and will not be part of the data.

subchapterNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure within a measure, typically the first major subdivision of a chapter (structure of legislation).

The formatting of a subchapter (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 will also control generation of text, for example, the word “Subchapter” before the enumerator and any punctuation or spacing surrounding or following the enumerator.

Any necessary casing, punctuation, and spaces following the header will also be generated for display or printing. For example, when a subchapter (structure of legislation) follows OLC style, the display or print system will generate a centered uppercased header with no punctuation following.

subclauseNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is contained directly with clauses. Levels contained within subclauses are items, and subitems. Subclauses are normally enumerated with uppercased roman-numeral values within parentheses (e.g., (II)).

subdivisionNOAmendmentBillsCommitteeConferenceHearingResolutionA hierarchical structure of a measure. If present, usually a top-level hierarchical structure, containing titles (structure of legislation) within it. The formatting of a subdivision (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 will also control generation of text, for example, the word “Subdivision ” before the enumerator and any punctuation or spacing surrounding or following the enumerator or the header. Accordingly, such punctuation will not be keyed and will not be part of the data.

subheaderNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeAn additional “header” that follows a <header> and provides additional information concerning the structure identified by the header element. Often used in appropriations legislation.

The text of headers will appear 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 location within various strucutres. 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 inital capped, except for the 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 maintaining 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 punctuation following. 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.

Note: In these DTDs, <title> and <subtitle> do not refer to a subcaption or heading. The element <title> and <subtitle> are very specific subdivisions of a legislative measure. The element subheader should only be used to describe a secondary heading or subcaption.

subitemNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is the lowest level represented within a measure and is contained directly with items. Subitems are normally enumerated with uppercased double characters within parentheses (e.g., (AA)). Once reaching (ZZ), subitems are enumerated with triple letters (e.g., (AAA), (BBB), etc.).

subparagraphNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is contained directly with paragraphs. Levels contained within subparagraphs are clauses, subclauses, items, and subitems. Subparagraphs are normally enumerated with an uppercased alpha character within parentheses (e.g., (A)). After reaching (Z), subparagraphs are enumerated with double letters (e.g., (AA), (BB), (CC), etc.).

subpartNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure, typically the major subdivision of a part (structure of legislation).

The formatting of a subpart (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 will also control generation of text, for example, the word “Subpart” 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 subpart (structure of legislation) follows OLC style, the display or print system will generate an uppercased, centered header with no punctuation following.

subscriptNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeElement to contain subscripted character string.

subsectionNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure. This level is contained directly within sections. Levels contained within subsections are paragraphs, subparagraphs, clauses, subclauses, items, and subitems. Subsections are normally enumerated with a lowercased alpha character within parentheses (e.g., (a)). After reaching (z), subsections are enumerated with double letters (e.g., (aa), (bb), (cc), etc.).

subsubaccountNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure used within appropriations legislation immediately below the level of a subaccount (structure of legislation). (Note: An 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”.).

An account (described by a title (structure of legislation) or an account (structure of legislation) is usually comprised of one or more subaccounts (structure of legislation). A subaccount (structure of legislation) may be comprised of one or more subsubaccounts (structure of legislation).

The formatting of a subsubaccount (structure of legislation) will be according to the rules of the appropriation style. The style will control such display issues as the fonts and highlighting used, centering of headings, the margins, and the indentation levels. The style will also control generation of text as well as any punctuation or spacing surrounding or following the header. Accordingly, such punctuation will not be keyed and will not be part of the data.

subsubsubaccountNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure used within appropriations legislation immediately below the level of a subsubaccount (structure of legislation). (Note: An 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”.).

An account (described by a title (structure of legislation) or an account (structure of legislation) is usually comprised of one or more subaccounts (structure of legislation). A subsubaccount (structure of legislation) may be comprised of one or more subsubsubaccounts (structure of legislation).

The formatting of a subsubsubaccount (structure of legislation) will be according to the rules of the appropriation style. The style will control such display issues as the fonts and highlighting used, centering of headings, the margins, and the indentation levels. The style will also control generation of text as well as any punctuation or spacing surrounding or following the header. Accordingly, such punctuation will not be keyed and will not be part of the data.

subtitleNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA hierarchical structure of a measure, usually the first major subdivision of a title (Structure of Legislation).

T he formatting of a subtitle (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 will also control generation of text, for example, the word “Subtitle” 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 subtitle (structure of legislation) follows OLC style, the display or print system will generate an uppercased centered header with no punctuation following. Where the style of a subtitle (structure of legislation) is different from the preceding and possibly following titles (structure of legislation) or subtitles (structure of legislation), for example, in situations where the subtitle (structure of legislation) is the title (structure of legislation) of another measure, the style attribute can be used to override the normally designated style.

Note: In these DTDs, a <subtitle> does not refer to a subcaption or secondary heading that adds additional material to the heading of a title, section, figure, etc. The element <subtitle> is a very specific subdivision of a legislative measure. The element subheader should be used to describe a secondary heading or subcaption

superscriptNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeElement to contain superscripted character string.

suspension-floor-actionNOBillsCommitteeConferenceHearingRamseyerResolution

suspension-instructionsNOBillsCommitteeConferenceHearingRamseyerResolutionThe suspension-instructions element defines instructions should the legislation be suspended. This is an internal element and should not be displayed.

tableNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionThe table model for Congressional legislative documents uses the OASIS (formerly known as CALS) Table Exchange Model with some additions and modifications to accommodate House and Senate requirements as defined by the U.S. Government Printing Office.

targetNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeTarget within a multi-column-toc-entry container. Used to provide various items in the last column of the multiple column table of contents entry.

tbodyNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeCALS Open Table Model.

tdescNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeCALS Open Table Model.

termNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA word or phrase referencing a definition elsewhere in the document usually in the same text area.

textNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeTextual material that follows a header, an enumerator, an enumerator/header pair, or as a cut-in (flush-left) final text after a non-structural element such as a quoted-block, table, graphic, etc..

In appropriations bills, the function performed by the text element is usually performed by the appropriations paragraph element.

tgroupNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeOASIS Open Table Model.

theadNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeOASIS Open Table Model.

titleNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeA 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.

toc-entryNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe words in a table of contents entry that contain the heading and enumeration of the structure for which this is an entry. For example, in the entry “Sec. 5 Underwater Resources”, everything between the quote marks is a toc-entry.

toc-enumNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeEnumerator when used within a multi-column-toc-entry.

toc-quoted-entryNOAmendmentBillsCommitteeConferenceHearingResolutionUS CodeThe toc-quoted-entry element is a container for table of contents entries (toc-entry) that reside within a quoted-block container.

tocNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS CodeThe 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).

ttitleNOAmendmentBillsCommitteeCompilationsConferenceHearingRamseyerResolutionUS Codeable title. This is used instead of <title> for tables.

version-creatorNOBillsCommitteeConferenceHearingRamseyerResolutionThe version-creator element is an internal metadata element that defines the creator of a specific version.

version-dateNOBillsCommitteeConferenceHearingRamseyerResolutionThe version-date element is an internal metadata element that defines the date of a specific version.

version-filenameNOBillsCommitteeConferenceHearingRamseyerResolutionThe version-filename element is an internal metadata element that defines the filename of a specific version.

versionNOBillsCommitteeConferenceHearingRamseyerResolutionThe version element defines the version of the document.