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

uslm:SignatureType

 
            Defines a basic signature element comprising a name and optionally 
            the person's role, their affiliation, and a date. All fields can be
            defined to include either an @href or an @idref to point to an 
            identifying resource that describes the person, their role, and
            their affiliation.

Complex type information

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

Schema document: uslm-components-2.1.0.xsd

Content

  • Any text (mixed) content, intermingled with:
  • Choice [0..*]
      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.
    • uslm:notation The <notation> is the label for a signature or group of signatures. It contains simple text, such as the word "Attest:".
    • uslm:autograph The <autograph> is the representation of the "wet signature". It is often a reference to an image, or a special character.
    • uslm:name The <name> is the name of a person attesting to this document.
    • uslm:role The <role> is the role of the person named in <name>.
    • uslm:affiliation The <affiliation> is the affiliation of the <name> in the signature.
    • uslm:signatureDate A date can be associated with a group of signatures, or using this element with a single signature.

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

Used in