Schema Central  >  USLM 2.1.0  >  uslm-table-module-2.1.0.xsd  >  xhtml:xhtml.caption.type
Advanced search

xhtml:xhtml.caption.type

Complex type information

Namespace: http://www.w3.org/1999/xhtml

Schema document: uslm-table-module-2.1.0.xsd

Content

  • Any text (mixed) content, intermingled with:
  • Choice [0..1]
    • Choice [0..*]
        from subst. group uslm:inline
      • uslm:inline The <inline> element is a primitive element to be used within <content> areas or within any other areas which can accept inline content.
      • uslm:amendingAction An <amendingAction> 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.
      • uslm:ref A <ref> element is a reference or link to another document, a location within another document, or a location with the same document.
      • uslm:date A <date> 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.
      • uslm:center A <center> element contains content text that is to be centered on the page.
      • uslm:fillIn A <fillIn> is an inline spacer which denotes an area to be filled in a form designed to be printed. Usually, a <fillIn> is rendered as dotted lines with the text content within the <fillIn> 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.
      • uslm:checkBox A <checkBox> is an inline tick box which denotes a box to be filled in on an form.
      • uslm:b A <b> is a simple inline element for text that is to be rendered in bold text.
      • uslm:i An <i> is a simple inline element for text that is to be rendered in italic text.
      • uslm:qualifier A <qualifier> element can be used to add a qualifier to a reference, such as the 'as amended by' language seen in amendments.
      • uslm:sub A <sub> is a simple inline element for text that is to be rendered in subscript text.
      • uslm:sup A <sup> is a simple inline element for text that is to be rendered in superscript text.
      • uslm:headingText A <headingText> element is for text that bears some relationship to a <heading> 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.
      • uslm:span A <span> element is general purpose wrapper for text similar to an html span. The @role attribute can be used to specify the type of span.
      • uslm:shortTitle The <shortTitle> element is used to surround the short title when it is first defined, usually in the first clause of the bill. Note that the <shortTitle> element is to be used in this case rather than the <docTitle> element.
      • uslm:term A <term> is a word or phrase that is being defined. The <term> element surrounds the words for the term being defined. It is possible for multiple <term> elements to be specified within a definition. When a <term> is the words in an alternate language, then the xml:lang attribute must be used. <term> 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 <term> element does not define rendering or add quote characters.
      • uslm:entity An <entity> is a generic inline element to identify a text fragment introducing or referring to an ontological concept. This is modelled after the Akoma Ntoso <entity> element. The @role attribute can be used to distinguish the concept. For example, a NAICS code or SEC code would be <entity @role="NAICS"> or <entity @role="SEC">.
      • 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: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.
    • uslm:p [0..*] 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.

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
Any attribute [0..*]Namespace: ##other, Process Contents: lax

Used in