Schema that includes the redefinitions for USLM/XHTML tables.
MathML3 Schema without modifications.
or
element, that changes the context.
* The @temporalId attribute that is intended to provide a changeable, human-meaningful,
identifier. Like the @name attribute, the @temporalId will vary with
time. For this reason, the @temporalId is computed each time a document
is extracted from the repository, based on the point-in-time requested,
rather than being statically stored with the text in the repository. The
@temporalId is specified to be nominally unique within the document to which
the element belongs. The @temporalId is composed by concatenating the
@temporalId of the element's parent, if existing (or the parent element's
name if the @temporalId does not exist), "_", and the element's
@value. For example, paragraph 2 of subsection (a) of section 1 should
have the @temporalId of "s1_a_2". This attribute is not currently used.
** Referencing Model **
All references are modeled as relative URLs. References are made to
a logical rather than a physical hierarchy that starts always from the
jurisdiction and reaches down to individual provisions within a bill,
resolution, or other Legislation. References do not predict or expect
any particular document partitioning. It is the intent of the URL handler
to map the logical hierarchy to any specific physical hierarchy.
The highest level of the hierarchy is always the jurisdiction code,
specified using the ISO 3166-1 country code and optionally followed by
a dash and a lower level jurisdiction code. For the U.S. Federal
Government, the jurisdiction code is "us".
Lower levels of the hierarchy should use an abbreviated prefix or a numeric/
alphabetic entry to identify the target. Each level in the reference is
separated with the "/" in a hierarchy. For instance, Title 5 is expressed
as "/us/usc/t5" while Pub. L. 111-314 is expressed as "/us/pl/111/314".
When a URL is extended to within a document, the document hierarchy is
expressed in an abbreviated form as in "/us/usc/t5/s101" or
"/us/pl/111/314/s1". To build this URL, append the reference to the
document with "/" + the level designators. So a reference to "title 2 of
division 3 of public law 113-314" would be "/us/pl/111/314/d3/t2".
A language-neutral reference does not include a language code. To
create a reference to a specific language version of the document,
include a language identifier using the three-letter system defined in
ISO 639-2, as used by the Library of Congress, using the Bibliographic
language code (B) where there is a choice.
(https://www.loc.gov/standards/iso639-2/php/code_list.php)
For instance, to specify a reference to section 101 of the English version
of title 51, the reference would be "/us/usc/t51@eng/s101".
This should be used in conjunction with the xml:lang attribute with the correct value.
To make a reference to a specified version of a provision or
level, an "@" symbol is used. For instance, to specify a reference to
section 101 of Title 51 on 1 February, 2013, the reference would be
"/us/usc/t51@2013-02-01/s101", which uses the ISO time reference
system. The version specification could also be an arbitrary name or
relative date, such as 'pre-1824' or 'v1.1.1'. A version string that is
not a date must not begin with a number, to avoid confusion with dates.
Version strings must not contain special characters or spaces.
For compability with AKN, or when including both a language and version
specification, the "!" designator may also be used for a
language-specific version of a provision instead of the "@" designator,
e.g., "/us/stat/53/1561!nor" for the Norwegian version of "/us/stat/53/1561!eng".
When including both a language and a version specification, place
the language specification ahead of the version specification. For
instance to combine both examples above, the result would be
"/us/usc/t51!eng@2013-02-01/s101" or "/us/usc/t51!eng@v1.1.1/s101".
]]> element, to be given a type specification. If the
@type attribute is not specified, then the default type is "bag".
The type values are inspired by the Resource Descriptor Framework
(RDF).
]]> level
or lower, but the model is general enough that it can be applied
anywhere in the level hierarchy.
]]> 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.
]]>
element, that changes the context.
The @identifier attribute is optional.
]]>.
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
is roughly equal to .
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:
=>
=>
This approach is easily reversible.
In a similar way to the @class attribute, multiple role values
can be specified in a space separated list.
]]>
and
elements can use the reference group.
All attributes are optional.
]]> element, then the referencing
element builds on top of that reference, acquiring its attributes
as default values (which may be overridden by local values). This
is a recursive structure; an element may, through the @idref
attribute, point to an element which itself builds on
another element, and so on. This is to support the complex
referencing sometimes found in legislation.
]]> and
elements.
]]>, , and elements.
]]> element,
that changes the context.
The @identifier attribute is optional.
]]> element, , and
elements are allowed in the ToC or index 1 or more times.
]]> element is a primitive element to be used to mark or
denote a spot in the text. It can be used in the areas or
anywhere else where an element is expected. The
element contains no text.
]]> element is a primitive element to be used within
areas or within any other areas which can accept
inline content.
]]> element is a primitive element to be used anywhere
where elements are permitted including within
elements or anywhere where elements have been explicitly
permitted.
]]> element is a primitive element to be used anywhere
where a very general content model is desired, including within
other elements.
]]> ... is the enclosing tag
* is a required child
* [] is an optional child
* []? is a sequence of zero or one child elements
* []* is a sequence of zero or more child elements
* | is either child1 or child2
* [|] is either child1 or child2 or neither
* [|]* is a sequence of zero or more child1s or
child2s in no particular pattern
Basic Model:
* [][][][][][][]*
* [|]*
* [||]+
* [? is used 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..
]]> contains information about the actions associated
with the document.
]]> is used in the preface and meta to hold a set of
relatedDocument elements that are related to each other. This is used
when multiple report parts are referenced, for example.
The element is used for individual references to documents.
In USLM 2, only related documents that are specifically added by the clerk or
drafter are to be added to the USLM relatedDocument elements.
]]> contains information about the actions associated
with the document.
]]> is used in the preface and meta to hold a set of
relatedDocument elements that are related to each other. This is used
when multiple report parts are referenced, for example.
The element is used for individual references to documents.
In USLM 2, only related documents that are specifically added by the clerk or
drafter are to be added to the USLM relatedDocument elements.
]]> from a public law.
]]>†"
where the dagger is the indicator. An endnote or footnote
reference should always use the @idref attribute to point to
an endnote or a footnote within the document.
]]> contains the alpha-numeric part of an item in a table of
contents or index. It is typically the number of the item (e.g. "Part 1").
]]> contains the textual part of an item in a table of contents
or index. It is typically the heading of the item (e.g. "Definitions").
]]> is a reference to the target in a table of contents or index.
It is typically found in the last column and may contain like the page
number or beginning section number. It has the usual attributes for references.
]]> are also allowed to be nested in a referenceItem.
]]> area,
properties can also be found in the main container.
Elements derived from the core and defined
within the property substitution group can also be
used.
]]> property and
included in the block substitution group, such as
approval signatures, can be placed in the main
container.
]]> property and included in the statement
substitution group can be placed in the main
container.
]]> body of the document may have a table of
contents. This may be authored or generated. The
model permits multiple elements.
]]> contains information about the actions associated
with the document.
]]>, closing ,
or a may be interspersed between levels in a hierarchical
structure.
]]> can, in some cases, begin with a heading.
]]> can be made up of a series of recitals.
Recitals typically begin "Whereas,".
]]> is present, the enacting formula
ends the preamble in a Bill.
]]> is present, the resolving clause
ends the preamble in a Resolution.
]]> is contains a series of statements,
typically before the words-of-issuance.
]]> may contain signatures, usually before
the words-of-issuance.
]]> is usually numbered. However, in a few cases,
typically preliminary sections or with item lists, this
may not be the case.
]]> may have a heading, but this is not required.
]]> will be manually defined
rather than generated.
]]>. This may not exist in
cases where the level has been repealed, omitted, spent,
or otherwise removed and a simple note has been left
behind.
]]> element can have multiple headings and sub-headings.
]]> element should surround the complete text of the number
including any preceding prefix and any decoration and punctuation.
This is to allow the complete text to be properly displayed in
the published form.
Numbers can be used for either single values or for number ranges.
]]> content. When the text content represents a
range of values, use the @beginValue and @endValue
attributes to record the range.
]]> element is a set of note elements.
Typically, rather than using the abstract
element, the note will be a more specific elements
like , etc.
]]> element is the text that is rendered in
place of the elided material. This content may be determined by
organizational conventions, such as the three- five- and seven- stars
found in the Federal Register. The content might also be authored to
indicate where the elided content can be found.
]]> may or may not be numbered.
]]> may or may not have a heading.
]]> may or may not have a table of contents.
]]> is to be included by reference, use the
@src attribute with a normal URL to point to the document
to be included.
]]> contains information about the actions associated
with the document.
]]> is used in the preface and meta to hold a set of
relatedDocument elements that are related to each other. This is used
when multiple report parts are referenced, for example.
The element is used for individual references to documents.
In USLM 2, only related documents that are specifically added by the clerk or
drafter are to be added to the USLM relatedDocument elements.
]]> is a statement that sets out the purposes of the bill
in general terms. Typically, it includes a followed by an
. Display of the content is suppressed in the rendered
document using the attribute @display set to "no".
]]> element allows for text such as 'Attest:'
to be placed once per block, or for each .
]]> may contain other collections.
]]> contains an individual item
of a collection.
]]> may come between items in a collection.
This allows page breaks.
]]> is a generic container for an individual item. The
content may be contained in the item, or the content may be included
by reference.
Components are typically used in collections, but may exist in other
parts of the document.
]]> element should apply to a different temporal period.
Notes will typically only follow a when found in a repealed,
omitted, spent, or otherwise removed section or level that is being
noted.
]]> should exist only once for a single temporal period.
Multiple headings are permitted to support versioning without having
to create a whole new parent level or appendix. This is
important in hierarchical upper levels where it is not desirable to
generate a whole new level should part of the heading change.
Use the optional in cases where there is one or more
subheadings to the parent item. Like the element,
different elements can be added to apply to different
temporal periods.
Notes may follow the heading. Often this is a source note.
]]>
followed by optional notes.
]]>
(such as a or ) followed by optional notes.
]]>, an
, or a can exist within the
part of a . When a is used, the
or is found within the
, at the bottom.
Notes may be defined after the , ,
or .
]]> elements should only be used for cases
where the content has been versioned and it is not desirable
to create a whole new version of the parent level. This use
case should be very rare.
]]>, an interstitial or
closing , or a .
]]> is not the lowest level of a hierarchy, it
will primarily be made up of child levels.
It is generally desirable to push all versioning down to
lower elements to avoid replicating large portions of
the document to support version changes. This means that
the , , and elements should
be defined across different temporal periods rather than
defining elements across temporal periods.
However, elements can be defined with the
temporal attributes and this applies to the lower levels,
such as the level, where practical
considerations necessitate versioning at the
element.
]]> is a base level element representing all types of
legislative documents.
]]> is a base level element for loosely structured
documents.
]]> block contains properties and sets of properties recording
metadata about the document. The information contained within the
meta block is not part of the official law and should not be printed
as such. Ordinarily, all text content in a document is intended for
publication in textual representations of the document. However,
this is not the case for textual content in the block. If,
for instance, a property in the meta block has text content, it
does not automatically become text to be included in a published
form. However, in some case this may be desirable and can be done.
However, the meaning is not implicit.
The block may contain elements from the Dublin Core. These have
the meanings as defined in Dublin Core, except for the dc:date element
in bills and resolutions. Enrolled bills do not have a dc:date element
defined except for Concurrent Resolutions. In other bill and resolution
stages, and in Concurrent Resolutions, the dc:date is defined as the
last action date for that document stage.
]]> is a simple value recorded with the document. Typically
properties are stored in the and/or blocks of the document.
If a property in the block has textual content, then this
text is not intended for publication. However, if a property in the
block has textual content, then this text is intended for publication.
]]> is a grouping of properties in the block. Sets
themselves can contain other sets. Sets can be typed using the
@type attribute with the SetTypeEnum enumeration. By default, sets
are simply unordered bags of properties.
]]> is a table of contents. A table of contents can appear in a
number of locations in document. A table of contents can appear in
three different locations:
- It can appear anywhere within the top of the element,
before the levels.
- It can appear in any level following the , ,
and any notes.
- It can appear in an .
]]> is a table of contents. A table of contents can appear in a
number of locations in document. A table of contents can appear in
three different locations:
- It can appear anywhere within the top of the element,
before the levels.
- It can appear in any level following the , ,
and any notes.
- It can appear in an .
]]> is a table of titles and chapters.
]]> is a list of agencies. It is found for example in the back
matter of the CFR.
]]> is a list of sections that are affected. It is found
for example in the back matter of the CFR.
]]> 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.
]]> is a list of public laws. It is found for example in the
front of the Statutes at Large.
]]> is a list of private laws. It is found for example in the
front of the Statutes at Large.
]]> is list of concurrent resolutions. It is found
for example in the front of the Statutes at Large.
]]> is a list of bills presidential proclamations. It is
found for example in the front of the Statutes at Large.
]]> is a list of popular names. It is found for example in the
back of the Statutes at Large.
]]> list is an index of subjects. It is found for example in the
back of the Statutes at Large.
]]> is an item in a ToCIndex that refers to specific content
in the document (versus a concept or a grouping). The referenceItem may also
contain lower level referenceItems if the content being referred to contains
lower level content.
]]> is an item in a ToCIndex that is a columnar-type heading for
the items below it. e.g. “Sec.” or “Page”. This is commonly repeated on
following pages.
]]>
is an item in a ToCIndex that collects a number of referenceItems
or other groupItems under a heading. The groupItem may or may not refer to a
specific place in the document. groupItems may also contain nested groupItems.
]]> is a reference to a numbered item in a table of contents or index.
It has attributes for leaders.
]]> is a textual reference in a table of contents or index.
It has attributes for leaders.
]]> is a reference to the target in a table of contents. This is
used to provide various items in the last column of the multiple column table of
contents entry. It has the usual attributes for references.
]]> is the primary container for the body of a legislative
document.
]]> is the general container for the official and document
titles as well as for heading sections in FR rulePreambles.
]]> is a container for the "Whereas" clauses and the
enacting formula. Modern practice is to not use the preamble,
but to use a standalone enacting formula. However, for the rare
cases where a preamble is desired, the elements are available.
]]> is a preliminary statement in a bill stating the reasons
for the Bill. Modern legislation seldom uses a recital although it
can still occur.
]]> is a special type of statement that begins with "resolved",
that is specified just before the main content of the resolution. The
can appear as either the last statement in a preamble or,
when a preamble is not present, standalone within the main element just prior
to the main provisions.
]]> is specified just before the main provisions of
a bill. The can appear as either the last statement
in a preamble or, when a preamble is not present, standalone within
the main element just prior to the main provisions.
]]> is a container for the statements, signature blocks, and words-of-issuance
within a Rule or Proposed Rule in the Federal Register.
]]> is a special type of statement that introduces the content
of a regulation rule or proposed rule. The is the last
statement in a rule preamble.
]]> is the general container for the main provisions of
legislation, often organized as a hierarchy.
]]> element is used for nesting
the various levels of appropriation agencies, bureaus, and
departments, as well as the various budget areas within those
agencies, bureaus, and departments.
The level attribute is used to distinguish major, intermediate,
and small levels of nesting.
]]> surrounds the numeric designation assigned to a level
in legislation. Numbering is not always present. The number should
always include the surrounding decoration including descriptive
text and parenthesis and grammar. This number should never be
auto-generated. A normalized value based on the text content of the
element should be stored in the @value attribute.
]]> element is a base class for , ,
, and any other type of text that can be interspersed
in the hierarchy of a document. It is similar to the tag,
but has more limited applicability. In general, use the
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.
]]> is an optional part of a level element and various other
elements. The heading is based on the content primitive and can contain
various elements including definitions.
]]> is an optional part of a level element and various
other elements. Like the heading, the subheading is based on the
content primitive and can contain various elements including
definitions. A subheading should only be created if a heading
already exists.
]]> is a non-hierarchical heading construct which can
be placed within and amongst heading levels. A acts
as a divider, separating items within a level.
Cross headings are typically shown as center-aligned headings
without any level identification or level numbering.
]]> is an atomic-level amendment instruction. The amending action
contains the text related to that action and the type of amending action to be
performed as well as optional attributes that old more information.
]]> is a generic element appended to the main part of a
document. Appendices can either be inline or included via a @src
reference.
]]> is a type of appendix.
It can contain a wide variety of content and the containment model is
consequently relatively loose. A is often a list of numbered items,
sometimes arranged in columns. Sometimes a schedule is a list of
consequential amendments. Schedules can also be tables or documents
defined externally such as extradition treaties or trade agreements.
Schedules are sometimes printed in a landscape rather that portrait
orientation.
]]> is a container for the back matter at the end of a
document.
]]> 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.
]]> element is a reference or link to another document, a
location within another document, or a location with the same
document.
]]> element is a wrapper around dates. A normalized value
of the date text can be stored in the @date attribute or in the
@startDate and @endDate attributes in the case of a date range.
]]> element is used for an extraction of simple text from
another source or origin. If the quoted text is to have literal
quotes surrounding it, then those characters must be included in the
text surrounding the quoted text. The element does not
generate those characters. By convention such characters are placed
around the quotedText tags, not within the tags.
Quoted text is seen in bills that amend law. The
element is not used for other cases where quote characters may appear,
such as place names or titles.
]]> 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, amendments,
and modifications. If the quoted content is to have literal quotes
within it, then those characters must be included in the text. The
element does not generate those characters.
]]> is the container for a collection of items or components.
]]> is an item or a reference to an item within a collection.
]]> element is used to contain an arbitrary fragment of
a USLM document. It may be used to transport a portion of a document
between subsystems, such as retrieving a section from a repository.
Having a fragment wrapper would allow, for instance, two sibling
elements to be transported, or allow an element to be moved with
processing instructions around it.
]]> 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 element may only contain text content (typically
asterisks, called 'stars').
]]>, , and elements to denote the rows and
columns of the structure. A can be either row oriented or
column oriented.
Use layout types when describing legislative structure in a column
oriented fashion. For regular tables as shown in forms, use the defined
table structure.
]]> type can contain various types of elements
as rows including headers, rows, TOC items, blocks,
and contents. All elements, aside from elements,
are treated as rows when found directly within a layout
structure.
]]> element, any child element directly in
a element, aside from a element, is regarded as a row.
]]>
element, it can contain a wide range of text and elements.
]]>
element, it can contain a wide range of text and elements.
]]> element.
]]> element is used to denote an area of text intended to
be displayed in a columns-oriented format similar to table. Use
the , , and elements to denote the rows and
columns of the structure.
Use when describing legislative structure in a column-
oriented fashion. For regular tables as shown for forms, use HTML
tables.
]]> denotes a header row within a column-based structure.
]]> denotes a row entry within a column-based structure.
In addition to the formal element, any child element
in a element, aside from a element, is regarded as
a row. There should always be a element as an
ancestor of a . Both column and row spans may be defined for
entries.
]]> denotes a column when specified directly under a
or a cell when specified within a (or equivalent) in a
structure. There should always be a element as an
ancestor of a . Both column and row spans may be defined for
entries.
]]> is a simple paragraph. This is different from the
more complex numbered element used for
the formal paragraph level of legislative documents.
]]> is simple marker element denoting a line break.
]]> is a simple marker element denoting where a graphic
image is to be inserted. Use the @src attribute to point to the
image with a normal URL.
]]> is a unit of content, optionally with a caption, that
is self-contained, that is typically referenced as a single unit from
the main flow of the document, and that can be moved away from the
main flow of the document without affecting the document’s meaning.
A figure usually contains an element, but may instead contain
mathematical or chemical markup. This element is modelled after the
HTML5 element.
]]> represents a caption or legend for a figure. It can
appear before or after the content within the figure. This element is
modelled after the HTML5 element, although in HTML5,
only one figCaption is allowed per figure element.
]]> element contains content text that is to be centered on the page.
]]> is an inline spacer which denotes an area to be filled
in a form designed to be printed. Usually, a is rendered
as dotted lines with the text content within the tags shown
just below. If parentheses are to surround the text shown below the line,
then those parentheses should be included in the text content.
]]> is an inline tick box which denotes a box to be filled
in on an form.
]]> is a simple inline element for text that is to be rendered in bold text.
]]> is a simple inline element for text that is to be rendered in italic text.
]]> is a simple inline element for text that is to be rendered in subscript text.
]]> is a simple inline element for text that is to be rendered in superscript text.
]]> is a simple inline element for text that is to be rendered as deleted text
within a modification.
]]> is a simple inline element for text that is to be rendered as inserted text
within a modification.
]]> element is for text that bears some relationship to a
element. It may be a reference to a heading, or an amendment to a heading,
or a quoted heading. The @role attribute is used to indicate the role and
thereby styling of the typeset text.
]]> element is general purpose wrapper for text similar to an
html span. The @role attribute can be used to specify the type
of span.
]]> element is used to tag references to committees in text. It is
used, for example, in the legislative history section of a Public Laws.
]]> is the version of the title that is rendered on the
cover page. This is, for example, found on some Public Laws.
]]> is content on the cover page that is in addition to, or
instead of, the coverTitle.
]]> and
by
allowing numbering elements to be included explicitly, instead of
generating them automatically. This allows more control over the numbering.
]]>
is a document containing a pre-enactment stage amendment, which
contains a proposed change to a pending text (e.g., a bill, resolution, another amendment,
or a treaty [or an associated resolution of ratification]).
]]> is a document containing proposed law. When enacted, a
becomes a .
]]> is a document containing an Amendment to the Constitution
of the United States.
]]> (public or private law) is a document containing an approved bill,
whether public or private.
]]> is a document containing an enacted bill.
]]> is a document containing a statute compilation; these are
compilations of public laws that incorporate the amendments made to the underlying
statute since it was originally enacted.
See https://www.govinfo.gov/help/comps for more details.
]]> volume is a compilation of statutes, public and private laws,
proclamations, and concurrent resolutions.
]]> is a simple resolution, joint resolution, or concurrent
resolution, as those terms are defined by the U.S. Congress.
]]> is a document containing a title or appendix of the
U.S. Code.
]]> is a document containing a Federal Register issue or
part of a Federal Register Issue.
]]> is a document containing a regulatory rule, as found in
the Federal Register.
]]> is a document containing a regulatory notice, as found in
the Federal Register.
]]> is a document containing a presidential document,
such as a proclamation or an executive order. The Federal Register
contains presidential documents, as does a Statutes at Large volume.
]]> is a document containing a title of the Code of
Federal Regulations.
]]> is the description of the legislative action taking place.
]]> is the associated committee.
]]> is the chief sponsor.
]]> also sponsors the bill or resolution.
]]> introduces the bill on behalf of the sponsor.
]]> element allows for longer action descriptions with line
breaks.
]]> is the instruction related to the action.
]]> is a property used to identify a provision or document
that is affected by this document. The definition of this element
may change in the next (2.1) release of this schema.
]]> property is the date on which the enrolled bill was approved.
The format when used in the element is ISO 8601 YYYY-MM-DD, when used as an
inline element is 'month day, year' with the ISO date in the @date attribute.
In public laws, this date matches that in the sidenote in the official title.
This includes bills that become law through a veto override or those
that are sent to the Archivist of the United States unsigned.
]]> is a property that specifies how this document may be cited.
There may be more than one form of citation for a document, such as a public law
that may also be cited by its Statute volume and page number.
The @value attribute may be used for a computer-readable version of the citation
property.
]]> is a property that specifies a short title by which this
document may be cited. Note that there may be multiple short titles in the document;
this property is reserved for the short title(s) that are defined for the complete
document.
See also and .
]]> is a property used to identify the congress number that the
document was created in. When in the element, the content is the normalized
form (e.g., 115). When in the element, the content is the form that
is rendered (e.g., One Hundred Fifteenth Congress of the United States of America).
]]> is a property that specifies a short title which is defined
in the document in a 'may be cited' clause. Note there may be different short titles
defined for different parts of the document. This is not the overall short title to
be used when citing the entire document; use for that purpose.
See also and .
]]> property is the date on which this document was created.
]]> is a property used to identify the chamber that currently
has control of the legislation (e.g., “In the House of Representatives” or
“In the Senate of the United States”). In the element the choices are
'HOUSE' or 'SENATE'. For conference reports there are two elements, one for each
of HOUSE and SENATE.
]]> is a property used to identify the public law number of the
latest amendment(s) applied to a statute compilation, or, if appropriate, the fact that no
amendments have been applied.
]]> is a property that signals to GPO how many copies to print by law.
These codes are used by several areas in Plant Operations.
]]> is a property that contains a numeric designation
assigned to this document. The document number should not contain
any document prefix. Use the for the prefix.
]]> is a property used to identify the part of the document, such
as "Part 2 of 3". The attribute @role holds the type of part, such as "book",
"part", etc.
]]> is a property used to record the name of
the publication that this document is part of. The values of the
are not defined.
]]> is a property used to record the point the document
was released. The values of the doc status are not defined. For a USC title,
this may be the Public Law number that the title is updated through.
]]> is a property used to hold the stage of the document, such
as Enrolled. The attribute @value holds the normalized stage, from the list
at https://www.govinfo.gov/help/bills#versions, capitalized.
]]> is a property used to hold the date and location
of the start of the session, which is printed on enrolled bills.
]]> is a property used to identify the issue of the document.
Sometimes used in conjunction with the volume.
]]> is a property used to identify the organization associated
with the document. The role attribute may be used to identify the type
of organization, e.g. @role="agency".
]]> is a property that specifies a popular name for the act.
This is not used for short titles that are defined in the act but rather for
unofficial name(s).
See also and .
]]> property identifies a system that has processed the document.
It can be used to identify a converter or editing tool that was used to make the
document. There may be more than one element.
]]> property is the date on which the processing system
created this version of the document.
]]> is a property that documents whether the bill, public law, or other
document is public or private. Two values are allowed: 'public' (the default value) and
'private'.
]]> is a property used to identify a document (such as a committee
report or chamber Calendar) that is related to this document and referenced
from it in the preface or meta. If there are multiple parts to the referenced report,
then the element is used as a wrapper around the individual reports.
]]> is used in the preface and meta to hold a set of
relatedDocument elements that are related to each other. This is used when multiple
report parts are referenced, for example.
]]> is a property used to identify the session within a congress
that the document was created in. When in the element, the content is the
normalized form (e.g., 1). When in the element, the content is the form
that is rendered (e.g., AT THE FIRST SESSION).
]]>
section, the content is the star print number; 0 is the default (no star print).
The maximum is 4 stars printed. Within the section, the content is
the actual star characters to be printed.
]]> is a property used to identify the subject associated
with the document.
]]> is a property used to identify volume of the document.
]]> is a property used to identify the starting page of the
document. Sometimes used in conjunction with the volume.
]]> is a property used to identify the enduing page of the
document. Sometimes used in conjunction with the volume.
]]> is a property used to identify the starting provision
of the document. This is used for example for part ranges for a volume of the CFR.
]]> is a property used to identify the ending provision
of the document. This is used for example for part ranges for a volume of the CFR.
]]> property gives the starting and ending provision that
is covered by the document.
]]> is the label for a signature or group of signatures.
It contains simple text, such as the word "Attest:".
]]> is the representation of the "wet signature". It
is often a reference to an image, or a special character.
]]> is the name of a person attesting to this document.
]]> is the role of the person named in .
]]> is the affiliation of the in the signature.
]]> is a line of text containing the date of the
signature. It may contain a element, footnotes, inline tagging,
or other content. It may have a @date attribute.
]]> is the set of 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.
]]> in an is the date or dates on which a particular 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. The date
attribute contains the date in machine-readable ISO 8601 format ("1995-01-30").
]]> is a statement that sets out the purposes of the bill
in general terms. Typically, it includes a followed by an
. Display of the content is suppressed in the rendered
document using the attribute @display set to "no".
]]> is a statement, such as "An Act", that precedes the long title
in legislation. The short title is typically declared in the
first clause of a bill and is tagged in that location using the
tag.
]]> is the portion of the long title after the .
]]> element is used to surround the short title when it
is first defined, usually in the first clause of the bill. Note
that the element is to be used in this case rather than
the element.
]]> is a word or phrase that is being defined. The element
surrounds the words for the term being defined. It is possible
for multiple elements to be specified within a definition.
When a is the words in an alternate language, then the
xml:lang attribute must be used. elements can also be used
for synonyms or near-synonyms which are also specified within the
definition. The containing element (such as a section) has a
@role="definitions" to indicate that definitions are contained within it.
The element does not define rendering or add quote characters.
]]> is a generic inline element to identify a text fragment
introducing or referring to an ontological concept. This is modelled after
the Akoma Ntoso element. The @role attribute can be used to
distinguish the concept. For example, a NAICS code or SEC code would be
or .
]]> level is used to create a hierarchical region
of the main document consisting of preliminary clauses that
are outside of the main document hierarchy.
]]> is the top hierarchical level of a legislative document.
When naming a title, use the case-sensitive prefix "t".
]]> is a hierarchical level of a legislative document.
When naming a subtitle, use the case-sensitive prefix "st".
]]> is a hierarchical level of a legislative document.
When naming a part, use the case-sensitive prefix "pt".
]]> is a hierarchical level of a legislative document.
When naming a subpart, use the case-sensitive prefix "spt".
]]> is a hierarchical level of a legislative document.
When naming a Division, use the case-sensitive prefix "d".
]]> is a hierarchical level of a legislative document.
When naming a subdivision, use the case-sensitive prefix "sd".
]]> is a hierarchical of a legislative document.
When naming a chapter, use the case-sensitive prefix "ch".
]]> is a hierarchical level of a legislative document.
When naming a subchapter, use the case-sensitive prefix "sch".
]]> is a used in bills.
When naming an article, use the case-sensitive prefix "a".
]]> is used in bills.
When naming a subarticle, use the case-sensitive prefix "sa".
]]> is used in title appendices.
When naming a compiledAct, use the case-sensitive prefix "cact".
]]> is used in title appendices.
courtRules is a containment level that is not named.
]]> is used in appendices.
When naming a courtRule, use the case-sensitive prefix "crule".
]]> are used in title appendices and the statutes at large.
reorganizationPlans is a containment level that is not named.
]]> is used in title appendices.
When naming a reorganizationPlan, use the case-sensitive prefix "rplan".
]]> 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".
]]> is an optional hierarchical level below a section.
Subsections are usually numbered with lower-case letters.
]]> is a numbered level usually found below a
subsection in the document hierarchy. Paragraphs are
usually numbered with Arabic numbers.
]]> is a level below a paragraph in the document
hierarchy. Subparagraphs are usually numbered with upper-case
letters.
]]> is an optional below-section hierarchical level.
Clauses are usually numbered with lower-case Roman numerals.
]]> is an optional hierarchical level below a clause.
Subclauses are usually numbered with upper-case Roman numerals.
]]> is a level usually below a subclause in the document
hierarchy. Items are usually numbered with double lower-case
letters.
]]> is a level below an item in the document
hierarchy. Subitems are usually numbered with double upper-case
letters.
]]> is a level below a subitem in the document
hierarchy. Subsubitems are usually numbered with triple lower-case
letters.
]]> is a collection of notices. These are typically found in the
Federal Register.
]]> is a collection of rules. These are typically found in the
Federal Register.
]]> is a collection of proposed rules. These are typically
found in the Federal Register.
]]> is a collection of Presidential Documents.
These are typically found in the Federal Register and Statutes at Large volumes.
]]> is a collection related to a specific agency. It is, for
example, used in the Federal Register to group together a set of rules,
proposed rules, or notices.
]]> is a collection of public laws. It is found, for example, in a Statutes
at Large volume.
]]> is a collection of private laws. It may be found, for example, in a
Statutes at Large volume.
]]> is a collection of concurrent resolutions. It is found, for
example in a Statutes at Large volume.
]]> 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.
]]> 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.
]]> is a sentence, clause, or paragraph that states conditions
relating to the law it is related to. A proviso generally begins with
"Provided that" or "Provided", or "Provided further". Proviso can contain
their own complex structure including sandwich structures.
]]> is a container for sets of individual notes.
]]> is a generic element for a note associated with items in the
document.
]]> 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.
]]> is a note below sections and big-level headings in the U.S.
Code.
]]> 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.
]]> is a note that becomes part of the law.
]]> 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.
]]> is a note that records a non-substantive change that
has been made to the document. Usually change notes are set out in
square brackets and these must be set out in the text and must not
be automatically added.
]]> is a note included to indicate the authority behind
a provision. In the CFR and statutes at large, the is
the law which authorizes the regulation.
]]> is a note included to indicate the source of a provision.
In the CFR, the is a citation to an entry in the Federal
Register where the provision is sourced. is similar to
in the U.S. Code, but is specifically called "Source"
in the CFR.
]]> is a note to indicate the effectivity of a
provision. In the CFR, the 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.
]]> is a note identifying the Document ID of an entry
in the Federal Register.
]]> is a note containing the billing code of an item. It is
used, for example, in the Federal Register.
]]> 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".
]]> 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.
]]> 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.
]]> 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.
]]> 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.
]]> element is a wrapper for content comes from an external
namespace.
]]> is a note that is to be rendered at the bottom of a page
or column or table. It typically has a corresponding
element, where the @idref matches the @id of the .
]]> is a note that is to be rendered in the side margins of a
page. It may have a corresponding element, where the
@idref matches the @id of the .
]]> 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 element,
where the @idref matches the @id of the .
]]> contains the text to be printed in the center
running header. It is used, for example, in amendment documents.
]]> contains the text to be printed in the left hand
running header. It is used, for example, in the CFR.
]]> contains the text to be printed in the right hand
running header. It is used, for example, in the CFR.
]]> contains the text to be printed in the outside margin. It is
used, for example, in the CFR.
]]> element is used at the end of a document and usually contains
the ○ (&all;) character. It is used, for example, in a public law.
]]> is a note indicating where a page boundary occurred. The
content will typically be the page number.
]]> is a note indicating where a line boundary occurred.
The content will typically be the line number, and possibly also
the page number.
]]>