This section contains guidelines for each type of element that can appear in a Legal XHTML document. These elements are presented according to the modules defined by XHTML 2.0. One additional module is also described, the Legal XHTML Module, which contains several additional elements extending the XHTML 2.0 set of elements.
This module contains XML elements which extend those provided by XHTML 2.0. The objectives of these elements are to
| Element | Content Model |
|---|---|
| endorsement | (PCDATA | Text | Controls | Object | Scripting | Metadata)* |
| footer | note*,
(PCDATA | Text | Controls
| Object | Scripting
| Metadata | endorsement)*,
id?, (PCDATA | Text | Controls | Object | Scripting | Metadata | endorsement)* |
| header | (PCDATA | Text
| Controls | Object | Scripting
| Metadata | endorsement)*,
id?, (PCDATA | Text | Controls | Object | Scripting | Metadata | endorsement)* |
| id | (PCDATA | object | id | Text | Controls | Object | Scripting | Metadata)* |
| instrument | Metadata*,
Scripting*, page+ | (div*, (heading | p | section | sidebar? | endorsement)+, div*), header?, footer? |
| note | id?, (PCDATA | Text | Controls | Object | Scripting | Metadata)* |
| page | header?, (div | endorsement | p | section)*, footer? |
| sidebar | (PCDATA | Text | Controls | Object | Heading | Structural | Table | Scripting | Metadata)* |
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:
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.
This is an optional attribute in a Normative Instrument, and is a required attribute in a Normative Presentation.
This is an optional attribute in a Normative Instrument, and is a required attribute in a Normative Presentation.
<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.
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.
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".
For example, if the ancestor's id contained "Article 3", then the caption for a child element could be generated as "Section 3.1".
For example, if the ancestor id contains "Appendix C", then the caption for a child element could be generated as "Appendix C-1".
<!-- 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>
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.
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.
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.
<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.
<!-- 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.
<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.
The XHTML Document Module defines four XML elements whose usage in Legal XHTML documents, Normative Instruments, and Normative Presentations is described by this section.
| Element | Attributes | Content Model |
|---|---|---|
| html | Common | (head, body) |
| head | Common | (title | Scripting | Metadata | Scripting | Stylesheet | XForms | XEvents) |
| title | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata)* |
| body | Common | (PCDATA | Heading | Structural | Tables | Scripting | Metadata | instrument | List)* |
<?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>
<?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>
Legal XHTML documents "strictly conform" to XHTML 2.0 guidelines. Legal XHTML documents
Further, all Legal XHTML documents
All Legal XHTML documents must contain a head element within an html element.
All Legal XHTML documents must contain a title element within a head element.
All Legal XHTML documents must contain a body element within an html element.
The XHTML Structural Module defines fifteen elements whose uses in Legal XHTML documents are described by this section.
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.
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.
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.
<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.
<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.
<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> <p resource='Article.1.Para.1'> <span>article 1 text.</span> </p> </section> <section> <h> <legal:id>Article 2</legal:id> </h> <p resource='Article.2.Para.1'> <h> <legal:id>1</legal:id> <span>Introduction</span> </h> <span>article introductory text.</span> </p> </section> </legal:instrument>4.3.7 The pre element Content Model
In XHTML2, the pre element identifies content whose internal white-spaces are sematically relevant. In Legal XHTML, this function is preserved. Structurally under Legal XHTML, an author may associate one or more note elements with a pre element.
Normative Transform
No instructions.
Within a legal instrument, the section element represents a text block (or 'clause') that is often subdivided into multiple paragraphs and sub-sections. In legal instruments, the caption for each of these 'clauses' must minimally contain a sequential identifier.
Structurally, Legal XHTML mandates that every section element must contain an h element which, in turn, must contain an id element. LegalXHTML also allows an author to specify a running header and running footer, and one or more note elements, applicable to the clause.
Normative Transform
Raise a structure error if the first child element is not an h
element or its first child is not an id element.
Ensure text content is located in a span element.
<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Clause.1' property='Clause'> <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> </section> </section> </section> </legal:instrument>4.3.9 The separator element Content Model
In XHTML2, the separator element by default represents a horizontal line. Legal XHTML preserves this function.
Normative Transform
No instructions.
The XHTML Text Module defines fourteen elements whose use in Legal XHTML documents is described by this section. Generally, Legal XHTML adds the note element to all elements in this module except the superscript and subscript elements, sup and sub, respectively.
Note: The "Text" content set referenced below and elsewhere in this document includes all XML elements defined by this module except for the sub and sup elements.
Legal instruments often contain abbreviations and acronyms. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Citations within legal instruments are made to bibliographic entries, and to legal authorities. These comprise the entries to either a Table of Citations or a Table of Authorities for a legal instrument.
Normative Transform
Raise an error if an xml:id attribute is not present when a TableOfAuthorities
is present.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p>Text for paragraph with a resource citation here <cite> <legal:id>JONES</legal:id> para citation here </cite> and within a table it is <table> <tr> <td>Text in table with a reference here <cite> <legal:id>SMITH</legal:id> table citation here </cite> </td> </tr> </table> </p> ... <div property='BackMatter'> <p> <dl property='TableOfCitations> <legal:id template='template'>[<legal:id/>]</legal:id> <di/> </dl> </p> </div> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html' property='NormativeInstrument'> <p> <span>Text for paragraph with a citation here</span> <cite property='CitationRef' href='#ref_1_id'> <legal:id>[JONES]</legal:id> </cite> <span>and within a table it is</span> <table> <tr> <td> <p> <span>Text in table with a citation here</span> <cite property='CitationRef' href='#ref_2_id'> <legal:id>[SMITH]</legal:id> </cite> </p> </td> </tr> </table> </p> ... <div property='BackMatter'> <p> <dl property='TableOfCitations'> <di xml:id='ref_1_id'> <dt> <legal:id>[JONES]</legal:id> </dt> <dd> <cite property='Citation'>para citation here< /cite> </dd> </di> <di xml:id='ref_2_id'> <dt> <legal:id>[SMITH]</legal:id> </dt> <dd> <cite property='Citation'>table citation here</cite> </dd> </di> </dl> </p> </div> </legal:instrument>
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <cite property='LegalAuthority'> Smith v Jones, 37 Adj 3d 421 (1968) </cite> more text </p> </section> <div property='BackMatter'> <p> <dl property='TableOfAuthorities'> <label>Table Of Authorities</label> <di/> </dl> </p> </div> </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <cite property='LegalAuthority' xml:id='Citation.1'> Smith v Jones, 37 Adj 3d 421 (1968) </cite> <span>more text</span> </p> </section> <div property='BackMatter'> <p> <dl property='TableOfAuthorities'> <label>Table Of Authorities</label> <di> <dt> <cite property='LegalAuthority'>Smith v Jones, 37 Adj 3d 421 (1968)</cite> </dt> <dd> <span href='#Citation.1'>Article 1</span> </dd> </di> </dl> </p> </div> </legal:instrument>4.4.3 The code element Content Model
Legal instruments rarely need to represent computer code within a clause, however attachments to the legal instrument may require recitation of computer code. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Legal instruments can define text phrases within a clause or paragraph, outside the context of a formal list of terms. These in-line definitions are accommodated in XHTML2 by the dfn element, to which subsequent uses of the terms can be linked. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <dfn>A term</dfn> is defined here </p> </section> ... <section resource='Article.X'> <h> <legal:id>Article X</legal:id> </h> <p resource='Article.X.Paragraph.1'> section X text. A term is used here </p> </section> ... </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <dfn xml:id='Phrase.1' property='DocumentPhrase'>A term</dfn> <span>is defined here</span> </p> </section> ... <section resource='Article.X'> <h> <legal:id>Article X</legal:id> </h> <p resource='Article.X.Paragraph.1'> <span>section X text.</span> <span href='#Phrase.1'>A term</span> <span>is used here</span> </p> </section> ... </legal:instrument>4.4.5 The em element Content Model
Legal instruments may contain text that is to be emphasized, for aesthetic reasons. Legal XHTML preserves this function, and adds the capacity to associate notes with the item. Note that the strong element is construed as highlighting that is applied for legal reasons, not for aesthetic reasons.
<!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <em>emphasized text <legal:note>note text for emphasized term.</legal:note> </em> <span>more text here</span> </p> </section> ... </legal:instrument> <!-- Normative Presentation --> <legal:instrument property='NormativePresentation' resource='.../R1234567.html'> <legal:page> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <em> <span>emphasized text</span> <note><legal:id>[1]</legal:id></note> </em> <span>more text here</span> </p> </section> ... <legal:footer> <legal:note> <legal:id>[1]</legal:id> <span>note text for emphasized term.</span> </legal:note> </legal:footer> </legal:page> </legal:instrument>4.4.6 The kbd element Content Model
Legal instruments rarely need to represent keyboard keys within a clause, however attachments to the legal instrument, such as a User Manual, may require representation of a keyboard key. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Legal instruments often need to identify specific lines of text, most particularly within signature blocks which follow the paragraphs and clauses within the instrument. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
<legal:instrument property='NormativeInstrument' resource='.../R1234567.html'>
...
<p property='SignatureBlock' style='float:left;line-height:95%'>
<l>Signed this date:</l>
<l style='padding-left:20em;'>October 22, 2004</l>
<l>
<span style='width:20em;border-top:1px black solid'>
<legal:endorsement>John Adams</legal:endorsement>
<span>, Purchaser</span>
</span>
<span style='width:8em;border-top:1px black solid'>Date</span>
</l>
<l>200 Main Street</l>
<l>Someplace, WA 98333</l>
</p>
...
</legal:instrument>
4.4.8 The quote
element
Content Model
Legal instruments can include in-line text quotations. Legal XHTML preserves this function, and adds the capacity to identify content that is to be added prior to and following the quote. notes may also be associated with the item.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <quote legal:marks='"'> quoted text <legal:note>note text for quoted text.</legal:note> </quote> more text here </p> </section> ... </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <quote> <span>"</span><span>quoted text</span><span >"</span> <legal:note>note text for quoted text.</legal:note><span>"</span> </quote> <span>more text here</span> </p> </section> ... </legal:instrument> <!-- Normative Presentation --> <legal:instrument property='NormativePresentation' resource='.../R1234567.html'> <legal:page> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <quote> <span>"</span><span>quoted text</span><span>"</span> <note><legal:id>[1]</legal:id></note><span>"</span> </quote> <span>more text here</span> </p> </section> ... <legal:footer> <legal:note> <legal:id>[1]</legal:id> <span>note text for emphasized term.</span> </legal:note> </legal:footer> </legal:page> </legal:instrument>4.4.9 The samp element Content Model
Legal instruments rarely need to represent computer output within a clause, however attachments to the legal instrument, such as a User Manual, may require this representation. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Legal instruments often need to specify formatting or other metadata for particular text phrases. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Legal instruments may contain text that is to be highlighted, for legal reasons. Legal XHTML preserves this function, and adds the capacity to associate notes with the item. Note that the em element is construed as highlighting that is applied for aesthetic reasons, not for legal reasons.
<!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <strong> <span>highlighted text</span> <legal:note>note text for highlighted text.</legal:note> </strong> <span>more text here</span> </p> </section> ... </legal:instrument> <!-- Normative Presentation --> <legal:instrument property='NormativePresentation' resource='.../R1234567.html'> <legal:page> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <span>section 1 text.</span> <strong> <span>highlighted text</span> <note><legal:id>[1]</legal:id></note> </strong> <span>more text here</span> </p> </section> ... <legal:footer> <legal:note> <legal:id>[1]</legal:id> <span>note text for highlighted text.</span> </legal:note> </legal:footer> </legal:page> </legal:instrument>4.4.12 The sub element Content Model
Legal instruments may contain text that is to be subscripted. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Legal instruments may contain text that is to be superscripted. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Legal instruments rarely need to represent variables for computer programs within a clause, however attachments to the legal instrument, such as a User Manual, may require this representation. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
The XHTML2 Hypertext Module defines one element primarily for purposes of backwards compatibility. Legal XHTML however uses this element to indicate a reference within text to a location internal to the instrument or document division.
| Element | Attributes | Content Model |
|---|---|---|
| a | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata | note)* |
Under XHTML2, a elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a link to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>
The XHTML List Module defines four types of lists, and their supporting elements.
| Element | Attributes | Content Model |
|---|---|---|
| dl | Common | id?, label?, ((dt | dd)+ | di) |
| di | Common | dt+, dd* |
| dt | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata | note)* |
| dd | Common | (PCDATA | Heading | Structural | Tables | Scripting | Metadata | Text | Controls | Object | note)* |
| label | Common | id?, (PCDATA | Text | Controls | Object | Scripting | Metadata | note)* |
| nl | Common | id?, label, li+ |
| ol | Common | id?, label?, li+ |
| ul | Common | id?, label?, li+ |
| li | Common | id?, (PCDATA | Heading | Structural | Tables | Scripting | Metadata | Text | Controls | Object | note)* |
Legal instruments often have a section or clause that defines terms and phrases used in the instrument. Complex instruments also may need to include a TableOfCitations whose entries are phrases used to represent a document reference. The dl element is used for these lists.
Normative Transform
Attach the Glossary property attribute if not present,
declaring the semantic of the list.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h><legal:id template='template'><legal:id/></legal:id> Terms</h> <p> <dl> <dt>a phrase</dt> <dd>a definition</dd> </dl> <p> </section> ... </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>1</legal:id> <span>Terms</span> </h> <p resource='Article.1.Paragraph.1'> <dl property='Glossary'> <di> <dt>a phrase</dt> <dd>a definition</dd> </di> </dl> </p> </section> ... </legal:instrument>
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p>Text for paragraph with a resource citation here <cite> <legal:id>JONES</legal:id> para citation here </cite> </p> ... <div property='BackMatter'> <p> <dl property='TableOfCitations> <legal:id>[<legal:id/>]</legal:id> <di/> </dl> </p> </div> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html' property=' NormativeInstrument'> <p> <span>Text for paragraph with a citation here</span> <cite property='CitationRef' href='#ref_1_id'> <legal:id>[JONES]</legal:id> </cite> </p> ... <div property='BackMatter'> <p> <dl property='TableOfCitations'> <di xml:id='ref_1_id'> <dt> <legal:id>[JONES]</legal:id> </dt> <dd> <cite property='Citation'>para citation here</cite> </dd> </di> </dl> </p> </div> </legal:instrument>4.6.2 The di element Content Model
XHTML2 defines the di element to optionally encapsulate a term and its definition. Normative Instruments require this element.
Normative Transform
Attach an xml:id attribute if not present, for links to
the definition(s) contained by the element.
Locate other instances of its defined term, and attach an href
attribute linking to this element.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h><legal:id template='template'><legal:id/></legal:id> Terms</h> <dl> <dt>a phrase</dt> <dd>a definition</dd> </dl> </section> ... </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>1</legal:id> <span>Terms</span> </h> <p resource='Article.1.Paragraph.1'> <dl property='Glossary'> <di property='PhraseDefinition' xml:id='Definition.1'> <dt property='DefinitionPhrase' about='Definition.1'>a phrase</dt> <dd property='DefinitionSense' about='Definition.1'>a definition</dd> </di> </dl> </p> </section> ... </legal:instrument>4.6.3 The dt element Content Model
Defined terms are named in a dt element. Legal XHTML preserves this function and extends it by allowing the term to have associated notes.
Normative Transform
Insert a parent di element if not present, formally
encapsulating this and subsequent dd elements.
Attach an xml:id attribute if not present, for
reference by its subsequent dd elements.
Attach the Phrase property attribute if not present,
declaring the semantic of the text.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h><legal:id template='template'><legal:id/></legal:id> Terms</h> <dl> <dt>a phrase</dt> <dd>a definition</dd> </dl> </section> ... </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>1</legal:id> <span>Terms</span> </h> <p resource='Article.1.Paragraph.1'> <dl property='Glossary'> <di property='PhraseDefinition' xml:id='Definition.1'> <dt property='TermLabel' resource='TermLabel.1'> a phrase</dt> <dd property='PhraseDefinition' >a definition</dd> </di> </dl> </p> </section> ... </legal:instrument>4.6.4 The dd element Content Model
Terms are provided definitions in one or more dd elements. Legal XHTML preserves this function and extends it by allowing the definition to have associated notes.
Normative Transform
Attach an about attribute if not present pointing at
the phrase being defined.
Attach the Definition property attribute if not present,
declaring the semantic of the text.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h><legal:id template='template'><legal:id/></legal:id> Terms</h> <dl> <dt>a phrase</dt> <dd>a definition</dd> <dd>another definition</dd> </dl> </section> ... </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>1</legal:id> <span>Terms</span> </h> <p resource='Article.1.Paragraph.1'> <dl property='Glossary'> <di xml:id='Definition.1' resource='Definition.1'> <dt property='TermLabel' about='Definition.1'>a phrase</dt> <dd property='PhraseDefinition' about='Definition.1'> a definition </dd> <dd property='PhraseDefinition' about='Definition.1'> another definition </dd> </di> </dl> </p> </section> ... </legal:instrument>4.6.5 The label element Content Model
XHTML2 provides the label element for captioning XHTML lists. Captioning is optional for the ul, ol, and dl list elements; captioning is required for the nl list element.
Normative Transform
No instructions.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p> <ol> <legal:id template='template' format='decimal'><legal:id/></legal:id> <label> <legal:id template='template'>List <legal:id/></legal:id> A list caption </label> <li>item one</li> <li>item two</li> </ol> </p> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html'> <p> <ol> <label> <legal:id>List 1</legal:id> <span>A list caption</span> </label> <li> <legal:id>1.</legal:id> <span>item one</span> </li> <li> <legal:id>2.</legal:id> <span>item two</span> </li> </ol> </p> </legal:instrument>4.6.6 The nl element Content Model
Complex legal instruments often contain indexes of the clauses, tables, images, references, and other material found within the instrument or within a division of the instrument, for instance, an attachment. The nl element is used to represent each of these indexes.
Normative Transform
Insert a parent p element if not present, enforcing the
Grammatical Paragraph mandate.
Attach the DocumentIndex property attribute if not
present, declaring the semantic of the list.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p> <nl> <label> <legal:id template='template'>List <legal:id/></legal:id> A required caption </label> <li href='#link1'>item one</li> <li href='#link2'>item two</li> </nl> </p> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html'> <p> <nl property='DocumentIndex'> <label> <legal:id>List 1</legal:id> <span>A list caption</span> </label> <li href='#link1'>item one</li> <li href='#link2'>item two</li> </nl> </p> </legal:instrument>4.6.7 The ol element Content Model
XHTML2 provides the ol element for lists that are to be automatically enumerated by user agents. Complex instruments often need to include a list of notes or citations whose entries are referenced in the body of the text for the instrument or document division.
Normative Transform
Attach the List property attribute if not present, the
default semantic.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p> <ol> <legal:id template='template'>< legal:id/>)</legal:id> <li>item one</li> </ol> </p> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html'> <p> <ol property='List'> <li> <legal:id>1)</legal:id> <span>item one</span> </li> </ol> </p> </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> </p> <div> <p> <ol property='TableOfNotations> <legal:id template='template'>[<legal:id/>]</legal:id> <li/> </ol> </p> </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> </p> <div property='BackMatter'> <p> <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> </ol> </p> </div> </legal:instrument>4.6.8 The ul element Content Model
XHTML2 provides the ul element for lists that are to be automatically bulleted by user agents. Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Normative Transform
Attach the List property attribute if not present, the
default semantic.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p> <ul> <legal:id template='template'>< legal:id/>)</legal:id> <li>item one</li> </ul> </p> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html'> <p> <ul> <li> <legal:id> <object property='Figure' href='image_uri' alt='1'/> </legal:id> <span>item one</span> </li> </ul> </p> </legal:instrument>4.6.9 The li element Content Model
Legal XHTML preserves this function, and adds the capacity to associate notes with the item.
Normative Transform
Generate the id element for the list item, using the
parent's template information.
<!-- Legal XHTML Document --> <legal:instrument resource='.../R12344.html'> <p> <ol> <legal:id template='template'><legal:id/>)</legal:id> <li>item one</li> </ol> </p> </legal:instrument> <!-- Normative Instrument --> <legal:instrument resource='.../R12344.html'> <p> <ol> <li> <legal:id>1)</legal:id> <span>item one</span> </li> </ol> </p> </legal:instrument>
The XHTML Core Attributes Module is a required module for XHTML2 Host Language Conforming Document Types such as Legal XHTML. It defines three attributes that may be used by all Legal XHTML elements.
Specification: class = NMTOKENS
The class attribute has been historically used to associate presentation directives with HTML elements. Legal XHTML preserves this function, defining no particular semantic for this attribute.
Normative Transform
Transfer valid values of this attribute without change.
Report invalid values for this attribute.
XHTML2 is likely replacing this attribute with use of the xml:id attribute now being developed by the W3C. In any event, the value for this attribute must be unique within a document.
Normative Transform
Transfer valid values of this attribute without change.
Report non-unique and invalid values for this attribute.
The title attribute is normally the 'tool-tip' displayed during a mouseover event for an XHTML2 element. Legal XHTML preserves this function, defining no particular semantic for this attribute.
Normative Transform
Transfer valid values of this attribute without change.
Report invalid values for this attribute.
The XHTML Hypertext Attributes Module is a required module for XHTML2 Host Language Conforming Document Types such as Legal XHTML. It defines nine attributes that may be used by all Legal XHTML elements.
This attribute contains the Uniform Resource Identifier of the target location for a link.
Normative Transform
Transfer valid values of this attribute without change.
For intra-instrument links, report target locations not found in the instrument.
For links between document divisions, report target locations found in
attachments.
Specification: hreftype = ContentTypes
This attribute contains specifications for the 'accept' parameter in an HTTP request for the resource identified by the URI specified in the href attribute.
Normative Transform
Transfer valid values of this attribute without change.
Specification: hreflang = LanguageCodes
This attribute contains specifications for the 'accept-language' parameter in an HTTP request for the resource identified by the URI specified in the href attribute.
Normative Transform
Transfer valid values of this attribute without change.
Report invalid values for this attribute.
This attribute contains the Uniform Resource Identifier of a source document that is related to the (text) content of the attribute's element. This is a hidden citation, in comparison to an explicit visible citation provided by the cite element; as such, it should be included in any TableOfCitations located within the instrument or document division, with the captioning text string of "Not Visible".
Normative Transform
Transfer valid values of this attribute without change.
Specification: target = NMTOKEN
This attribute contains the Uniform Resource Identifier of an applications environment that is to display the resource indicated by the href attribute value.
Normative Transform
Transfer valid values of this attribute without change.
This attribute contains the name of a navigational index for the resource indicated by the href attribute value.
Normative Transform
Transfer valid values of this attribute without change.
Specification: nextfocus = IDREF
This attribute identifies the next element in a tabbing sequence within the instrument or document division.
Normative Transform
Transfer valid values of this attribute without change.
Specification: prevfocus = IDREF
This attribute identifies the previous element in a tabbing sequence within the instrument or document division.
Normative Transform
Transfer valid values of this attribute without change.
This attribute contains a Uniform Resource Identifier that is to be used to resolve a relative URI specified by the href attribute.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML I18N Attributes Module is included in the Legal XHTML Document Type. It defines one attribute that may be used by all Legal XHTML elements.
Specification: xml:lang = LanguageCode
This attribute identifies the language of the text content within a Legal XHTML element.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Bi-directional Text Module is included in the Legal XHTML Document Type. It defines one attribute that may be used by all Legal XHTML elements.
Specification: dir = 'ltr | rtl | lto | rto'
This attribute identifies the writing direction for the text content within a Legal XHTML element.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Edit Attributes Module is included in the Legal XHTML Document Type. It defines two attributes that may be used by all Legal XHTML elements.
Specification: datetime = Datetime
This attribute identifies when text content within a Legal XHTML element was last changed.
Normative Transform
Transfer valid values of this attribute without change.
Specification: edit = "inserted | deleted | changed | moved"
This attribute identifies how text content within a Legal XHTML element was last changed.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Embedding Attributes Module is included in the Legal XHTML Document Type. It defines two attributes that may be used by all Legal XHTML elements.
This attribute identifies a resource to be displayed instead of the Legal XHTML element; if the resource cannot be displayed by a user agent, then the contents of the Legal XHTML element is to be displayed. For the link element, this attribute identifies the resource that is being linked to the legal instrument.
Normative Transform
Transfer valid values of this attribute without change.
Specification: type = ContentTypes
This attribute contains specifications for the 'accept' parameter in an HTTP request for the URI specified in the src attribute.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Image Map Attributes Module is included in the Legal XHTML Document Type. It defines four attributes that may be used by all Legal XHTML elements.
This attribute associates an image map with an nl element. The value of usemap must match the value of the id attribute of an nl element that contains one or more li elements with shape and coords attributes.
Normative Transform
Transfer valid values of this attribute without change.
Specification: ismap = "ismap"
This attribute declares the element's display area is controlled by a "server-side " image map processor.
Normative Transform
Transfer valid values of this attribute without change.
Specification: shape = "default | rect | circle | poly"
This attribute identifies the shape of the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: coords = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Metadata Attributes Module is included in the Legal XHTML Document Type. It defines eight attributes that may be used by all Legal XHTML elements.
This attribute identifies the resource that has the property indicated or implied by the property attribute.
Normative Transform
Transfer valid values of this attribute without change.
Specification: content = CDATA
This attribute identifies the content for the property indicated or implied by the property attribute.
Normative Transform
Transfer valid values of this attribute without change.
Specification: datatype = QName
This attribute identifies the datatype of the content for the property indicated or implied by the property attribute.
Normative Transform
Transfer valid values of this attribute without change.
Specification: property = QName
This attribute identifies the property for the resource indicated or implied by the about attribute.
Normative Transform
Transfer valid values of this attribute without change.
This attribute identifies the relationship between the resources specified or implied by the about and resource attributes.
Normative Transform
Transfer valid values of this attribute without change.
This attribute identifies the resource that is named by the element's text content or, in the case of markup content or an empty element, this identifies the resource that is represented by the element.
Normative Transform
Transfer valid values of this attribute without change.
Create an xml:id from this value as needed.
Specification: restype = ContentTypes
This attribute contains specifications for the 'accept' parameter in an HTTP request for the URI specified in the resource attribute.
Normative Transform
Transfer valid values of this attribute without change.
This attribute identifies the relationship from the resource specified by the resource attribute to the current document, that is, the legal instrument.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Metadata Module is included in the Legal XHTML Document Type. It defines two XML elements that may be children of the a, body, dd, dt, endorsement, footer, head, header, id, instrument, label, li, meta, note, sidebar, or title elements, or any of the elements within the Object, Scripting, Structural, Tables, Text, XForms, and XEvents modules.
| Element | Attributes | Content Model |
|---|---|---|
| link | Common | (link | meta)* |
| meta | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata)* | meta+ |
The link element is used to associate another resource with the legal instrument or with an element within the legal instrument. Because legal instruments may be embedded within a larger XHTML document, link elements within the document's head element are ignored.
Normative Transform
Consolidate all links with about attributes, as
children of the instrument element.
Report other links appearing in any element other than the instrument
element.
Report non-standard attribute values.
Transfer valid links.
<legal:instrument resource='.../R1234567.html'> <link rel='meta' property='AdministrationRecord' src='/admin/R1234567.rdf'/> <link rel='meta' property='OriginationRecord' src='/negot/R1234567.rdf'/> <link rel='meta' property='FinancialAnalysis' src='/fin/R1234567.rdf'/> <link rel='meta' property='LegalAnalysis' src='/lgl/R1234567.rdf'/> ... </legal:instrument>
<legal:instrument resource='.../R1234567.html'> <link rel='alternate' media='print' src='/pdf/R1234567.pdf'/> <link rel='alternate' xml:lang='fr' src='/fr/R1234567.html'/> ... </legal:instrument>
<legal:instrument resource='.../R1234567-2.html'> <link rel='prev' title='previous folder document' src='/db/R1234567-1.html'/> <link rel='next' title='next folder document' src='/db/R1234567-3.html'/> ... </legal:instrument>
<legal:instrument resource='.../R1234567.html'>
<link rel='up' title='Document Folder' src='/db/R23456.html'/>
...
</legal:instrument>
<legal:instrument resource='.../R1234567.html'>
<link rel='copyright' title='Copyright Statement' src='/copyright.html'/>
...
</legal:instrument>
<legal:instrument resource='.../R1234567.html'> <link rel='glossary' title='Legal Glossary' src='/glossary.html'/> <link rel='help' title='About This Instrument' src='/help.html'/> ... </legal:instrument>4.14.2 The meta element Content Model
The meta element is used to convey textual metainformation about a legal instrument or about the element in which it is embedded. This element should not be used to convey metadata that is a Universal Resource Identifier (URI); rather, the link element is used to convey relationships with external resources.
Only Dublin Core metadata not conveyed by an element representing text formatted within the legal instrument, may be specified using the meta element contained by the instrument element.
Normative Transform
Consolidate all meta elements with about
attributes, as children of the instrument
element.
Report other meta elements appearing in any element
other than the instrument element.
Report non-standard attribute values.
Transfer valid meta elements.
<legal:instrument resource='.../R1234567.html'> <meta property='dc:contributor' content='name of contributor'/> <meta property='dc:coverage' content='name of contributor'/> <meta property='dc:creator' content='name of contributor'/> <meta property='dc:date' content='name of contributor'/> <meta property='dc:description' content='name of contributor'/> <meta property='dc:format' content='name of contributor'/> <meta property='dc:identifier' content='name of contributor'/> <meta property='dc:language' content='name of contributor'/> <meta property='dc:publisher' content='name of contributor'/> <meta property='dc:relation' content='name of contributor'/> <meta property='dc:rights' content='name of contributor'/> <meta property='dc:source' content='name of contributor'/> <meta property='dc:subject' content='name of contributor'/> <meta property='dc:title' content='name of contributor'/> <meta property='dc:type' content='name of contributor'/> ... </legal:instrument>
The XHTML Object Module is included in the Legal XHTML Document Type. It defines three XML elements that may be located within the a, caption, dd, dt, endorsement, footer, header, id, label, li, meta, note, object, summary, sidebar, td, th, or title elements, or any of the elements within the Scripting, Structural, and Text modules.
| Element | Attributes | Content Model |
|---|---|---|
| object | Common | caption?,
standby?, param*, (PCDATA | Text | Controls | Object | Scripting | Metadata | Structural | Tables | Heading)* |
| param | Common | EMPTY |
| standby | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata)* |
In Legal XHTML, the object element is ued for image figures.
Normative Transform
Report .
<!-- 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>4.16.2 The param element Content Model
The param element is not modified by Legal XHTML.
The standby element is not modified by Legal XHTML.
The Ruby Module is typically included in XHTML Family Documents that contain Asian language content. This module is not included by default in the Legal XHTML Document Type. Refer to the Ruby Module for information regarding the content model supported by XHTML 2.0, and refer to the Ruby Annotation specification for information about the individual elements.
The XHTML Scripting Module is included in the Legal XHTML Document Type. It defines one XML element that may be located within the a, caption, body, dd, dt, endorsement, footer, head, header, id, instrument, label, li, meta, note, object, sidebar, summary, td, tr, or title elements, or any of the elements within the Scripting, Structural, Tables, and Text modules.
| Element | Attributes | Content Model |
|---|---|---|
| script | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata | note)* |
An application may implement and execute scripts which retrieve values from a data source, format, and display, the resulting string or markup.
Normative Transform
Report .
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <script type='text/javascript' property='SelectionScript' resource='Script.1'> ... script for selecting the instrument ... </script> ... </legal:instrument>
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section> <script type='text/javascript' property='SelectionScript' resource='Script.2'> ... script for selecting the clause ... </script> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. </p> </section> </legal:instrument>
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section> <script type='text/javascript' property='MarkupScript' resource='Script.4'> ... script for generating or retrieving the clause content markup ... </script> </section> </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section> <script type='text/javascript' property='MarkupScript' src='#Script.4'/> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> ... generated text ... </p> </section> </legal:instrument>
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <script type='text/javascript' property='ValueScript' resource='Script.4'> ... script for generating or retrieving the paragraph content ... </script> </p> </section> </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> <script type='text/javascript' property='ValueScript' src='#Script.4'/> ... generated text ... </p> </section> </legal:instrument>
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> ... <span> <script type='text/javascript' property='ValueScript' resource='Script.4'> ... script for generating or retrieving the inline content ... </script> </span> ... </p> </section> </legal:instrument> <!-- Normative Instrument --> <legal:instrument property='NormativeInstrument' resource='.../R1234567.html'> <section> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> ... <span> <script type='text/javascript' property='ValueScript' src='#Script.4'/> ... generated text ... </span> ... </p> </section> </legal:instrument>
The XHTML Style Attributes Module is included in the Legal XHTML Document Type. It defines one attribute that may be used by all Legal XHTML elements.
This attribute identifies a resource to be displayed instead of the Legal XHTML element; if the resource cannot be displayed by a user agent, then the contents of the Legal XHTML element is to be displayed.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML Stylesheet Module is included in the Legal XHTML Document Type. It defines one XML element that may be located within the head element.
| Element | Attributes | Content Model |
|---|---|---|
| style | Common | PCDATA |
Under XHTML2, style elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a param to a location internal to the legal instrument or its document division,
The XHTML Tables Module is included in the Legal XHTML Document Type. It defines eleven XML elements which are described in this section. It defines one XML element that may be located within the body, blockcode, blockquote, div, section, dd, li, object, sidebar elements,
| Element | Attributes | Content Model |
|---|---|---|
| table | Common | caption?, summary?, (col* | colgroup*), ((thead?, tfoot?, tbody+) | tr+) |
| caption | Common | (PCDATA | Text | Controls | Object | Scripting | Metadata | note)* |
| summary | Common | (PCDATA | Heading | Structural | Tables | Text | Controls | Object | Scripting | Metadata | note)* |
| col | Common | EMPTY |
| colgroup | Common | col* |
| thead | Common | tr+ |
| tfoot | Common | tr+ |
| tbody | Common | tr+ |
| tr | Common | ( td | th)* |
| td | Common | (PCDATA | Heading | Structural | Tables | Text | Controls | Object | Scripting | Metadata | note)* |
| th | Common | (PCDATA | Heading | Structural | Tables | Text | Controls | Object | Scripting | Metadata | note)* |
Under XHTML2, table elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a table to a location internal to the legal instrument or its document division,
Under XHTML2, caption elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a caption to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.3 The summary element Content Model
Under XHTML2, summary elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a summary to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.4 The col element Content Model
Under XHTML2, col elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a col to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.5 The colgroup element Content Model
Under XHTML2, colgroup elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a colgroup to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.6 The thead element Content Model
Under XHTML2, thead elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a thead to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.7 The tfoot element Content Model
Under XHTML2, tfoot elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a tfoot to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.8 The tbody element Content Model
Under XHTML2, tbody elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a tbody to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.9 The tr element Content Model
Under XHTML2, tr elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a tr to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.10 The td element Content Model
Under XHTML2, td elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a td to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.21.11 The th element Content Model
Under XHTML2, th elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a th to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>
The XForms Core Module is included in the Legal XHTML Document Type. It defines four XML elements discussed in this section.
| Element | Attributes | Content Model |
|---|---|---|
| model | Common | (PCDATA | Text | Scripting | Metadata | note)* |
| instance | Common | ANY |
| submission | Common | Acion* |
| bind | Common | ANY |
Under XHTML2, model elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a table to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.22.2 The instance element Content Model
Under XHTML2, instance elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a instance to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.22.3 The submission element Content Model
Under XHTML2, submission elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a submission to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.22.4 The bind element Content Model
Under XHTML2, bind elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a bind to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>
The XForms Controls Module is included in the Legal XHTML Document Type. It defines nineteen XML elements, thirteen of which are briefly discussed here. The XForms Controls Module also defines five attributes that can be used on all Legal XHTML elements.
| Element | Attributes | Content Model |
|---|---|---|
| group | Common | (PCDATA | Text | Scripting | Metadata | note)* |
| input | Common | label, (help|hint|alert|action)* |
| output | Common | label? |
| range | Common | label, (help|hint|alert|action)* |
| repeat | Common | (PCDATA | Text | Scripting | Metadata | note)* |
| secret | Common | label, (help|hint|alert|action)* |
| select | Common | label, (choices|item|itemset)+, (help|hint|alert|action)* |
| selectl | Common | label, (choices|item|itemset)+, (help|hint|alert|action)* |
| submit | Common | label, (help|hint|alert|action)* |
| switch | Common | (PCDATA | Text | Scripting | Metadata | note)* |
| textarea | Common | label, (help|hint|alert|action)* |
| trigger | Common | label, (help|hint|alert|action)* |
| upload | Common | label, filename?, mediatype?, (help|hint|alert|action)* |
Under XHTML2, th elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a th to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.2 The input element Content Model
Under XHTML2, input elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a table to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.3 The output element Content Model
Under XHTML2, output elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a output to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.4 The range element Content Model
Under XHTML2, range elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a range to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.5 The repeat element Content Model
Under XHTML2, th elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a th to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.6 The secret element Content Model
Under XHTML2, secret elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a secret to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.7 The select element Content Model
Under XHTML2, tr elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a tr to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.9 The select1 element Content Model
Under XHTML2, td elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a td to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.9 The submit element Content Model
Under XHTML2, submit elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a submit to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.10 The switch element Content Model
Under XHTML2, th elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a th to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.11 The textarea element Content Model
Under XHTML2, textarea elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a textarea to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.12 The trigger element Content Model
Under XHTML2, trigger elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a trigger to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.23.10 The upload element Content Model
Under XHTML2, upload elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a upload to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>
XForms' three User Interface Modules (Group Module, Switch Module, and Repeat Module) are included in the Legal XHTML Document Type. They define nineteen XML elements, ten of which are briefly discussed here.
| Element | Attributes | Content Model |
|---|
Specification: repeat-model = URI
This attribute associates an image map with an nl element. The value of repeat-model must match the value of the id attribute of an nl element that contains one or more li elements with repeat-nodesete and repeat-startindex attributes.
Normative Transform
Transfer valid values of this attribute without change.
Specification: repeat-bind = "repeat-bind"
This attribute declares the element's display area is controlled by a "server-side " image map processor.
Normative Transform
Transfer valid values of this attribute without change.
Specification: repeat-nodesete = "default | rect | circle | poly"
This attribute identifies the repeat-nodesete of the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: repeat-startindex = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: repeat-startnumber = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
The XHTML XEvents Module is included in the Legal XHTML Document Type. It defines one XML element and seven attributes that can be used on all XHTML and Legal XHTML elements.
| Element | Attributes | Content Model |
|---|---|---|
| listener | Common | (PCDATA | Text | Scripting | Metadata | note)* |
Under XHTML2, th elements are functionally equivalent to span elements which specify an href attribute or, in the case of anchors, an id attribute.
Normative Instruments use a elements within its text to declare a th to a location internal to the legal instrument or its document division,
<!-- Legal XHTML Document --> <legal:instrument resource='.../R1234567.html'> <section resource='Article.1'> <h> <legal:id>Article 1</legal:id> </h> <p resource='Article.1.Paragraph.1'> section 1 text. <a property='ClauseRef' href='#Article.5'> Article 5 </a> more text here </p> </section> ... </legal:instrument>4.24.2 The defaultAction attribute
Specification: defaultAction = URI
This attribute associates an image map with an nl element. The value of defaultAction must match the value of the id attribute of an nl element that contains one or more li elements with handlere and repeat-startindex attributes.
Normative Transform
Transfer valid values of this attribute without change.
Specification: event = "event"
This attribute declares the element's display area is controlled by a "server-side " image map processor.
Normative Transform
Transfer valid values of this attribute without change.
Specification: handler = "default | rect | circle | poly"
This attribute identifies the handler of the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: observer = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: phase = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: propagate = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
Specification: target = "default | rect | circle | poly"
This attribute contains display coordinate information for the region.
Normative Transform
Transfer valid values of this attribute without change.
The scope of Legal XHTML includes a relatively unstructured legal instrument, and various structured metadata documents that may be linked to the legal instrument. While legal instruments are encoded in XHTML2, all metadata documents are represented using the Resource Description Framework (RDF):
This section describes each object class that may be used within the metadata documents described above. For each class, its properties are identified and defined. This information about an object class is presented in a table divided into three parts:
|
"ClassName" Superclasses |
"ClassName" Subclasses |
Class Description | |
|---|---|---|---|
| superclass list | subclass list | Description of the class and justification or explanation of the choices made for its superclass(es). | |
| Attributes (Supertype) |
Subtypes | Attribute Description | |
| PropertyName (Resource) | SubpropertyName | Description of the property. Usually, a generic property is named here. The cardinality of the property within class instances is specified, however it is practically always a zero-to-many relationship. | |
| Subtypes (Superclass) |
Attribute Supertypes | Attribute Description | |
| SubpropertyName (Resource) | PropertyName | Description of the subproperty type. There are two types of properties. First, a property that is a plain text string. Second, a property that is another resource. In the former case, this property "contains" text or image data while, in the latter case, the class of the object represented by the property is named. | |
legal:instrument { overflow : hidden }
p h,
legal:footer h,
legal:header h { display:inline }
h legal:id { padding-right: 1em }
This stylesheet transforms a Legal XHTML document into a Normative Instrument.
| Error 001 | Invalid legal instrument structure. |
| Error 002 | <head> element must contain a <title> element. |
| Error 003 | <Atdress> elements are not allowed in a legal instrument. |
| Error 100 | Invalid attribute value. |
| Error 200 | Invalid attribute value. |
| Error 201 | Invalid attribute value -- URI expected. |
| Warning 100 | Empty attributes are not allowed in a Normative Instrument. |
This stylesheet extracts RDF resource information from an XHTML document.
Validation Messages, by NumberThis stylesheet extracts Dublin Core information from an XHTML document.
Validation Messages, by NumberThis stylesheet extracts Dublin Core information from an XHTML document.
Validation Messages, by Number