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

uslm:name

 
            The <name> is the name of a person attesting to this document.

Element information

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

Schema document: uslm-components-2.1.0.xsd

Type: uslm:PropertyType

Properties: Global, Qualified

Content

  • Any text (mixed) content, intermingled with:
  • Choice [0..*]
      from subst. group uslm:marker
    • uslm:marker The <marker> element is a primitive element to be used to mark or denote a spot in the text. It can be used in the <content> areas or anywhere else where an <inline> element is expected. The <marker> element contains no text.
    • uslm:br A <br> is simple marker element denoting a line, page, or column break. The default is a line break; the @verticalSpace attribute can be used to denote a page or column break, or a vertical space of a defined height.
    • uslm:img An <img> 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.
      • 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.
      • 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.
    • uslm:affected The <affected> is an element used to identify a provision or document that is affected by this document.
      • 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.

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:BaseContentType
date [0..1]uslm:DateSimpleType The @date attribute is used for a single date value. from group uslm:DateGroup
legisDate [0..1]uslm:DateSimpleType The @legisDate attribute is used for a logical legislative date, which may be different from the calendar date. from group uslm:DateGroup
startDate [0..1]uslm:DateSimpleType The @startDate attribute is used for the starting date of a date range. from group uslm:DateGroup
endDate [0..1]uslm:DateSimpleType The @endDate attribute is used for the ending date of a date range. from group uslm:DateGroup
display [0..1]uslm:YesOrNoEnum The @display attribute specifies whether the element is rendered, either on screen or in print. The values are @display="yes" to render the element; this is the default. @display="no" is used when the information is to be retained in the document but not rendered. There are no exceptions; if display="yes" then the item will be rendered, regardless of stage, status, or other rules. Default value is "yes". from group uslm:DisplayGroup
value [0..1]uslm:MediumStringSimpleType The @value attribute is used when there is a single value. from group uslm:ValueGroup
startValue [0..1]uslm:MediumStringSimpleType The @startValue attribute is used for the lower end of a value range. from group uslm:ValueGroup
endValue [0..1]uslm:MediumStringSimpleType The @endValue attribute is used for the upper end of a value range. from group uslm:ValueGroup
href [0..1]xsd:anyURI The @href attribute is used to specify references to external documents or items in documents. The value must always be specified as a relative URL conforming to the reference specification. from group uslm:ReferenceGroup
idref [0..1]xsd:IDREF The @idref attribute is used to specify references to internal elements within the same document. The @idref is specified as the value of the @id attribute of the element being referenced. As in HTML, there is an equivalence between an @href specified as href="#{id}" and idref="{id}". However, the @idref attribute is preferred for internal references. If the @idref points to a <ref> 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 <ref> element which itself builds on another <ref> element, and so on. This is to support the complex referencing sometimes found in legislation. from group uslm:ReferenceGroup
portion [0..1]uslm:MediumStringSimpleType The @portion attribute is used, in conjunction with the @idref attribute, when only a portion of the referenced item is being affected. The value of @portion is an additional part to append to the URL, with a "/" separator to identify the item affected. Do not include a leading "/" in the @portion value. from group uslm:ReferenceGroup
type [0..1]uslm:PropertyTypeEnum By default, a property is a string. The @type attribute is used to define an alternate property type. The attributes of the Reference Group are used when the @type is set to "url". The attributes of the Value Group are used when the @type is set to "string", "number", "token", or "boolean" or the @type is not set. The attributes of the Date Group are used when the @type is set to "date". Default value is "string".

Used in

Sample instance

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