Schema Central  >  USLM 2.1.0  >  uslm-components-2.1.0.xsd  >  uslm:LevelStructure
Advanced search

uslm:LevelStructure

            The level structure is the primary structure of hierarchy. A level
            is structured either as an instruction, loosely structured content, 
            or as a hierarchy.

Group information

Namespace: http://schemas.gpo.gov/xml/uslm

Schema document: uslm-components-2.1.0.xsd

Content

  • Choice [1..1]
    • Sequence [1..1]
      1. Choice [1..*]
          from subst. group uslm:content
        • uslm:content The <content> element is a primitive element to be used anywhere where a very general content model is desired, including within other <content> elements.
        • uslm:quotedContent A <quotedContent> element is used for an extraction of structured text (text with XML elements) from another source or origin or destined for another document. Quoted content is used in USC Notes and bills that amend law. If the quoted content is to have literal quote characters within it, then those characters must be included in the text. The <quotedContent> element does not generate those characters. By convention such characters are placed within the quotedContent tags at the first location where mixed content is allowed, not outside the tags.
        • uslm:p A <p> is a simple paragraph. This is different from the more complex numbered <paragraph> element used for the formal paragraph level of legislative documents.
      2. Choice [0..*]
          from group uslm:NoteStructure
          from subst. group uslm:note
        • uslm:note A <note> is a generic element for a note associated with items in the document.
        • uslm:elided An <elided> element is a replacement for text content that has been elided or omitted from this document. The optional ref attribute may point to the text that was elided. The <elided> element may only contain text content (typically asterisks, called 'stars').
        • uslm:sourceCredit A <sourceCredit> is a note included to indicate the source of a provision. It usually will contain a reference to the source of the provision and the Statute(s) that have affected it. Source credits are usually set out in parenthesis. The surrounding parentheses are shown in the text - they are not automatically added.
        • uslm:uscNote A <uscNote> is a note below sections and big-level headings in the U.S. Code.
        • uslm:statutoryNote An <statutoryNote> is a note that becomes part of the law.
        • uslm:drafterNote A <drafterNote> is a note that does not become part of the law. It is used by drafters for their own purposes (commenting out a section of drafted content, for example, or asking questions, or proposing alternative wording) and is generally deleted before the document is published to others.
        • uslm:editorialNote An <editorialNote> is a note included for editorial purposes only. While present in the text of the document as printed, it is not a part of the law. Editorial notes are often used to record where provisions have been omitted or other changes have been made, or in a preface of the CFR.
        • uslm:changeNote A <changeNote> is a note that records a non-substantive change that has been made to the US Code. Usually change notes are set out in square brackets and these must be set out in the text and must not be automatically added.
        • uslm:authority An <authority> is a note included to indicate the authority behind a provision. In the CFR and statutes at large, the <authority> is the law which authorizes the regulation.
        • uslm:source A <source> is a note included to indicate the source of a provision. In the CFR, the <source> is a citation to an entry in the Federal Register where the provision is sourced. <source> is similar to <sourceCredit> in the U.S. Code, but is specifically called "Source" in the CFR.
        • uslm:effectiveDateNote An <effectiveDateNote> is a note to indicate the effectivity of a provision. In the CFR, the <effectiveDateNote> contains a heading, explanatory text, and sometimes the text of the provision that will become effective on that date. Some of this new text may be elided.
        • uslm:frDocId An <frDocId> is a note identifying the Document ID of an entry in the Federal Register.
        • uslm:billingCode A <billingCode> is a note containing the billing code of an item. It is used, for example, in the Federal Register.
        • uslm:editionNote An <editionNote> is a note that describes the edition of the document. It is used, for example, in the preface of the CFR for the "Official Edition Notice".
        • uslm:organizationNote An <organizationNote> is a note that identifies an organization associated with the document. It is used, for example, in the preface of the CFR and the statutes at large to identify the organization that publishes the document.
        • uslm:citationNote A <citationNote> is a note that gives information about how to cite this document and/or about citations within the document. It is used, for example, in the preface of the CFR.
        • uslm:explanationNote An <explanationNote> is a note that gives an explanation. It is used, for example. in the preface in the CFR and statutes at large to explain the document.
        • uslm:findingAidsNote A <findingAids> element is one or more finding aids, typically found in the back matter of a publication. It is used, for example, in the back matter of the CFR.
          • from subst. group uslm:notes
        • uslm:notes The <notes> is a container for sets of individual notes.
        • uslm:legislativeHistory A <legislativeHistory> contains a set of notes about a piece of legislation. It is typically found at the end of a Public Law. This element does not contain the 'amended by' or 'amended through' information associated with a statute compilation; there are meta elements defined for that purpose.
          • from subst. group uslm:footnote
        • uslm:footnote A <footnote> is a note that is to be rendered at the bottom of a page or column or table. It typically has a corresponding <ref idref="xxx"> element, where the @idref matches the @id of the <footnote>.
        • uslm:sidenote A <sidenote> is a note that is to be rendered in the side margins of a page. It may have a corresponding <ref idref="xxx"> element, where the @idref matches the @id of the <sidenote>.
        • uslm:endnote An <endnote> is a note that is to be rendered at the bottom logical unit of content. The logical unit can be specified in the @relativeTo attribute. It typically has a corresponding <ref idref="xxx"> element, where the @idref matches the @id of the <endnote>.
        • uslm:ear An <ear> contains the text to be printed in the outside margin. It is used, for example, in the CFR.
          • from subst. group uslm:page
        • uslm:page A <page> is an element indicating where a page boundary occurred. The content will typically be the page number.
        • uslm:line A <line> is an element indicating where a line boundary occurred. The content will typically be the line number, and possibly also the page number.
    • Sequence [1..*]
      1. Choice [1..1]
          from subst. group uslm:text
        • uslm:text The <text> element is a base class for <chapeau>, <continuation>, <proviso>, <def> and any other type of text that can be interspersed in the hierarchy of a document. It is similar to the <content> tag, but has more limited applicability. In general, use the <content> tag when a hierarchical level is made up largely of general content and use one of the derivatives of the text tag when limited text is found interstitially between levels or other tags.
        • uslm:chapeau Use a <chapeau> whenever there is introductory text that comes before lower levels in a level hierarchy and the text alone is not permitted by the content model.
        • uslm:continuation Use a <continuation> for interstitial text or whenever there is final text that comes after lower levels in a level hierarchy and the text alone is not permitted by the content model.
        • uslm:proviso Used for a proviso interspersed between levels in a hierarchical structure. This element may also be a child of a content, continuation, or chapeau element.
          • from subst. group uslm:level
        • uslm:level A <level> is the general container for the main provisions of legislation, often organized as a hierarchy.
        • uslm:preliminary A <preliminary> level is used to create a hierarchical region of the main document consisting of preliminary clauses that are outside of the main document hierarchy.
        • uslm:title A <title> is the top hierarchical level of a legislative document. When naming a title, use the case-sensitive prefix "t".
        • uslm:subtitle A <subtitle> is a hierarchical level of a legislative document. When naming a subtitle, use the case-sensitive prefix "st".
        • uslm:part A <part> is a hierarchical level of a legislative document. When naming a part, use the case-sensitive prefix "pt".
        • uslm:subpart A <subpart> is a hierarchical level of a legislative document. When naming a subpart, use the case-sensitive prefix "spt".
        • uslm:division A <division> is a hierarchical level of a legislative document. When naming a Division, use the case-sensitive prefix "d".
        • uslm:subdivision A <subdivision> is a hierarchical level of a legislative document. When naming a subdivision, use the case-sensitive prefix "sd".
        • uslm:chapter A <chapter> is a hierarchical of a legislative document. When naming a chapter, use the case-sensitive prefix "ch".
        • uslm:subchapter A <subchapter> is a hierarchical level of a legislative document. When naming a subchapter, use the case-sensitive prefix "sch".
        • uslm:article An <article> is a used in bills. When naming an article, use the case-sensitive prefix "a".
        • uslm:subarticle A <subarticle> is used in bills. When naming a subarticle, use the case-sensitive prefix "sa".
        • uslm:compiledAct An <compiledAct> is used in title appendices. When naming a compiledAct, use the case-sensitive prefix "cact".
        • uslm:courtRules <courtRules> is used in title appendices. courtRules is a containment level that is not named.
        • uslm:courtRule A <courtRule> is used in appendices. When naming a courtRule, use the case-sensitive prefix "crule".
        • uslm:reorganizationPlans <reorganizationPlans> are used in title appendices and the statutes at large. reorganizationPlans is a containment level that is not named.
        • uslm:reorganizationPlan A <reorganizationPlan> is used in title appendices. When naming a reorganizationPlan, use the case-sensitive prefix "rplan".
        • uslm:section A <section> is the primary hierarchical level in a USC Title, bill or other formally structured document. When naming a section, use the case-sensitive prefix "s".
        • uslm:subsection A <subsection> is an optional hierarchical level below a section. Subsections are usually numbered with lower-case letters.
        • uslm:paragraph A <paragraph> is a numbered level usually found below a subsection in the document hierarchy. Paragraphs are usually numbered with Arabic numbers.
        • uslm:subparagraph A <subparagraph> is a level below a paragraph in the document hierarchy. Subparagraphs are usually numbered with upper-case letters.
        • uslm:clause A <clause> is an optional below-section hierarchical level. Clauses are usually numbered with lower-case Roman numerals.
        • uslm:subclause A <subclause> is an optional hierarchical level below a clause. Subclauses are usually numbered with upper-case Roman numerals.
        • uslm:item An <item> is a level usually below a subclause in the document hierarchy. Items are usually numbered with double lower-case letters.
        • uslm:subitem A <subitem> is a level below an item in the document hierarchy. Subitems are usually numbered with double upper-case letters.
        • uslm:subsubitem A <subsubitem> is a level below a subitem in the document hierarchy. Subsubitems are usually numbered with triple lower-case letters.
        • uslm:crossHeading A cross heading is an interstitial heading appearing between level items, but is not part of the hierarchy.
          • from subst. group uslm:leftRunningHead
        • uslm:leftRunningHead A <leftRunningHead> contains the text to be printed in the left hand running header. It is used, for example, in the CFR.
        • uslm:centerRunningHead A <centerRunningHead> contains the text to be printed in the center running header. It is used, for example, in amendment documents.
        • uslm:rightRunningHead A <rightRunningHead> contains the text to be printed in the right hand running header. It is used, for example, in the CFR.
        • uslm:slugLine The <slugLine> contains the information that may be printed on the slug (footer) line. This is the USLM equivalent to the I90 line.
        • uslm:appropriations Appropriations elements are used in bills.
      2. Choice [0..*]
          from group uslm:NoteStructure
          from subst. group uslm:note
        • uslm:note A <note> is a generic element for a note associated with items in the document.
        • uslm:elided An <elided> element is a replacement for text content that has been elided or omitted from this document. The optional ref attribute may point to the text that was elided. The <elided> element may only contain text content (typically asterisks, called 'stars').
        • uslm:sourceCredit A <sourceCredit> is a note included to indicate the source of a provision. It usually will contain a reference to the source of the provision and the Statute(s) that have affected it. Source credits are usually set out in parenthesis. The surrounding parentheses are shown in the text - they are not automatically added.
        • uslm:uscNote A <uscNote> is a note below sections and big-level headings in the U.S. Code.
        • uslm:statutoryNote An <statutoryNote> is a note that becomes part of the law.
        • uslm:drafterNote A <drafterNote> is a note that does not become part of the law. It is used by drafters for their own purposes (commenting out a section of drafted content, for example, or asking questions, or proposing alternative wording) and is generally deleted before the document is published to others.
        • uslm:editorialNote An <editorialNote> is a note included for editorial purposes only. While present in the text of the document as printed, it is not a part of the law. Editorial notes are often used to record where provisions have been omitted or other changes have been made, or in a preface of the CFR.
        • uslm:changeNote A <changeNote> is a note that records a non-substantive change that has been made to the US Code. Usually change notes are set out in square brackets and these must be set out in the text and must not be automatically added.
        • uslm:authority An <authority> is a note included to indicate the authority behind a provision. In the CFR and statutes at large, the <authority> is the law which authorizes the regulation.
        • uslm:source A <source> is a note included to indicate the source of a provision. In the CFR, the <source> is a citation to an entry in the Federal Register where the provision is sourced. <source> is similar to <sourceCredit> in the U.S. Code, but is specifically called "Source" in the CFR.
        • uslm:effectiveDateNote An <effectiveDateNote> is a note to indicate the effectivity of a provision. In the CFR, the <effectiveDateNote> contains a heading, explanatory text, and sometimes the text of the provision that will become effective on that date. Some of this new text may be elided.
        • uslm:frDocId An <frDocId> is a note identifying the Document ID of an entry in the Federal Register.
        • uslm:billingCode A <billingCode> is a note containing the billing code of an item. It is used, for example, in the Federal Register.
        • uslm:editionNote An <editionNote> is a note that describes the edition of the document. It is used, for example, in the preface of the CFR for the "Official Edition Notice".
        • uslm:organizationNote An <organizationNote> is a note that identifies an organization associated with the document. It is used, for example, in the preface of the CFR and the statutes at large to identify the organization that publishes the document.
        • uslm:citationNote A <citationNote> is a note that gives information about how to cite this document and/or about citations within the document. It is used, for example, in the preface of the CFR.
        • uslm:explanationNote An <explanationNote> is a note that gives an explanation. It is used, for example. in the preface in the CFR and statutes at large to explain the document.
        • uslm:findingAidsNote A <findingAids> element is one or more finding aids, typically found in the back matter of a publication. It is used, for example, in the back matter of the CFR.
          • from subst. group uslm:notes
        • uslm:notes The <notes> is a container for sets of individual notes.
        • uslm:legislativeHistory A <legislativeHistory> contains a set of notes about a piece of legislation. It is typically found at the end of a Public Law. This element does not contain the 'amended by' or 'amended through' information associated with a statute compilation; there are meta elements defined for that purpose.
          • from subst. group uslm:footnote
        • uslm:footnote A <footnote> is a note that is to be rendered at the bottom of a page or column or table. It typically has a corresponding <ref idref="xxx"> element, where the @idref matches the @id of the <footnote>.
        • uslm:sidenote A <sidenote> is a note that is to be rendered in the side margins of a page. It may have a corresponding <ref idref="xxx"> element, where the @idref matches the @id of the <sidenote>.
        • uslm:endnote An <endnote> is a note that is to be rendered at the bottom logical unit of content. The logical unit can be specified in the @relativeTo attribute. It typically has a corresponding <ref idref="xxx"> element, where the @idref matches the @id of the <endnote>.
        • uslm:ear An <ear> contains the text to be printed in the outside margin. It is used, for example, in the CFR.
          • from subst. group uslm:page
        • uslm:page A <page> is an element indicating where a page boundary occurred. The content will typically be the page number.
        • uslm:line A <line> is an element indicating where a line boundary occurred. The content will typically be the line number, and possibly also the page number.
      3. uslm:signature [0..*] A <signature> consists of a name and, any of the optional elements role, affiliation, and date. Both the name and the role may be hyperlinked to something which identifies the person or role.

Used in