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

uslm:SetType

 
            The set type is the core type for a group of properties. Property
            sets are found within the meta area only. Sets can contain other
            sets as well as properties.

Complex type information

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

Schema document: uslm-components-2.1.0.xsd

Content

  • Choice [0..*]
    • Any element Namespace: http://purl.org/dc/elements/1.1/, Process Contents: lax
      • from subst. group uslm:property
    • uslm:property A <property> is a simple value recorded with the document. Typically properties are stored in the <meta> and/or <preface> blocks of the document. If a property in the <meta> block has textual content, then this text is not intended for publication. However, if a property in the <preface> block has textual content, then this text is intended for publication.
    • uslm:coverTitle A <coverTitle> is the version of the title that is rendered on the cover page. This is, for example, found on some Public Laws.
    • uslm:amendmentNumber The <amendmentNumber> is a property used to identify the amendment number attached to this amendment document.
    • uslm:congress The <congress> is a property used to identify the congress number that the document was created in. When in the <meta> element, the content is the normalized form (e.g., 115). When in the <preface> element, the content is the form that is rendered (e.g., One Hundred Fifteenth Congress of the United States of America).
    • uslm:currentChamber The <currentChamber> 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 <meta> element the choices are 'HOUSE' or 'SENATE'. For conference reports there are two elements, one for each of HOUSE and SENATE.
    • uslm:currentThroughPublicLaw The <currentThroughPublicLaw> 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.
    • uslm:distributionCode The <distributionCode> is a property that signals to GPO how many copies to print by law. These codes are used by several areas in Plant Operations.
    • uslm:docNumber The <docNumber> is a property that contains a numeric designation assigned to this document. The document number should not contain any document prefix. Use the <docType> for the prefix, or the <docTitle> in amendment documents where that is appropriate.
    • uslm:docPart The <docPart> 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.
    • uslm:docPublicationName The <docPublicationName> is a property used to record the name of the publication that this document is part of. The values of the <docPublicationName> are not defined.
    • uslm:docReleasePoint The <docReleasePoint> 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.
    • uslm:docStage The <docStage> 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.
    • uslm:enrolledDateline The <enrolledDateline> is a property used to hold the date and location of the start of the session, which is printed on enrolled bills.
    • uslm:purpose The <purpose> is a property that documents the purpose in amendment documents. This is often related to the official title of the bill being amended.
    • uslm:relatedDocument The <relatedDocument> 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 <relatedDocuments> element is used as a wrapper around the individual reports.
    • uslm:session The <session> is a property used to identify the session within a congress that the document was created in. When in the <meta> element, the content is the normalized form (e.g., 1). When in the <preface> element, the content is the form that is rendered (e.g., AT THE FIRST SESSION).
    • uslm:subject The <subject> is a property used to identify the subject associated with the document.
    • uslm:volume The <volume> is a property used to identify volume of the document.
    • uslm:provisionRange The <provisionRange> property gives the starting and ending provision that is covered by the document.
    • uslm:set A set can contain 0 or more sets.

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
type [0..1]uslm:SetTypeEnum By default, the properties in a set are a simple "bag" of properties, known as an unordered set. However, a set of properties can also be typed using the @type attribute, choosing values from the set type enumeration. Default value is "bag".

Used in

Type inheritance chain