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

uslm:backMatter

 
            A <backMatter> is a container for the back matter at the end of a
            document.

Element information

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

Schema document: uslm-components-2.1.0.xsd

Type: uslm:BackMatterType

Properties: Global, Qualified

Content

  • Any text (mixed) content, intermingled with:
  • 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.
      • from subst. group uslm:index
    • uslm:index An <index> is an index element. An index can appear before or after the main content of the document. The most common use for an <index> is as a basis of elements that have specific names for the specific type of item that is indexed or listed, such as the <listOf...> elements. The <index> element is closely related to the <toc> element.
    • uslm:tableOfTitlesAndChapters A <tableOfTitlesAndChapters> is a table of titles and chapters.
    • uslm:listOfAgencies A <listOfAgencies> is a list of agencies. It is found for example in the back matter of the CFR.
    • uslm:listOfSectionsAffected A <listOfSectionsAffected> is a list of sections that are affected. It is found for example in the back matter of the CFR.
    • uslm:listOfBillsEnacted A <listOfBillsEnacted> is a list of bills enacted into law; either public law or private law. It is found for example in the front of the Statutes at Large.
    • uslm:listOfPublicLaws A <listOfPublicLaws> is a list of public laws. It is found for example in the front of the Statutes at Large.
    • uslm:listOfPrivateLaws A <listOfPrivateLaws> is a list of private laws. It is found for example in the front of the Statutes at Large.
    • uslm:listOfConcurrentResolutions A <listOfConcurrentResolutions> is a list of concurrent resolutions. It is found for example in the front of the Statutes at Large.
    • uslm:listOfProclamations A <listOfProclamations> is a list of presidential proclamations. It is found for example in the front of the Statutes at Large.
    • uslm:popularNameIndex A <popularNameIndex> is a list of popular names for acts. It is found for example in the back of the Statutes at Large.
    • uslm:subjectIndex A <subjectIndex> list is an index of subjects. It is found for example in the back of the Statutes at Large.
    • 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.
      • 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.
      • 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.

Attributes

NameOccTypeDescriptionNotes
xml:base [0..1]xsd:anyURIdenotes an attribute whose value provides a URI to be used as the base for interpreting any relative URIs in the scope of the element on which it appears; its value is inherited. This name is reserved by virtue of its definition in the XML Base specification.from group uslm:XmlSpecialAttrs
xml:lang [0..1]Anonymousdenotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. from group uslm:XmlSpecialAttrs
xml:space [0..1]Anonymousdenotes an attribute whose value is a keyword indicating what whitespace processing discipline is intended for the content of the element; its value is inherited.from group uslm:XmlSpecialAttrs
id [0..1]xsd:ID The @id attribute should always be assigned an immutable (non-changing) value. If the item is subject to renaming or renumbering, then the @id attribute should not reflect any part of the changeable part. This is to allow the @id to be long lasting without causing confusion should the item be renamed or renumbered. The @id should be prefixed with "id" and followed by a GUID that is guaranteed to be globally unique across both time and space. As an "xsd:ID", the identity must be ensured to be unique in the document - and it is a good idea that it be guaranteed globally unique. As the @id is immutable, it is a good identity with which to associate external information to the item. If an item is deleted and later a similarly named item is created, then the new item should be assigned a newly generated identity as it is not the same item as the earlier item. The @id attribute is optional, but recommended for all elements which will contain any other identity attributes. from group uslm:IdentificationGroup
temporalId [0..1]uslm:MediumStringSimpleType The @temporalId attribute is a name, scoped to the document, that is intended to reflect the current identify of the element in a human-readable way. This means that the @temporalId may need to be recomputed based on the temporal state of a document or according to the temporal specification in a requesting URL. A @temporalId is intended to be scoped to the document as a whole while the @name is scoped to its immediate parent. The @temporalId is built as an "_" separated hierarchy of @name or, in the absence of an @name, element names. However, in a couple cases, the levels of the hierarchy are suppressed. First of all, the <main> level is suppressed when calculating any @temporalId contained within. Secondly, when dealing with sections which are numbered as a sequence without regard to the upper levels, then the upper levels are suppressed from the computation of the @temporalId. Some examples: * "s2" - section 2 in the main part of the document * "schedule_s2" - section 2 in the schedule * "pt2_d1" - division 1 of part 2 in the main part of the document The @temporalId attribute is optional. from group uslm:IdentificationGroup
identifier [0..1]uslm:LongStringSimpleType Use the @identifier attribute to specify the URL context of the element. Typically, the @identifier will be established on the root element or on any element, such as a <quotedContent> element, that changes the context. The @identifier attribute is optional. from group uslm:IdentificationGroup
scope [0..1]uslm:LongStringSimpleType Use the @scope attribute to specify the scope within which the @identifier attribute is valid. Typically, @scope is formatted as a URL, referring to a specific context. @scope is used for terms within in definitions to specify the scope of the definition. The @scope attribute is optional. from group uslm:IdentificationGroup
role [0..1]uslm:ShortStringSimpleType Use the @role attribute to provide further refinement to an element's type. This is particularly useful when defining a refinement of an element from the abstract set. Another possible use is to use the customary local name for an element whenever the element name is not a complete match. For example, if the customary name for an "explanation" is "summary", then the element can be expressed as <explanation role="summary">. There is a rough equivalence between an element of a base class with a @role attribute and a derived class in the schema, although this equivalence is not explicit. For example <level role="division"> is roughly equal to <division>. When transforming XML to HTML, the @role attribute should be appended to the element name using an "_" underscore and used as the first value in the HTML @class attribute. If desired, the proposed XHTML @role attribute can be computed as either the XML @role attribute or, in the absence of the XML @role attribute, the XML element name. For example: <level role="division"> => <div role="division" class="level_division"> <division> => <div role="division" class="division"> This approach is easily reversible. In a similar way to the @class attribute, multiple role values can be specified in a space separated list. from group uslm:ClassificationGroup
class [0..1]uslm:MediumStringSimpleType The @class attribute corresponds to the @class attribute in HTML. It can be used to specify presentation characteristics of an element that are not specified by the element name and the @role attribute. For example, the @class attribute can be used to specify the presence or absence of the ending separator. Like the HTML @class attribute, multiple class values can be specified in a space separated list. from group uslm:ClassificationGroup
style [0..1]uslm:LongStringSimpleType The @style attribute is used to specify CSS attributes that override the default styles defined for an element or an element class. The current loose-leaf publication standards should be specified using an external style sheet and the use of the @style attribute should be reserved for exception cases where the default presentation must be overridden. from group uslm:ClassificationGroup
styleType [0..1]uslm:StyleTypeEnum The @styleType attribute is used to set the overall semantic type of the block. This has rendering implications. Only a small set of values is allowed. Default value is "OLC". from group uslm:ClassificationGroup
note [0..1]uslm:LongStringSimpleType The @note attribute should be the primary mechanism for recording simple text notes to be associated with elements. from group uslm:AnnotationGroup
alt [0..1]uslm:LongStringSimpleType The @alt attribute should be used to provide an alternative description of the element. For use with WCAG 2.0 and other accessibility initiatives. from group uslm:AnnotationGroup
meta [0..1]uslm:LongStringSimpleType The @meta attribute should be used to associate metadata information with the element for search and other uses. How this attribute is used is not prescribed by the schema. from group uslm:AnnotationGroup
misc [0..1]uslm:LongStringSimpleType The @misc attribute is provided for future use. from group uslm:AnnotationGroup
draftingTip [0..1]uslm:LongStringSimpleType The @draftingTip is for internal use. from group uslm:AnnotationGroup
codificationTip [0..1]uslm:LongStringSimpleType The @codificationTip is for internal use by the OLRC. from group uslm:AnnotationGroup
title [0..1]uslm:MediumStringSimpleType The @title attribute is used to specify the text describing the element in a table of contents or index. It must be a simple text string and should consist of fewer than 40 or so characters - although this is not enforced. from group uslm:DescriptionGroup
brief [0..1]uslm:LongStringSimpleType The @brief attribute is an alternate method for providing a longer description of an element, limited to 1024 characters. from group uslm:DescriptionGroup
sortOrder [0..1]xsd:integer The @sortOrder attribute is used to specify a sorting order for a list of items, when that sort order is not the document sequence. The @sortOrder value must be specified as a positive integer. This attribute should rarely be used. from group uslm:DescriptionGroup
startPeriod [0..1]uslm:DateSimpleType The @startPeriod attribute is the earliest date that a particular version applies to. The @startPeriod is not necessarily the effective date. It's merely the earliest date that the particular version of the text should be returned in point-in-time calculations. The @startPeriod works with the @endPeriod which defines that last date that a specific version applies to. Together, the @startPeriod and the @endPeriod define a period of time that the version applies to. This version may be in states such as pending, operational, partially commenced, suspended, or even repealed. If the @startPeriod is not specified, then all past time is assumed. from group uslm:VersioningGroup
endPeriod [0..1]uslm:DateSimpleType The @endPeriod attribute is the last date that a specific version of the text should be returned in point-in-time calculations. If the @endPeriod is not specified, then all future time is assumed. from group uslm:VersioningGroup
status [0..1]uslm:StatusEnum The @status attribute is used to show the status of a version of provision. This attribute works with the @startPeriod and the @endPeriod and applies to the period of time defined by these attributes. from group uslm:VersioningGroup
partial [0..1]xsd:boolean The @partial attribute is used, in conjunction with the @status attribute to indicate that the status is not fully applied. from group uslm:VersioningGroup
inEffect [0..1]xsd:boolean The @inEffect attribute is used to indicate whether the level or provision is currently in effect. The default value is 'true'. Note that the @status attribute also contains information about the state of a provision. If the value of the @status attribute is anything other than 'inEffect' the value of the @inEffect attribute should be 'false'. The net effect of contradictory values of these two attributes is not defined. from group uslm:VersioningGroup
Any attribute [0..*]Namespace: ##other, Process Contents: laxfrom type uslm:BaseBlockType

Used in

Sample instance

<uslm:backMatterNamespace: ##other, Process Contents: laxfrom type />