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

uslm:editorialContent

 
            Documents may optionally have content defined in the preface that 
            is non-statutory content written by an editorial team, for example
            in a statute compilation. This content may include a table of 
            contents or other finding aids that are of use to the reader, but
            are not officially part of the legislation.
            This content model may be restricted to better match current known
            usage in the next minor (2.1) release.

Element information

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

Schema document: uslm-components-2.1.0.xsd

Type: Anonymous

Properties: Global, Qualified

Content

  • Any text (mixed) content, intermingled with:
  • Choice [1..*]
      from subst. group uslm:toc
    • uslm:toc A <toc> 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 <main> element, before the levels. - It can appear in any level following the <heading>, <subheading>, and any notes. - It can appear in an <appendix>.
    • 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.
      • from subst. group uslm:index
    • 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.

Attributes

NameOccTypeDescriptionNotes
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
type [0..1]xsd:string The @type attribute defines the type of preliminary content. Currently only 'editorial' is used. Default value is "editorial".

Used in

Sample instance

<uslm:editorialContent/>