OASIS LegalXML Member Section XML Court Document 1.1 Proposed Specification

<!ELEMENT legal (courtDocument+)>

<legal/> is the root element of an XML court document and contains one or more required <courtDocument/> elements. This generic tag precedes all legal related XML.

<!ELEMENT courtDocument (documentMetadata , caseMetadata , documentBody , signers? , 
proofOfService? , attachedItem* , electronicSignature?)> 
<!ATTLIST courtDocument version CDATA #FIXED '1.1'>

<courtDocument/> holds the container elements for the contents of an XML court document. The<documentMetadata/>, <caseMetadata/>, and <documentBody/> elements must be present in the order stated. The <signers/>, <proofOfService/>, and <attachedItem/> elements are optional, but must appear in that order if used. There is also an optional <electronicSignature/> element which describes information about the electronic signature used for electronically signing a court document. The <courtDocument/> element has a fixed "version" attribute specifying the version number as "1.1".

<!ELEMENT documentMetadata (%documentMetadata.content;)>

<documentMetadata/> contains the elements for describing metadata about the XML court document. Its child elements and content model are described in the %documentMetadata.content; parameter entity. Only the <documentTitle/>, <documentType/>, and <format/> elements are required. The remaining child elements are optional.

The optional <displayInformation/> element contains information for displaying the XML court document. It has a content model substantially similar to the <attachedItemContent/> element with some additional attributes. It may contain display information, such as a stylesheet, as base-64 encoded text or, alternatively, as a <![CDATA[ (unparsed character data) section substantially similar to an attached item. The required "mimeType" attribute indicates how the contents of the <displayInformation/> element are to be interpreted (e.g., text/xsl, text/css, etc.). The optional "id" attribute describes the unique identifier for the display information. The optional "contentEncoding" attribute indicates the type of content encoding used and allows for future revisions. The optional "application" attribute names the application using the display information (e.g. Instant Saxon 6.2.2, msie 5.5, etc.), and the optional "description" attribute describes the general nature of the display information being provided (e.g. xslt stylesheet, etc.).

<!ELEMENT documentIdentifier (#PCDATA)>

<documentIdentifier/> contains an unambiguous reference, typically a string or number conforming to an identification system, uniquely identifying the court document. The <documentIdentifier/> element is substantially similar to the Dublin Core "identifier" element.

<!ELEMENT dateTimeCreated (%dateTime.content;)>

<dateTimeCreated/> contains the date and time associated with the creation or last modification of the court document. The <dateTimeCreated/> element is substantially similar to the Dublin Core "date" element and is based on the <creation/> element in the Court Filing 1.1 DTD. The %dateTime.content; parameter entity contains the content model for this element.

<!ELEMENT documentStatus (#PCDATA)>
<!ATTLIST documentStatus draft (draft | final ) 'draft'
privacy (sealed | redacted | restricted ) #IMPLIED
specialHandling (yes | no ) 'yes' >

<documentStatus/> is an optional element describing the status of the court document. The "draft" attribute indicates whether the court document is a draft or final version (the default enumerated attribute value is "draft"). The optional "privacy" enumerated attribute indicates whether the court document is sealed, redacted, or restricted. The "specialHandling" attribute indicates whether special handling of the court document is needed (the default enumerated attribute value is "yes"). If the <documentStatus/> element is not present in a court document, then the court document is presumed to be a final version which is not sealed or redacted and which does not require any special handling.

<!ELEMENT documentTitle (#PCDATA)>

<documentTitle/> contains the title or name given to the court document. It is a required element of the <documentMetadata/> element. The <documentTitle/> element is substantially similar to the Dublin Core "title" element and is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT documentType (#PCDATA)>
<!ATTLIST documentType documentCode CDATA #IMPLIED>

<documentType/> is a required element containing a description of the nature, category, or genre of the content of the court document (e.g. complaint, answer, order, etc.). The <documentType/> element is substantially similar to the Dublin Core "type" element and is incorporated from the Court Filing 1.1 DTD. For consistency with the Court Filing 1.1 DTD, it takes an optional "documentCode" attribute which can contain a specific code describing the type of court document.

<!ELEMENT creator (person | organization)>

<creator/> is a required element containing either a single <person/> or <organization/> element and describes the person or organization primarily responsible for making the content of the court document.

<!ELEMENT contributor (person | organization)>

<contributor/> is an optional element and may appear multiple times. It contains either a single <person/> or <organization/> element and describes a person or organization responsible for contributing to the content of the court document.

<!ELEMENT submitter (party | attorney | judicialOfficer | administrativeOfficer | 
enforcementOfficer | notary | court | agency)>

<submitter/> is a required element containing information regarding the party, attorney, judicial officer, administrative officer, enforcement officer, notary, court, or agency responsible for making the court document available by serving it or submitting it for filing. The <submitter/> element is substantially similar to the Dublin Core "publisher" element.

<!ELEMENT description (#PCDATA)>

<description/> is an optional element containing an abstract or text summary of the contents of the court document.

<!ELEMENT subject (#PCDATA)>

<subject/> is an optional element containing comma-separated keywords or key phrases describing the topic(s) addressed in the court document.

<!ELEMENT reference (link | image)*>
<!ATTLIST reference sourceTitle CDATA #IMPLIED
sourceCreator CDATA #IMPLIED
sourceDate CDATA #IMPLIED
sourceIdentifier CDATA #IMPLIED >

<reference/> contains links to related documents, images, or other resources or to documents or other resources from which the contents of the court document have been derived. The <reference/> element is substantially similar to the Dublin Core "relation" and "source" elements. It can contain multiple <link/> or <image/> elements. The <reference/> element uses optional attributes to provide additional information about a reference. The optional "sourceTitle" attribute contains the name of the referenced resource. The optional "sourceCreator" attribute describes the author or publisher of the referenced resource. The "sourceDate" attribute contains the date of the referenced resource in ISO 8601 number format. The "sourceIdentifier" attribute contains a string or number unambiguously identifying the referenced resource and typically conforming to a formal identification system, such as a URI or ISBN.

<!ELEMENT coverage (#PCDATA)>

<coverage/> is an optional element containing a description of the extent or scope of the content of the court document, such as the jurisdiction of the court or administrative agency to which or by which it is submitted.

<!ELEMENT language (#PCDATA)>

<language/> is an optional element containing a description of the language of the court document. The description of the language must follow RFC 1766 , which includes a two-letter language code from the ISO 639-1 standard followed optionally, by a two-letter country code from the ISO 3166 standard. For example, 'en' for English, 'fr' for French, or 'en-uk' for English as used in the United Kingdom.

<!ELEMENT format (#PCDATA)>

<format/> is a required element containing the media type, usually the MIME type (text/xml), of the court document.

<!ELEMENT displayInformation (#PCDATA)>
<!ATTLIST displayInformation id ID #IMPLIED
mimeType CDATA #REQUIRED
contentEncoding (base64 ) #IMPLIED
application CDATA #IMPLIED
description CDATA #IMPLIED >

The optional <displayInformation/> element contains information for displaying the XML court document. It has a content model substantially similar to the <attachedItemContent/> element with some additional attributes. It may contain display information, such as a stylesheet, as base-64 encoded text or, alternatively, as a <![CDATA[ (unparsed character data) section substantially similar to an attached item.

The required "mimeType" attribute indicates how the contents of the <displayInformation/> element are to be interpreted (e.g., text/xsl, text/css, etc.). The optional "id" attribute describes the unique identifier for the display information. The optional "contentEncoding" attribute indicates the type of content encoding used and allows for future revisions. The optional "application" attribute names the application using the display information (e.g. Instant Saxon 6.2.2, msie 5.5, etc.), and the optional "description" attribute describes the general nature of the display information being provided (e.g. xslt stylesheet, etc.).

<!ELEMENT party ((person | organization | inRem ) , attorney*)>
<!ATTLIST party id ID #IMPLIED
partyType CDATA #REQUIRED>

<party/> contains information about a person or organization that is a party in the proceeding. It contains either a single <person/>, <organization/>, or <inRem/> child element (and incorporates the respective content models used by those elements). Information about a party's attorney(s) is optionally contained in the <party/> element to reflect the attorney's relationship with the party.

The <party/> element has a required "partyType" attribute to describe the particular type of party, e.g. "Plaintiff," "Defendant," "Respondent," "Third-Party Defendant," etc. A more specific text description of the particular role of a party also can be contained in the <roleName/> element of the <person/> or <organization/> elements. The <party/> element has an optional "id" attribute.

<!ELEMENT victim (person | organization)+>
<!ATTLIST victim id ID #IMPLIED>

<victim/> contains information about a person or organization that is the victim of a crime or other wrong. It contains either a single <person/> or <organization/> child element, and thus incorporates the content models used by those elements. It has an optional "id" attribute.

<!ELEMENT person (%personName.content; , %contact.content; , personIdentification? , role* 
%person.ANY;)>
<!ATTLIST person id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<person/> contains the name, contact, identification, and specific role information for a person. It uses the content models from the %personName.content; parameter entity, %contact.content; parameter entity, <personIdentification/>, and <role/> elements. The %personName.content; parameter entity requires authors to provide the full name, alias name, or last name of a person; all other name, contact, or identification information is optional. This content model is loosely based on the content model of the <actor/> element in the Court Filing 1.1 DTD.

The <person/> element has almost all the attributes of the <actor/> element in the Court Filing 1.1 DTD. The optional "id" attribute contains a unique identifier for the person. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <person/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about a <person/> is sealed, redacted, or restricted.

The %person.ANY; parameter entity is for incorporating extensions. An extension element must first be declared in the DTD and then included as an optional element in the %person.ANY; parameter entity declaration preceded by the appropriate "connector" (e.g. "|" or ","). The extension then will be automatically included in the content model for this element.

<!ELEMENT attorney (%personName.content; , %contact.content; , barNumber* , 
personIdentification? , role* %person.ANY;)>
<!ATTLIST attorney id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<attorney/> contains the name, contact, identification, and role information for an attorney. It uses the content models from the %personName.content; parameter entity, the %contact.content; parameter entity, the <barNumber/>, <personIdentification/>, and <role/> elements. Information about the name of an attorney must be provided; all other information is optional. The %person.ANY; parameter entity is for incorporating extensions. This content model is nearly identical to the content model for the <person/> element -- only the <barNumber/> element has been added. This element has the same attributes as the <person/> element.

<!ELEMENT judicialOfficer (%personName.content; , %contact.content; , personIdentification? , 
role* %person.ANY;)>
<!ATTLIST judicialOfficer id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<judicialOfficer/> contains the name, contact, identification, and role information for a judge, clerk of court, magistrate, or other judicial official. It uses the same content models as the <person/> element. The %personName.content; parameter entity requires authors to provide the full name, alias name, or last name of the judicial officer; all other information is optional. The %person.ANY; parameter entity is for incorporating extensions. The <judicialOfficer/> element also has the same attributes as the <person/> element. The optional "id" attribute contains a unique identifier for the judicial officer. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <judicialOfficer/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about a <judicialOfficer/> is sealed, redacted, or restricted.

<!ELEMENT administrativeOfficer (%personName.content; ,
%contact.content; , 
personIdentification? , role* %person.ANY;)>
<!ATTLIST administrativeOfficer id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<administrativeOfficer/> contains the name, contact, identification, and role information for an administrative law judge, hearing officer, board member or other administrative official. It uses the same content models as the <person/> element. The %personName.content; parameter entity requires authors to provide the full name, alias name, or last name of the administrative officer; all other information is optional. The %person.ANY; parameter entity is for incorporating extensions. The <administrativeOfficer/> element also has the same attributes as the <person/> element. The optional "id" attribute contains a unique identifier for the administrative officer. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <administrativeOfficer/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about an <administrativeOfficer/> is sealed, redacted, or restricted.

<!ELEMENT enforcementOfficer (%personName.content; ,%contact.content; , 
personIdentification? , role* %person.ANY;)>
<!ATTLIST enforcementOfficer id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<enforcementOfficer/> contains the name, contact, identification, and role information for a police officer, sheriff, deputy, detective, or other law enforcement official. It uses the same content models as the <person/> element. The %personName.content; parameter entity requires authors to provide the full name, alias name, or last name of the enforcement officer; all other information is optional. The %person.ANY; parameter entity is for incorporating extensions. The <enforcementOfficer/> element also has the same attributes as the <person/> element. The optional "id" attribute contains a unique identifier for the enforcement officer. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <enforcementOfficer/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about an <enforcementOfficer/> is sealed, redacted, or restricted.

<!ELEMENT witness (%personName.content; , %contact.content; , personIdentification? , role* 
%person.ANY;)>
<!ATTLIST witness id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<witness/> contains the name, contact, identification, and role information for a witness. It uses the same content models as the <person/> element. The %personName.content; parameter entity requires authors to provide the full name, alias name, or last name of the witness; all other information is optional. The %person.ANY; parameter entity is for incorporating extensions. The <witness/> element also has the same attributes as the <person/> element. The optional "id" attribute contains a unique identifier for the witness. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <witness/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about an <witness/> is sealed, redacted, or restricted.

<!ELEMENT notary (%personName.content; , %contact.content; , personIdentification? , role* 
%person.ANY;)>
<!ATTLIST notary id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<notary/> contains the name, contact, identification, and role information for a notary public. It uses the same content models as the <person/> element. The%personName.content; parameter entity requires authors to provide the full name, alias name, or last name of the notary; all other information is optional. The %person.ANY; parameter entity is for incorporating extensions. The <notary/> element also has the same attributes as the <person/> element. The optional "id" attribute contains a unique identifier for the notary. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <notary/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about a <notary/> is sealed, redacted, or restricted.

<!ELEMENT personIdentification (%personIdentification.content;)>

<personIdentification/> contains elements to describe information uniquely identifying a person, such as personal id numbers, date of birth or age, or similar information. It uses the content models declared in the %personIdentification.content; parameter entity. The content model is loosely based on the <personDescription/> element in the Court Filing 1.1 DTD, but elements for describing physical characteristics and other personal information are not included to simplify this content model.

<!ELEMENT personalIDNumber (#PCDATA)>
<!ATTLIST personalIDNumber issuingAuthority CDATA #IMPLIED
%common.attributes;>

<personalIDNumber/> contains an identification number assigned by various agencies and organizations for a person. It is incorporated from the Court Filing 1.1 DTD. The "type" attribute identifies the category of ID number assigned, e.g., "social security", "driver's license". This element has an additional attribute, "issuingAuthority" , which contains the name of the organization or state issuing the identification number.

<!ELEMENT birthDate (#PCDATA)>
<!ATTLIST birthDate date CDATA #REQUIRED
%common.attributes;>

<birthDate/> contains a text string giving the date of birth of a person. It is incorporated from the Court Filing 1.1 DTD, but a required "date" attribute has been added for providing date information in machine readable, ISO 8601 format.

<!ELEMENT age (#PCDATA)>

<age/> contains the age of a person. It is not included in the Court Filing 1.1 DTD.

<!ELEMENT comment (#PCDATA)>
<!ATTLIST comment %common.attributes;>

<comment/> contains the text of a comment. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT barNumber (#PCDATA)>
<!ATTLIST barNumber issuingAuthority CDATA #IMPLIED
yearAdmitted CDATA #IMPLIED
barStatus CDATA #IMPLIED>

<barNumber/> contains the bar number for an attorney. It is incorporated from the Court Filing 1.1 DTD, although the attributes "issuingAuthority" , "yearAdmitted" , and "barStatus" have been added. These attributes contain information describing the state bar issuing the bar number, the year the attorney was admitted to practice, and the status of the attorney's license. These attributes are based on elements appearing in the <barMembershipInformation/> element of the Court Filing 1.1 DTD, but have been changed to attributes to simplify this DTD.

<!ELEMENT organization ((%organizationName.content; , %contact.content;) , 
organizationIdentification? , role*)>
<!ATTLIST organization id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED>

<organization/> contains the name, contact, identification, and specific role information for an organization, such as a corporation, association, partnership, or similar legal entity. It uses many of the same content models as the <person/> element. However, it uses the %organizationName.content; parameter entity instead of the %personName.content; parameter entity for name information and the <organizationIdentification/> element instead of the <personIdentification/> element.

The <organization/> element has the same attributes as the <person/> element. The optional "id" attribute contains a unique identifier for the organization. The optional "reference" attribute contains the value of the "id" attribute of a fully defined <organization/> element appearing elsewhere in the document. The "privacy" attribute can be used to indicate whether information about an <organization/> is sealed, redacted, or restricted.

<!ELEMENT organizationIdentification (%organizationIdentification.content;)>

<organizationIdentification/> contains elements to describe information uniquely identifying an organization. It uses the content models declared in the %organizationIdentification.content; parameter entity. The content model is based on the <personIdentification/> element and provides consistency in the content models used to describe identification information for persons and organizations.

<!ELEMENT organizationIDNumber (#PCDATA)>
<!ATTLIST organizationIDNumber issuingAuthority CDATA #IMPLIED
%common.attributes;>

<organizationIDNumber/> contains identifiers for an organization. The "type" attribute identifies the category of ID number assigned. This element has an additional attribute, "issuingAuthority", which contains the name of the authority issuing the identification number.

<!ELEMENT fullName (#PCDATA)>
<!ATTLIST fullName %common.attributes;>

<fullName/> contains the entire, or complete name of a person, including any prefix or suffix. It also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral". It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT aliasName (#PCDATA)>
<!ATTLIST aliasName aliasFor IDREF #IMPLIED
aliasType (dba | aka | fka | nka | nee | ex ) #REQUIRED>

<aliasName/> contains the alias of a person or organization. It is not included in the Court Filing 1.1 DTD. In addition to the %common.attributes;, the "aliasFor" attribute is a reference to the "id" attribute value of the party, person, or organization using the alias. The "aliasType" attribute is required to indicate the type of the alias name.

<!ELEMENT nickName (#PCDATA)>

<nickName/> contains the nickname of a person. It is not included in the Court Filing 1.1 DTD.

<!ELEMENT namePrefix (#PCDATA)>
<!ATTLIST namePrefix %common.attributes;>

<namePrefix/> contains any formal prefix that is used with a person's name, e.g., "The Honorable", "Mr.", "Ms.". It also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral". It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT firstName (#PCDATA)>
<!ATTLIST firstName %common.attributes;>

<firstName/> contains the first, or given, name of a person. It also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral". It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT middleName (#PCDATA)>
<!ATTLIST middleName %common.attributes;>

<middleName/> contains a person's middle name, initials, or multiple initials. Each of the names of a person between their first and last names are described by this element. It also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral". It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT lastName (#PCDATA)>
<!ATTLIST lastName %common.attributes;>

<lastName/> contains the last, or family, name of a person. It also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral". It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT nameSuffix (#PCDATA)>
<!ATTLIST nameSuffix %common.attributes;>

<nameSuffix/> contains a suffix to a person's name, such as "Jr.", "PhD", or "III". It also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral". It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT organizationName (#PCDATA)>
<!ATTLIST organizationName %common.attributes;>

<organizationName/> contains an organization's full name. It is based on the <entityName/> element in the Court Filing 1.1 DTD and also takes the optional common attributes -- "id", "type", "status", "referenceDate", "codeSource", "codeValue", and "codeLiteral".

<!ELEMENT organizationUnit (#PCDATA)>
<!ATTLIST organizationUnit %common.attributes;>

<organizationUnit/> contains the name of a division or department within an organization. It is not included in the Court Filing 1.1 DTD.

<!ELEMENT abbreviatedName (#PCDATA)>
<!ATTLIST abbreviatedName %common.attributes;>

<abbreviatedName/> contains the abbreviated name of an organization (or court or agency). It is based on the <entityAbbreviatedName/> element in the Court Filing 1.1 DTD.

<!ELEMENT organizationAcronym (#PCDATA)>
<!ATTLIST organizationAcronym %common.attributes;>

<organizationAcronym/> contains any common acronym by which an organization is known. It is based on the <entityAcronym/> element in the Court Filing 1.1 DTD.

<!ELEMENT postalAddress (%postalAddress.content;)>
<!ATTLIST postalAddress addressType (business | home | unknown ) 'business'
%common.attributes;>

<postalAddress/> contains the %postalAddress.content; parameter entity, which in turn contains a content model for describing a postal location to which paper mail can be directed. This content model is based on the <postalAddress/> element in the Court Filing 1.1 DTD and makes its child elements optional. It includes an additional enumerated attribute "addressType" from which authors can indicate the type of postal address information being provided. An enumerated attribute list of such choices is provided to standardize the descriptions of postal address types. The content model also requires authors to choose either the separate elements for an address or a full address, but not both. This difference, however, does not result in a collision with the content model used in the Court Filing 1.1 DTD for postal addresses, which allows either approach.

<!ELEMENT addressLine (#PCDATA)>
<!ATTLIST addressLine %common.attributes;>

<addressLine/> contains text address lines, and may include alternative text for locations that don't have a postal address system. <addressLine/> elements must be sequenced in the order they would appear on an address label. The attribute "type" may be used to identify the context of the address line, e.g., a firm name, a suite number, street, or post office box. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT city (#PCDATA)>
<!ATTLIST city %common.attributes;>

<city/> contains the name of a city, town, or township. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT county (#PCDATA)>
<!ATTLIST county %common.attributes;>

<county/> contains the name of a county. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT state (#PCDATA)>
<!ATTLIST state stateCode (%state.codes; ) #IMPLIED
%common.attributes;>

<state/> contains the name of a state or province. This content model is based on the <state/> element in the Court Filing 1.1 DTD, but includes an additional enumerated attribute "stateCode" from which authors can select the USPS abbreviation for a U.S. state. An enumerated attribute list (as set out in the %state.codes; parameter entity containing the USPS abbreviations for U.S. states) is provided for purposes of standardization. This element is substantially consistent with the Court Filing 1.1 DTD, which provides that USPS abbreviations are preferred for U.S. states, but uses the "codeValue" and "codeSource" attributes to indicate the value and source of the abbreviated codes instead of including them in an enumerated attribute.

<!ELEMENT postalCode (#PCDATA)>
<!ATTLIST postalCode %common.attributes;>

<postalCode/> contains the zip or postal code. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT country (#PCDATA)>
<!ATTLIST country %common.attributes;>

<country/> contains the name of the country. It is incorporated from the Court Filing 1.1 DTD. The ISO 3166 abbreviations for country names must be used if the country name is abbreviated.

<!ELEMENT fullAddress (#PCDATA)>
<!ATTLIST fullAddress %common.attributes;>

<fullAddress/> contains a complete address. The content model is identical to the content model of the <addressFull/> element in the Court Filing 1.1 DTD, but the element name has been changed for greater consistency with similarly named elements, such as <fullName/> and <fullTelephone/> in this DTD.

<!ELEMENT telephone (telephonePrefix? , telephoneNumber , telephoneSuffix?)>
<!ATTLIST telephone %common.attributes;>

<telephone/> contains the information for a telephone number. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT telephonePrefix ((telephoneCountryCode? , telephoneCityCode?) | areaCode?)>
<!ATTLIST telephonePrefix %common.attributes;>

<telephonePrefix/> contains the prefix information related to a telephone number, e.g., a country and city code, or an area code. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT telephoneCountryCode (#PCDATA)>
<!ATTLIST telephoneCountryCode %common.attributes;>

<telephoneCountryCode/> contains the country code for an international telephone number. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT telephoneCityCode (#PCDATA)>
<!ATTLIST telephoneCityCode %common.attributes; >

<telephoneCityCode/> contains the city code for an international telephone number. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT areaCode (#PCDATA)>
<!ATTLIST areaCode %common.attributes;>

<areaCode/> contains the area code for a telephone number. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT telephoneNumber (#PCDATA)>
<!ATTLIST telephoneNumber format CDATA #IMPLIED
%common.attributes;>

<telephoneNumber/> contains the main telephone number. The "format" attribute is used to define the format of the digits comprising the telephone number. Format information includes: the hash ("#") character to indicate the position of a telephone keypad digit, and white space characters to specify the position for optional white space. This element is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT telephoneSuffix (#PCDATA)>
<!ATTLIST telephoneSuffix %common.attributes;>

<telephoneSuffix/> contains the suffix, such as an extension, for a telephone number. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT fullTelephone (#PCDATA)>
<!ATTLIST fullTelephone telephoneType (business | home | mobile | pager | unknown )
'business'>

<fullTelephone/> contains a complete telephone number. It includes an enumerated attribute "telephoneType" from which authors can indicate the type of telephone information being provided. An enumerated attribute list of such choices is provided to standardize the descriptions of telephone types. It is not included in the Court Filing 1.1 DTD.

<!ELEMENT fax (telephone)>
<!ATTLIST fax %common.attributes;>

<fax/> contains a fax telephone number. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT fullFax (#PCDATA)>
<!ATTLIST fullFax faxType (business | home | unknown ) 'business'>

<fullFax/> contains a complete fax telephone number. It includes an enumerated attribute "faxType" to indicate the type of fax telephone information being provided. An enumerated attribute list of such choices is provided to standardize the descriptions of fax telephone types. It is not included in the Court Filing 1.1 DTD.

<!ELEMENT email (#PCDATA)>
<!ATTLIST email emailType (business | home | mobile | unknown ) 'business'
%common.attributes;>

<email/> contains an email address. It is incorporated from the Court Filing 1.1 DTD, but includes a new enumerated attribute "emailType" from which authors can indicate the type of email address being provided. An enumerated attribute list of such choices is provided to standardize the descriptions of email address types.

<!ELEMENT uri (#PCDATA)><!ELEMENT uri (#PCDATA)>

<uri/> contains either a Universal Resource Identifier (URI) or a Universal Resource Locator (URL). It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT role (roleName , roleWith*)>

<role/> contains elements describing the specific role of a person, attorney, witness, judicial officer, organization, etc. and information about related persons or organizations. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT roleName (#PCDATA)>

<roleName/> contains the name or description of the specific role taken by a person, attorney, witness, judicial officer, organization, etc. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT roleWith (organization | court | agency | party | person | attorney | witness | 
victim | judicialOfficer | administrativeOfficer | enforcementOfficer)?>
<!ATTLIST roleWith actorID IDREFS #IMPLIED
matterID IDREFS #IMPLIED>

<roleWith/> contains a description of the person or organization with which a relationship exists and thus provides context for a specific role (e.g. <roleWith/><organization><organizationName>Legal XML, Inc.</organizationName></organization></roleWith>). As an alternative, <roleWith/> also has optional "actorID" and "matterID" attributes which can point to the "id" attributes of other person, organization, or case elements to indicate a relationship with them. For example, a relationship between a person and an organization can be described by using the "actorID" attribute. This element is based on the <roleWith/> element from the Court Filing 1.1 DTD.

<!ELEMENT date (#PCDATA)>
<!ATTLIST date %common.attributes;
date CDATA #REQUIRED
dateType CDATA #IMPLIED>

<date/> contains a text string describing a date. It is incorporated from the Court Filing 1.1 DTD, but includes two additional attributes. It includes a required attribute "date" for providing date information in ISO 8601 number format (e.g. 2002-05-31) as noted in the description of the %dateTime; entity. It also includes the optional attribute "dateType" to contain further information describing the category of date information provided.

<!ELEMENT time (#PCDATA)>
<!ATTLIST time time CDATA #REQUIRED
%common.attributes;>

<time/> contains a text string describing a time. It is incorporated from the Court Filing 1.1 DTD, but includes an additional required attribute "time" for providing time information in ISO 8601 number format as noted in the description of the %dateTime; entity.

<!ELEMENT link (#PCDATA)>
<!ATTLIST link %xlink.attributes;>

<link/> contains the information to create an XML link. It uses the global attributes from the XLink namespace for compatibility with the W3C's XML Linking Language (XLink) Version 1.0 Recommendation . The XLink global attributes used by the <link/> element are declared in the %xlink.attributes; parameter entity and the default attribute values are set to create a simple link identical to an HTML link. For instance, a simple link to the Legal XML, Inc. home page would be <link xlink:type="simple" xlink:href="http://www.legalxml.org" xlink:title="Legal XML, Inc." xlink:show="replace" xlink:actuate="onRequest">Legal XML</link>. Although XLink global attributes can be used to make any element a linking element, they are used only by the <link/> and <image/> elements in this DTD .

<!ELEMENT image EMPTY>
<!ATTLIST image xmlns:xlink CDATA #FIXED 'http://www.w3.org/1999/xlink'
xlink:type CDATA #FIXED 'simple'
xlink:href CDATA #REQUIRED
xlink:title CDATA #IMPLIED
xlink:show CDATA #FIXED 'onLoad'
xlink:actuate CDATA #FIXED 'embed' >

<image/> is an empty element for an image link using the global attributes from the XLink namespace for compatibility with the W3C's XML Linking Language (XLink) Version 1.0 Recommendation . The fixed attribute values of the global XLink attributes create a simple link for embedding an image and thus are different from the default attribute values declared in the %xlink.attributes; parameter entity. Although XLink global attributes can be used to make any element a linking element, they are used only by the <link/> and <image/> elements in this DTD.

<!ELEMENT caseMetadata (%caseMetadata.content;)>
<!ATTLIST caseMetadata caseType CDATA #IMPLIED
id ID #IMPLIED>

<caseMetadata/> contains the elements and content model for describing metadata about the case or proceeding in which the court document is being filed or served. Its child elements and content model are described in the %caseMetadata.content; parameter entity. An author must identify the tribunal in which the document is being filed as either a court or administrative agency. The <fullCaseNumber/> and <caseTitle/> elements are optional, but may occur only once. The optional <relatedCase/> element may occur multiple times.

The <caseMetadata/> element has an optional "caseType" attribute, which can be used to describe the case type. This attribute may contain the case types described in the Court Filing 1.1 DTD (e.g. civil, domesticRelations, probate, smallClaims, etc.) or additional case types not listed in the Court Filing 1.1 DTD (e.g. arbitration, industrialCommission, etc.).

<!ELEMENT court (((courtName , (courtDivision | courtDistrict | courtCircuit |
courtDepartment)* , abbreviatedName?) | abbreviatedName) , (venue | (%contact.content;))? , 
judicialOfficer*)>
<!ATTLIST court courtType CDATA #IMPLIED>

<court/> contains the elements and content model to describe the name of the court in which the case is pending, its venue or more detailed contact information, and information regarding the judicial officers involved in the case. This content model requires authors to provide the court's name (optionally followed by a division, district, or circuit name or an abbreviated name) or just an abbreviated name of the court. It also requires authors to provide either the venue of the court (city or county and state) or to provide more detailed contact information (using the content model of the %contact.content; parameter entity previously described). Information about the judicial officer(s) involved is optionally contained in the <court/> element to reflect their relationship with the court. The <court/> element also has an optional "courtType" element to describe the general category or level of the court.

<!ELEMENT courtName (#PCDATA)>

<courtName/> is a required element containing the name of the court in which the case is pending. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT courtDivision (#PCDATA)>

<courtDivision/> is an optional element containing the name of the division of the court in which the case is pending.

<!ELEMENT courtDistrict (#PCDATA)>

<courtDistrict/> is an optional element containing the name of the district of the court in which the case is pending.

<!ELEMENT courtCircuit (#PCDATA)>

<courtCircuit/> is an optional element containing the name of the circuit of the court in which the case is pending.

<!ELEMENT courtDepartment (#PCDATA)>

<courtDepartment/> is an optional element containing the name of the department of the court in which the case is pending.

<!ELEMENT venue (city? , county? , state)>

<venue/> contains the content model for describing a location optionally using either the name of the city or county and the state. The <state/> element is required. Within the <court/> element, <venue/> describes the general location of the court.

<!ELEMENT agency (((agencyName , (agencyOffice | agencyBureau | agencyDepartment | 
agencyBoard)* , (abbreviatedName | agencyAcronym)?) | abbreviatedName | agencyAcronym) , 
((venue) | (%contact.content;))? , administrativeOfficer*)>
<!ATTLIST agency agencyType CDATA #IMPLIED>

<agency/> contains the elements and content model to describe the name of the agency in which the proceeding is pending, its venue or more detailed contact information, and information regarding the administrative officers involved in the proceeding. This content model requires authors to provide the agency's name (optionally followed by an office, bureau, department, or board name or either an abbreviated name or agency acronym) or just an abbreviated name or acronym of the agency. It also requires authors to provide either the venue of the agency (city or county and state) or to provide more detailed contact information (using the content model of the %contact.content; parameter entity previously described). Information about the administrative officer(s) involved is optionally contained in the <agency/> element to reflect their relationship with the agency. The <agency/> element also has an optional "agencyType" element to describe the general category or level of the agency.

<!ELEMENT agencyName (#PCDATA)>

<agencyName/> is a required element containing the name of the agency in which the proceeding is pending.

<!ELEMENT agencyAcronym (#PCDATA)>

<agencyAcronym/> is an optional element containing any common acronym by which the agency is known.

<!ELEMENT agencyOffice (#PCDATA)>

<agencyOffice/> is an optional element containing the name of the office of the agency in which the proceeding is pending.

<!ELEMENT agencyBureau (#PCDATA)>

<agencyBureau/> is an optional element containing the name of the bureau of the agency in which the proceeding is pending.

<!ELEMENT agencyDepartment (#PCDATA)>

<agencyDepartment/> is an optional element containing the name of the department of the agency in which the proceeding is pending.

<!ELEMENT agencyBoard (#PCDATA)>

<agencyBoard/> is an optional element containing the name of the board of the agency in which the proceeding is pending.

<!ELEMENT fullCaseNumber (#PCDATA)>

<fullCaseNumber/> is an optional element containing the full case number of the case or proceeding. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT caseTitle (fullCaseTitle | (partyGroup | party | vs)+ | (inRe , party+))>

<caseTitle/> is a required element containing the content model and elements for describing the title of the case or administrative proceeding. It requires authors to provide either 1) a full case title (e.g. Smith, et al. v. Jones, et al.); 2) information regarding the group(s) of parties or individual parties (separated by a <vs/> element as appropriate or, alternatively, information for an "In Re" (i.e. "In the Matter of") case optionally followed by the name of the party involved (e.g. In the Matter of D. R. Horton, Inc.); or 3) the title for an "in rem" case or proceeding that does not involve people or organizations as parties (e.g., In re Foreclosure of Lot #21, In the matter of Five 1999 Acura Automobiles, etc.).

<!ELEMENT fullCaseTitle (#PCDATA)>

<fullCaseTitle/> contains the full case title of the case or proceeding.

<!ELEMENT inRem ((inRemName, aliasName*) , comment?)>
<!ATTLIST inRem id ID #IMPLIED
reference IDREF #IMPLIED
privacy (sealed | redacted | restricted ) #IMPLIED >

<inRem/> contains information for an "in rem" party that is not a person or organization. It contains a required <inRemName/> element for the name of the "thing" involved, together with optional <aliasName/> and <comment/> elements.

<!ELEMENT inRemName (#PCDATA)>

<inRemName/> contains the name of an in rem "thing" involved in a legal proceeding.

<!ELEMENT partyGroup (party+)>
<!ATTLIST partyGroup id ID #IMPLIED
partyType CDATA #REQUIRED>

<partyGroup/> contains one or more<party/> elements. Information about the attorney(s) for the party group also is optionally contained within the <partyGroup/> element to reflect the attorney's relationship with the group. The <partyGroup/> element has a required "partyType" attribute to describe the particular type of party, e.g. "Plaintiffs," "Respondents," "Third-Party Defendants," etc. It also has an optional "id" attribute.

<!ELEMENT vs (#PCDATA)>

<vs/> is an element used to separate the <party/> or <partyGroup/> elements.

<!ELEMENT inRe (#PCDATA)>

<inRe/> contains the text of an "In Re" (i.e. In the Matter of) case title (e.g. "In the Matter of the Arbitration between Smith Construction Co. and Jones Building, Inc."). If used, it must be followed by one or more <party/> elements.

<!ELEMENT relatedCase ((court | agency) , fullCaseNumber? , caseTitle? , comment*)>
<!ATTLIST relatedCase id ID #IMPLIED
referenceCase IDREF #IMPLIED
relationshipType (consolidated | transferred | removed | appealed | 
other ) #REQUIRED>

<relatedCase/> is an optional element containing the content model and elements for describing information about a related case or proceeding, such as one that has been consolidated, transferred, or appealed. It uses the same content model and elements in the %caseMetadata; parameter entity, except that the <relatedCase/> element is replaced by an optional <comment/> element.

The <relatedCase/> element has two attributes. The "id" attribute is optional. The "relationshipType" is a required enumerated attribute indicating whether the related case or proceeding was consolidated, transferred, removed, appealed, or has some other relationship with the pending case or proceeding.

<!ELEMENT documentBody ((paragraphGroup | (%paragraph.model;) | machineData)+ ,
dateTimeSigned)>

<documentBody/> contains the elements and content models for marking up the text contents of the body of a court document. It must contain one or more <paragraphGroup/> elements, one or more combinations of an optional <paragraphTitle/> element immediately followed by a <paragraph/> element, or an optional <machineData/> element. These elements are followed by a single required <dateTimeSigned/> element.

<!ELEMENT paragraphGroup (%paragraphGroup.model;)>
<!ATTLIST paragraphGroup id ID #REQUIRED
%content.attributes;>

<paragraphGroup/> contains the content model described in the %paragraphGroup.model; parameter entity. This element must contain either one or more paragraphs or first-level subgroup(s) of paragraphs (i.e. a subsection). It also contains an optional <paragraphGroupTitle/> element, which must precede any other elements if it is used.

The <paragraphGroup/> element has a required "id" attribute to hold a unique identifier. It also takes the optional content attributes defined in the %content.attributes; parameter entity. The "label" attribute can contain a label, such as a number or letter designation, for the paragraph group. The "type" attribute can describe the general category or nature of the paragraph group's contents, and the "subject" attribute can contain comma-separated keywords or key phrases describing the concepts discussed. The "language" attribute describes the language of the text using a two-letter ISO 639 language code. The "privacy" attribute indicates whether the paragraph group should be sealed or redacted.

<!ELEMENT paragraphGroupTitle (#PCDATA)>

<paragraphGroupTitle/> contains the title of a paragraph group or subgroup.

<!ELEMENT paragraphSubgroup1 (paragraphGroupTitle?,
(paragraphSubgroup2|(%paragraph.model;))+)>
<!ATTLIST paragraphSubgroup1 %content.attributes;>

<paragraphSubgroup1/> describes a first-level subgroup of paragraphs and must contain either one or more paragraphs or second-level subgroup(s) of paragraphs (i.e. a sub-subsection). It also contains an optional <paragraphGroupTitle/> element, which must precede any of the other elements. The <paragraphSubgroup1/> element takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT paragraphSubgroup2 (paragraphGroupTitle?,
(paragraphSubgroup3|(%paragraph.model;))+)>
<!ATTLIST paragraphSubgroup2 %content.attributes;>

<paragraphSubgroup2/> describes a second-level subgroup of paragraphs and must contain either one or more paragraphs or third-level subgroup(s) of paragraphs (i.e. a sub-sub-subsection). It also contains an optional <paragraphGroupTitle/> element. The <paragraphSubgroup2/> element takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT paragraphSubgroup3 (paragraphGroupTitle? ,
(%paragraph.model;)+)>
<!ATTLIST paragraphSubgroup3 %content.attributes;>

<paragraphSubgroup3/> describes a third-level subgroup of paragraphs and must contain one or more paragraphs. It also contains an optional <paragraphGroupTitle/> element. The <paragraphSubgroup3/> element takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT paragraph (#PCDATA | subparagraphTitle | subparagraph1 | 
%paragraph.core; %paragraph.ANY;)*>
<!ATTLIST paragraph id ID #REQUIRED
%content.attributes;>

<paragraph/> contains text expressing a thought, concept, or argument of an author. It has a mixed content model (i.e. it can hold text and subelements). The subelements that an author can optionally use to mark up information within a paragraph are described primarily in the %paragraph.core; parameter entity. These optional subelements include any of the elements describing persons or organizations involved in the case (e.g. <party/>, <attorney/>, <person/>, etc.), the <addIn/> element discussed previously, and a variety of "in-line" elements describing particular items of text content that frequently appear in the paragraphs of court documents, such as footnotes, citations, phrases, quotations, lists, links, dates, and addresses or venues. An <annotation/> element is provided to contain an author's notes. A <paragraphTitle/> element and an element for first-level subparagraphs (<subparagraph1/>) also are provided.

The %paragraph.ANY; parameter entity permits extensions to the subelements that can be included within paragraphs. The additional subelements must be separately declared in the DTD and then must be listed in the declaration of the %paragraph.ANY; parameter entity described above.

Like paragraph groups and subgroups, the <paragraph/> element takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It also has a required "id" attribute.

<!ELEMENT paragraphTitle (#PCDATA)>

<paragraphTitle/> contains the title of a paragraph.

<!ELEMENT subparagraph1 (#PCDATA | subparagraphTitle | subparagraph2 | 
%paragraph.core; %paragraph.ANY;)*>
<!ATTLIST subparagraph1 %content.attributes;>

<subparagraph1/> contains a first level subparagraph. It has a mixed content model (i.e. it can hold text and subelements) like the <paragraph/> element. It contains the subelements described in the %paragraph.core; parameter entity along with any extension elements included in the %paragraph.ANY; parameter entity. It also includes a <subparagraphTitle/> element and second-level subparagraphs (<subparagraph2/>). The <subparagraph1/> element also takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT subparagraphTitle (#PCDATA)>

<subparagraphTitle/> contains the title of a subparagraph.

<!ELEMENT subparagraph2 (#PCDATA | subparagraphTitle | subparagraph3 | 
%paragraph.core; %paragraph.ANY;)*>
<!ATTLIST subparagraph2 %content.attributes;>

<subparagraph2/> contains a second level subparagraph (i.e. a sub-subparagraph). It has a mixed content model (i.e. it can hold text and subelements) like the <paragraph/> element. It contains the subelements described in the %paragraph.core; parameter entity along with any extension elements included in the %paragraph.ANY; parameter entity. It also includes a <subparagraphTitle/> element and third-level subparagraphs (<subparagraph3/>). The <subparagraph2/> element also takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT subparagraph3 (#PCDATA | subparagraphTitle | %paragraph.core; %paragraph.ANY;)*>
<!ATTLIST subparagraph3 %content.attributes;>

<subparagraph3/> contains a third level subparagraph (i.e. a sub-sub-subparagraph). It has a mixed content model (i.e. it can hold text and subelements) like the <paragraph/> element. It contains the subelements described in the %paragraph.content; parameter entity along with a <subparagraphTitle/> element. The <subparagraph3/> element also takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT addIn ANY>
<!ATTLIST addIn addInType CDATA #IMPLIED>

<addIn/> is a special element containing ANY content. Thus, it can contain parsed character data or any of the other elements declared in the Court Document 1.1 DTD. It is provided as a convenient mechanism for easily customizing and extending the DTD by adding in new markup. New elements or parameter entities can be added to the DTD and then used within an <addIn/> element in the paragraphs of an XML court document. However, the <addIn/> element should be used with care, because new markup added by means of an <addIn/> element may be meaningless to applications created to process existing XML court documents.

<!ELEMENT simpleCite (#PCDATA)>
<!ATTLIST simpleCite %content.attributes;>

<simpleCite/> contains a complete text citation to a case, statute, or other legal authority. It also takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT keyword (#PCDATA)>
<!ATTLIST keyword id ID #IMPLIED
%content.attributes;>

<keyword/> contains a single word or term having special significance or meaning. It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It also has additional optional attributes that can be used to more specifically define the particular meaning of the keyword. The "description" attribute contains a description or account of the content of the keyword. The <keyword/> element also has an optional "id" attribute.

<!ELEMENT literal (#PCDATA)>
<!ATTLIST literal id ID #IMPLIED
%content.attributes;>

<literal/> contains some specific piece of text or other data taken literally. It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It also has a "description" attribute, which contains a description or account of the content of the literal text or other data. The <literal/> element has an optional "id" attribute.

<!ELEMENT phrase (#PCDATA)>
<!ATTLIST phrase id ID #IMPLIED
%content.attributes;>

<phrase/> contains a short span of text having special significance or meaning. It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It also has additional optional attributes that can be used to more specifically define the particular meaning of the phrase. The <phrase/> element also has an optional "id" attribute.

<!ELEMENT quotation (#PCDATA | simpleCite | keyword | literal | phrase | date | link)*>
<!ATTLIST quotation id ID #IMPLIED
source CDATA #IMPLIED
%content.attributes;>

<quotation/> contains a quotation from another document or resource. It has mixed content and can contain <simpleCite/>, <keyword/>, <literal/>, <phrase/>, <date/>, or <link/> elements as well as parsed text.

It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It also has a "description" attribute, which contains a description or account of the content of the quotation. The "source" attribute refers to the resource from which the quotation is taken. The <quotation/> element has an optional "id" attribute.

<!ELEMENT footnote (footnoteNumber , footnoteBody)>
<!ATTLIST footnote id ID #IMPLIED
label CDATA #IMPLIED
type CDATA #IMPLIED
subject CDATA #IMPLIED
title CDATA #IMPLIED>

<footnote/> contains a footnote. It must contain a <footnoteNumber/> element followed by a <footnoteBody/> element. It takes three of the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", and "subject". It also has a "title" attribute and an optional "id" attribute.

<!ELEMENT footnoteNumber (#PCDATA)>

<footnoteNumber/> must contain the number of a footnote. It has no attributes.

<!ELEMENT footnoteBody (#PCDATA | simpleCite | keyword | literal | phrase | quotation | date | 
link)*>

<footnoteBody/> contains the body of a footnote. It has mixed content and can contain <simpleCite/>, <keyword/>, <literal/>,<phrase/>, <quotation/>, <date/>, or <link/> elements as well as parsed text. It has no attributes.

<!ELEMENT list (list | listItem)+>
<!ATTLIST list id ID #IMPLIED
%content.attributes;>

<list/> contains any sequence of items organized as a list. It must contain either one or more <listItem/> element(s) or another <list/> element. It is the only element in the Court Document 1.1 DTD having a recursive content model (i.e. a list can contain a list which can contain another list, etc.). It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". The "type" attribute may be used to describe whether the list is an ordered, unordered, or other type of list. The <list/> element has an optional "id" attribute.

<!ELEMENT listItem (#PCDATA | simpleCite | keyword | literal | phrase | quotation | date | 
link | person | attorney | witness | judicialOfficer | administrativeOfficer | 
enforcementOfficer | organization | court | agency | victim | party | fullCaseNumber | 
caseTitle | relatedCase %paragraph.ANY;)*>
<!ATTLIST listItem %content.attributes;>

<listItem/> contains a single item in a list. It has mixed content and can contain numerous other elements declared in the Court Document 1.1 DTD as well as parsed text. It also includes the %paragraph.ANY; parameter entity and thus can contain extension elements added to the DTD. It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT table (tableTitle? , tgroup)>
<!ATTLIST table id ID #IMPLIED
%content.attributes; >

<table/> contains information organized in a formal table. It takes an optional "id" attribute and the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It is based on the "table" element used in the DocBook DTD, which in turn is based on the CALS table model. The OASIS CALS table model describes tables using columns, rows, and cells. The <table/> element contains an optional <tableTitle/> element followed by a required <tgroup/> element. <table> uses child elements and attributes from the CALS table model and for consistency with that model and applications implementing it, the child elements of <table/> use a different naming convention than the one followed for other elements in this DTD.

<!ELEMENT tableTitle (#PCDATA)>

<tableTitle/> is an optional element containing the title of a table.

<!ELEMENT tgroup (colspec* , spanspec* , thead? , tbody)>
<!ATTLIST tgroup cols CDATA #IMPLIED >

<tgroup/> contains elements that describe the contents of a table. It is based on the CALS table model and contains optional <colspec/> and <spanspec> elements to describe columns and column spans, an optional <thead/> element to describe a heading row, and a required <tbody/> element to describe the body of a table. The "columns" attribute contains the number of columns in the table.

<!ELEMENT colspec EMPTY>
<!ATTLIST colspec colname CDATA #IMPLIED
colnum CDATA #IMPLIED >

<colspec/> is an optional empty element containing attributes describing the name and number of a column. The "colname" and "colnum" attributes are optional.

<!ELEMENT spanspec EMPTY>
<!ATTLIST spanspec spanname CDATA #REQUIRED
namest CDATA #REQUIRED
nameend CDATA #REQUIRED >

<spanspec/> is an optional empty element containing attributes to describe a horizontal span of columns. The "spanname" attribute contains the name of the horizontal span. The "namest" attribute contains the name of the starting or leftmost column of the span. The "nameend" attribute contains the name of the ending or rightmost column of the span. All attributes of <spanspec/> are required.

<!ELEMENT thead (row)>

<thead/> is an optional element containing a single heading row for a table. It must precede the rows in the body of the table.

<!ELEMENT tbody (row+)>

<tbody/> contains one or more required row elements comprising the body of a table.

<!ELEMENT row (entry+)>

<row/> contains a row in a table. It consists of one or more <entry/> elements. Within a <row/>, <entry/> elements are arranged sequentially in column order and may specify the column in which they appear. If no <entry/> elements are allocated to a column (i.e. if there are fewer <entry/> elements in a row than columns in a table), the "missing" <entry/> elements are assumed to be empty.

<!ELEMENT entry (#PCDATA | simpleCite | keyword | literal | phrase | quotation | 
date | link | person | attorney | witness | judicialOfficer | administrativeOfficer | 
enforcementOfficer | organization | court | agency | victim | party | fullCaseNumber | 
caseTitle | relatedCase %paragraph.ANY;)*>
<!ATTLIST entry colname CDATA #IMPLIED
%content.attributes; >

<entry/> describes a cell in a table row. Like the <listItem/> element, it has mixed content and can contain numerous other elements declared in the Court Document 1.1 DTD as well as parsed text. It also includes the %paragraph.ANY; parameter entity and thus can contain extension elements added to the DTD. The optional "colname" attribute may be used to specify the name of the table column in which the entry is to appear. Similarly the optional "spanname" attribute may be used to specify the name of a horizontal span in which the entry is to appear. <entry/> also takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy".

<!ELEMENT annotation (#PCDATA | simpleCite | keyword | literal | phrase | quotation | date | 
link)*>
<!ATTLIST annotation id ID #IMPLIED
description CDATA #IMPLIED
refersTo IDREFS #IMPLIED
creator CDATA #IMPLIED
%content.attributes; >

<annotation/> contains an annotation by an author or editor regarding the contents of a paragraph. It has mixed content and can contain <simpleCite/>, <keyword/>, <literal/>, <phrase/>,<quotation/>, <date/>, or <link/> elements as well as parsed text.

It takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". It also has several additional attributes. The optional "id" attribute identifies the annotation. The optional "refersTo" attribute contains the values of the "id" attributes of other elements to which it points. The "creator" attribute identifies the annotation author, and the "description" attribute describes the contents of the annotation.

<!ELEMENT dateTimeSigned (%dateTime.content;)>

<dateTimeSigned/> is a required element containing the date and time associated with the signing of the court document for service or filing. It contains the %dateTime.content; parameter entity to incorporate the <date/> and <time/> elements and it has no attributes.

<!ELEMENT machineData (addIn)+>
<!ATTLIST machineData id ID #IMPLIED
%content.attributes; >

<machineData/> contains one or more<addIn/> elements, but no text. The <machineData/> element is intended to serve as a container for marked up data-containing elements needed by processing applications and from which such applications can extract and use the data more easily and more reliably. Providing a container element for this purpose avoids ambiguities that might arise from relying on data elements within text-containing paragraphs because the surrounding textual context might make the meaning of the marked up data element unclear. As described previously, an <addIn/> element can contain any of the other elements declared in the Court Document 1.1 DTD and also is a mechanism for customizing and extending the DTD by adding in new markup.

The <machineData/> element takes the optional content attributes defined in the %content.attributes; parameter entity -- "label", "type", "subject", "language", or "privacy". The <machineData/> element also has an optional "id" attribute .

<!ELEMENT signers (signatory+ , notarization?)>

<signers/> contains the content model described in the %signers.content; parameter entity. It is an optional element, but if used it must contain signatory information for one or more signers of the court document optionally followed by a notarization. It has no attributes.

<!ELEMENT signatory (%signatory.content;)>

<signatory/> contains the content model described in the %signatory.content; parameter entity. It requires authors either to mark up one or more signature lines followed by information about one or more signatories, such as an attorney, judicial officer, or enforcement officer, or to mark up information about the signatory or signatories followed by one or more signature lines depending on the sequence desired. It has no attributes.

<!ELEMENT signatureLine (#PCDATA)>

<signatureLine/> contains a signature line for the text of a signature. It has no attributes.

<!ELEMENT notarization (signatureLine+ , (%notarization.content;))>

<notarization/> contains the content model described in the %notarization.content; parameter entity. It is an optional element, but if used it must contain notarization information for one or more notaries. It has no attributes. Notarizations typically appear in affidavits or verified court documents, such as verified complaints.

<!ELEMENT notaryDate (#PCDATA)>
<!ATTLIST notaryDate date CDATA #REQUIRED >

<notaryDate/> contains a text string giving the date of the notarization. It has a required "date" attribute to contain date information in ISO 8601 number format.

<!ELEMENT notarySeal (#PCDATA)>

<notarySeal/> contains the notary's seal. It has no attributes.

<!ELEMENT notaryExpiration (#PCDATA)>
<!ATTLIST notaryExpiration date CDATA #REQUIRED >

<notaryExpiration/> contains a text string giving the expiration date of the notary's authority. It has a required "date" attribute to contain date information in ISO 8601 number format.

<!ELEMENT proofOfService ((%paragraph.model;)+ , dateTimeServed , signatory)>

<proofOfService/> contains the content model for a certificate or proof of service. It is an optional element, but if used it must contain one or more paragraphs followed by the date (and optionally the time) of service, and information about the signer of the certificate or proof of service. It has no attributes.

<!ELEMENT dateTimeServed (%dateTime.content;)>

<dateTimeServed/> is a required element containing the date and optionally the time of the serving of the court document. It contains the %dateTime.content; parameter entity to incorporate the <date/> and <time/> elements and it has no attributes.

<!ELEMENT attachedItem (documentMetadata? , attachedItemContent)+>

<attachedItem/> describes the content model for an attachment to the XML court document. It contains an optional <documentMetadata/> element, which contains elements for describing metadata about the attached item, followed by one or more <attachedItemContent/> elements. This content model is different from the content model used to describe attachments in the Court Filing 1.1 DTD and thus has a different element name.

To accommodate the variety of items that might be included as attachments, the Court Document 1.1 DTD follows an approach similar to the Court Filing 1.1 DTD. It assumes that attached items will be either base-64 encoded BLOBs or, alternatively, a <![CDATA[ (unparsed character data) section within the <attachedItemContent/> element or a hyperlink (when allowed by a court as a matter of local policy). Base-64 encoding removes the < and & characters and other XML delimiters recognized as such by an XML parser. The alternative, marking a section of text as CDATA, can be used for attachments that are XML documents since it in effect turns off the parser so that the presence of XML elements that are not declared in the XML Court Document 1.1 DTD will not trigger parsing errors.

<!ELEMENT attachedItemContent (#PCDATA)>
<!ATTLIST attachedItemContent id ID #IMPLIED
mimeType CDATA #REQUIRED
contentEncoding (base64 ) #IMPLIED
href CDATA #IMPLIED>

<attachedItemContent/> contains the contents of an attachment to the court document. The attachment may be a base-64 encoded BLOB (particularly useful when the document being filed is a binary file), or, alternatively, a <![CDATA[ (unparsed character data) section. The <attachedItemContent/> element uses attributes borrowed from the Court Filing 1.1 DTD. It has a required "mimeType" attribute to indicate how the contents of decoded PCDATA are to be interpreted (e.g., application/PDF). The optional "id" attribute describes the unique identifier for the attached item. The "contentEncoding" attribute indicates the type of content encoding used and allows for future revisions. The "href" attribute specifies the location of a hyperlinked document.

<!ELEMENT electronicSignature (dataIntegrity?, authentication? , dsig:Signature?)+>

<electronicSignature/> describes information by which an application can determine whether an XML court document has been electronically signed, and if so, the particular electronic signature technologies that have been used. The <authentication/> element provides for authentication by means of a user id and password in keeping with the Court Filing 1.1 DTD. As previously noted, the <dsig:Signature/> element is incorporated from the W3C's XML-Signature Syntax and Processing Recommendation (2002-02-12).

<!ELEMENT dataIntegrity (#PCDATA)>
<!ATTLIST dataIntegrity bindingType (none | hash | authenticationCode | digitalSignature | 
symmetricKey | other ) #REQUIRED >

<dataIntegrity/> identifies the type of binding used for purposes of data integrity. It has a required "bindingType" enumerated attribute from which the specific type of binding can be selected.

<!ELEMENT authentication (userIdentification , password?)>
<!ATTLIST authentication userIdentification CDATA #IMPLIED
password CDATA #IMPLIED
authenticationType (none | passwordPlain | passwordCrypto | X-509 | 
biometric | signatureDynamics | signatureImage | other ) #REQUIRED >

<authentication/> contains information for authenticating an XML court document. The <userIdentification/> and optional <password/> elements provide for authentication by means of a user id and password for consistency with the Court Filing 1.1 DTD. The <authentication/> element has a required "authenticationType" enumerated attribute to indicate the type of authentication used.

<!ELEMENT userIdentification (#PCDATA)>

<userIdentification/> is the user name or logon identifier being authenticated by the password. It is incorporated from the Court Filing 1.1 DTD.

<!ELEMENT password (#PCDATA)>

<password/> is the secret word known to the user who is identified by userIdentification. It is incorporated from the Court Filing 1.1 DTD.

XML Digital Signature Elements and Attributes

<!ELEMENT dsig:Signature (dsig:SignedInfo , dsig:SignatureValue , dsig:KeyInfo? , dsig:Object*)>
<!ATTLIST dsig:Signature 
xmlns:dsig CDATA#FIXED 'http://www.w3.org/2000/09/xmldsig#'
Id ID#IMPLIED>

<!ELEMENT dsig:SignedInfo (dsig:CanonicalizationMethod , dsig:SignatureMethod ,
dsig:Reference+)>
<!ATTLIST dsig:SignedInfo Id ID #IMPLIED >

<!ELEMENT dsig:CanonicalizationMethod (#PCDATA)*>
<!ATTLIST dsig:CanonicalizationMethod Algorithm CDATA #REQUIRED >

<!ELEMENT dsig:SignatureMethod (#PCDATA | dsig:HMACOutputLength)*>
<!ATTLIST dsig:SignatureMethod Algorithm CDATA #REQUIRED >

<!ELEMENT dsig:Reference (dsig:Transforms? , dsig:DigestMethod , dsig:DigestValue)>
<!ATTLIST dsig:Reference Type CDATA #IMPLIED
URI CDATA #IMPLIED
Id ID #IMPLIED >

<!ELEMENT dsig:Transforms (dsig:Transform+)>

<!ELEMENT dsig:Transform (#PCDATA | dsig:XPath)*>
<!ATTLIST dsig:Transform Algorithm CDATA #REQUIRED >

<!ELEMENT dsig:XPath (#PCDATA)>

<!ELEMENT dsig:DigestMethod (#PCDATA)*>
<!ATTLIST dsig:DigestMethod Algorithm CDATA #REQUIRED >

<!ELEMENT dsig:DigestValue (#PCDATA)>

<!ELEMENT dsig:KeyInfo (#PCDATA | dsig:KeyName | dsig:KeyValue | dsig:RetrievalMethod | 
dsig:X509Data | dsig:PGPData | dsig:SPKIData | dsig:MgmtData %KeyInfo.ANY;)*>
<!ATTLIST dsig:KeyInfo Id ID #IMPLIED >

<!ELEMENT dsig:KeyName (#PCDATA)>

<!ELEMENT dsig:KeyValue (#PCDATA | dsig:DSAKeyValue | dsig:RSAKeyValue)*>

<!ELEMENT dsig:MgmtData (#PCDATA)>

<!ELEMENT dsig:RetrievalMethod (dsig:Transforms?)>
<!ATTLIST dsig:RetrievalMethod Type CDATA #IMPLIED
URI CDATA #REQUIRED >

<!ELEMENT dsig:X509Data ((dsig:X509IssuerSerial | dsig:X509SKI | dsig:X509SubjectName | 
dsig:X509Certificate | dsig:X509CRL)+)>

<!ELEMENT dsig:X509IssuerSerial (dsig:X509IssuerName , dsig:X509SerialNumber)>

<!ELEMENT dsig:X509IssuerName (#PCDATA)>

<!ELEMENT dsig:X509SubjectName (#PCDATA)>

<!ELEMENT dsig:X509SerialNumber (#PCDATA)>

<!ELEMENT dsig:X509SKI (#PCDATA)>

<!ELEMENT dsig:X509Certificate (#PCDATA)>

<!ELEMENT dsig:X509CRL (#PCDATA)>

<!ELEMENT dsig:PGPData ((dsig:PGPKeyID , dsig:PGPKeyPacket?) | (dsig:PGPKeyPacket))>

<!ELEMENT dsig:PGPKeyPacket (#PCDATA)>

<!ELEMENT dsig:PGPKeyID (#PCDATA)>

<!ELEMENT dsig:SPKIData (dsig:SPKISexp)>

<!ELEMENT dsig:SPKISexp (#PCDATA)>

<!ELEMENT dsig:Object (#PCDATA | dsig:Signature | dsig:SignatureProperties |
dsig:Manifest)*>
<!ATTLIST dsig:Object Encoding CDATA #IMPLIED
MimeType CDATA #IMPLIED
Id ID #IMPLIED >

<!ELEMENT dsig:Manifest (dsig:Reference+)>
<!ATTLIST dsig:Manifest Id ID #IMPLIED >

<!ELEMENT dsig:SignatureProperties (dsig:SignatureProperty+)>
<!ATTLIST dsig:SignatureProperties Id ID #IMPLIED >

<!ELEMENT dsig:SignatureProperty (#PCDATA)*>
<!ATTLIST dsig:SignatureProperty Id ID #IMPLIED
Target CDATA #REQUIRED >

<!ELEMENT dsig:HMACOutputLength (#PCDATA)>

<!ELEMENT dsig:DSAKeyValue ((dsig:P , dsig:Q)? , dsig:G? , dsig:Y , dsig:J? , 
(dsig:Seed , dsig:PgenCounter)?)>

<!ELEMENT dsig:P (#PCDATA)>

<!ELEMENT dsig:Q (#PCDATA)>

<!ELEMENT dsig:G (#PCDATA)>

<!ELEMENT dsig:Y (#PCDATA)>

<!ELEMENT dsig:J (#PCDATA)>

<!ELEMENT dsig:Seed (#PCDATA)>

<!ELEMENT dsig:PgenCounter (#PCDATA)>

<!ELEMENT dsig:RSAKeyValue (dsig:Modulus , dsig:Exponent)>

<!ELEMENT dsig:Modulus (#PCDATA)>

<!ELEMENT dsig:Exponent (#PCDATA)>

<!ELEMENT dsig:SignatureValue (#PCDATA)>
<!ATTLIST dsig:SignatureValue Id ID #IMPLIED >

<dsig:Signature/> is the root element for XML digital signatures. The W3C's XML-Signature Syntax and Processing Recommendation (2002-02-12) provides the current specification regarding XML digital signatures and should be consulted for a detailed explanation. Elements incorporated from the W3C XML digital signature Recommendation use the XML namespace prefix "dsig." In general, XML digital signatures "provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere."