4.1.1 The endorsement element Content Model

Signatures from all parties to a legal instrument are required before, following, or in the midst of the paragraphs and clauses included in a legal instrument. Additionally, signatures from one or more parties may be required at the top or Left of one or more pages prior to the final page of the instrument, and also above, below, to the side or in the midst of, one or more text blocks within the instrument. One XML element is defined to handle these requirements.

The endorsement element achieves several goals:

• provide a standard element for the application of standardized formatting rules;
• signal that a signature from a specific party is to be requested or has been recorded in the Signed Envelope in which the instrument is placed; and
• record a party's decline of an instrument or some portion of the instrument.

This inline element can be located within an instrument, footer, header, or page element, or within any XHTML element allowing inline content.

The endorsement element normally contains a text string for the name or initials of the party endorsing the instrument or endorsing some content within the instrument. Using appropriate style directives, this text can appear above or below a drawn line and, in the case of multiple initials, a "signature cross" can be formatted.

about = anyURI

Contains the URI of a party to supply the endorsement. During signature processing, it is an application responsibility to determine if the viewer of a document matches, or is an agent for, the party represented by the URI. No attempt is made to map digital signature instances to instances of this element; see Instrument Endorsements for more information.

This is an optional attribute in a Normative Instrument, and is a required attribute in a Normative Presentation.

endorsed = QName

Indicates the status of the endorsement from the party. Reserved values are

declined

The party has declined assent to the instrument, page, clause, or term.

endorsed

An endorsement for the party is physically recorded in the instrument's Signed Envelope.

irrelevant

An endorsement from the party is unnecessary. Assume this value if the attribute is not supplied, or it is an empty or unknown value.

optional

An endorsement from the party is optional.

required

An endorsement from the party is required.

virtual

An endorsement is virtually recorded for the party, either by an agent's signature within the instrument's Signed Envelope, or as implied by the circumstances of the instrument's display or processing.

This is an optional attribute in a Normative Instrument, and is a required attribute in a Normative Presentation.

Common Attributes

See Core Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<legal:instrument resource='.../R12344.html'>
    ...
    <p property='SignatureBlock'>
      <legal:endorsement about='/party/R12344.rdf' endorsed='required'>
        James R. Smith
      </legal:endorsement>
    </p>
    ...
</legal:instrument resource='.../R12344.html'>

<legal:instrument resource='.../R12344.html'>
    <legal:page>
      ...
      <legal:footer>
        <p property='SignatureBlock'>
          <legal:endorsement about='/party/R12344.rdf' endorsed='optional'>
            James R. Smith
          </legal:endorsement>
        </p>
      </legal:footer>
      ...
    </legal:page>
</legal:instrument>

<legal:instrument resource='.../R12344.html'>
    <section>
      <legal:endorsement about='/party/R12344.rdf' endorsed='virtual'>
        JRS
      </legal:endorsement>
      <h>
        <legal:id>1.0</legal:id>
        <span property='SignatureBlock'>
      </h>
      ...
    </section>
</legal:instrument>

4.1.2 The id element Content Model

In legal instruments, a caption is composed of an optional text label, a mandatory sequential identifier, an optional suffix, and an optional text heading. Captions are used to easily reference the document part and can be used to populate tables of contents, tables of figures, and other indexes that can be created for complex legal instruments. See Instrument Captioning and Instrument Linking for information about the architectural implications of captions.

Within instruments, captions are generally considered mandatory for document divisions, clauses, tables, and figures; optional for generic text blocks such as paragraphs, lists, and quotes; mandatory for pages and notes; and optional for text lines within a page, document division, or clause.

For structural items, captions are represented in XHTML 2.0 by heading elements; for lists only, by label elements; and for tables, by the caption element. XHTML includes the heading elements in the content models for the section, table, object, blockcode, blockquote, dd, li, and div elements. The label element is an optional component of the dl, nl, ol, and ul element content models.

The id element is provided by the Legal XHTML Module to encapsulate the identifier portion of a caption. The Legal XHTML Document Type then extends XHTML 2.0 by the following implementation.

• to support text block captioning requirements, the id element is included in the content models for the heading elements and the label element, and the heading elements are included in the content models for the p and sidebar elements; and
• for note numbering and line numbering, the id element is included within the content models for the note and l elements. For page numbers the id element is included in the content models for the header and footer elements.

Empty id elements may only occur within identifier templates, functioning as a placeholder for the sequentially-assigned identifier text when the Normative Instrument or Normative Presentation is created. See the coding samples below.

counter = anyURI

Identifies the container element for counting child instances of a certain element type and property value. For identifier templates only. The default value is the containing ancestor document division element.

For example, a document division could have its own set of figures; this attribute enables the counting of all its child elements whose element name is "object " and whose property value is "Figure" whenever an id is to be generated for an element whose name is "object" and whose property value is "Figure".

format = QName

Indicates the format of the text for a sequential identifier. For identifier templates only, this attribute is ignored if the template attribute is not "template". Reserved values are

number

Numbers are to be used, for example, 1, 2, 3, .... This is the default value for this attribute.

decimal

Decimal numbers are to be used, that is, a 'period' follows the number.

upper-alpha

The upper-case alphabet is to be used, for example in Latin languages, A, B, C, ....

lower-alpha

The lower-case alphabet is to be used, for example in Latin languages, a, b, c, ....

upper-roman

Roman numerals are to be used, in upper-case, for example, I, II, III, ....

lower-roman

Roman numerals are to be used, in lower-case, for example, i, ii, iii, ....

inherit = QName

Indicates whether the template is to inherit the identifier format from an ancestor element. For identifier templates only. Reserved values are

id

The nearest ancestor element's generated sequence id is used as a prefix. This is the default value if this attribute is not specified.

For example, if the ancestor's id contained "Article 3", then the caption for a child element could be generated as "Section 3.1".

label

The contents of the id element from the nearest ancestor element is used as a prefix.

For example, if the ancestor id contains "Appendix C", then the caption for a child element could be generated as "Appendix C-1".

none

No prefix is implied.

separator = TEXT

Provides a text string to use as a separator between an inherited id or label, and the number or letter generated from counting. The default value is ". ".

start = NUMBER

Indicates the starting value when generating ids from a template. A sequential id is calculated by adding this value to the count of child elements of the same name and property value within the element indicated by the counter attribute. For identifier templates only. The default value for this attribute is zero.

template = QName

Indicates whether the element is a template. Reserved values are

template

The element is an identifier template.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <section>
      <h>
        <legal:id template='template'>Article <legal:id/></legal:id>
      </h>
      text for first article, first paragraph.
      <section>
        <h>
          <legal:id template='template' inherit='id'> 
          Section <legal:id/>< 
          /legal:id>
        </h>
        text for first article, first section, first paragraph.
      </section>
    </section>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    <section>
      <h>
        <legal:id>Article 1</legal:id>
      </h>
      <p>text for first article, first paragraph </p>
      <section>
        <h>
          <legal:id>Section 1.1</legal:id>
        </h>
        <p>text for first article, first section, first paragraph</p>
      </section>
    </section>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <dl>
        <label>
          <legal:id template='template'>List <legal:id/></legal:id>
          Part 1 Definitions
        </label>
        <dt>a phrase</dt>
        <dd>a definition</dd>
      </dl>
      <dl>
        <label>
          <legal:id template='template'>List <legal:id/></legal:id>
          Part 2 Definitions
        </label>
        <dt>a phrase</dt>
        <dd>another definition</dd>
      </dl>
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <dl>
        <label>
          <legal:id>List 2</legal:id>
          <span>Part 2 Definitions</span>
        </label>
        <di resource='Definition.2'>
          <dt about='Definition.2' property='DefinitionLabel'>a phrase</dt>
          <dd about='Definition.2' property='DefinitionText'>a definition</dd>
        </di>
      </dl>
    </p>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    ...
    <div property='Attachment'>
      <h>
        <legal:id template='template' format='upper-case'>
          Appendix <legal:id/>
        </legal:id>
        Sample Lease Commencement Memo
      </h>
      ...
    </div>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    ...
    <div property='Attachment'>
      <h>
        <legal:id>Appendix A</legal:id>
        <span>Sample Lease Commencement Memo</span>
      </h>
      ...
    </div>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>Text for paragraph with a note here
      <legal:note>
        <legal:id template='template'>[<legal:id/>]</legal:id>
        note text here
      </legal:note>
    </p>
</legal:instrument>
            
<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    <p>
      <span>Text for paragraph with a note here</span>
      <legal:note>
        <legal:id>[1]</legal:id>
        <span>note text here</span>
      </legal:note>
    </p>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <legal:page>
      <p>
        <span>Text for paragraph with a note here</span>
        <legal:note>
          <legal:id href='#note_id'>[1]</legal:id>
        </legal:note>
      </p>
      ...
      <legal:footer>
        <legal:note xml:id='note_id'>
          <legal:id>[1]</legal:id>
          <span>note text here</span>
        </legal:note>
      </legal:footer>
    </legal:page>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <ol property='PriceList'>
        <legal:id template='template'><legal:id/>.</legal:id>
        <label>
          <legal:id template='template'>Price List #<legal:id/></legal:id>
        </label>
        <li>Product A: Price A</li>
        <li>Product B: Price B</li>
      </ol>
      <ol property='PriceList'>
        <legal:id template='template'><legal:id/>.</legal:id>
        <label>
          <legal:id template='template'>Price List #<legal:id/></legal:id>
        </label>
        <li>Product C: Price C</li>
        <li>Product D: Price D</li>
      </ol>
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument resource='.../R12344.html' property='NormativeInstrument'>
    <p>
      <ol property='PriceList'>
        <label>
          <legal:id>Price List #1</legal:id>
        </label>
        <li>
          <legal:id>1.</legal:id>
          <span>Product A: Price A</span>
        </li>
        <li>
          <legal:id>2.</legal:id>
          <span>Product B: Price B</span>
        </li>
      </ol>
      <ol property='PriceList'>
        <label>
          <legal:id>Price List #2</legal:id>
        </label>
        <li>
          <legal:id>1.</legal:id>
          <span>Product C: Price C</span>
        </li>
        <li>
          <legal:id>2.</legal:id>
          <span>Product D: Price D</span>
        </li>
      </ol>
    </p>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <ol property='PriceList'>
        <legal:id template='template' format='decimal'><legal:id/></legal:id>
        <label>
          <legal:id template='template'>Schedule <legal:id/></legal:id>
          Product A Pricing
        </label>
        <li>
          <h>
            <legal:id template='template'>Period #<legal:id/></legal:id>
            Date 1 through Date 2
          </h>
          Price A
        </li>
        <li>
          <h>
            <legal:id template='template'>Period #<legal:id/></legal:id>
            Date 3 through Date 4
          </h>
          Price B
        </li>
      </ol>
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument resource='.../R12344.html' property=' 
NormativeInstrument'>
    <p>
      <ol property='PriceList'>
        <label>
          <legal:id>Schedule 1</legal:id>
          <span>Product A Pricing</span>
        </label>
        <li>
          <legal:id>1.</legal:id>
          <h>
            <legal:id>Period #1</legal:id>
            <span>Date 1 through Date 2</span>
          </h>
          <span>Price A</span>
        </li>
        <li>
          <legal:id>2.</legal:id>
          <h>
            <legal:id>Period #2</legal:id>
            <span>Date 3 through Date 4</span>
          </h>
          <span>Price B</span>
        </li>
      </ol>
    </p>
</legal:instrument>

<!-- Legal XHTML Document and Normative Instrument -->
<legal:instrument resource='.../R12344.html'>
    ...
    <legal:header>
      <legal:id template='template'>Page <legal:id/></legal:id>
    </legal:header>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument resource='.../R12344.html' property='NormativePresentation'>
    <legal:page>
      <legal:header>
        <legal:id>Page 1</legal:id>
      </legal:header>
      ...
    </legal:page>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <h>
        <legal:id template='template' format='decimal'><legal:id/></legal:id>
        Terms and Conditions.
      </h>
      paragraph text
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument resource='.../R12344.html' property='NormativeInstrument'>
    <p>
      <h>
        <legal:id>1.</legal:id>
        <span>Terms and Conditions.</span>
      </h>
      <span>paragraph text</span>
    </p>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <object property='Figure'>
        <h>
          <legal:id template='template' format='decimal'> 
          Figure <legal:id/></legal:id>
          Actual vs. Estimated Income
        </h>
      </object>
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    <p>
      <object property='Figure'>
        <h>
          <legal:id>Figure 1.</legal:id>
          <span>Actual vs. Estimated Income</span>
        </h>
      </object>
    </p>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>
      <table>
        <h>
          <legal:id template='template' format='decimal'> 
          Table <legal:id/></legal:id>
          Actual vs. Estimated Income
        </h>
        <tr/>
      </table>
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    <p>
      <table>
        <h>
          <legal:id>Table 1.</legal:id>
          <span>Actual vs. Estimated Income</span>
        </h>
        <tr/>
      </table>
    </p>
</legal:instrument>

<!-- Legal XHTML Document and Normative Instrument -->
<legal:instrument resource='.../R12344.html'>
    <p>
      First line of text for paragraph. Second line of text for paragraph.
    </p>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <p>
      <l>First line of text for paragraph. <legal:id> 
      1</legal:id></l>
      <l>Second line of text for paragraph. <legal:id> 
      2</legal:id></l>
    </p>
</legal:instrument>

4.1.3 The footer element Content Model

When printed, legal instruments often contain blocks of text at the bottom of each page. Page footers optionally contain the title and reference date for the instrument; the names of its parties or subject premises; the caption for the clause begun or continued on the page; a page label, with the current page number; and one or more signature blocks. Apart from the page number, the content of a page footer does not vary from page to page. Some pages contain a footer, and others (such as a title page) do not. Lastly, the page labelling and numbering scheme can vary across divisions of the instrument.

The footer element is used to encapsulate text and inline content that is positioned at the bottom of a page. When located within any element other than a page element, the footer element is a template to be used when converting a Normative Instrument into a Normative Presentation, at which time page elements are created.

If the footer is a child of an instrument element, then it is a template for a running footer block of content to be formatted into the presentation of the legal instrument. If the footer is within an XHTML element such as the section element, it is a template for a running footer block of content beginning on the page where the element's content first appears, and ending on the page where the content for that element completes. If more than one element each containing a footer template specification physically begins on the same page, then the first footer specified is to be formatted. If more than one element each containing a footer template specification physically ends on the same page, then the last footer specified is to be formatted for that page.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

The only difference in the content models for the page footer and page header elements is that a page footer may include one or more note elements. For a coding sample involving the footer element, see the note element.

For both a header and footer, if the id element is specified, it is an expression of a page number. A coding sample for page numbers, albeit using the header element, is found at Page Captioning.

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    ...
    <legal:footer style='text-align:center'>
      <span style='clear:none;float:left'>05 January 2005</span>
      <legal:id template='template' style='clear:none;float:right'>
        Page <legal:id/>
      </legal:id>
      <span>Title of document</span>
    </legal:footer>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <legal:page>
      ...
      <legal:footer>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id style='clear:none;float:right'> 
        Page 1</legal:id>
        <span>Title of document</span>
      </legal:footer>
    </legal:page>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    <section>
      <h>
        <legal:id>1.2</legal:id>
        <span>Terms and Conditions</span>
      </h>
      <p>Text of clause</p>
      <legal:footer style='text-align:center'>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id template='template' style='clear:none;float:right'>
          Page <legal:id/>
        </legal:id>
        <span>Clause heading</span>
      </legal:footer>
    </section>
  </legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <legal:page>
      <section>
        <h>
          <legal:id>1.2</legal:id>
          <span>Terms and Conditions</span>
        </h>
        <p>Text of clause</p>
      <section>
      <legal:footer style='text-align:center'>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id style='clear:none;float:right'>Page 1</legal:id>
        <span>1.2 Terms and Conditions</span>
      </legal:footer>
    </legal:page>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    ...
    <div property='Attachment'>
      ...
      <legal:footer style='text-align:center'>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id template='template' style='clear:none;float:right'>
          Page A-<legal:id/>
        </legal:id>
        <span>Title of attachment</span>
      </legal:footer>
    </div>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    ...
    <legal:page>
      <div property='Attachment'>
        ...
      </div property='Attachment'>
      <legal:footer>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id style='clear:none;float:right'> 
        Page A-1</legal:id>
        <span>Title of attachment</span>
      </legal:footer>
    </legal:page>
</legal:instrument>

4.1.4 The header element Content Model

When printed, legal instruments often contain blocks of text at the top of each page. Page headers optionally contain the title and reference date for the instrument; the names of its parties or subject premises; the caption for the clause begun or continued on the page; a page label, with the current page number; and one or more signature blocks. Apart from the page number, the content of a page header does not vary from page to page. Some pages contain a header, and others (such as a title page) do not. Lastly, the page labelling and numbering scheme can vary across divisions of the instrument.

The header element is used to encapsulate text and inline content that is positioned at the top of a page. When located within any element other than a page element, the header element is a template to be used when converting a Normative Instrument into a Normative Presentation, at which time page elements are created.

If the header is a child of an instrument element, then it is a template for a running header block of content to be formatted into the presentation of the legal instrument. If the header is within an XHTML element such as the section element, it is a template for a running header block of content beginning on the page where the element's content first appears, and ending on the page where the content for that element completes. If more than one element each containing a header template specification physically begins on the same page, then the first header specified is to be formatted. If more than one element each containing a header template specification physically ends on the same page, then the last header specified is to be formatted for that page.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

If the id element is specified, it is an expression of a page number. A coding sample for page numbers is found at Page Captioning.

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    ...
    <legal:header style='text-align:center'>
      <span style='clear:none;float:left'>05 January 2005</span>
      <legal:id template='template' style='clear:none;float:right'>
        Page <legal:id/>
      </legal:id>
      <span>Title of document</span>
    </legal:header>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <legal:page>
      <legal:header style='text-align:center'>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id style='clear:none;float:right'>Page 1</legal:id>
        <span>Title of document</span>
      </legal:header>
      ...
    </legal:page>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument property='NormativeInstrument' resource='.../R12344.html'>
    <section>
      <h>
        <legal:id>1.2</legal:id>
        <span>Terms and Conditions</span>
      </h>
      <p>Text of clause</p>
      <legal:header style='text-align:center'>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id template='template' style='clear:none;float:right'>
          Page <legal:id/>
        </legal:id>
        <span>Clause heading</span>
      </legal:header>
    </section>
  </legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <legal:page>
      <legal:header style='text-align:center'>
        <span style='clear:none;float:left'>05 January 2005</span>
        <legal:id style='clear:none;float:right'>Page 1</legal:id>
        <span>1.2 Terms and Conditions</span>
      </legal:header>
      <section>
        <h>
          <legal:id>1.2</legal:id>
          <span>Terms and Conditions</span>
        </h>
        <p>Text of clause</p>
      <section>
    </legal:page>
</legal:instrument>

4.1.5 The instrument element Content Model

This element allows a legal instrument to be identified and extracted from a larger XHTML document. Rules for XHTML markup within an instrument element are defined in this document, while no rules are defined for element content external to the instrument element that is, for sibling XHTML elements within a body.

property = QName

Indicates the semantic applicable to the element. Reserved values are

NormativeInstrument

The instrument conforms to rules for a Normative Instrument.

NormativePresentation

The instrument conforms to rules for a Normative Presentation.

resource = anyURI

A Uniform Resource Identifier (URI) is required.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
  <div property='CoverPage' resource='CoverPage.1'>
    ...
  </div>
  <div property='TableOfContents' resource='CoverPage.1'>
    ...
  </div>
  <div property='TableOfFigures' resource='TableOfFigures.1'>
    ...
  </div>
  <div property='BlankPage' resource='BlankPage.1'>
    ...
  </div>
  <p resource='Para.1'>
    <span>
      Often a preamble or recital paragraph precedes
      numbered clauses within the document.
    </span>
  </p>
  <section resource='Article.1'>
    ...
  </section>
  <div property='Attachment' resource='Attachment.1'>
    ...
  </div>
</legal:instrument>

4.1.6 The note element Content Model

In legal instruments, notes are used to annotate text in clauses, paragraphs, tables, and lists. When the instrument is formatted, the note's text is positioned either at the bottom of a page (above a page footer) or in a separate list normally at the end of the document.

The note element is an inline element which encapsulates text and inline content, or a link to the note text, depending on the state of the instrument. This element is a component of the content models for the p, section, li, dd, dt, and td elements, and for all elements defined in the Text module.

Normative Transform
Attach the Footnote property attribute if not present, the default semantic of the note.

property = QName

Indicates the semantic applicable to the note element. Reserved values are

Footnote

The note element is a footnote.

FootnoteRef

The note element is a link to a footnote.

Notation

The note element is a notation (to be) placed in a TableOfNotations.

NotationRef

The note element is a link to an notation located in a TableOfNotations.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>Text for paragraph with a note here
      <legal:note>para note content here</legal:note>
      and within a table it is
      <table>
        <tr>
          <td>Text in table with a note here
              <legal:note>table note content here</legal:note>
          </td>
        </tr>
      </table>
    </p>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument resource='.../R12344.html' property='NormativeInstrument'>
    <p>
      <span>Text for paragraph with a note here</span>
      <legal:note property='Footnote'>para note content here</legal:note>
      <span>and within a table it is</span>
      <table>
        <tr>
          <td>
            <p>
              <span>Text in table with a note here</span>
              <legal:note property='Footnote'>table note content here</legal:note>
            </p>
          </td>
        </tr>
      </table>
    </p>
</legal:instrument>

<!-- Normative Presentation -->
<legal:instrument property='NormativePresentation' resource='.../R12344.html'>
    <legal:page>
      <p>
        <span>Text for paragraph with a note here</span>
        <legal:note property='FootNoteRef'>
          <legal:id href='#note_1_id'>1</legal:id>
        </legal:note>
        <span>and within a table it is</span>
        <table>
          <tr>
            <td>
              <p>
                <span>Text in table with a note here</span>
                <legal:note property='FootNoteRef'>
                  <legal:id href='#note_2_id'>2</legal:id>
                </legal:note>
              </p>
            </td>
          </tr>
        </table>
      </p>
      <legal:footer>
        <legal:note property='Footnote'>
          <legal:id>1</legal:id>
          <span xml:id='note_1_id'>para note content here</span>
        </legal:note>
        <legal:note property='Footnote'>
          <legal:id>2</legal:id>
          <span xml:id='note_2_id'>table note content here</span>
        </legal:note>
      </legal:footer>
    </legal:page>
</legal:instrument>

<!-- Legal XHTML Document -->
<legal:instrument resource='.../R12344.html'>
    <p>Text for paragraph with a note here
      <legal:note property='Notation'>para note content here</legal:note>
      and within a table it is
      <table>
        <tr>
          <td>Text in table with a note here
              <legal:note property='Notation'>table note content here</legal:note>
          </td>
        </tr>
      </table>
    </p>
    <div>
      <ol property='TableOfNotations>
        <legal:id template='template'>[<legal:id/>]</legal:id>
        <li/>
      </ol>
    </div>
</legal:instrument>

<!-- Normative Instrument -->
<legal:instrument resource='.../R12344.html' property='NormativeInstrument'>
    <p>
      <span>Text for paragraph with a note here</span>
      <legal:note property='NotationRef' href='#note_1_id'> 
      [1]</legal:note>
      <span>and within a table it is</span>
      <table>
        <tr>
          <td>
            <p>
              <span>Text in table with a note here</span>
              <legal:note property='NotationRef' href='#note_2_id'> 
              [2]</legal:note>
            </p>
          </td>
        </tr>
      </table>
    </p>
    <div>
      <ol property='TableOfNotations>
        <li xml:id='note_1_id'>
          <legal:id>[1]</legal:id>
          <legal:note property='Notation'>para note content here</legal:note>
        </li>
        <li xml:id='note_2_id'>
          <legal:id>[2]</legal:id>
          <legal:note property='Notation'>table note content here</legal:note>
        </li>
      </ol>
    </div>
</legal:instrument>

4.1.7 The page element Content Model

The page element characterizes Normative Presentation documents. See the Design Overview and Instrument Formatting for justification for this element, and for information about the pagination process.

Within each of its document divisions, a paginated legal instrument contains content that flows from one page to another. In the coding sample below, a standard method is demonstrated for maintaining the instrument's hierarchy as content is flowed across pages. The method relies on the about attribute referencing the structural element that has been continued on a page following its starting page. In the sample, note that the continued section contains a different heading than that originally provided for the clause.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<legal:instrument property='NormativePresentation' resource='.../R1234567.xhtml'>
  <legal:page>
    <p resource='Para.1>
      <span>
        Often a preamble or recital paragraph precedes
        numbered clauses within the document.
      </span>
    </p>
    <section resource='Article.1'>
      <h>
        <legal:id>1.0</legal:id>
        <span>Terms and Conditions</span>
      </h>
      <p resource='Article.1.Para.1'>
        <span>A complete paragraph</span>
      </p>
      <p resource='Article.1.Para.2'>
        <span>An incomplete paragraph starts here, and ends on the next page.</span>
      </p>
    </section>
  </legal:page>
  <legal:page>
    <section about='Article.1'>
      <h>
        <legal:id>1.0</legal:id>
        <span>Terms and Conditions</span><span>, continued</span>
      </h>
      <p about='Article.1.Para.2'>
        <span>The incomplete paragraph ends on this page.</span>
      </p>
      <p resource='Article.1.Para.3'>
        <span>The last paragraph of the article.</span>
      </p>
    </section>
    <section resource='Article.2'>
      <p resource='Article.2.Para.1'>
        <span>paragraph for next article.</span>
      </p>
    </section>
  </legal:page>
</legal:instrument>

4.1.8 The sidebar element Content Model

Legal instruments may contain blocks of text and images that are application-related (such as action buttons) and that are not to be construed as operative content of the instrument.

The sidebar element is used to encapsulate all markup that is to be removed from a legal instrument prior to its placement into a Signed Envelope.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

Legal XHTML Document Skeleton

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE html PUBLIC "-//LEGALXHTML//DTD XHTML LEGAL 1.0//EN" "TBD">

<html xmlns="http://www.w3.org/2002/06/xhtml2"
      xmlns:legal="http://www.legalxhtml.org/xmlns/legalxhtml-1"
      xmlns:form="http://www.w3.org/TR/2003/REC-xforms-20031014/"
      xmlns:event="http://www.w3.org/2001/xml-events"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xsi:schemaLocation="http:///www.legalxhtml.org/legalxhtml-1.xsd"
      version="TBD" xml:lang='EN'>
      
  <head>
        <title>any title</title>
  </head>
  
  <body>
        <legal:instrument resource='.../R12344.html'/>
  </body>
  
</html>

Legal XHTML Document Form Skeleton

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE html PUBLIC "-//LEGALXHTML//DTD XHTML LEGAL 1.0//EN" "TBD">

<html xmlns="http://www.w3.org/2002/06/xhtml2"
      xmlns:legal="http://www.legalxhtml.org/xmlns/legalxhtml-1"
      xmlns:form="http://www.w3.org/TR/2003/REC-xforms-20031014/"
      xmlns:ev="http://www.w3.org/2001/xml-events"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:dc=""http://purl.org/dc/elements/1.1/""
      xsi:schemaLocation="http:///www.legalxhtml.org/legalxhtml-1.xsd"
      version="TBD" xml:lang='EN'>
      
  <head>
        <title>any title</title>
  </head>
  
  <body>
        <legal:instrument resource='.../R12344.html'/>
  </body>
  
</html>

4.2.1 The html element

Legal XHTML documents "strictly conform" to XHTML 2.0 guidelines. Legal XHTML documents

• must specify the DOCTYPE for the document, referencing that defined for Legal XHTML
• the html element must identify XHTML 2.0 as the default namespace for the document, and must identify the Resource Description Framework (RDF) namespace
• the html element must identify the location of the XML Schema for Legal XHTML and must provide the URI for the XML Schema namespace

Further, all Legal XHTML documents

• should specify the version attribute on the html element so that processors can identify the document as an XHTML Family Document
• should specify the xml:lang attribute on the html element, identifying the dominant natural language for the instrument(s) within the Legal XHTML document. If multiple languages are used for documents located within the body element then this attribute should not be specified.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

4.2.2 The head element

All Legal XHTML documents must contain a head element within an html element.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

4.2.3 The title element

All Legal XHTML documents must contain a title element within a head element.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

4.2.4 The body element

All Legal XHTML documents must contain a body element within an html element.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

4.3.1 The address element Content Model

This block-level element contains metadata ("contact information for a document or a major part of a document") that can change over time, and therefore should not be used within an instrument element.

Normative Transform
Do not output this element to a Normative Instrument.
Create the following in a Origination Record:

<rdf:Description rdf:about='firstAncestorURI'>
  <has>
    <dc:Publisher>
      <has>
        <dc:Identifier xsi:type='Address' text='text from address element'/>
      </has>
    </dc:Publisher>
  </has>
</rdf:Description>

4.3.2 The blockcode element Content Model

This element has semantic relevance within a legal instrument: its content is inconstruable to natural language processors. Within an instrument element, this block-level element should have only a p element as its parent element.

Normative Transform
Insert a parent p element as necessary into a Normative Instrument.
Ensure text content is located in a span element.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

4.3.3 The blockquote element Content Model

Within an instrument element, this block-level element should have only a p element as its parent element.

Normative Transform
Insert a parent p element as necessary into a Normative Instrument.
Ensure text content is located in a span element.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

4.3.4 The div element Content Model

In a legal instrument, the div element represents a document part, distinguishing front matter and back matter from the body of paragraphs and clauses that comprise the instrument. Front matter includes cover pages, tables of contents, and tables of figures. Back matter includes attachments, sub-instruments, and indexes.

Normative Transform
Ensure the parent element is an instrument or another div, raising an invalid structure error if not.
Ensure text content is located in a span element.

property = QName

Indicates the semantic applicable to this element. Reserved values are

Appendix

The element is for one or more pages normally referenced within the instrument clauses or paragraphs and which is normally included in a Table of Contents for the instrument.

Attachment

The element is an attachment to the containing instrument that may or may not be referenced by the instrument clauses and paragraphs, but which is normally excluded from a Table of Contents for the instrument.

BackMatter

The element is for one or more pages following the instrument clauses and paragraphs, normally containing one or more document indexes.

BlankPage

The element is for one or more 'blank' pages which may have content indicating that it is a blank page.

CoverPage

The element is for one or more cover pages for the document. A cover page normally does not carry a page header or footer.

FrontMatter

The element is for one or more pages located prior to the instrument clauses and paragraphs, normally containing one or more document indexes.

SubInstrument

The element is an instrument subordinate to the containing instrument which is normally included in a Table of Contents for the instrument.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
  <div property='CoverPage' resource='CoverPage.1'>
    <h1>
      <l>Lease Contract</l>
      <l>Between</l>
      <l>Party #1 and Party #2</l>
    </h1>
    <h2>Dated January 5, 2005</h2>
  </div>
  <div property='FrontMatter' resource='FrontMatter.1'>
    <p>
      <nl property='TableOfContents'>
        <li href='#Sec1'>Section 1</li>
        <li href='#Sec2'>Section 2</li>
        ...
        <li href='#SubInstrument.1'>Declaration of Corporate Officers</li>
        <li href='#Appendix.1'>Example Commencement Memorandum</li>
      </nl>
      <nl property='TableOfFigures'>
        <li href='#Tab1'>Table 1</li>
        <li href='#Obj1'>Figure 1</li>
      </nl>
    </p>
  </div>
  <div property='BlankPage' resource='BlankPage.1'>
    <p>
      <l>This page is intentionally blank.</l>
    </p>
  </div>
  ...
  <div property='SubInstrument' resource='SubInstrument.1'>
    <legal:instrument property='NormativeInstrument'
                      resource='.../R1234567.html#CorporateDeclaration'>
    ...
   </legal:instrument>
  </div>
  <div property='Appendix' resource='Appendix.1'>
    <h1>
      <l>Example</l>
      <l>Commencement Memorandum</l>
    </h1>
    ...
  </div>
</legal:instrument>

4.3.5 The heading elements Content Model

XHTML2 provides seven block-level XML elements for headings, and all may be used interchangeably. Six of the elements are normally used to indicate primary headings and varying levels of sub-headings, or to conveniently apply associated formatting styles. Legal XHTML documents duplicates this approach while constraining these six elements to be located within a div or section element; this accommodates the needs of cover pages and other material attached to the instrument, and the need for grouping sections and paragraphs in a manner irrelevant to their sequential numbering. In all other cases, the h element is to be used.

Structurally, Legal XHTML allows an optional id element and note element to be associated with the heading element.

Normative Transform
Convert h1 - h6 elements whose parent element is not a section or div element, to an h element.
Within paragraphs, convert consecutive h elements to a span-based structure.
Convert consecutive heading elements, of a type, to an l-based structure.
Raise a block structure warning if more than one heading element, of a type, exists for a block.
Ensure text content is located in a span element.

property = QName

Indicates the semantic applicable to this element. Common values are

dc:creator

The element contains the Dublin Core author for the legal instrument.

dc:date

The element contains the Dublin Core date for the legal instrument.

dc:subject

The element contains the Dublin Core subject for the legal instrument.

dc:title

The element contains the Dublin Core title for the legal instrument.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
  <div property='CoverPage' resource='CoverPage.1'>
    <h1 property='dc:title'>
      <l>Lease Contract</l>
      <l>Between</l>
      <l>Party #1 and Party #2</l>
    </h1>
    <h2 property='dc:subject'>
      <l style='text-decoration:underline>Rental Unit</l>
      <l>211 Taylor Street #32-A</l>
      <l>Port Townsend WA 98368</l>
    </h2>
    <h3 property='dc:date'>Dated January 5, 2005</h3>
    <h4 property='dc:creator'>
      <l style='text-decoration:underline>Prepared by</l>
      <l>McClure and Associates</l>
    </h4>
  </div>
    ...
</legal:instrument>

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
</legal:instrument>

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
    <h><legal:id>Article 1</legal:id></h>
    <p>
      <span>article 1 text.</span>
    </p>
    <section property='Clause' resource='Clause.1.1'>
      <h><legal:id>Article 1 Section 1</legal:id></h>
      <p>
        <span>section 1 text.</span>
      </p>
      <section property='Clause' resource='Clause.1.1.1'>
        <h><legal:id>Article 1 Section 1 Clause 1</legal:id></h>
        <p>
          <span>clause 1 text.</span>
        </p>
        <h2><span>Sub clause set A</span></h2>
        <section property='Clause' resource='Clause.1.1.1.1'/>
        <section property='Clause' resource='Clause.1.1.1.2'/>
        <section property='Clause' resource='Clause.1.1.1.3'/>
        <h2><span>Sub clause set B</span></h2>
        <section property='Clause' resource='Clause.1.1.1.4'/>
        <section property='Clause' resource='Clause.1.1.1.5'/>
        <section property='Clause' resource='Clause.1.1.1.6'/>
      </section>
    </section>
  </section>
</legal:instrument>

<legal:instrument property='NormativeInstrument' resource='.../ 
R1234567.html'>
</legal:instrument>

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
</legal:instrument>

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
</legal:instrument>

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
</legal:instrument>

4.3.6 The p element Content Model

The p element represents a grammatical paragraph which cannot be nested.

Structurally, Legal XHTML allows an author to associate an h element with the p element, however note that paragraph headings are formatted as in-line components by default . Further, the paragraph may contain specifications for a running header and running footer, and for one or more note elements.

Normative Transform
Ensure text content is located in a span element.

resource = URI

A resource identifier is required for every section to enable easy reference by metadata documents.

Common Attributes

See Core, Events, I18N, Bi-directional, Edit, Embedding, Map, Metadata, and Hypertext.

<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
  <p resource='Para.1'>
    <h>
      <span>Introduction</span>
    </h>
    <span>document introductory text.</span>
  </p>
  <section>
    <h>
      <legal:id>Article 1</legal:id>
    </h>