This specification defines the first (1.0) version of the eNotarization Markup Language (ENML), an XML-based messaging protocol, by which applications executing on computing devices may notarize electronic documents for legal purposes. The specification accommodates most business and legal requirements of notarizing electronic documents without being constrained to a specific legal jurisdiction. While the initial specification was driven by notarization requirements of the fifty United States and the District of Columbia, there is foundational support for international jurisdictions and can be easily extended to accommodate specific requirements if needed.

This document was last revised by the LegalXML eNotarizationTC as of the above date. The level of approval is also listed above. Check the "Latest Version" or "Latest Approved Version" location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=legalxml-enotary.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/legalxml-enotary/ipr.php).

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The names "OASIS" and “ENML” are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

1 Introduction 7

1.1 Terminology 7

1.2 Glossary 7

1.3 Normative References 8

1.4 Non-normative References 9

2 Background (non-normative) 10

2.1 Requirements (non-normative) 11

3 Examples of use of ENML (non-normative) 13

3.1 eNotarized document – Single Signer & Notary with NULL Cryptographic Signatures 13

3.2 eNotarized document - Multiple Signers & Single Notary with NULL Cryptographic Signatures 19

3.3 eNotarized document - Multiple Signers & Notaries with NULL Cryptographic Signatures 22

3.4 eWitnessed document – Single Signer & Notary Public with NULL Cryptographic Signatures 26

3.5 eNotarized document - Multiple Signers, Single Notary & Symmetric Key Signature 31

3.6 eNotarized document - Multiple Signers, Multiple Notaries & Symmetric Key Signatures 41

3.7 eWitnessed document - Single Signer, Single Notary & Symmetric Key Signature 48

3.8 eNotarized document - Single Signer, Single Notary & Digital Signature 51

3.9 eNotarized document - Multiple Signers, Multiple Notaries & Digital Signatures 55

3.10 eWitnessed document - Multiple Signers, Single Notary & Digital Signature 58

3.11 eApostillized document with a Digital Signature 60

3.12 The use of XPath in <ds:Signature> 65

4 Specification 66

4.1 Element <NotarizedDocument> 66

4.2 Element <WitnessedDocument> 68

4.3 Element <ApostillizedDocument> 70

4.4 Element <SignedDocuments> & <SignedDocument> 73

4.5 Element <DocumentSigners> & <DocumentSigner> 76

4.6 Element <NotaryCertificates> & <NotaryCertificate> 82

4.7 Element <NotarySignatures> & <NotarySignature> 85

4.8 Element <NotariesPublic> & <NotaryPublic> 90

4.9 Element <Document> 95

4.10 Element <DocumentMIMEType> & <SignedDocumentMIMEType> 97

4.11 Element <DocumentMIMETypeComments> 99

4.12 Element <DocumentComments> 100

4.13 Element <SignerName> 101

4.14 Element <SignerTitle> 105

4.15 Element <SignerInternationalAddress> 106

4.16 Element <SignerUSAddress> 110

4.17 Element <SignerIdentificationMethod> 113

4.18 Element <SignerSignature> 114

4.19 Element <CertificateContent> 115

4.20 Element <NotaryName> 118

4.21 Element <NotaryCommissionNumber> 122

4.22 Element <NotaryCommissionExpiryDate> 123

4.23 Element <NotaryInternationalJurisdiction> 124

4.24 Element <NotaryUSJurisdiction> 127

4.25 Element <NotaryBondNumber> 130

4.26 Element <PersonPrefixName> 131

4.27 Element <PersonFirstName> & <PersonGivenName> 132

4.28 Element <PersonMiddleName> 133

4.29 Element <PersonLastName> & <PersonSurName> 133

4.30 Element <PersonSuffixName> 134

4.31 Element <PersonMaidenName> 135

4.32 Element <PersonFullName> 136

4.33 Element <StreetAddress1> 136

4.34 Element <StreetAddress2> 137

4.35 Element <City> 138

4.36 Element <County> 138

4.37 Element <State> 139

4.38 Element <PostalCode> 140

4.39 Element <Country> (International) 140

4.40 Element <USState> 141

4.41 Element <USZipCode> 148

4.42 Element <Country> (USA) 149

4.43 Element <NotarizationType> 150

4.44 Element <NotarizationDate> 151

4.45 Element <NotarizationInternationalLocation> 152

4.46 Element <NotarizationUSLocation> 154

4.47 Element <ApostilleContent> 155

4.48 Element <IssuingCountry> 161

4.49 Element <ApostilleNumber> 162

4.50 Element <ApostilleDate> 163

4.51 Element <IssuedAtInternationalLocation> 165

4.52 Element <IssuedAtUSLocation> 167

4.53 Element <DocumentSigningOfficialName> 168

4.54 Element <DocumentSigningOfficialTitle> 170

4.55 Element <DocumentSigningOfficialSeal> 172

4.56 Processing Rule for ID attributes within ENML 176

5 Conformance 181

Appendix A.Acknowledgments 182

Appendix B.Revision History 183

Appendix C.ENML Security Implications (Non-normative) 184

Appendix D.ENML Error Codes and Error Messages 185

Appendix E.Process for requesting a block of ENML Error Codes for Vendor Use 194

1 Introduction

This document presents the specification for the eNotarization Markup Language (ENML), a protocol by which applications may notarize electronic documents for legal purposes. All text is normative unless otherwise indicated.

1.1 Terminology

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in IETF RFC 2119.

1.2 Glossary

3DES – Triple Data Encryption Standard; an advancement of the Data Encryption Standard that triples the size of the cryptographic key

AES – Advanced Encryption Standard; a new encryption standard standardized by NIST

Apostille – A certificate, issued by a competent authority (normally Secretaries of State in the USA for notarized documents), attesting to the validity of the notary's signature in the notarized document.

Ciphertext – Encrypted data that must be decrypted before it can be used by an application

Conforming Application – A software application that has implemented the ENML protocol and meets the conformance requirements specified within this document

Cryptographic Module – A software library or hardware module dedicated to performing cryptographic operations

Cryptographic Signature – The encryption of a message digest using a symmetric or an asymmetric cryptographic key

DES – Data Encryption Standard; an encryption standard that is deprecated and no longer used in secure environments

ENML – The eNotarization Markup Language, a specification of the OASIS LegalXML eNotarization Technical Committee

eNotarized Document – An electronic document that has been electronically signed by a Notary Public, in their official capacity, and which includes a notarial certificate

eWitnessed Document – An electronic document that has been electronically signed by a Notary Public, in their official capacity, but which DOES NOT include a notarial certificate

Manifest – An XML element that contains references to other XML elements within the same document

Message Digest – The result of a one-way cryptographic transformation of a document (or input) into a fixed-length value which is deemed to be unique. A message digest cannot be used to reconstruct the original document

Notarial Certificate - Official text, specified by law in some states, providing context for the Notary Public's signature within a notarized document

Notarization – The act of a Notary Public signing a document in their official capacity

NULL Cryptographic Signature – Legally admissible text typed by a Document Signer and/or Notary Public, indicating their fixation of an electronic signature to an electronic document. The NULL Signature IS NOT a Cryptographic Signature and does NOT use any cryptographic algorithms. Some sample NULL Cryptographic Signatures are “Signed by John Doe”, or “/Signed by John Doe”, “XXX John Doe XXX Signed by John Doe on January 27, 2008”, etc.

Notary Public – An individual, conferred by authority of a jurisdiction to notarize documents

PII – Personally Identifiable Information, such as credit card numbers, social security numbers, bank account numbers, drivers license numbers, etc.

Plaintext – Unencrypted data that can readily be processed by an application without any transformation

Schema or XML Schema – A specification of the World Wide Consortium, whose constructs can be used to structurally define an XML document. All documents that conform to a specific XML Schema definition, have the same structure

SHA – Secure Hashing Algorithm; a specific cryptographic transformation of a document (or input) into a fixed-length value (message digest) which is deemed to be unique

SKMS – Symmetric Key Management System; a collection of hardware and software providing symmetric encryption key-management services

SKS - Symmetric Key Services; a server that provides symmetric key management services to requesting applications and/or devices

SKSML – Symmetric Key Services Markup Language; an XML-based protocol to request and receive symmetric encryption key-management services

XMLEncryption – Encrypted content represented in eXtensible Markup Language that conforms to the World Wide Web Consortium's XML Encryption standard

XMLSignature – A digital signature represented in eXtensible Markup Language that conforms to the World Wide Web Consortium's XML Signature standard

1.3 Normative References

[AES] Advanced Encryption Standard
NIST FIPS 197. http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf

[DSS] OASIS Standard
Digital Signature Services
11 April 2007
http://docs.oasis-open.org/dss/v1.0/oasis-dss-core-spec-v1.0-os.html

[HCCH] Convention of 5th October 1961
Abolishing the Requirement of Legalisation for Foreign Public Documents
http://hcch.e-vision.nl/index_en.php?act=conventions.text&cid=41
http://www.hcch.net/index_en.php?act=publications.details&pid=3198&dtid=28

[ISO-3166-1] International Standards Organization (ISO)
English country names and code elements
http://www.iso.org/iso/country_codes/iso_3166_code_lists/ \
english_country_names_and_code_elements.htm

[RFC 2119] S. Bradner. Key words for use in RFCs to Indicate Requirement Levels.
IETF RFC 2119, March 1997. .http://www.ietf.org/rfc/rfc2119.txt

[SKSML] OASIS Committee Specification 01
Symmetric Key Services Markup Language
18 January 2009
http://docs.oasis-open.org/ekmi/sksml/v1.0/SKSML-1.0-Specification.html

[XPATH] XML Path Language
W3C Recommendation 16 Nov 1999. http://www.w3.org/TR/xpath

[XMLEncryption] XML Encryption Syntax and Processing
W3C Recommendation 10 Dec 2002. http://www.w3.org/TR/xmlenc-core/

[XMLSignature] XML Signature Syntax and Processing
W3C Recommendation 12 Feb 2002. http://www.w3.org/TR/xmldsig-core/

1.4 Non-normative References

2 Background (non-normative)

Notarized paper documents are a mainstay of many legal transactions around the world. Requiring a modicum of formality in the US – perhaps more than a modicum in others - it offers a safe and reasonably-priced, sometimes free, procedure for engendering trust in business transactions of significant value. With a notarized document, relying parties have access to the legal framework of their jurisdiction in the event they must seek redress for a transaction gone awry.

Computers have dramatically improved the efficiency of business procedures in many fields, including the legal field. The notarization of electronic documents is a logical extension of developments that continue the improvement. To ensure that electronically notarized (“eNotarized”) documents are used and understood consistently and uniformly across applications, a standard protocol for depicting eNotarized documents is needed. The eNotarized Markup Language (ENML) is that protocol.

Using ENML, any application – be it a word-processor, a document-management system, a web-application to manage property recordings, a standalone notarizing application, etc. - can either electronically notarize a document, or verify a notarized document depicted in ENML.

ENML is a language that describes the content of electronically notarized, witnessed or apostillized document. An eNotarized document described by ENML, will carry similar constructs as a paper-notarized document:

ENML is designed to allow applications to speed the processing of business transactions by performing two specific actions:

ENML is not an electronic notary. It DOES NOT replace the human Notary Public or the non-technological processes typically involved amongst humans as part of a standard paper-document notarization.

While ENML builds on existing standards, it does not tie the language to any specific type of technology (other than the use of the eXtensible Markup Language (XML). While XML is meant to be a readable language by human beings, ENML is designed to be used mostly with software products that implement ENML's constructs. It can ONLY be verified by Conforming Applications and cannot be verified by human beings without such tools.

2.1 Requirements (non-normative)

ENML is the result of many notarial, business, legal, technical and security experts coming together to create a standard that works for today's environment while being flexible to address tomorrow's needs.

3 Examples of use of ENML (non-normative)

While Section 4 provides the definitive and normative details of ENML, this section provides many examples describing the use of ENML in various use-cases.

IMPORTANT NOTE: The documents, digest values, signatures and other cryptographic elements shown in these examples are NOT cryptographically valid. They are shown here, merely as illustrations of what ENML will look like when created by conforming applications. Conforming applications, however, must produce cryptographically valid elements in eNotarized documents, where required by the standard.

3.1 eNotarized document – Single Signer & Notary with NULL Cryptographic Signatures

The first example shows ENML for a document signed by one DocumentSigner and notarized by one Notary Public, who both use NULL Cryptographic Signatures to indicate their consent to having signed the electronic document.

[a001] <enml:NotarizedDocument
[a002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[a003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[a004] xsi:schemaLocation=
[a005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[a006] Id="NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[a007] 
[a012] <enml:SignedDocuments>
[a013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222640886-
1ba2c527bcec7e94442cc36d63b204fe2950970b84bbc7115409d387d33afecf">
[a014] <enml:Document>
[a015] PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
[a016] Y2VtYmVyIDIwMDcgQWxsIFJpZ2h0cyBSZXNlcnZlZC4KCiAgVGhpcyBkb2N1bWVu
[a017] dCBhbmQgdHJhbnNsYXRpb25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5p
[a018] c2hlZCB0byBvdGhlcnMsIAogIGFuZCBkZXJpdmF0aXZlIHdvcmtzIHRoYXQgY29t
[a019] bWVudCBvbiBvciBvdGhlcndpc2UgZXhwbGFpbiBpdCBvciBhc3Npc3QgaW4gaXRz
[a020] CiAgaW1wbGVtZW50YXRpb24gbWF5IGJlIHByZXBhcmVkLCBjb3BpZWQsIHB1Ymxp
[a021] c2hlZCBhbmQgZGlzdHJpYnV0ZWQsIGluIHdob2xlIG9yCiAgaW4gcGFydCwgd2l0
[a022] LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
[a023] aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
[a024] ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
[a025] </enml:Document>
[a026] <enml:DocumentMIMEType>application/xml</enml:DocumentMIMEType>
[a027] <enml:DocumentComments>
[a028] A Base64-encoded document
[a029] </enml:DocumentComments>
[a030] </enml:SignedDocument>
[a031] </enml:SignedDocuments>
[a032] 
[a037] <enml:DocumentSigners>
[a038] 
[a039] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222640905-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[a040] <enml:SignerName>
[a041] <enml:PersonGivenName>John</enml:PersonGivenName>
[a042] <enml:PersonSurName>Doe</enml:PersonSurName>
[a043] </enml:SignerName>
[a044] <enml:SignerIdentificationMethod>
[a045] Produced Government-issued Identification Document
[a046] </enml:SignerIdentificationMethod>
[a047] <enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
[a048] </enml:DocumentSigner>
[a049] </enml:DocumentSigners>
[a050] 
[a055] <enml:NotaryCertificates>
[a056] <enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-
1222640980-0ef2d548e82b637a0568fc1c4e69e2eb896acfc083fdefb82e24a05cab840f54">
[a057] <enml:CertificateContent>
[a058] <enml:NotarizationType>
[a059] Acknowledgment
[a060] </enml:NotarizationType>
[a061] <enml:NotarizationDate>
[a062] 2007-02-07T15:19:17-08:00
[a063] </enml:NotarizationDate>
[a064] <enml:NotarizationUSLocation>
[a065] <enml:City>Cupertino</enml:City>
[a066] <enml:County>Santa Clara</enml:County>
[a067] <enml:USState>CA</enml:USState>
[a068] <enml:Country>USA</enml:Country>
[a069] </enml:NotarizationUSLocation>
[a070] <enml:StatutoryContent>
[a071] State of California
[a072] County of Santa Clara
[a073]
[a074] On February 07 2007, before me Arshad Noor, personally
[a075] appeared John Doe, who proved to me on the basis of
[a076] satisfactory evidence to be the person whose name is
[a077] subscribed to the within instrument and acknowledged to
[a078] me that he executed the same in his authorized capacity,
[a079] and that by his signature on the instrument the person,
[a080] or the entity upon behalf of which the person acted,
[a081] executed the instrument.
[a082]
[a083] I certify under PENALTY OF PERJURY under the laws of the
[a084] State of California that the foregoing paragraph is true
[a085] and correct.
[a086]
[a087] WITNESS my hand and official seal.
[a088] </enml:StatutoryContent>
[a089] </enml:CertificateContent>
[a090]
[a091] 
[a092] <enml:NotaryPublic>
[a093] <enml:NotaryName>
[a094] <enml:PersonGivenName>Arshad</enml:PersonGivenName>
[a095] <enml:PersonSurName>Noor</enml:PersonSurName>
[a096] </enml:NotaryName>
[a097] <enml:NotaryCommissionNumber>
[a098] 1565986
[a099] </enml:NotaryCommissionNumber>
[a100] <enml:NotaryCommissionExpiryDate>
[a101] 2009-04-29T23:59:59-08:00
[a102] </enml:NotaryCommissionExpiryDate>
[a103] <enml:NotaryUSJurisdiction>
[a104] <enml:County>Santa Clara</enml:County>
[a105] <enml:USState>CA</enml:USState>
[a106] <enml:Country>USA</enml:Country>
[a107] </enml:NotaryUSJurisdiction>
[a108] </enml:NotaryPublic>
[a109] </enml:NotaryCertificate>
[a110] </enml:NotaryCertificates>
[a111] 
[a116] <enml:NotarySignatures>
[a117] <enml:NotarySignature>Signed by Arshad Noor</enml:NotarySignature>
[a118] </enml:NotarySignatures>
[a119] 
[a124] </enml:NotarizedDocument>

[a001] is the start tag of the NotarizedDocument element, the root of this eNotarized document instance.

[a002] indicates that this is an instance – an occurrence - of a document that conforms to a specific XML Schema Definition (XSD).

[a003] identifies the namespace to which this XML instance document conforms.

[a004] - [a005] identifies the name and location of the XML Schema Definition (XSD) file that defines the structure of this XML instance document.

[a006] is an attribute called “ID” whose value is “NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4”. The ID attribute allows this document to be uniquely identified within other XML documents (such as an ApostillizedDocument). The value of the ID attribute is created by the application generating this ENML, and is unique for this instance of a NotarizedDocument.

[a012] is the start tag of the SignedDocuments element, which indicates the documents that are being eNotarized. Note: While current laws only allow for a single document to be notarized by a single notarial certificate and notary signature per notarization, the ENML schema allows for eNotarizing multiple documents with a single notarial certificate and notary signature. However, applications using/implementing ENML are expected to contain only a single document within this element for the foreseeable future.

[a013] is the start tag of a SignedDocument element, which has an attribute called “ID” whose value is “SignedDocument-US-CA-1565986-1222640886-1ba2c527bcec7e94442cc36d63b204fe2950970b84bbc7115409d387d33afecf”. This is the only document being eNotarized within this NotarizedDocument instance. The ID attribute allows this document to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[a015] - [a024] contains the Base64-encoded document that is being eNotarized. The Base64-encoding allows any type of document – text, graphics, multimedia, etc. - to be eNotarized and transported from machine to machine over networks, and rendered consistently.

[a026] indicates the Multipurpose Internet Mail Extension (MIME)-type of the document in the DocumentMIMEType element. This element identifies the type of document that is being eNotarized: a word-processing document created by OpenOffice Writer or Microsoft Word, a Portable Network Graphics (PNG) or Graphics Image File (GIF) file, etc. Receiving computers can use this element to determine which application to use to display the eNotarized document.

[a028] is a free-form comment about the document being eNotarized. If there is no standard MIME-type for the document being eNotarized, this field can be used to provide hints to the receiving computer about which application to use to display the document.

[a037] is is the start tag of the DocumentSigners element. This element contains information about all document-signers of the eNotarized document, which does not include the Notary Public.

[a039] is the start tag of a DocumentSigner element, which has an attribute called “ID” whose value is “DocumentSigner-US-CA-1565986-1222640905-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7”. This is the only signer of the document being eNotarized within this NotarizedDocument instance. The ID attribute allows this signer to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[a040] is the start tag of the SignerName element. This element contains information about the document-signer's name.

[a041] indicates the DocumentSigner's given name (first name) in the PersonGivenName element.

[a042] indicates the DocumentSigner's surname (last name) in the PersonSurName element.

[a044] is the start tag of the SignerIdentificationMethod element. This element contains information about how the document-signer identified himself/herself to the Notary Public. For privacy reasons, this element should not show any information considered sensitive, such as the Social Security Number, a Drivers License Number, a Passport or Identification Card Number, etc., but just indicate what type of identification was provided.

[a045] is free-form text that indicates that this signer provided a “Government-issued Identification Document”. It is assumed that the Notary Public has performed his/her duties with diligence, as required by law, in verifying the authenticity of the identification information.

[a047] is a SignerSignature element containing a NULL Cryptographic Signature. This implies that the document's signer's signature does not use a cryptographic mechanism to create an electronic signature. Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of security issues within ENML.

[a055] is the start tag of the NotaryCertificates element. This element contains one or more notarial certificates for eNotarized documents.

[a056] is the start tag of the NotaryCertificate element. This element has an attribute called “ID” (with the value “NotaryCertificate-US-CA-1565986-1222640980-0ef2d548e82b637a0568fc1c4e69e2eb896acfc083fdefb82e24a05cab840f54” in this example) that allows this notarial certificate to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[a057] is the start tag of the CertificateContent element. This element contains information about the eNotarization act.

[a058] is the start tag of the NotarizationType element. This element identifies the type of eNotarization being performed.

[a059] identifies the type of eNotarization being performed; in this case, it is an Acknowledgment.

[a061] is the start tag of the NotarizationDate element. This element identifies the date, time and time-zone on which the eNotarization was performed.

[a062] identifies the date, time and time-zone of eNotarization; in this case, it is February 7^th, 2007 at 3:19PM in the Pacific Time Zone (- 08:00 from Coordinated Universal Time or UTC).

[a064] is the start tag of the NotarizationUSLocation element. This element identifies the political jurisdiction in the United States of America where the eNotarization was performed.

[a065] identifies the City where the eNotarization was performed; in this case, it is Cupertino.

[a066] identifies the County where the eNotarization was performed; in this case, it is Santa Clara.

[a067] identifies the USState where the eNotarization was performed; in this case, it is an CA (for California).

[a068] identifies the Country where the eNotarization was performed; in this case, it is in the USA.

[a070] is the start tag of the StatutoryContent element. This element provides the statutory content that must be provided in a notarial certificate for an eNotarized document in the United States of America.

[a071] – [a087] identifies the statutory content for this NotarizedDocument; in this case, it is free-form text for an Acknowledgment as specified by the State of California.

[a092] is the start tag of the NotaryPublic element. This element provides details about the Notary Public who eNotarized this NotarizedDocument.

[a093] is the start tag of the NotaryName element. This element contains information about the Notary Public's name.

[a094] indicates the Notary Public's given name (first name) in the PersonGivenName element.

[a095] indicates the Notary Public's surname (last name) in the PersonSurName element.

[a097] is the start tag of the NotaryCommissionNumber element. This element identifies the identification number, if any, given to a Notary Public within a political jurisdiction.

[a098] identifies the Notary Public's commission number; in this case, it is 1565986.

[a100] is the start tag of the NotaryCommissionExpiryDate element. This element identifies the date and time on which the Notary Public's authorized commission expires.

[a101] identifies the expiry date, time and time-zone of the Notary Public's commission; in this case, it is April 29, 2009 at the 59^th second of 11:59 PM in the Pacific time zone (-08:00 from UTC).

[a103] is the start tag of the NotaryUSJurisdiction element. This element identifies the political jurisdiction in the United States of America where the Notary Public is authorized to perform his/her official duties.

[a104] identifies the County where the Notary Public performs his/her official duties; in this case, it is Santa Clara.

[a105] identifies the USState where the Notary Public performs his/her official duties; in this case, it is an CA (for California).

[a106] identifies the Country where the Notary Public performs his/her official duties; in this case, it is in the USA.

[a116] is the start tag of the NotarySignatures element. This element contains information the notarial signatures of the Notaries Public.

[a117] is a NotarySignature element containing a NULL Cryptographic Signature. This implies that the Notary Public's signature was not created using any cryptographic mechanism. Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of security issues within ENML.

[a124] is the closing tag of the NotarizedDocument element, signifying the end of this XML instance.

3.2 eNotarized document - Multiple Signers & Single Notary with NULL Cryptographic Signatures

In this example of an eNotarized document, we show how two document signers are stored in one instance of a NotarizedDocument. It shows ENML for a document signed by multiple document-signers and notarized by one:Notary Public, all of whom use NULL Cryptographic Signatures within the ENML

We dispense with showing the SignedDocuments, the NotaryCertificates and the NotarySignatures elements, and assume them to be similar to the ones shown in the previous example in Section 3.1, for brevity.

[b001] <enml:NotarizedDocument
[b002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
...
[b031] 
[b036] <enml:DocumentSigners>
[b037] 
[b038] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222640905-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[b039] <enml:SignerName>
[b040] <enml:PersonFirstName>John</enml:PersonFirstName>
[b041] <enml:PersonLastName>Doe</enml:PersonLastName>
[b042] </enml:SignerName>
[b043] <enml:SignerUSAddress>
[b044] <enml:StreetAddress1>123 Main Street</enml:StreetAddress1>
[b045] <enml:City>Sunnyvale</enml:City>
[b046] <enml:County>Santa Clara</enml:County>
[b047] <enml:USState>CA</enml:USState>
[b048] <enml:USZipCode>94085</enml:USZipCode>
[b049] <enml:Country>USA</enml:Country>
[b050] </enml:SignerUSAddress>
[b051] <enml:SignerIdentificationMethod>
[b052] Personally Known to Notary Public
[b053] </enml:SignerIdentificationMethod>
[b054] <enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
[b055] </enml:DocumentSigner>
[b056]
[b057] 
[b058] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
[b059] <enml:SignerName>
[b060] <enml:PersonFirstName>Jane</enml:PersonFirstName>
[b061] <enml:PersonLastName>Doe</enml:PersonLastName>
[b062] </enml:SignerName>
[b063] <enml:SignerUSAddress>
[b064] <enml:StreetAddress1>123 Main Street</enml:StreetAddress1>
[b065] <enml:City>Sunnyvale</enml:City>
[b066] <enml:County>Santa Clara</enml:County>
[b067] <enml:USState>CA</enml:USState>
[b068] <enml:USZipCode>94085</enml:USZipCode>
[b069] <enml:Country>USA</enml:Country>
[b070] </enml:SignerUSAddress>
[b071] <enml:SignerIdentificationMethod>
[b072] Personally Known to Notary Public
[b073] </enml:SignerIdentificationMethod>
[b074] <enml:SignerSignature>Signed by Jane Doe</enml:SignerSignature>
[b075] </enml:DocumentSigner>
[b076] </enml:DocumentSigners>
...
[b102] 
[b107] </enml:NotarizedDocument>

[b001] is the start tag of the NotarizedDocument element, the root of this eNotarized document instance.

[b002] indicates that this is an instance – an occurrence - of a document that conforms to a specific XML Schema Definition (XSD).

[b036] is is the start tag of the DocumentSigners element. This element contains information about all document-signers of the eNotarized document, which does not include the Notary Public.

[b038] is the start tag of the first DocumentSigner element, which has an attribute called “ID” (whose value is “DocumentSigner-US-CA-1565986-1222640905-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7” in this example). This is the first of multiple signers of the document being eNotarized within this NotarizedDocument instance. The ID attribute allows this signer to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[b039] is the start tag of the SignerName element. This element contains information about the document-signer's name.

[b040] indicates the DocumentSigner's first name (given name) in the PersonFirstName element.

[b041] indicates the DocumentSigner's last name (surname) in the PersonLastName element.

[b043] is the start tag of the SignerUSAddress element. This element contains the address of the DocumentSigner in the United States of America.

[b044] indicates the first line of the street address of the DocumentSigner in the StreetAddress1 element. In this example it is “123 Main Street”.

[b045] identifies the City of the DocumentSigner's US address; in this case, it is Sunnyvale.

[b046] identifies the County of the DocumentSigner's US address; in this case, it is Santa Clara.

[b047] identifies the USState of the DocumentSigner's US address; in this case, it is CA (for California).

[b048] identifies the USZipCode of the DocumentSigner's US address; in this case, it is 94085.

[b049] identifies the Country of the DocumentSigner's address; in this case, it is in the USA.

[b051] is the start tag of the SignerIdentificationMethod element. This element contains information about how the document-signer identified himself/herself to the Notary Public.

[b052] is free-form text that indicates that this signer was personally known to the Notary Public.

[b054] is a SignerSignature element using the NULL Cryptographic Signature.

[b058] is the start tag of the second DocumentSigner element, which has an attribute called “ID” (whose value is “DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc” in this example). This is the second of multiple signers of this NotarizedDocument instance.

[b059] is the start tag of the SignerName element. This element contains information about the document-signer's name.

[b060] indicates the DocumentSigner's first name (given name) in the PersonFirstName element.

[b061] indicates the DocumentSigner's last name (surname) in the PersonLastName element.

[b063] is the start tag of the SignerUSAddress element. This element contains the address of the DocumentSigner in the United States of America.

[b064] indicates the first line of the street address of the DocumentSigner in the StreetAddress1 element. In this example it is “123 Main Street”.

[b065] identifies the City of the DocumentSigner's US address; in this case, it is Sunnyvale.

[b066] identifies the County of the DocumentSigner's US address; in this case, it is Santa Clara.

[b067] identifies the USState of the DocumentSigner's US address; in this case, it is CA (for California).

[b068] identifies the USZipCode of the DocumentSigner's US address; in this case, it is 94085.

[b069] identifies the Country of the DocumentSigner's address; in this case, it is the USA.

[b071] is the start tag of the SignerIdentificationMethod element. This element contains information about how the document-signer identified himself/herself to the Notary Public.

[b072] is free-form text that indicates that this signer was personally known to the Notary Public.

[b074] is a SignerSignature element using the NULL Cryptographic Signature.

[b107] is the closing tag of the NotarizedDocument element, signifying the end of this XML instance.

3.3 eNotarized document - Multiple Signers & Notaries with NULL Cryptographic Signatures

In this example of an eNotarized document, we show two document signers in two different locations, signing a document at different times, and notarized by two different Notaries Public at their respective locations. The business use-case requires both document signers to have signed the document and their signings notarized, before the document is accepted by a Relying Party. ENML supports this use-case, as shown below. This example, like the earlier ones, depicts the use of NULL Cryptographic Signatures.

We dispense with showing the SignedDocuments element and assume it to be similar to the ones shown in the previous example in Sections 3.1.

[c001] <enml:NotarizedDocument
[c002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
...
[c031] 
[c036] <enml:DocumentSigners>
[c037] 
[c038] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643713-
8b62ffc3df242c5832169d6514feb2799b3759883bbc3aadf68718a0d1a66250">
[c039] <enml:SignerName>
[c040] <enml:PersonFirstName>James</enml:PersonFirstName>
[c041] <enml:PersonLastName>Doe</enml:PersonLastName>
[c042] </enml:SignerName>
[c043] <enml:SignerUSAddress>
[c044] <enml:StreetAddress1>123 California Ave</enml:StreetAddress1>
[c045] <enml:City>Buffalo</enml:City>
[c046] <enml:County>Erie</enml:County>
[c047] <enml:USState>NY</enml:USState>
[c048] <enml:USZipCode>14202</enml:USZipCode>
[c049] <enml:Country>USA</enml:Country>
[c050] </enml:SignerUSAddress>
[c051] <enml:SignerIdentificationMethod>
[c052] Personally Known to Notary Public
[c053] </enml:SignerIdentificationMethod>
[c054] <enml:SignerSignature>Signed by James Doe</enml:SignerSignature>
[c055] </enml:DocumentSigner>
[c056]
[c057] 
[c058] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222640905-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[c059] <enml:SignerName>
[c060] <enml:PersonFirstName>John</enml:PersonFirstName>
[c061] <enml:PersonLastName>Doe</enml:PersonLastName>
[c062] </enml:SignerName>
[c063] <enml:SignerUSAddress>
[c064] <enml:StreetAddress1>123 Main Street</enml:StreetAddress1>
[c065] <enml:City>Sunnyvale</enml:City>
[c066] <enml:County>Santa Clara</enml:County>
[c067] <enml:USState>CA</enml:USState>
[c068] <enml:USZipCode>94085</enml:USZipCode>
[c069] <enml:Country>USA</enml:Country>
[c070] </enml:SignerUSAddress>
[c071] <enml:SignerIdentificationMethod>
[c072] Personally Known to Notary Public
[c073] </enml:SignerIdentificationMethod>
[c074] <enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
[c075] </enml:DocumentSigner>
[c076] </enml:DocumentSigners>
[c077] 
[c082] <enml:NotaryCertificates>
[c083] 
[c084] <enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-
1222643804-a56e5f27beae87a8e19d5652771d939291baca2ec4bfb9148a3b0af374b2af79">
[c085] <enml:CertificateContent>
[c086] <enml:NotarizationType>
[c087] Acknowledgment
[c088] </enml:NotarizationType>
[c089] <enml:NotarizationDate>
[c090] 2007-02-07T15:19:17-08:00
[c091] </enml:NotarizationDate>
[c092] <enml:NotarizationUSLocation>
[c093] <enml:City>Buffalo</enml:City>
[c094] <enml:County>Erie</enml:County>
[c095] <enml:USState>NY</enml:USState>
[c096] <enml:Country>USA</enml:Country>
[c097] </enml:NotarizationUSLocation>
[c098] <enml:StatutoryContent>
[c099] State of New York
[c100] County of Erie
[c101]
[c102] On the 7th day of February in the year 2007 before me,
[c103] the undersigned, personally appeared James Doe personally
[c104] known to me or proved to me on the basis of satisfactory
[c105] evidence to be the individual whose name is subscribed
[c106] to the within instrument and acknowledged to me that he
[c107] executed the same in his capacity, and that by his
[c108] signature on the instrument, the individual, or the
[c109] person upon behalf of which the individual acted,
[c110] executed the instrument.
[c111] </enml:StatutoryContent>
[c112] </enml:CertificateContent>
[c113]
[c114] 
[c115] <enml:NotaryPublic>
[c116] <enml:NotaryName>
[c117] <enml:PersonGivenName>Howard</enml:PersonGivenName>
[c118] <enml:PersonSurName>Jones</enml:PersonSurName>
[c119] </enml:NotaryName>
[c120] <enml:NotaryCommissionNumber>
[c122] N1234567
[c123] </enml:NotaryCommissionNumber>
[c124] <enml:NotaryCommissionExpiryDate>
[c125] 2009-07-19T23:59:59-05:00
[c126] </enml:NotaryCommissionExpiryDate>
[c127] <enml:NotaryUSJurisdiction>
[c128] <enml:County>Erie</enml:County>
[c129] <enml:USState>NY</enml:USState>
[c130] <enml:Country>USA</enml:Country>
[c131] </enml:NotaryUSJurisdiction>
[c132] </enml:NotaryPublic>
[c133] </enml:NotaryCertificate>
[c134]
[c135] 
[c136] <enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-
1222643918-3a2f6ca77ba1556fa4b7654874beddf0e5b026b9155ad725c040f6c13c1816b0">
[c137] <enml:CertificateContent>
[c138] <enml:NotarizationType>
[c139] Acknowledgment
[c140] </enml:NotarizationType>
[c141] <enml:NotarizationDate>
[c142] 2007-02-10T14:56:32-08:00
[c143] </enml:NotarizationDate>
[c144] <enml:NotarizationUSLocation>
[c145] <enml:City>Cupertino</enml:City>
[c146] <enml:County>Santa Clara</enml:County>
[c147] <enml:USState>CA</enml:USState>
[c148] <enml:Country>USA</enml:Country>
[c149] </enml:NotarizationUSLocation>
[c150] <enml:StatutoryContent>
[c151] State of California
[c152] County of Santa Clara
[c153]
[c154] On February 07 2007, before me Arshad Noor, personally
[c155] appeared John Doe, who proved to me on the basis of
[c156] satisfactory evidence to be the person whose name is
[c157] subscribed to the within instrument and acknowledged to
[c158] me that he executed the same in his authorized capacity,
[c159] and that by his signature on the instrument the person,
[c160] or the entity upon behalf of which the person acted,
[c161] executed the instrument.
[c162]
[c163] I certify under PENALTY OF PERJURY under the laws of the
[c164] State of California that the foregoing paragraph is true
[c165] and correct.
[c166]
[c167] WITNESS my hand and official seal.
[c168] </enml:StatutoryContent>
[c169] </enml:CertificateContent>
[c170]
[c171] 
[c172] <enml:NotaryPublic>
[c173] <enml:NotaryName>
[c174] <enml:PersonGivenName>Arshad</enml:PersonGivenName>
[c175] <enml:PersonSurName>Noor</enml:PersonSurName>
[c176] </enml:NotaryName>
[c177] <enml:NotaryCommissionNumber>
[c178] 1565986
[c179] </enml:NotaryCommissionNumber>
[c180] <enml:NotaryCommissionExpiryDate>
[c181] 2009-04-29T23:59:59-08:00
[c182] </enml:NotaryCommissionExpiryDate>
[c183] <enml:NotaryUSJurisdiction>
[c184] <enml:County>Santa Clara</enml:County>
[c185] <enml:USState>CA</enml:USState>
[c186] <enml:Country>USA</enml:Country>
[c187] </enml:NotaryUSJurisdiction>
[c188] </enml:NotaryPublic>
[c189] </enml:NotaryCertificate>
[c190] </enml:NotaryCertificates>
[c191] 
[c196] <enml:NotarySignatures>
[c197] <enml:NotarySignature>Signed by Howard Jones</enml:NotarySignature>
[c198] <enml:NotarySignature>Signed by Arshad Noor</enml:NotarySignature>
[c199] </enml:NotarySignatures>
[c200] 
[c205] </enml:NotarizedDocument>

[c001] is the start tag of the NotarizedDocument element, the root of this eNotarized document instance.

[c002] indicates that this is an instance – an occurrence - of a document that conforms to a specific XML Schema Definition (XSD).

[c036] is is the start tag of the DocumentSigners element. This element contains information about all document-signers of the eNotarized document, which does not include the Notary Public.

[c038] – [c055] identifies the first of two DocumentSigner elements. These lines in this XML example refer to a DocumentSigner, James Doe, in Buffalo city of Erie county in New York state, in the USA.

[c058] – [c075] identifies the second of two DocumentSigner elements. These lines in this XML example refer to a DocumentSigner, John Doe, in Sunnyvale city of Santa Clara county in the state of California.

[c082] is the start tag of the NotaryCertificates element. This element, in this example, contains two notarial certificates , one for each DocumentSigner.

[c083] - [c133] is the first of the two NotaryCertificate elements. This element contains information about the NotaryCertificate and the NotaryPublic, which in this example, refers to Howard Jones in Buffalo city in Erie county in New York state.

[c135] - [c189] is the second of the two NotaryCertificate elements. This element contains information about the NotaryCertificate and the NotaryPublic, which in this example, refers to Arshad Noor in Cupertino city of Santa Clara county in the state of California.

[c196] is the start tag of the NotarySignatures element. This element contains information the notarial signatures of the Notaries Public.

[c197] – [c198] are two NotarySignature elements with NULL Cryptographic Signatures used by the two Notaries.

[c205] is the closing tag of the NotarizedDocument element, signifying the end of this XML instance.

3.4 eWitnessed document – Single Signer & Notary Public with NULL Cryptographic Signatures

An eWitnessed document is one, in which the signing of the document by the DocumentSigner(s) is witnessed by the Notary Public, and the document is notarized, but does not contain a Notarial Certificate. The following ENML shows a sample eWitnessed document that contains NULL Cryptographic Signatures:

[d001] <enml:WitnessedDocument>
[d002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[d003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[d004] xsi:schemaLocation=
[d005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[d006] Id="WitnessedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[d007] 
[d012] <enml:SignedDocuments>
[d013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222644436-
42051bbfad827707d07e362511e44bc200636e045c4dd01f1b1ed30590ac3a74">
[d014] <enml:Document>
[d015] PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
[d016] Y2VtYmVyIDIwMDcgQWxsIFJpZ2h0cyBSZXNlcnZlZC4KCiAgVGhpcyBkb2N1bWVu
[d017] dCBhbmQgdHJhbnNsYXRpb25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5p
[d018] c2hlZCB0byBvdGhlcnMsIAogIGFuZCBkZXJpdmF0aXZlIHdvcmtzIHRoYXQgY29t
[d019] bWVudCBvbiBvciBvdGhlcndpc2UgZXhwbGFpbiBpdCBvciBhc3Npc3QgaW4gaXRz
[d020] CiAgaW1wbGVtZW50YXRpb24gbWF5IGJlIHByZXBhcmVkLCBjb3BpZWQsIHB1Ymxp
[d021] c2hlZCBhbmQgZGlzdHJpYnV0ZWQsIGluIHdob2xlIG9yCiAgaW4gcGFydCwgd2l0
[d022] LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
[d023] aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
[d024] ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
[d025] </enml:Document>
[d026] <enml:DocumentMIMEType>image/gif</enml:DocumentMIMEType>
[d027] <enml:DocumentComments>
[d028] A recent W-2 of the borrower.
[d029] </enml:DocumentComments>
[d030] </enml:SignedDocument>
[d031] </enml:SignedDocuments>
[d032] 
[d037] <enml:DocumentSigners>
[d038] 
[d039] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222644495-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[d040] <enml:SignerName>
[d041] <enml:PersonGivenName>John</enml:PersonGivenName>
[d042] <enml:PersonSurName>Doe</enml:PersonSurName>
[d043] </enml:SignerName>
[d044] <enml:SignerIdentificationMethod>
[d045] Produced Government-issued Identification Document
[d046] </enml:SignerIdentificationMethod>
[d047] <enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
[d048] </enml:DocumentSigner>
[d049] </enml:DocumentSigners>
[d050] 
[d055] <enml:NotariesPublic>
[d056] 
[d057] <enml:NotaryPublic Id="NotaryPublic-US-CA-1565986-1222644533-
4c8e1a0eff954439fef46b8694ca8641ae64a16790d7504b6dcc69014d9bd624">
[d058] <enml:NotaryName>
[d059] <enml:PersonGivenName>Arshad</enml:PersonGivenName>
[d060] <enml:PersonSurName>Noor</enml:PersonSurName>
[d061] </enml:NotaryName>
[d062] <enml:NotaryCommissionNumber>
[d063] 1565986
[d064] </enml:NotaryCommissionNumber>
[d065] <enml:NotaryCommissionExpiryDate>
[d066] 2009-04-29T23:59:59-08:00
[d067] </enml:NotaryCommissionExpiryDate>
[d068] <enml:NotaryUSJurisdiction>
[d069] <enml:County>Santa Clara</enml:County>
[d070] <enml:USState>CA</enml:USState>
[d071] <enml:Country>United States of America</enml:Country>
[d072] </enml:NotaryUSJurisdiction>
[d073] </enml:NotaryPublic>
[d074] </enml:NotariesPublic>
[d075] 
[d080] <enml:NotarySignatures>
[d081] <enml:NotarySignature>Signed by Arshad Noor</enml:NotarySignature>
[d082] </enml:NotarySignatures>
[d083] 
[d088] </enml:WitnessedDocument>

[d001] is the start tag of the WitnessedDocument element, the root of this eWitnessed document instance.

[d002] indicates that this is an instance – an occurrence - of a document that conforms to a specific XML Schema Definition (XSD).

[d003] identifies the namespace to which this XML instance document conforms.

[d004] - [d005] identifies the name and location of the XML Schema Definition (XSD) file that defines the structure of this XML instance document.

[d006] is an attribute called “ID” whose value is “WitnessedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4". The ID attribute allows this document to be uniquely identified within other XML documents (such as an ApostillizedDocument). The value of the ID attribute is created by the application generating this ENML, and is unique for this instance of a WitnessedDocument.

[d012] is the start tag of the SignedDocuments element, which indicates the documents that are being eWitnessed. Note: While current laws only allow for a single document to be witnessed by a notary signature per eWitnessing, the ENML schema allows for eWitnessing multiple documents with a single notary signature. However, applications using/implementing ENML are expected to contain only a single document within this element for the foreseeable future.

[d013] is the start tag of a SignedDocument element, which has an attribute called “ID” whose value is “SignedDocument-US-CA-1565986-1222644436-42051bbfad827707d07e362511e44bc200636e045c4dd01f1b1ed30590ac3a74” in this example. This is the only document being eWitnessed within this WitnessedDocument instance. The ID attribute allows this document to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eWitnessing. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a WitnessedDocument.

[d015] - [d024] contains the Base64-encoded document being eWitnessed. The Base64-encoding allows any type of document – text, graphics, multimedia, etc. - to be eWitnessed and transported from machine to machine over networks, and rendered consistently.

[d026] indicates the Multipurpose Internet Mail Extension (MIME)-type of the document in the DocumentMIMEType element. This element identifies the type of document being eWitnessed: a word-processing document created by OpenOffice Writer or Microsoft Word, a Portable Network Graphics (PNG) or Graphics Image File (GIF) file, etc. Receiving computers can use this element to determine which application to use to display the eWitnessed document.

[d028] is a free-form comment about the document being eNotarized. If there is no standard MIME-type for the document being eWitnessed, this field can be used to provide hints to the receiving computer about which application to use to display the document.

[d037] is is the start tag of the DocumentSigners element. This element contains information about all document-signers of this eWitnessed document, which does not include the Notary Public.

[d039] is the start tag of a DocumentSigner element, which has an attribute called “ID” whose value is “DocumentSigner-US-CA-1565986-1222644495-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7” in this example. This is the only signer of the document being eWitnessed within this WitnessedDocument instance. The ID attribute allows this signer to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eWitnessing. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a WitnessedDocument.

[d040] is the start tag of the SignerName element. This element contains information about the document-signer's name.

[d041] indicates the DocumentSigner's given name (first name) in the PersonGivenName element.

[d042] indicates the DocumentSigner's surname (last name) in the PersonSurName element.

[d044] is the start tag of the SignerIdentificationMethod element. This element contains information about how the document-signer identified himself/herself to the Notary Public. For privacy reasons, this element should not show any information considered sensitive, such as the Social Security Number, a Drivers License Number, a Passport or Identification Card Number, etc., but just indicate what type of identification was provided.

[d045] is free-form text indicating that this signer provided a “Government-issued Identification Document”. It is assumed that the Notary Public has performed his/her duties with diligence, as required by law, in verifying the authenticity of the identification information.

[d047] is a SignerSignature element containing a NULL Cryptographic Signature. Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of ENML security.

[d055] is the start tag of the NotariesPublic element. This element provides information about all Notaries who witnessed this document-signing.

[d057] is the start tag of the NotaryPublic element. This element provides details about the Notary Public who eWitnessed this WitnessedDocument. It has an attribute called “ID” (with the value “NotaryPublic-US-CA-1565986-1222644533-4c8e1a0eff954439fef46b8694ca8641ae64a16790d7504b6dcc69014d9bd624” in this example) that allows this Notary Public to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eWitnessing. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a WitnessedDocument.

[d058] is the start tag of the NotaryName element. This element contains information about the Notary Public's name.

[d059] indicates the Notary Public's given name (first name) in the PersonGivenName element.

[d060] indicates the Notary Public's surname (last name) in the PersonSurName element.

[d062] is the start tag of the NotaryCommissionNumber element. This element identifies the identification number, if any, given to a Notary Public within a political jurisdiction.

[d063] identifies the Notary Public's commission number; in this case, it is 1565986.

[d065] is the start tag of the NotaryCommissionExpiryDate element. This element contains the date and time at which the Notary Public's authorized commission expires.

[d066] defines the expiry date of the Notary Public's commission; in this case, it is April 29, 2009.

[d068] is the start tag of the NotaryUSJurisdiction element. This element identifies the political jurisdiction in the United States of America where the Notary Public is authorized to perform his/her official duties.

[d069] identifies the County where the Notary Public performs his/her official duties; in this case, it is Santa Clara.

[d070] identifies the USState where the Notary Public performs his/her official duties; in this case, it is an CA (for California).

[d071] identifies the Country where the Notary Public performs his/her official duties; in this case, it is the United States of America.

[d080] is the start tag of the NotarySignatures element. This element contains information the notarial signatures of the Notaries Public.

[d081] is a NotarySignature element with a NULL Cryptographic Signature. Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of ENML security.

[d088] is the closing tag of the WitnessedDocument element, signifying the end of this XML instance.

3.5 eNotarized document - Multiple Signers, Single Notary & Symmetric Key Signature

In this example of an eNotarized document, we show two document signers, signing a document with NULL Cryptographic Signatures and notarized by one Notary Public using a symmetric cryptographic key to encrypt the message digest of the Signature's Manifest, thus creating a Cryptographic Signature. Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of ENML security and symmetric encryption keys.

While all the elements of the eNotarized document are shown, for the sake of some brevity, much of the Document element's content is not shown below.

[e001] <enml:NotarizedDocument
[e002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[e003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[e004] xsi:schemaLocation=
[e005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[e006] Id="NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[e007] 
[e012] <enml:SignedDocuments>
[e013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222646484-
546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b">
[e014] <enml:Document>
[e015] PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
[e016] ZwdhbFhNTCBlTm90YXJpemF0aW9uIDEuMCBTcGVjaWZpY2F0aW9uCgogIDA5IERl
...
...
[e017] ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
[e018] </enml:Document>
[e019] <enml:DocumentMIMEType>application/xml</enml:DocumentMIMEType>
[e020] <enml:DocumentComments>A mortgage contract</enml:DocumentComments>
[e021] </enml:SignedDocument>
[e022] </enml:SignedDocuments>
[e023] 
[e028] <enml:DocumentSigners>
[e029] 
[e030] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[e031] <enml:SignerName>
[e032] <enml:PersonGivenName>John</enml:PersonGivenName>
[e033] <enml:PersonSurName>Doe</enml:PersonSurName>
[e034] </enml:SignerName>
[e035] <enml:SignerUSAddress>
[e036] <enml:City>Sunnyvale</enml:City>
[e037] <enml:County>Santa Clara</enml:County>
[e038] <enml:USState>CA</enml:USState>
[e039] <enml:Country>USA</enml:Country>
[e040] </enml:SignerUSAddress>
[e041] <enml:SignerIdentificationMethod>
[e042] Personally Known to Credible Witnesses
[e043] </enml:SignerIdentificationMethod>
[e044] <enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
[e045] </enml:DocumentSigner>
[e046]
[e047] 
[e048] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
[e049] <enml:SignerName>
[e050] <enml:PersonFirstName>Jane</enml:PersonFirstName>
[e051] <enml:PersonLastName>Doe</enml:PersonLastName>
[e052] </enml:SignerName>
[e053] <enml:SignerIdentificationMethod>
[e054] Produced Government-issued Identification Document
[e055] </enml:SignerIdentificationMethod>
[e056] <enml:SignerSignature>Signed by Jane Doe</enml:SignerSignature>
[e057] </enml:DocumentSigner>
[e058] </enml:DocumentSigners>
[e059] 
[e064] <enml:NotaryCertificates>
[e065] <enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
[e066] <enml:CertificateContent>
[e067] <enml:NotarizationType>Acknowledgment</enml:NotarizationType>
[e068] <enml:NotarizationDate>
[e069] 2007-01-27T15:23:46-08:00
[e070] </enml:NotarizationDate>
[e071] <enml:NotarizationUSLocation>
[e072] <enml:City>Cupertino</enml:City>
[e073] <enml:County>Santa Clara</enml:County>
[e074] <enml:USState>CA</enml:USState>
[e075] <enml:Country>USA</enml:Country>
[e076] </enml:NotarizationUSLocation>
[e077] <enml:StatutoryContent>
[e078] State of California
[e079] County of Santa Clara
[e080]
[e081] On January 27 2007, before me Arshad Noor, personally
[e082] appeared John Doe and Jane Doe, who proved to me on the
[e083] basis of satisfactory evidence to be the persons whose
[e084] names are subscribed to the within instrument and
[e085] acknowledged to me that they executed the same in their
[e086] authorized capacity, and that by their signatures on the
[e087] instrument the persons, or the entity upon behalf of
[e088] which the persons acted, executed the instrument.
[e089]
[e090] I certify under PENALTY OF PERJURY under the laws of the
[e091] State of California that the foregoing paragraph is true
[e092] and correct.
[e093]
[e094] WITNESS my hand and official seal.
[e095] </enml:StatutoryContent>
[e096] </enml:CertificateContent>
[e097]
[e098] 
[e099] <enml:NotaryPublic>
[e100] <enml:NotaryName>
[e101] <enml:PersonGivenName>Arshad</enml:PersonGivenName>
[e102] <enml:PersonSurName>Noor</enml:PersonSurName>
[e103] </enml:NotaryName>
[e104] <enml:NotaryCommissionNumber>
[e105] 1565986
[e106] </enml:NotaryCommissionNumber>
[e107] <enml:NotaryCommissionExpiryDate>
[e108] 2009-04-29T23:59:59-08:00
[e109] </enml:NotaryCommissionExpiryDate>
[e110] <enml:NotaryUSJurisdiction>
[e111] <enml:County>Santa Clara</enml:County>
[e112] <enml:USState>CA</enml:USState>
[e113] <enml:Country>USA</enml:Country>
[e114] </enml:NotaryUSJurisdiction>
[e115] </enml:NotaryPublic>
[e116] </enml:NotaryCertificate>
[e117] </enml:NotaryCertificates>
[e118] 
[e123] <enml:NotarySignatures>
[e124] <ds:Signature>
[e125] <ds:SignedInfo>
[e126] <ds:CanonicalizationMethod
[e127] Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
[e128] <ds:SignatureMethod
[e129] Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
[e130] <ds:Reference Type="http://www.w3.org/2000/09/xmldsig#Manifest" URI="#Manifest-US-CA-1565986-1222641281">
[e131] <ds:Transforms>
[e132] <ds:Transform
[e133] Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
[e134] </ds:Transforms>
[e135] <ds:DigestMethod
[e136] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[e137] <ds:DigestValue>
[e138] MtGcQfervxf/b3xvrPEstt0h1fg=
[e139] </ds:DigestValue>
[e140] </ds:Reference>
[e141] </ds:SignedInfo>
[e142] <ds:SignatureValue>
[e143] 09fbf143326bb09beefabe8d84094ee14c5eee8c
[e144] </ds:SignatureValue>
[e145] <ds:KeyInfo>
[e146] <ds:KeyName>10514-1-123</ds:KeyName>
[e147] <ds:RetrievalMethod
[e148] URI="http://skms.somecompany.com/symkeyServlet/getsymkey"/>
[e149] </ds:KeyInfo>
[e150]
[e151] <ds:Object>
[e152] <ds:Manifest Id="Manifest-US-CA-1565986-1222641281">
[e153]
[e154] <ds:Reference URI="#SignedDocument-US-CA-1565986-
1222646484-546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b">
[e155] <ds:DigestMethod
[e156] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[e157] <ds:DigestValue>
[e158] W4DupJioi0mM7aG+N1qiNLtqvsk=
[e159] </ds:DigestValue>
[e160] </ds:Reference>
[e161]
[e162] <ds:Reference URI="#DocumentSigner-US-CA-1565986-
1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[e163] <ds:DigestMethod
[e164] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[e165] <ds:DigestValue>
[e166] Yx5JkTS0ZxaM0uEpm/SxmSRSgAw=
[e167] </ds:DigestValue>
[e168] </ds:Reference>
[e169]
[e170] <ds:Reference URI="#DocumentSigner-US-CA-1565986-
1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
[e171] <ds:DigestMethod
[e172] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[e173] <ds:DigestValue>
[e174] M0uEpmYx5JkTS0Zxa/SxmSRSgAw=
[e175] </ds:DigestValue>
[e176] </ds:Reference>
[e177]
[e178] <ds:Reference URI="#NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
[e179] <ds:DigestMethod
[e180] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[e181] <ds:DigestValue>
[e182] +w49wI2IZOiUOVSx7L0fQp1nO30=
[e183] </ds:DigestValue>
[e184] </ds:Reference>
[e185] </ds:Manifest>
[e186] </ds:Object>
[e187]
[e188] </ds:Signature>
[e189] </enml:NotarySignatures>
[e190] 
[e195] </enml:NotarizedDocument>

[e001] is the start tag of the NotarizedDocument element, the root of this eNotarized document instance.

[e002] indicates that this is an instance – an occurrence - of a document that conforms to a specific XML Schema Definition (XSD).

[e003] identifies the namespace to which this XML instance document conforms.

[e004] - [e005] identifies the name and location of the XML Schema Definition (XSD) file that defines the structure of this XML instance document.

[e006] is an attribute called “ID” whose value is “NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4". The ID attribute allows this document to be uniquely identified within other XML documents (such as an ApostillizedDocument). The value of the ID attribute is created by the application generating this ENML, and is unique for this instance of a NotarizedDocument.

[e012] is the start tag of the SignedDocuments element, which indicates the documents that are being eNotarized. Note: While current laws only allow for a single document to be notarized by a single notarial certificate and notary signature per notarization, the ENML schema allows for eNotarizing multiple documents with a single notarial certificate and notary signature. However, applications using/implementing ENML are expected to contain only a single document within this element for the foreseeable future.

[e013] is the start tag of a SignedDocument element, which has an attribute called “ID” whose value is “SignedDocument-US-CA-1565986-1222646484-546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b“. This is the only document being eNotarized within this NotarizedDocument instance. The ID attribute allows this document to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[e015] - [e017] contains the Base64-encoded document that is being eNotarized. The Base64-encoding allows any type of document – text, graphics, multimedia, etc. - to be eNotarized and transported from machine to machine over networks, and rendered consistently.

[e019] indicates the Multipurpose Internet Mail Extension (MIME)-type of the document in the DocumentMIMEType element. This element identifies the type of document that is being eNotarized: a word-processing document created by OpenOffice Writer or Microsoft Word, a Portable Network Graphics (PNG) or Graphics Image File (GIF) file, etc. Receiving computers can use this element to determine which application to use to display the eNotarized document.

[e020] is the DocumentComments tag which permits document creators to place free-form comments about the document in this element.

[e028] is is the start tag of the DocumentSigners element. This element contains information about all document-signers of the eNotarized document, which does not include the Notary Public.

[e030] is the start tag of the first DocumentSigner element, which has an attribute called “ID” whose value is “DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7”. This is the first of two signers of this document. The ID attribute allows this signer to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[e031] is the start tag of the SignerName element. This element contains information about the document-signer's name.

[e032] indicates the DocumentSigner's given name (first name) in the PersonGivenName element.

[e033] indicates the DocumentSigner's surname (last name) in the PersonSurName element.

[e038] provides the SignerUSAddress's USState element as a two-character abbreviation.

[e041] is the start tag of the SignerIdentificationMethod element. This element contains information about how the document-signer identified himself/herself to the Notary Public. For privacy reasons, this element should not show any information considered sensitive, such as the Social Security Number, a Drivers License Number, a Passport or Identification Card Number, etc., but just indicate what type of identification was provided.

[e042] is free-form text that indicates that this signer was “Personally known to credible witnesses”. It is assumed that the Notary Public has performed his/her duties with diligence, as required by law, in verifying the identity of the DocumentSigner.

[e044] is the SignerSignature element. The value of this element, in this example, states “Signed by John Doe” indicating the use of a NULL Cryptographic Signature.

[e045] is the closing tag of the DocumentSigner element for the first signer.

[e048] is the start tag of the second DocumentSigner element, which has an attribute called “ID” whose value is “DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc”.

[e049] is the start tag of the SignerName element. This element contains information about the document-signer's name.

[e050] indicates the DocumentSigner's given name (first name) in the PersonGivenName element.

[e051] indicates the DocumentSigner's surname (last name) in the PersonSurName element.

[e053] is the start tag of the SignerIdentificationMethod element. This element contains information about how the document-signer identified himself/herself to the Notary Public. For privacy reasons, this element should not show any information considered sensitive, such as the Social Security Number, a Drivers License Number, a Passport or Identification Card Number, etc., but just indicate what type of identification was provided.

[e054] is free-form text that indicates that this signer “Produced Government-issued Identification Document”. It is assumed that the Notary Public has performed his/her duties with diligence, as required by law, in verifying the identity of the DocumentSigner.

[e056] is the SignerSignature element, which contains a NULL Cryptographic Signature and the value “Signed by Jane Doe”.

[e057] is the closing tag of the DocumentSigner element for the second signer.

[e064] is the start tag of the NotaryCertificates element. This element contains one or more notarial certificates as required by law for eNotarized documents.

[e065] is the start tag of the NotaryCertificate element. This element has an attribute called “ID” (with the value “NotaryCertificate-US-CA-1565986-1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f” in this example) that allows this notarial certificate to be uniquely identified within this instance, and to be referenced and covered by the Notary Public's signature as part of the eNotarization. The value of the ID attribute is specified by the application creating this ENML, and is unique within this instance of a NotarizedDocument.

[e066] is the start tag of the CertificateContent element. This element contains information about the eNotarization act.

[e067] is the NotarizationType element. This element identifies the type of eNotarization being performed; in this case, it is an Acknowledgment.

[e068] - [e070] is the NotarizationDate element. This element identifies the date on which the eNotarization was performed; in this case, it is January 27, 2007 at 3:23:46PM in the Pacific time-zone (-08:00 from UTC).

[e071] is the start tag of the NotarizationUSLocation element. This element identifies the political jurisdiction in the United States of America where the eNotarization was performed.

[e072] identifies the City where the eNotarization was performed; in this case, it is Cupertino.

[e073] identifies the County where the eNotarization was performed; in this case, it is Santa Clara.

[e074] identifies the USState where the eNotarization was performed; in this case, it is an CA (for California).

[e075] identifies the Country where the eNotarization was performed; in this case, it is the USA.

[e077] is the start tag of the StatutoryContent element. This element provides the statutory content that must be provided in a notarial certificate for an eNotarized document in the United States of America.

[e078] – [e094] identifies the statutory content for this NotarizedDocument; in this case, it is free-form text for an Acknowledgment as specified by the State of California.

[e099] is the start tag of the NotaryPublic element. This element provides details about the Notary Public who eNotarized this NotarizedDocument.

[e100] is the start tag of the NotaryName element. This element contains information about the Notary Public's name.

[e101] indicates the Notary Public's given name (first name) in the PersonGivenName element.

[e102] indicates the Notary Public's surname (last name) in the PersonSurName element.

[e104] is the start tag of the NotaryCommissionNumber element. This element identifies the identification number, if any, given to a Notary Public within a political jurisdiction.

[e105] identifies the Notary Public's commission number; in this case, it is 1565986.

[e107] is the start tag of the NotaryCommissionExpiryDate element. This element identifies the date and time at which the Notary Public's authorized commission expires.

[e108] identifies the expiry date of the Notary Public's commission; in this case, it is April 29, 2009.

[e110] is the start tag of the NotaryUSJurisdiction element. This element identifies the political jurisdiction in the United States of America where the Notary Public is authorized to perform his/her official duties.

[e111] identifies the County where the Notary Public performs his/her official duties; in this case, it is Santa Clara.

[e112] identifies the USState where the Notary Public performs his/her official duties; in this case, it is an CA (for California).

[e113] identifies the Country where the Notary Public performs his/her official duties; in this case, it is the USA.

[e123] is the start tag of the NotarySignatures element. This element contains information the notarial signatures of the Notaries Public.

[e124] is the start tag of the ds:Signature element. This element belongs to the [XMLSignature] namespace, and consequently has the ds: prefix in front of the element name. It contains information about the notarial signature of the Notary Public.

[e125] is the start tag of the ds:SignedInfo element. This element provides information about what is signed within this eNotarized document.

[e126] – [e127] describes the ds:CanonicalizationMethod element. To ensure that XML documents and their signatures are calculated consistently, software that complies with the [XMLSignature] standard “normalizes” the XML content based on the method specified in the Algorithm attribute of this element. In this example, the algorithm used to normalize the XML content is indicated by the "http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments" value.

[e128] – [e129] describes the ds:SignatureMethod element. Application generating and verifying signatures using the [XMLSignature] standard, need to know the method by which the XML document is signed. The Algorithm attribute of this element identifies this method. In this example, the algorithm used to sign the XML content is the Hashed Message Authentication Code (HMAC) using the SHA1 method, as indicated by the "http://www.w3.org/2000/09/xmldsig#hmac-sha1" value.

[e130] describes the ds:Reference element, which identifies the element(s) that are signed within this eNotarized document. In this example, the Reference element indicates that the object being signed is a ds:Manifest which can be located by the URI “#Manifest-US-CA-1565986-1222641281” within the same document.

[e131] identifies start of the ds:Transforms element. This element identifies what transformations were applied to the element(s) before signing this eNotarized document. This also implies that application software verifying this signature must apply the same transformations to the XML elements before verifying the signature.

[e132] – [e133] describes the ds:Transform element. In this instance, the algorithm used to transform the XML content is indicated by the "http://www.w3.org/2000/09/xmldsig#enveloped-signature" value.

[e135] – [e136] describes the ds:DigestMethod element. The Algorithm attribute of this element identifies how the message-digest of the content in the ds:Manifest was calculated. In this instance, the algorithm used to calculate the message-digest of the XML content is indicated by the "http://www.w3.org/2000/09/xmldsig#sha1" value.

[e138] provides the Base64 encoded message-digest value of the contents of the ds:Manifest element.

[e142] is the start tag of the ds:SignatureValue element. This element is the container for the electronic signature of the Notary Public on this instance of the eNotarized document.

[e143] provides the actual electronic signature of the Notary Public on this instance of the eNotarized document. It is a Base64-encoded value.

[e145] is the start tag of the ds:KeyInfo element. This element is the container for the cryptographic symmetric-key, or information about the cryptographic key, used by the Notary Public to sign this instance of the eNotarized document.

[e146] defines the ds:KeyName element. The value in this element is, typically, an identifier to a cryptographic key that may be accessed at some location. In this example, the identifier follows the format of a GlobalKeyID as defined in [ENML].

[e147] – [e148] defines the ds:RetrievalMethod element. The URI attribute in this element identifies a location where the cryptographic key referenced in ds:KeyName can be accessed. In this example, the URI “http://skms.somecompany.com/symkeyServlet/getsymkey” follows the format defined in [ENML].

[e150] is the start tag of the ds:Manifest element. This element carries information about the elements in the eNotarized document that are covered by the Notary's signature. The unique identifier of this element is shown in this example, in the ID attribute as “Manifest-US-CA-1565986-1222641281”.

[e154] describes the first ds:Reference element within this Manifest. The URI attribute of this element identifies the content in this instance of an eNotarized document that is covered by the Notary Public's signature. In this instance, the URI points to the SignedDocument element that has "SignedDocument-US-CA-1565986-1222646484-
546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b" in its ID attribute.

[e155] – [e156] describes the ds:DigestMethod element. The Algorithm attribute identifies the method used to calculate the message-digest of the XML content referenced in the above-mentioned ds:Reference. In this example, it is indicated by the "http://www.w3.org/2000/09/xmldsig#sha1" value.

[e158] provides the Base64 encoded message-digest value of the contents of the element(s) referenced by this ds:Reference URI.

[e160] describes the second ds:Reference element within this Manifest. The URI attribute of this element identifies the content in this instance of an eNotarized document that is covered by the Notary Public's signature. In this instance, the URI points to the DocumentSigner element that has "DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7" in its ID attribute.

[e162] – [e164] describes the ds:DigestMethod element. The Algorithm attribute identifies the method used to calculate the message-digest of the XML content referenced in the above-mentioned ds:Reference. In this example, it is indicated by the "http://www.w3.org/2000/09/xmldsig#sha1" value.

[e166] provides the Base64 encoded message-digest value of the contents of the element(s) referenced by this ds:Reference URI.

[e170] describes the third ds:Reference element within this Manifest. The URI attribute of this element identifies the content in this instance of an eNotarized document that is covered by the Notary Public's signature. In this instance, the URI points to a second DocumentSigner element that has "DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc" in its ID attribute.

[e171] – [e172] describes the ds:DigestMethod element. The Algorithm attribute identifies the method used to calculate the message-digest of the XML content referenced in the above-mentioned ds:Reference. In this example, it is indicated by the "http://www.w3.org/2000/09/xmldsig#sha1" value.

[e174] provides the Base64 encoded message-digest value of the contents of the element(s) referenced by this ds:Reference URI.

[e178] describes the last ds:Reference element within this Manifest. The URI attribute of this element identifies the content in this instance of an eNotarized document that is covered by the Notary Public's signature. In this instance, the URI points to the NotaryCertificate element that has "NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f" in its ID attribute.

[e179] – [e180] describes the ds:DigestMethod element. In this instance, the algorithm used to calculate the message-digest of the XML content referenced in the above-mentioned ds:Reference is indicated by the "http://www.w3.org/2000/09/xmldsig#sha1" value.

[e182] provides the Base64 encoded message-digest value of the contents of the element(s) referenced by this ds:Reference URI.

[e184] is the closing tag of the ds:Reference element. This is the last Reference included in this Manifest.

[e195] is the closing tag of the NotarizedDocument element, signifying the end of this XML instance.

3.6 eNotarized document - Multiple Signers, Multiple Notaries & Symmetric Key Signatures

In this example of an eNotarized document, we show three document signers, two signing a document with NULL Cryptographic Signatures and the third signing with a symmetric key to create a Cryptographic Signature, separately; and two Notaries Public using different symmetric cryptographic keys to encrypt the message digest of the Signature's Manifest separately, thus creating two distinct Cryptographic Signatures. Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of ENML security and symmetric encryption keys.

For the sake of brevity, many elements content are not repeated here, and only relevant content distinct from the previous example is shown below.

[f001] <enml:NotarizedDocument
[f002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[f003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[f004] xsi:schemaLocation=
[f005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[f006] Id="NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[f007] 
[f012] <enml:SignedDocuments>
[f013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222646484-
546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b">
...
...
[e040] </enml:SignedDocument>
[e041] </enml:SignedDocuments>
[f042] 
[f047] <enml:DocumentSigners>
[f048] 
[f049] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[f050] <enml:PersonFirstName>John</enml:PersonFirstName>
[f051] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[f060] </enml:DocumentSigner>
[f061]
[f062] 
[f063] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643179-c44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
[f064] <enml:SignerName>
[f065] <enml:PersonFirstName>Jane</enml:PersonFirstName>
[f066] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[f080] </enml:DocumentSigner>
[f081]
[f082] 
[f083] <enml:DocumentSigner Id="DocumentSigner-US-NJ-1234567-1223663478-
849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6">
[f084] <enml:SignerName>
[f085] <enml:PersonFirstName>Jeff</enml:PersonFirstName>
[f086] <enml:PersonLastName>Doe</enml:PersonLastName>
[f087] </enml:SignerName>
[f088] <enml:SignerIdentificationMethod>
[f089] Personally Known to Credible Witnesses
[f090] </enml:SignerIdentificationMethod>
[f091] <enml:SignerSignature>
[f092] <comment>
[f093] Signed by Jeff Doe on February 12, 2008.
[f094] </comment>
[f095] <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
[f096] <ds:SignatureValue>
[f097] 3fbe2548f11bdf0177233a9f6d60bae060088452
[f098] </ds:SignatureValue>
[f099] <ds:KeyInfo>
[f100] <ds:KeyName>
[f101] JeffDoe-NJ123457-1223663478-01
[f102] </ds:KeyName>
[f103] </ds:KeyInfo>
[f104] </enml:SignerSignature>
[f105] </enml:DocumentSigner>
[f106] </enml:DocumentSigners>
[f107] 
[f112] <enml:NotaryCertificates>
[f113] <enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
...
...
[f130] </enml:NotaryCertificate>
[f131] 
[f136] <enml:NotaryCertificates>
[f137] <enml:NotaryCertificate Id="NotaryCertificate-US-NJ-4665986-
1223683212-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
[f138] <enml:CertificateContent>
[f129] <enml:NotarizationType>Acknowledgment</enml:NotarizationType>
[f140] <enml:NotarizationDate>2008-02-12</enml:NotarizationDate>
[f141] <enml:NotarizationUSLocation>
[f142] <enml:City>Basking Ridge</enml:City>
[f143] <enml:County>Middlesex</enml:County>
[f144] <enml:USState>NJ</enml:USState>
[f145] <enml:Country>USA</enml:Country>
[f146] </enml:NotarizationUSLocation>
[f147] <enml:StatutoryContent>
[f148] State of New Jersey
[f149] County of Middlesex
[f150]
[f151] On February 12 2008, before me Abraham Lincoln, Notary
[f152] Public in and for said county, personally appeared Jeff
[f153] Doe, who has satisfactorily identified himself as the
[f154] signer or witness to the above-referenced document.
[f155]
[f156] My Commission Expires on April 29, 2009.
[f157] </enml:StatutoryContent>
[f158] </enml:CertificateContent>
[f159]
[f160] 
[f161] <enml:NotaryPublic>
[f162] <enml:NotaryName>
[f163] <enml:PersonGivenName>Abraham</enml:PersonGivenName>
[f164] <enml:PersonSurName>Lincoln</enml:PersonSurName>
[f165] </enml:NotaryName>
[f166] <enml:NotaryCommissionNumber>
[f167] NJ4665986
[f168] </enml:NotaryCommissionNumber>
[f169] <enml:NotaryCommissionExpiryDate>
[f170] 2009-04-29T23:59:59-08:00
[f171] </enml:NotaryCommissionExpiryDate>
[f172] <enml:NotaryUSJurisdiction>
[f173] <enml:County>Middlesex</enml:County>
[f174] <enml:USState>NJ</enml:USState>
[f175] <enml:Country>USA</enml:Country>
[f176] </enml:NotaryUSJurisdiction>
[f177] </enml:NotaryPublic>
[f178] </enml:NotaryCertificate>
[f179] </enml:NotaryCertificates>
[f180] 
[f185] <enml:NotarySignatures>
[f186] <ds:Signature Id="Signature-US-CA-1565986-1222641290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
[f187] <ds:SignedInfo>
[f188] <ds:CanonicalizationMethod
[f189] Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
[f190] <ds:SignatureMethod
[f191] Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
[f192] <ds:Reference Type="http://www.w3.org/2000/09/xmldsig#Manifest" URI="#Manifest-US-CA-1565986-1222641281">
[f193] <ds:Transforms>
[f194] <ds:Transform
[f195] Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
[f196] </ds:Transforms>
[f197] <ds:DigestMethod
[f198] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f199] <ds:DigestValue>
[f200] MtGcQfervxf/b3xvrPEstt0h1fg=
[f201] </ds:DigestValue>
[f202] </ds:Reference>
[f203] </ds:SignedInfo>
[f204] <ds:SignatureValue>
[f205] 09fbf143326bb09beefabe8d84094ee14c5eee8c
[f206] </ds:SignatureValue>
[f207] <ds:KeyInfo>
[f208] <ds:KeyName>10514-1-123</ds:KeyName>
[f209] <ds:RetrievalMethod
[f210] URI="http://skms.somecompany.com/symkeyServlet/getsymkey"/>
[f211] </ds:KeyInfo>
[f212]
[f213] <ds:Object>
[f214] <ds:Manifest Id="Manifest-US-CA-1565986-1222641281">
[f215]
[f216] <ds:Reference URI="#SignedDocument-US-CA-1565986-
1222646484-546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b">
[f217] <ds:DigestMethod
[f218] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f219] <ds:DigestValue>
[f220] W4DupJioi0mM7aG+N1qiNLtqvsk=
[f221] </ds:DigestValue>
[f222] </ds:Reference>
[f223]
[f224] <ds:Reference URI="#DocumentSigner-US-CA-1565986-
1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[f225] <ds:DigestMethod
[f226] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f227] <ds:DigestValue>
[f228] Yx5JkTS0ZxaM0uEpm/SxmSRSgAw=
[f229] </ds:DigestValue>
[f230] </ds:Reference>
[f231]
[f232] <ds:Reference URI="#DocumentSigner-US-CA-1565986-
1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
[f233] <ds:DigestMethod
[f234] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f235] <ds:DigestValue>
[f236] M0uEpmYx5JkTS0Zxa/SxmSRSgAw=
[f237] </ds:DigestValue>
[f238] </ds:Reference>
[f239]
[f240] <ds:Reference URI="#NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
[f241] <ds:DigestMethod
[f242] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f243] <ds:DigestValue>
[f244] +w49wI2IZOiUOVSx7L0fQp1nO30=
[f245] </ds:DigestValue>
[f246] </ds:Reference>
[f247] </ds:Manifest>
[f248] </ds:Object>
[f249]
[f250] </ds:Signature>
[f251]
[f252] 
[f257] <ds:Signature Id="Signature-US-NJ-4665986-1223683793-
897d00adf82aaa5aee7addd9974407f62779807db73af12dcf6b3adf0b87e603">
[f258] <ds:SignedInfo>
[f259] <ds:CanonicalizationMethod
[f260] Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
[f261] <ds:SignatureMethod
[f262] Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
[f263] <ds:Reference Type="http://www.w3.org/2000/09/xmldsig#Manifest" URI="#Manifest-US-NJ-4665986-1223683785">
[f264] <ds:Transforms>
[f265] <ds:Transform
[f266] Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
[f267] </ds:Transforms>
[f268] <ds:DigestMethod
[f269] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f270] <ds:DigestValue>
[f271] xtGxfc78fervgfvb3xvrzAEstt0h1fg=
[f272] </ds:DigestValue>
[f273] </ds:Reference>
[f274] </ds:SignedInfo>
[f275] <ds:SignatureValue>
[f276] c6fbf14dd26bb09beefabe8d84235ee14c5abc8c
[f277] </ds:SignatureValue>
[f278] <ds:KeyInfo>
[f279] <ds:KeyName>10514-2-651</ds:KeyName>
[f280] <ds:RetrievalMethod
[f281] URI="http://skms.somecompany.com/symkeyServlet/getsymkey"/>
[f282] </ds:KeyInfo>
[f283]
[f284] <ds:Object>
[f285] <ds:Manifest Id="Manifest-US-NJ-4665986-1223683785">
[f286]
[f287] <ds:Reference URI="#SignedDocument-US-CA-1565986-
1222646484-546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b">
[f288] <ds:DigestMethod
[f289] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f290] <ds:DigestValue>
[f291] W4DupJioi0mM7aG+N1qiNLtqvsk=
[f292] </ds:DigestValue>
[f293] </ds:Reference>
[f294]
[f295] <ds:Reference URI="#DocumentSigner-US-NJ-1234567-
1223663478-849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6">
[f296] <ds:DigestMethod
[f297] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f298] <ds:DigestValue>
[f299] M0uEpmYx5JkTS0Zxa/SxmSRSgAw=
[f300] </ds:DigestValue>
[f301] </ds:Reference>
[f302]
[f303] <ds:Reference URI="#NotaryCertificate-US-NJ-4665986-
1223683212-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
[f304] <ds:DigestMethod
[f305] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[f306] <ds:DigestValue>
[f307] adf41bce489970d774304c36037351f988b9bbb1
[f308] </ds:DigestValue>
[f309] </ds:Reference>
[f310] </ds:Manifest>
[f311] </ds:Object>
[f312]
[f313] </ds:Signature>
[f314] </enml:NotarySignatures>
[f315] 
[f320] </enml:NotarizedDocument>

[f001] – [f006] is the usual preamble to an XML instance document as discussed in the previous examples.

[f012] - [f041] is the SignedDocuments element, which indicates the documents that are being eNotarized. [f012] provides the identifier of the single SignedDocument in this section: “SignedDocument-US-CA-1565986-1222646484-546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b”. This identifier is referenced in the two Notary signatures section of the eNotarized document.

[f048] - [f060] represents information about the first DocumentSigner, in this case “John Doe” and carrying the following value in its ID attribute: “ DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7”.

[f062] – [f080] represents information about the second DocumentSigner, in this case “Jane Doe” and carrying the ID attribute value: “ DocumentSigner-US-CA-1565986-1222643179-c44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc”.

[f082] – [f105] represents information about the third DocumentSigner, in this case “Jeff Doe”; this element has the following value in its ID attribute: “DocumentSigner-US-NJ-1234567-1223663478-
849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6”. A notable fact about the third DocumentSigner element is that this signer does not use the NULL Cryptographic Signature for signing the document, but uses a Cryptographic Signature created by a symmetric key. While the SignerSignature element can contain any content, this example shows the use of some elements from the [XMLSignature] schema.

[f113] – [f130] contains information about the first NotaryCertificate element, with the ID attribute value of: NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f. This element refers tot he Notary Public from the state of California in this example.

[f136] – [f178] contains information about the second NotaryCertificate element, with the ID attribute value of: NotaryCertificate-US-NJ-4665986-1223683212-
c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4. This element refers to the notary public from the state of New Jersey where the second notarization of this document takes place.

[f185] is the start tag of the NotarySignatures element. This element contains information the notarial signatures of the two Notaries Public.

[f186] – [f250] contains information about the first Signature element. This element, identified by the ID attribute value of “ Signature-US-CA-1565986-1222641290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 “, would have been created by the notary public in California. The Manifest it refers to on [f261] is indicated by the URI value “Manifest-US-NJ-4665986-1223683785”. This manifest is within the Object element between lines [f211] and [f246]. As can be noticed, the manifest refers to the single SignedDocument, the two signers from California and the notarial certificate created in California.

[f257] – [f313] contains information about the second Signature element. This element, identified by the ID attribute value of “ Signature-US-NJ-4665986-1223683793-
897d00adf82aaa5aee7addd9974407f62779807db73af12dcf6b3adf0b87e603 “, would have been created by the notary public in New Jersey. The Manifest it refers to on [f190] (indicating the elements of this document covered by the signature of the first notary public) is indicated by the URI value “Manifest-US-CA-1565986-1222641281”. This manifest is within the Object element between lines [f282] and [f309]. As can be noticed, the manifest refers to the same SignedDocument as for the first notary. However, only one DocumentSigner's signature is referred to in this manifest, and secondly, the NotaryCertificate it refers to, is the one created in New Jersey. This implies that this Signature element covers only the second eNotarization act and does so without altering any of the content related to the first eNotarization performed by the California notary.

3.7 eWitnessed document - Single Signer, Single Notary & Symmetric Key Signature

The ENML is capable of “witnessing” the signing of documents, in addition to notarizing them. An eWitnessed document is identical to an eNotarized document in all respects, save one: it does not contain a notarial certificate. The following example shows an eWitnessed document.

[g001] <enml:WitnessedDocument
[g002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[g003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[g004] xsi:schemaLocation=
[g005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[g006] Id="WitnessedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[g007] 
[g012] <enml:SignedDocuments>
[g013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-
1222646532-849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6">
...
...
[g040] </enml:SignedDocument>
[g041] </enml:SignedDocuments>
[g042] 
[g047] <enml:DocumentSigners>
[g048] 
[g049] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[g050] <enml:PersonFirstName>John</enml:PersonFirstName>
[g051] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[g060] </enml:DocumentSigner>
[g061] </enml:DocumentSigners>
[g062] 
[g067] <enml:NotariesPublic>
[g068] <enml:NotaryPublic Id=”NotaryPublic-US-CA-1565986-1222643107-b269051b713ef56b17b3439ecbdb96c266e8d1c4ae5449deccb3e0bb9b007ddd”>
[g069] <enml:NotaryName>
[g070] <enml:PersonGivenName>Arshad</enml:PersonGivenName>
[g071] <enml:PersonSurName>Noor</enml:PersonSurName>
[g072] </enml:NotaryName>
[g073] <enml:NotaryCommissionNumber>
[g074] 1565986
[g075] </enml:NotaryCommissionNumber>
[g076] <enml:NotaryCommissionExpiryDate>
[g077] 2009-04-29T23:59:59-08:00
[g078] </enml:NotaryCommissionExpiryDate>
[g079] <enml:NotaryUSJurisdiction>
[g080] <enml:County>Santa Clara</enml:County>
[g081] <enml:USState>CA</enml:USState>
[g082] <enml:Country>United States of America</enml:Country>
[g083] </enml:NotaryUSJurisdiction>
[g084] </enml:NotaryPublic>
[g085] </enml:NotariesPublic>
[g086] 
[g091] <enml:NotarySignatures>
[g092] <ds:Signature Id="Signature-US-CA-1565986-1222645055-
5d2960331a078f80a8504d4c6ae02e73e193ff0a4cd962f1c2e0bf4f9223bf98">
[g093] <ds:SignedInfo>
[g094] <ds:CanonicalizationMethod
[g095] Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
[g096] <ds:SignatureMethod
[g097] Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
[g098]
[g099] <ds:Reference URI="#SignedDocument-US-CA-1565986-
1222646532-849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6">
[g100] <ds:DigestMethod
[g101] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[g102] <ds:DigestValue>
[g103] 94973de9331f7446d15601328d5b990bf3048448
[g104] </ds:DigestValue>
[g105] </ds:Reference>
[g106]
[g107] <ds:Reference URI="#DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[g108] <ds:DigestMethod
[g109] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[g110] <ds:DigestValue>
[g111] 1c7a6c37cd201fb109ca58ff1703a63e29a0025a
[g112] </ds:DigestValue>
[g113] </ds:Reference>
[g114]
[g115] <ds:Reference URI="#NotaryPublic-US-CA-1565986-1222643107-b269051b713ef56b17b3439ecbdb96c266e8d1c4ae5449deccb3e0bb9b007ddd">
[g116] <ds:DigestMethod
[g117] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[g118] <ds:DigestValue>
[g119] 685ded60801600b0dd38d2e57ef3cd98eeb58de5
[g120] </ds:DigestValue>
[g121] </ds:Reference>
[g122] </ds:SignedInfo>
[g123]
[g124] <ds:SignatureValue>
[g125] 3fbe2548f11bdf0177233a9f6d60bae060088452
[g126] </ds:SignatureValue>
[g127]
[g128] <ds:KeyInfo>
[g129] <ds:KeyName>Key-US-CA-1565986-1222646532-01</ds:KeyName>
[g130] <ds:RetrievalMethod URI="http://krs.someserviceprovider.com"/>
[g131] </ds:KeyInfo>
[g132] </ds:Signature>
[g133] </enml:NotarySignatures>
[g134] 
[g139] </enml:WitnessedDocument>

[g001] – [g006] is the usual preamble to an XML instance document as discussed in the previous examples.

[g012] - [g041] is the SignedDocuments element, which indicates the documents that are being eWitnessed. [g012] provides the identifier of the single SignedDocument in this section: “SignedDocument-US-CA-1565986-
1222646532-849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6”. This identifier is referenced in the Notary signature section of the eWitnessed document.

[g049] - [g060] represents information about the first DocumentSigner, in this case “John Doe” and carrying the following value in its ID attribute: “ DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7”.

[g068] - [g084] represents information about the Notary Public that witnessed the signing of this document.

[g092] is the start of the Signature element. This element and all its sub-elements conform to the [XMLSignature] schema. The ID attribute in this example carries the value “ Signature-US-CA-1565986-1222645055-5d2960331a078f80a8504d4c6ae02e73e193ff0a4cd962f1c2e0bf4f9223bf98”.

[g093] is the start tag of the ds:SignedInfo element. This element provides information about what is signed within this eWitnessed document.

[g094] – [g095] describes the ds:CanonicalizationMethod element. To ensure that XML documents and their signatures are calculated consistently, software that complies with the [XMLSignature] standard “normalizes” the XML content based on the method specified in the Algorithm attribute of this element. In this example, the algorithm used to normalize the XML content is indicated by the "http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments" value.

[g096] - [g097] describes the ds:SignatureMethod element. Application generating and verifying signatures using the [XMLSignature] standard, need to know the method by which the XML document is signed. The Algorithm attribute of this element identifies this method. In this example, the algorithm used to sign the XML content is the Hashed Message Authentication Code (HMAC) using the SHA1 method, as indicated by the "http://www.w3.org/2000/09/xmldsig#hmac-sha1" value.

[g099] – [g105] describes the first ds:Reference element, which identifies the document being signed as identified by the ID attribute: “ SignedDocument-US-CA-1565986-1222646532-
849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6”.

[g107] – [g113] describes the second ds:Reference element, which identifies the signer of the document as identified by the ID attribute: “DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7”.

[g115] – [g121] describes the third and last ds:Reference element, which identifies the Notary Public that witnessed the signing of the document, as identified by the ID attribute: “NotaryPublic-US-CA-1565986-1222643107-b269051b713ef56b17b3439ecbdb96c266e8d1c4ae5449deccb3e0bb9b007ddd”.

[g124] – [g126] describes the ds:SignatureValue element. This element is the container for the electronic signature of the Notary Public on this instance of the eWitnessed document.

[g128] is the start tag of the ds:KeyInfo element. This element is the container for the cryptographic symmetric-key, or information about the cryptographic key, used by the Notary Public to sign this instance of the eNotarized document.

[g129] defines the ds:KeyName element. The value in this element is, typically, an identifier to a cryptographic key that may be accessed at some location.

[g130] defines the ds:RetrievalMethod element. The URI attribute in this element identifies a location where the cryptographic key referenced in ds:KeyName can be accessed.

3.8 eNotarized document - Single Signer, Single Notary & Digital Signature

The following example shows an eNotarized document, with a true digital signature generated by a Private Key corresponding to the digital certificate of a Notary Public. The document's signer is assumed to have signed the document with a NULL Cryptographic Signature. It is possible for the document signer to have signed with a cryptographic key too, but this example assumes a NULL Cryptographic Signature for the document's signer and a digital signature for the Notary Public.

Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of ENML security and asymmetric cryptographic keys and X.509-compliant digital certificates.

[h001] <enml:NotarizedDocument
[h002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[h003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[h004] xsi:schemaLocation=
[h005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[h006] Id="NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[h007] 
[h012] <enml:SignedDocuments>
[h013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[h040] </enml:SignedDocument>
[h041] </enml:SignedDocuments>
[h042] 
[h047] <enml:DocumentSigners>
[h048] 
[h049] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[h050] <enml:PersonFirstName>John</enml:PersonFirstName>
[h051] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[h060] </enml:DocumentSigner>
[h061] </enml:DocumentSigners>
[h062] 
[h067] <enml:NotaryCertificates>
[h068] <enml:NotaryCertificate Id="NotaryCertificate-US-NJ-4665986-
1223683212-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[h090] </enml:NotaryCertificate>
[h091] </enml:NotaryCertificates>
[h092] 
[h097] <enml:NotarySignatures>
[h098] <ds:Signature Id="Signature-US-CA-1565986-1222649290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
[h099] <ds:SignedInfo>
[h100] <ds:CanonicalizationMethod
[h101] Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
[h102] <ds:SignatureMethod
[h103] Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
[h104]
[h105] 
[h106] <ds:Reference URI="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
[h107] <ds:Transforms>
[h108] <ds:Transform
[h109] Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
[h110] </ds:Transforms>
[h111] <ds:DigestMethod
[h112] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[h113] <ds:DigestValue>3b3Bd7TGR/niVS+d3WbnLReFK+g=</ds:DigestValue>
[h114] </ds:Reference>
[h115]
[h116] 
[h117] <ds:Reference URI="#DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[h118] <ds:Transforms>
[h119] <ds:Transform
[h120] Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
[h121] </ds:Transforms>
[h122] <ds:DigestMethod
[h123] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[h124] <ds:DigestValue>
[h125] 275ded60801633b0dd38d2e57ef3cd98eeb58de5
[h126] </ds:DigestValue>
[h127] </ds:Reference>
[h128]
[h129] 
[h130] <ds:Reference URI="#NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
[h131] <ds:Transforms>
[h132] <ds:Transform
[h133] Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
[h134] </ds:Transforms>
[h135] <ds:DigestMethod
[h136] Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[h137] <ds:DigestValue>
[h138] 275ded60801633b0dd38d2e57ef3cd98eeb58de5
[h139] </ds:DigestValue>
[h140] </ds:Reference>
[h141] </ds:SignedInfo>
[h142]
[h143] 
[h144] <ds:SignatureValue>
[h145] RVLpQofvWPK2mkmmL1mQW5cxqgmciNUa6MuAKA71qq/
[h146] NkhIu9ilN6TnAN7EwxNTkFpc5CBFbje4M7sbcdzzF1A==
[h147] </ds:SignatureValue>
[h148] <ds:KeyInfo>
[h149] <ds:X509Data>
[h150]
[h151] 
[h152] <ds:X509Certificate>
MIIDfDCCAmSgAwIBAgIIAe/AvliGc3AwDQYJKoZIhvcNAQELBQAwZzEmMCQGA1UEAxMdU3Ryb25n
S2V5IERFTU8gU3Vib3JkaW5hdGUgQ0ExJDAiBgNVBAsTG0ZvciBTdHJvbmdLZXkgREVNTyBVc2Ug
T25seTEXMBUGA1UEChMOU3Ryb25nQXV0aCBJbmMwHhcNMDYwNzI1MTcxMDMwWhcNMDcwNzI1MTcy
MDMwWjBtMREwDwYKCZImiZPyLGQBARMBMjEZMBcGA1UEAxMQUE9TIFJlZ2lzdGVyIDIyMjEkMCIG
A1UECxMbRm9yIFN0cm9uZ0tleSBERU1PIFVzZSBPbmx5MRcwFQYDVQQKEw5TdHJvbmdBdXRoIElu
YzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAyAmxMZhYA8wHJ4UE4b61s51JVWe4Fygj4MCf
U7LA3JhpUS4TlX0XFWqrcmltLOiVG7YBFarJFluBFJW2X6q8FuvUprv4V9nJrgiwAPtkiRyIx96n
qKXIxkUlQ4idlEg1AZI9dEdf4Y5cqBBCygPYnBoTudglM7R47AjR4nr4ks8CAwEAAaOBqTCBpjAO
BgNVHQ8BAf8EBAMCBLAwHQYDVR0OBBYEFOIOrWrZo0LdBRLVncRAwLBqVZpCMB8GA1UdIwQYMBaA
FPTYwEHoJG4iFVHRnt2EWxGluAQVMBgGA1UdIAQRMA8wDQYLKwYEAdISg30BBAEwOgYDVR0fBDMw
MTAvoC2gK4YpaHR0cDovL2RlbW8uc3Ryb25na2V5Lm9yZy9kZW1vLXN1Yi1jYS5jcmwwDQYJKoZI
hvcNAQELBQADggEBACK05PtvZD4WPglOe+EHUiApzFyCdRzf0pFZtxRwG9lR1PZUWUjmwTNfGFsL
S6kyoHgUfVa5fpT1EU1mXUB/Lmo3hFGyprZjfmD7DwuBcYgmZHv7yHrmGOMIOXjFTACvHpM0vOce
hVx2e4VE0yhBLu/ldH9awGGDp6Bk2XzxqQcs8y6ZzOXZAnPgKQZdjbFKERSsy/d1D8pk5baBk4bd
Zh568OcaUrbm9ZReRVTVaY5qiQpkOU+tDrBSj/HIL6GAqegYllkz6KYCy6RVOy6iVVSjHocDqdJr
EVOR+ds6xn8mmojdlERrILmuxiLpibPp609SfnDIxNlzLwe5g7ep3lc=
[h153] </ds:X509Certificate>
[h154] </ds:X509Data>
[h155] </ds:KeyInfo>
[h156] </ds:Signature>
[h157] </enml:NotarySignatures>
[h158] 
[h163] </enml:NotarizedDocument>

[h001] – [h101] contains XML elements that have already been described in previous examples.

[h102] - [h103] has the first real difference; the SignatureMethod element in this example uses an algorithm not previously presented in these examples. Specifically, it uses the asymmetric-key based RSA cryptographic algorithm with the SHA-1 message digest algorithm for generating the digital signature, as denoted by the URL: http://www.w3.org/2000/09/xmldsig#rsa-sha1.

[h105] - [h114] identifies the first Reference element that is covered under the Notary's signature in this document. In this example, the Reference points to the SignedDocument instance denoted by the identifier: SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4.

[h116] - [h127] identifies the second Reference element covered by the Notary's signature in this document. In this example, the Reference points to the DocumentSigner instance denoted by the identifier: DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7.

[h129] - [h140] identifies the final Reference element covered by the Notary's signature. In this example, the Reference points to the NotaryCertificate denoted by the identifier: NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f.

[h141] signals the end of the SignedInfo element which identifies the information signed in this document.

[h143] - [h147] defines the actual SignatureValue of the digital signature in this document.

[h148] is the start of the KeyInfo element which provides information about the cryptographic key related to the cryptographic signature in this document.

[h149] is the start of the International Standards Organization's (ISO) X.509-related data about the digital certificate related to the cryptographic signature in this document.

[h150] - [h151] is a blank line and a comment for better readability of the XML data.

[h152] – [h153] contains the X.509 Base64-encoded digital certificate which must be used to verify the digital signature of this document.

[h154] – [h163] contain the end-tags of the element-hierarchy in this document, which signifies the end of this XML eNotarized document.

3.9 eNotarized document - Multiple Signers, Multiple Notaries & Digital Signatures

The following example differs from the previous one in that is show multiple signers for a single document, and multiple Notaries Public signing the document with digital signatures generated by Private Keys corresponding to their digital certificates.

[i001] <enml:NotarizedDocument
[i002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[i003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[i004] xsi:schemaLocation=
[i005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[i006] Id="NotarizedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[i007] 
[i012] <enml:SignedDocuments>
[i013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[i040] </enml:SignedDocument>
[i041] </enml:SignedDocuments>
[i042] 
[i047] <enml:DocumentSigners>
[i048] 
[i049] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[i050] <enml:PersonFirstName>John</enml:PersonFirstName>
[i051] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[i060] </enml:DocumentSigner>
[i061]
[i062] 
[i063] <enml:DocumentSigner Id="DocumentSigner-US-NJ-1234567-1223663478-
849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6">
[i064] <enml:PersonFirstName>Jeff</enml:PersonFirstName>
[i065] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[i066] </enml:DocumentSigner>
[1067] </enml:DocumentSigners>
[i068] 
[i073] <enml:NotaryCertificates>
[i074]
[i075] 
[i076] <enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
...
...
[i090] </enml:NotaryCertificate>
[i091]
[i092] 
[i093] <enml:NotaryCertificate Id="NotaryCertificate-US-NJ-4665986-
1223683212-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[i094] </enml:NotaryCertificate>
[i095] </enml:NotaryCertificates>
[i096] 
[i101] <enml:NotarySignatures>
[i102]
[i103] 
[i104] <ds:Signature Id="Signature-US-CA-1565986-1222649290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
...
...
[i148] <ds:KeyInfo>
[i149] <ds:X509Data>
[i150] 
[i151] <ds:X509Certificate>
MIIDfDCCAmSgAwIBAgIIAe/AvliGc3AwDQYJKoZIhvcNAQELBQAwZzEmMCQGA1UEAxMdU3Ryb25n
S2V5IERFTU8gU3Vib3JkaW5hdGUgQ0ExJDAiBgNVBAsTG0ZvciBTdHJvbmdLZXkgREVNTyBVc2Ug
T25seTEXMBUGA1UEChMOU3Ryb25nQXV0aCBJbmMwHhcNMDYwNzI1MTcxMDMwWhcNMDcwNzI1MTcy
MDMwWjBtMREwDwYKCZImiZPyLGQBARMBMjEZMBcGA1UEAxMQUE9TIFJlZ2lzdGVyIDIyMjEkMCIG
A1UECxMbRm9yIFN0cm9uZ0tleSBERU1PIFVzZSBPbmx5MRcwFQYDVQQKEw5TdHJvbmdBdXRoIElu
YzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAyAmxMZhYA8wHJ4UE4b61s51JVWe4Fygj4MCf
U7LA3JhpUS4TlX0XFWqrcmltLOiVG7YBFarJFluBFJW2X6q8FuvUprv4V9nJrgiwAPtkiRyIx96n
qKXIxkUlQ4idlEg1AZI9dEdf4Y5cqBBCygPYnBoTudglM7R47AjR4nr4ks8CAwEAAaOBqTCBpjAO
BgNVHQ8BAf8EBAMCBLAwHQYDVR0OBBYEFOIOrWrZo0LdBRLVncRAwLBqVZpCMB8GA1UdIwQYMBaA
FPTYwEHoJG4iFVHRnt2EWxGluAQVMBgGA1UdIAQRMA8wDQYLKwYEAdISg30BBAEwOgYDVR0fBDMw
MTAvoC2gK4YpaHR0cDovL2RlbW8uc3Ryb25na2V5Lm9yZy9kZW1vLXN1Yi1jYS5jcmwwDQYJKoZI
hvcNAQELBQADggEBACK05PtvZD4WPglOe+EHUiApzFyCdRzf0pFZtxRwG9lR1PZUWUjmwTNfGFsL
S6kyoHgUfVa5fpT1EU1mXUB/Lmo3hFGyprZjfmD7DwuBcYgmZHv7yHrmGOMIOXjFTACvHpM0vOce
hVx2e4VE0yhBLu/ldH9awGGDp6Bk2XzxqQcs8y6ZzOXZAnPgKQZdjbFKERSsy/d1D8pk5baBk4bd
Zh568OcaUrbm9ZReRVTVaY5qiQpkOU+tDrBSj/HIL6GAqegYllkz6KYCy6RVOy6iVVSjHocDqdJr
EVOR+ds6xn8mmojdlERrILmuxiLpibPp609SfnDIxNlzLwe5g7ep3lc=
[i152] </ds:X509Certificate>
[i153] </ds:X509Data>
[i154] </ds:KeyInfo>
[i155] </ds:Signature>
[i156]
[i157] 
[i158] <ds:Signature Id="Signature-US-CA-1565986-1222649290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
...
...
[i184] <ds:KeyInfo>
[i185] <ds:X509Data>
[i186] 
[i187] <ds:X509Certificate>
MIIDtTCCAp2gAwIBAgIRANAeQJAAAEZSAAAAAQAAAAQwDQYJKoZIhvcNAQEFBQAw gYkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJEQzETMBEGA1UEBxMKV2FzaGluZ3Rv bjEXMBUGA1UEChMOQUJBLkVDT00sIElOQy4xGTAXBgNVBAMTEEFCQS5FQ09NIFJv b3QgQ0ExJDAiBgkqhkiG9w0BCQEWFWFkbWluQGRpZ3NpZ3RydXN0LmNvbTAeFw05 OTA3MTIxNzMzNTNaFw0wOTA3MDkxNzMzNTNaMIGJMQswCQYDVQQGEwJVUzELMAkG A1UECBMCREMxEzARBgNVBAcTCldhc2hpbmd0b24xFzAVBgNVBAoTDkFCQS5FQ09N LCBJTkMuMRkwFwYDVQQDExBBQkEuRUNPTSBSb290IENBMSQwIgYJKoZIhvcNAQkB FhVhZG1pbkBkaWdzaWd0cnVzdC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw ggEKAoIBAQCx0xHgeVVDBwhMywVCAOINg0Y95JO6tgbTDVm9PsHOQ2cBiiGo77zM 0KLMsFWWU4RmBQDaREmA2FQKpSWGlO1jVv9wbKOhGdJ4vmgqRF4vz8wYXke8OrFG PR7wuSw0X4x8TAgpnUBV6zx9g9618PeKgw6hTLQ6pbNfWiKX7BmbwQVo/ea3qZGU LOR4SCQaJRk665WcOQqKz0Ky8BzVX/tr7WhWezkscjiw7pOp03t3POtxA6k4ShZs iSrK2jMTecJVjO2cu/LLWxD4LmE1xilMKtAqY9FlWbT4zfn0AIS2V0KFnTKo+SpU +/94Qby9cSj0u5C8/5Y0BONFnqFGKECBAgMBAAGjFjAUMBIGA1UdEwEB/wQIMAYB Af8CAQgwDQYJKoZIhvcNAQEFBQADggEBAARvJYbk5pYntNlCwNDJALF/VD6Hsm0k qS8Kfv2kRLD4VAe9G52dyntQJHsRW0mjpr8SdNWJt7cvmGQlFLdh6X9ggGvTZOir vRrWUfrAtF13Gn9kCF55xgVM8XrdTX3O5kh7VNJhkoHWG9YA8A6eKHegTYjHInYZ w8eeG6Z3ePhfm1bR8PIXrI6dWeYf/le22V7hXZ9F7GFoGUHhsiAm/lowdiT/QHI8 eZ98IkirRs3bs4Ysj78FQdPB4xTjQRcm0HyncUwZ6EoPclgxfexgeqMiKL0ZJGA/ O4dzwGvky663qyVDslUte6sGDnVdNOVdc22esnVApVnJTzFxiNmIf1Q=
[i188] </ds:X509Certificate>
[i189] </ds:X509Data>
[i190] </ds:KeyInfo>
[i191] </ds:Signature>
[i192] </enml:NotarySignatures>
[i193] 
[i198] </enml:NotarizedDocument>

[i001] – [i041] contains the usual preamble and SignedDocuments element that have already been described in previous examples.

[i042] – [i067] contains the two DocumentSigner elements – in this example, one for the signer in California and the other for the signer in New Jersey. Each element is expected to have been added independent of each other to the eNotarized document.

[i068] – [i095] contains the two NotaryCertificate elements. In this example, once again, each notarization is expected to have been done independent of the other by a distinct Notary Public.

[i096] – [i192] contains the two NotarySignature elements. Each Notary is expected to have their own X.509 digital certificate and corresponding private key to perform the signing. Each individual verification digital certificate is available in the distinct KeyInfo elements – the first at [i151]-[i152] and the second at [i187]-[i188].

3.10 eWitnessed document - Multiple Signers, Single Notary & Digital Signature

As was shown earlier in the example of an eWitnessed document with symmetric-key based cryptographic signature, the ENML is also capable of eWitnessing the eNotarization of documents using X.509 digital certificates and corresponding private keys. (An eWitnessed document is identical to an eNotarized document in all respects, save one: it does not contain a notarial certificate). The following example shows an eWitnessed document with a NULL Cryptographic Signature created by the document's signer and a digital signature created by the Notary Public.

[j001] <enml:WitnessedDocument
[j002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[j003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[j004] xsi:schemaLocation=
[j005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[j006] Id="WitnessedDocument-US-CA-1565986-1226972451-8023243532a0e30067350d469c4e7f79729ad7da392d3a18974d5a2e7bd09ee4">
[j007] 
[j012] <enml:SignedDocuments>
[j013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-
1222646532-849d55746eec2d91189e0f7f02ff374c0f5b53767ecdf9794b3a7e92a1abcfe6">
...
...
[j040] </enml:SignedDocument>
[j041] </enml:SignedDocuments>
[j042] 
[j047] <enml:DocumentSigners>
[j048] 
[j049] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
[j050] <enml:PersonFirstName>John</enml:PersonFirstName>
[j051] <enml:PersonLastName>Doe</enml:PersonLastName>
...
...
[j060] </enml:DocumentSigner>
[j061] </enml:DocumentSigners>
[j062] 
[j067] <enml:NotariesPublic>
[j068] <enml:NotaryPublic Id=”NotaryPublic-US-CA-1565986-1222643107-b269051b713ef56b17b3439ecbdb96c266e8d1c4ae5449deccb3e0bb9b007ddd”>
...
...
[j083] </enml:NotaryPublic>
[j084] </enml:NotariesPublic>
[j085] 
[j090] <enml:NotarySignatures>
[j091] <ds:Signature Id="Signature-US-CA-1565986-1222649290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
[j092] <ds:SignedInfo>
[j093] <ds:CanonicalizationMethod
[j094] Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
[j095] <ds:SignatureMethod
[j096] Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
...
...
[j108] <ds:KeyInfo>
[j109] <ds:X509Data>
[j110]
[j111] 
[j112] <ds:X509Certificate>
MIIDfDCCAmSgAwIBAgIIAe/AvliGc3AwDQYJKoZIhvcNAQELBQAwZzEmMCQGA1UEAxMdU3Ryb25n
S2V5IERFTU8gU3Vib3JkaW5hdGUgQ0ExJDAiBgNVBAsTG0ZvciBTdHJvbmdLZXkgREVNTyBVc2Ug
T25seTEXMBUGA1UEChMOU3Ryb25nQXV0aCBJbmMwHhcNMDYwNzI1MTcxMDMwWhcNMDcwNzI1MTcy
MDMwWjBtMREwDwYKCZImiZPyLGQBARMBMjEZMBcGA1UEAxMQUE9TIFJlZ2lzdGVyIDIyMjEkMCIG
A1UECxMbRm9yIFN0cm9uZ0tleSBERU1PIFVzZSBPbmx5MRcwFQYDVQQKEw5TdHJvbmdBdXRoIElu
YzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAyAmxMZhYA8wHJ4UE4b61s51JVWe4Fygj4MCf
U7LA3JhpUS4TlX0XFWqrcmltLOiVG7YBFarJFluBFJW2X6q8FuvUprv4V9nJrgiwAPtkiRyIx96n
qKXIxkUlQ4idlEg1AZI9dEdf4Y5cqBBCygPYnBoTudglM7R47AjR4nr4ks8CAwEAAaOBqTCBpjAO
BgNVHQ8BAf8EBAMCBLAwHQYDVR0OBBYEFOIOrWrZo0LdBRLVncRAwLBqVZpCMB8GA1UdIwQYMBaA
FPTYwEHoJG4iFVHRnt2EWxGluAQVMBgGA1UdIAQRMA8wDQYLKwYEAdISg30BBAEwOgYDVR0fBDMw
MTAvoC2gK4YpaHR0cDovL2RlbW8uc3Ryb25na2V5Lm9yZy9kZW1vLXN1Yi1jYS5jcmwwDQYJKoZI
hvcNAQELBQADggEBACK05PtvZD4WPglOe+EHUiApzFyCdRzf0pFZtxRwG9lR1PZUWUjmwTNfGFsL
S6kyoHgUfVa5fpT1EU1mXUB/Lmo3hFGyprZjfmD7DwuBcYgmZHv7yHrmGOMIOXjFTACvHpM0vOce
hVx2e4VE0yhBLu/ldH9awGGDp6Bk2XzxqQcs8y6ZzOXZAnPgKQZdjbFKERSsy/d1D8pk5baBk4bd
Zh568OcaUrbm9ZReRVTVaY5qiQpkOU+tDrBSj/HIL6GAqegYllkz6KYCy6RVOy6iVVSjHocDqdJr
EVOR+ds6xn8mmojdlERrILmuxiLpibPp609SfnDIxNlzLwe5g7ep3lc=
[j113] </ds:X509Certificate>
[j114] </ds:X509Data>
[j115] </ds:KeyInfo>
[j116] </ds:Signature>
[j117] </enml:NotarySignatures>
[j118] 
[j123] </enml:WitnessedDocument>

All the elements in this example have been introduced in earlier examples, so they are not repeated. The only distinction of note from the eWitnessed document presented in Section 3.4 is that this example shows the use of the RSA with SHA1 cryptographic algorithm in line [j096] and the X.509 digital certificate that can be used for verifying the digital signature is shown in lines [j112] – [j113].

3.11 eApostillized document with a Digital Signature

In international transactions, it is sometimes necessary for a notarized document to be certified by the competent authority that has jurisdiction over notaries public, and certify that the signature of the public official in the document is a valid signature. In conformance with the Convention at The Hague in 1961 [HCCH], such a certified document is called an Apostille. (A model of the certificate is shown below):

Given that ENML defines a markup language for electronically notarizing electronic documents, it is a natural consequence that ENML-based documents may need to be apostillized in the future. Such an “eApostillized” document must meet the data-element requirements of the 1961 Convention of the Hague, and match the model certificate shown above.

The ENML specification supports this feature, as is shown in the following example of a NotarizedDocument with a digital signature of the notary public, certified by the Secretary of State in California, whose own digital certificate is shown in the ApostillizedDocument. The data-elements of the model-certificate are contained in the ApostilleContent element.

While this is an XML document, readers must remember that software applications that implement ENML will be able to parse the XML, verify its contents cryptographically, and then display the apostille in the visual convention required by [HCCH].

[k001] <enml:ApostillizedDocument
[k002] xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
[k003] xmlns:enml="http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901"
[k004] xsi:schemaLocation=
[k005] 'http://docs.oasis-open.org/legalxml-enotary/ns/enml-200901.xsd'
[k006] Id="ApostillizedDocument-US-CA-SecretaryOfState-1226972584-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
[k007] 
[k012] <enml:SignedDocuments>
[k013] <enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[k040] </enml:SignedDocument>
[k041] </enml:SignedDocuments>
[k042] 
[k047] <enml:DocumentSigners>
[k049] <enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
...
...
[k060] </enml:DocumentSigner>
[k061] </enml:DocumentSigners>
[k062] 
[k067] <enml:NotaryCertificates>
[k068] <enml:NotaryCertificate Id="NotaryCertificate-US-NJ-4665986-
1223683212-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[k090] </enml:NotaryCertificate>
[k091] </enml:NotaryCertificates>
[k092] 
[k097] <enml:NotarySignatures>
[k098] <ds:Signature Id="Signature-US-CA-1565986-1222649290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
...
...
[k105] 
[k106] <ds:Reference URI="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
...
...
[k116] 
[k117] <ds:Reference URI="#DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
...
...
[k129] 
[k130] <ds:Reference URI="#NotaryCertificate-US-CA-1565986-
1222643229-1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
...
...
[k143] 
[k144] <ds:SignatureValue>
[k145] RVLpQofvWPK2mkmmL1mQW5cxqgmciNUa6MuAKA71qq/
[k146] NkhIu9ilN6TnAN7EwxNTkFpc5CBFbje4M7sbcdzzF1A==
[k147] </ds:SignatureValue>
[k148] <ds:KeyInfo>
[k149] <ds:X509Data>
[k150]
[k151] 
[k152] <ds:X509Certificate>
...
...
[k153] </ds:X509Certificate>
[k154] </ds:X509Data>
[k155] </ds:KeyInfo>
[k156] </ds:Signature>
[k157] </enml:NotarySignatures>
[k235] 
[k001] <enml:NotarizedDocument
[k158] 
[k242] </enml:ApostillizedDocument>

[k001] – [k157] contains XML elements that have already been described in previous examples for digital-signature based eNotarized documents (see Sections 3.8 and 3.9). The only exception is that [k001] identifies this document as being an ApostillizedDocument with an ID attribute, on line [k006], that has a value of “ ApostillizedDocument-US-CA-SecretaryOfState-1226972584-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4”. This value is unique for this apostille.

[k163] identifies the start of the ApostilleContent element with an ID attribute value of “ ApostilleContent-US-CA-1565986-1226972923-89e89c11cac335b3d7c1030f78ffca5527cbd4cc61479fc88526c38e01d912a5”.

[k164] contains the element IssuingCountry which identifies the country issuing this eApostille; this example contains the value “United States of America”.

[k165] - [k167] contains the ApostilleNumber element which identifies unique number of this eApostille within the country issuing it. In this example, the number is “ ApostilleNumber-US-CA-1565986-1226971821-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4”. This number is expected to be unique for each eApostille issued by the competent authority in this jurisdiction.

[k168] contains the element ApostilleDate which identifies the date, time and time-zone this eApostille was issued; this example contains the value “2008-11-17T12:13:14-08:00” indicates November 17, 2008 at 12:13:14PM in the Pacific time-zone (-08:00 hours from UTC).

[k169] - [k173] contains the IssuedAtUSLocation element which identifies geographic location this eApostille was issued. In this example, it is in the county of “Sacramento”, state of “California” in the “USA”.

[k174] - [k176] contains the SignerTitle element which identifies official title of the signer of this eApostille. In this example, it is the “Secretary of State” in the “State of California”.

[k177] - [k179] contains the StatutoryContent element for an ApostillizedDocument, in accordance with [HCCH]. This value is always “(Convention de La Haye du 5 octobre 1961)”.

[k180] - [k183] contains the DocumentSigningOfficialName element, which identifies the full name of the official (the notary public) who signed the document for which this eApostille is being issued. In this example, the NotarizedDocument is presumed to have been signed by the notary public, Arshad Noor, in the NotaryCertificate, it appears again in this element.

[k184] - [k186] contains the DocumentSigningOfficialTitle element, which identifies the official title of the person who signed the NotarizedDocument. In this example, the official title is “Notary Public”.

[k187] - [k191] contains the DocumentSigningOfficialSeal element, which identifies the official seal of the person who signed the NotarizedDocument. In this example, the seal defined in this ENML is of a text-string with the words: “Notary Public, State of California”.

[k193] – [k236] represents the digital signature of the person signing the eApostille. The elements have been previously described in Sections 3.8 and 3.9, so they will not be repeated. It is important to note that the apostille signer's signature refers to NotarizedDocument (in line [k202]) and the ApostilleContent (in line [k211]) elements referenced within this ApostillizedDocument, thus binding the apostille-signer's signature to the referenced NotarizedDocument and ApostilleContent.

[k237] – [k242] contain the comment and end-tags of the element-hierarchy in this document, which signifies the end of this eApostillized document.

3.12 The use of XPath in <ds:Signature>

This specification does not explicitly show the use of XPath transforms in the any of the examples in this section. This is simply because it has not been tested by the creators of this specification. Implementers of ENML are encouraged to use XPath transforms with caution and to verify all test cases (as given in this non-normative section) before releasing their software. The OASIS LegalXML eNotary Technical Committee will be grateful to implementers for any information they provide with respect to their experience in using XPath in their implementation.

4 Specification

4.1 Element <NotarizedDocument>

The <NotarizedDocument> element is the raison d'etre of the ENML protocol. It defines the standard for an electronically notarized document, and contains the required elements, under US law, for such a document.

Schema Definition:

<xsd:element name="NotarizedDocument" type="enml:NotarizedDocumentType"/>

<xsd:complexType name="NotarizedDocumentType">
<xsd:sequence>
<xsd:element
name="SignedDocuments"
type="enml:SignedDocumentsType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="DocumentSigners"
type="enml:DocumentSignersType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotaryCertificates"
type="enml:NotaryCertificatesType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotarySignatures"
type="enml:NotarySignaturesType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="required"/>
</xsd:complexType>

The <NotarizedDocument> element, is of type NotarizedDocumentType defined in the ENML schema, and consists of a sequence of four children elements and one attribute, all of which are required:

(Note that US law, currently allows only for a single document to be notarized within a unique <NotarizedDocument>. While ENML has the ability to include multiple documents within the <SignedDocuments> element, software implementations of ENML are expected to comply with legal requirements of the jurisdiction in which they expect the software to be operated).

The <SignedDocuments> element is specified in Section 4.4.

This element of type DocumentSignersType, identifies one or more signers of the electronic documents being notarized within an instance of a <NotarizedDocument>. The document signers are distinct from the Notary Public who will also sign this document, but whose signature will be carried in the <NotarySignatures> (discussed later). There MUST be exactly ONE <DocumentSigners> element in a <NotarizedDocument>element.

The <DocumentSigners> element is specified in Section 4.5.

This element of type NotaryCertificatesType, identifies one or more notarial certificates created by the Notary Public, and being notarized within an instance of a <NotarizedDocument>. There MUST be exactly ONE <NotaryCertificates> element in a <NotarizedDocument> element.

This element of type NotarySignaturesType, identifies one or more electronic signatures of the Notary Public notarizing an instance of a <NotarizedDocument>. There MUST be exactly ONE <NotarySignatures> element in a <NotarizedDocument> element.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Many examples of the <NotarizedDocument> element were provided in the non-normative Section 3 of this specification document. Please refer to that section for examples of the <NotarizedDocument> element.

4.2 Element <WitnessedDocument>

The <WitnessedDocument> element is the second-most important element of the ENML. Almost identical to the <NotarizedDocument>, it differs from the <NotarizedDocument> in that it does not carry a <NotaryCertificates> element, but carries a <NotariesPublic> element in its stead.

<xsd:element name="WitnessedDocument" type="enml:WitnessedDocumentType"/>

<xsd:complexType name="WitnessedDocumentType">
<xsd:sequence>
<xsd:element
name="SignedDocuments"
type="enml:SignedDocumentsType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="DocumentSigners"
type="enml:DocumentSignersType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotariesPublic"
minOccurs="1"
maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="NotaryPublic"
type="enml:NotaryPublicType"
minOccurs="1"
maxOccurs="unbounded">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

The <WitnessedDocument> element, is of type WitnessedDocumentType defined in the ENML schema, and consists of a sequence of four children elements and one attribute, all of which are required:

(Note that US law, currently allows only for a single document to be witnessed within a unique <WitnessedDocument>. While ENML has the ability to include multiple documents within the <SignedDocuments> element, software implementations of ENML are expected to comply with legal requirements of the jurisdiction in which they expect the software to be operated).

This element of type DocumentSignersType, identifies one or more signers of the electronic documents being notarized within an instance of a <WitnessedDocument> The document signers are distinct from the Notary Public who will also sign this document, but whose signature will be carried in the <NotarySignatures> (discussed later). There MUST be exactly ONE <DocumentSigners> element in a <WitnessedDocument> element.

The <DocumentSigners> element is specified in Section 4.5.

The <NotariesPublic> element is a container-element, whose purpose is to organize a collection of <NotaryPublic> elements inside one element. The <NotaryPublic> element, which is of NotaryPublicType, contains information about the Notary Public who witnessed the signing of the documents contained within the above-mentioned <SignedDocuments> element.

There MUST be exactly ONE <NotariesPublic> element in a <WitnessedDocument> element. The <NotariesPublic> element MUST contain at least ONE <NotaryPublic> element, but may contain an unbounded (unlimited) number of <NotaryPublic> elements as needed.

This element of type NotarySignaturesType, identifies one or more electronic signatures of the Notary Public notarizing an instance of a <WitnessedDocument>. There MUST be exactly ONE <NotarySignatures> element in a <WitnessedDocument> element.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Two examples of the <WitnessedDocument> element were provided in the non-normative Section 3.4 and Section 3.10 of this specification document. Please refer to those sections for examples of the <WitnessedDocument> element.

4.3 Element <ApostillizedDocument>

The <ApostillizedDocument> element is used to certify the signature of the Notary Public who signed the <NotarizedDocument> or the <WitnessedDocument> element, in accordance with conventions defined in [HCCH].

Schema Definition:

<xsd:element name="ApostillizedDocument" type="enml:ApostillizedDocumentType"/>

<xsd:complexType name="ApostillizedDocumentType">
<xsd:sequence>
<xsd:choice>
<xsd:element
name="NotarizedDocument"
type="enml:NotarizedDocumentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="WitnessedDocument"
type="enml:WitnessedDocumentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:choice>

<xsd:element
name="ApostilleContent"
type="enml:ApostilleContentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:choice>
<xsd:element
ref="ds:Signature"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="ApostilleSignature"
type="xsd:anyType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="required"/>
</xsd:complexType>

The <ApostillizedDocument> element, is of type ApostillizedDocumentType defined in the ENML schema, and consists of a sequence of three children elements and one attribute, all of which are required:

There MUST be exactly ONE <ds:Signature> or <ApostilleSignature> element in a <ApostillizedDocument> element.

This element of type ds:SignatureType is defined in the [XMLSignature] schema. It provides details about the electronic signature of the document-signer who signed the electronic document.

The <ds:Signature> element is a versatile element that allows for electronically signing documents with a variety of technologies, depicted in the XML. It supports the use of symmetric, as well as asymmetric, cryptographic keys for the generation of electronic signatures, and a variety of cryptographic algorithms to provide most implementers with the flexibility to choose a signing mechanism of their choice (as long as they satisfy the semantic meanings of the elements within the <ds:Signature> element).

The <ds:Signature> element is specified in [XMLSignature].

Please see Section 3.12 for a note on the use of XPath in <ds:Signature> elements within ENML.

The <ApostilleSignature> element of type xsd:anyType are for those situations where the software implementation of ENML chooses NOT to use any specific signing technology, and represents the apostille-signer's signature with simple text (or similar representations).

As the type implies, this element does not mandate what content may be placed in it, but it is strongly recommended that implementers use meaningful text (sch as “Signed by John Doe”, or “/S=John Doe” or similar well-known and accepted norms of electronic signatures) to represent the signer's signature.

Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of security issues within ENML.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

An example of the <ApostillizedDocument> element was provided in the non-normative Section 3.11 of this specification document. Please refer to that section for the example.

4.4 Element <SignedDocuments> & <SignedDocument>

The <SignedDocuments> element carries information about the business document that was notarized or whose signing was witnessed by a Notary Public and appears only within a <NotarizedDocument> or <WitnessedDocument> element. It is a container-element, whose purpose is to organize a collection of <SignedDocument> elements inside itself.

The <SignedDocument> element is the actual element that carries information about the electronic document signed by the document-signers and notarized (or whose signing was witnessed) by the Notary Public.

Note: Current US law does not permit notarizing or witnessing more than one document per notarization or witnessing. If the law changes to permit the electronic notarization or witnessing of multiple electronic documents within a single notarization or witnessing act, the ENML schema does not need to change. Application developers who implement ENML must take legal requirements into account when developing their software.

<xsd:element
name="SignedDocuments"
type="enml:SignedDocumentsType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="SignedDocumentsType">
<xsd:sequence>
<xsd:element
name="SignedDocument"
type="enml:SignedDocumentType"
minOccurs="1"
maxOccurs="unbounded">
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="SignedDocumentType">
<xsd:sequence>
<xsd:element
name="Document"
type="enml:DocumentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="DocumentMIMEType"
type="enml:SignedDocumentMIMEType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="DocumentMIMETypeComments"
minOccurs="0"
maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1024"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

<xsd:element
name="DocumentComments"
minOccurs="0"
maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1024"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="required"/>
</xsd:complexType>

The <SignedDocuments> element is of type SignedDocumentsType defined in the ENML schema, while the <SignedDocument> element is of the SignedDocumentType .

There MUST be exactly ONE <SignedDocuments> element in either a <NotarizedDocument> or <WitnessedDocument> element. The <SignedDocuments> element MUST contain at least ONE <SignedDocument> element, but may contain an unbounded (unlimited) number of <SignedDocument> elements as needed.

The <SignedDocument> element of type SignedDocumentType, consists of a sequence of four children elements and one ID attribute:

This element of type SignedDocumentMIMEType, identifies the type of electronic document being notarized or witnessed . There MUST be exactly ONE <DocumentMIMEType> element in a <SignedDocument> element.

The <DocumentMIMEType> element is specified in Section 4.10.

The optional <DocumentMIMETypeComments> element of type xsd:String allows applications creating the ENML-marked document, to provide hints to receiving applications about what application was used to create the ENML and what other applications are/maybe compatible with the document-MIME type.

When present, There MUST be exactly ONE <DocumentMIMETypeComments> element in a <SignedDocument> element. Its value may not be more than 1,024-characters in length including white-space, which is preserved as-is.

The optional <DocumentComments> element of type xsd:String allows applications creating the ENML-marked document, to provide a comment to receiving applications and/or users about the embedded document itself.

When present, there MUST be exactly ONE <DocumentComments> element in a <SignedDocument> element. Its value may not be more than 1,024-characters in length including white-space, which is preserved as-is.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Many examples of the <SignedDocument> element were provided in the non-normative Section 3 of this specification document. Please refer to that section for examples of the <SignedDocument> element .

4.5 Element <DocumentSigners> & <DocumentSigner>

The <DocumentSigners> element carries information about the individuals who signed the document, and appears only within a <NotarizedDocument> or <WitnessedDocument> element. It is a container-element, whose purpose is to organize a collection of <DocumentSigner> elements inside itself.

Each <DocumentSigner> element carries information about each signer of the electronic document that was notarized (or whose signing was witnessed) by the Notary Public.

Schema Definition:

<xsd:element
name="DocumentSigners"
type="enml:DocumentSignersType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="DocumentSignersType">
<xsd:sequence>
<xsd:element
name="DocumentSigner"
type="enml:DocumentSignerType"
minOccurs="1"
maxOccurs="unbounded">
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="DocumentSignerType">
<xsd:sequence>
<xsd:element
name="SignerName"
type="enml:PersonNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="SignerTitle"
type="enml:PersonTitleType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:choice>
<xsd:element
name="SignerInternationalAddress"
type="enml:InternationalAddressType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:element
name="SignerUSAddress"
type="enml:USAddressType"
minOccurs="0"
maxOccurs="1">
</xsd:element>
</xsd:choice>

<xsd:element
name="SignerIdentificationMethod"
type="enml:PersonIdentificationMethodType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:choice>
<xsd:element
ref="ds:Signature"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="SignerSignature"
type="xsd:anyType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="required"/>
</xsd:complexType>

The <DocumentSigners> element is of type DocumentSignersType defined in the ENML schema, while the <DocumentSigner> element is of the DocumentSignerType,

There MUST be exactly ONE <DocumentSigners> element in either a <NotarizedDocument> or <WitnessedDocument> element. The <DocumentSigners> element MUST contain at least ONE <DocumentSigner> element, but may contain an unbounded (unlimited) number of <DocumentSigner> elements as needed.

The <DocumentSigner> element of type DocumentSignerType, consists of a sequence of five children elements and one ID attribute:

The optional element of type PersonTitleType, identifies the official title of the person signing the document, when the notarized or witnessed document is being signed in an official capacity. When present, there MUST be exactly ONE <SignerTitle> element in a <DocumentSigner> element.

The <SignerTitle> element is specified in Section 4.14.

The next sub-element represents the physical address of the document-signer. However, depending on the geographical location – either an international or US-based location - this optional element must be a choice of either the <SignerInternationalAddress> or the <SignerUSAddress> element, respectively. It is the responsibility of the application generating the ENML-marked document to choose the appropriate element based on the jurisdiction of the signer or signing.

When present, there MUST be exactly ONE <SignerInternationalAddress> or <SignerUSAddress> element in a <DocumentSigner> element.

The optional <SignerIdentificationMethod> element of PersonIdentificationMethodType indicates how the document-signer identified himself/herself during the notarization or witnessing.

When present, There MUST be exactly ONE <SignerIdentificationMethod> element in a <DocumentSigner> element.

The next sub-element represents the electronic signature of the document-signer. However, depending on the type of technology chosen, this element must be a choice of either the <ds:Signature> or the <SignerSignature> element. It is the responsibility of the application generating the ENML-marked document to choose the appropriate element.

There MUST be exactly ONE <ds:Signature> or <SignerSignature> element in a <DocumentSigner> element.

Please see Section 3.12 for a note on the use of XPath in <ds:Signature> elements within ENML.

The <SignerSignature> element of type xsd:anyType are for those situations where the software implementation of ENML chooses NOT to use any specific signing technology, and represents the signer's signature with simple text (or similar representations).

As the type implies, this element does not mandate what content may be placed in it, but it is strongly recommended that implementers use meaningful text (sch as “Signed by John Doe”, or “/S=John Doe” or similar well-known and accepted norms of electronic signatures) to represent the signer's signature.

The <SignerSignature> element is specified in 4.18.

Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of security issues within ENML.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Example 1 – A <DocumentSigners> element with one <DocumentSigner> using a NULL Cryptographic Signature:

Example 2 – A <DocumentSigners> element with two <DocumentSigner> elements, both using NULL Cryptographic Signatures:

<enml:DocumentSigners>
<enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
<enml:SignerName>
<enml:PersonFirstName>John</enml:PersonFirstName>
<enml:PersonLastName>Doe</enml:PersonLastName>
</enml:SignerName>
<enml:SignerUSAddress>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:SignerUSAddress>
<enml:SignerIdentificationMethod>
Produced Government-issued Identification Document
</enml:SignerIdentificationMethod>
<enml:SignerSignature>
Signed by John Doe
</enml:SignerSignature>
</enml:DocumentSigner>

<enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
<enml:SignerName>
<enml:PersonFirstName>Jane</enml:PersonFirstName>
<enml:PersonLastName>Doe</enml:PersonLastName>
</enml:SignerName>
<enml:SignerUSAddress>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:SignerUSAddress>
<enml:SignerIdentificationMethod>
Produced Government-issued Identification Document
</enml:SignerIdentificationMethod>
<enml:SignerSignature>
Signed by Jane Doe
</enml:SignerSignature>
</enml:DocumentSigner>
<enml:DocumentSigners>

Example 3 – A <DocumentSigners> element with one <DocumentSigner> element, with an international address and using a symmetric-key based cryptographic signature:

<enml:DocumentSigners>
<enml:DocumentSigner Id="DocumentSigner-NL-DR-123456789-1222643107-c3edac5c23fa36aace2afd6d273fd7f91b09f20bfa099beb6b1cb493dfdd957">
<enml:SignerName>
<enml:PersonFirstName>Jan</enml:PersonFirstName>
<enml:PersonLastName>Doer</enml:PersonLastName>
</enml:SignerName>
<enml:SignerInternationalAddress>
<enml:City>Utrecht</enml:City>
<enml:County>Utrecht</enml:County>
<enml:Country>Netherlands</enml:Country>
</enml:SignerInternationalAddress>
<enml:SignerIdentificationMethod>
Produced Government-issued Identification Document
</enml:SignerIdentificationMethod>
<enml:SignerSignature>
Signed by Jan Doer
</enml:SignerSignature>
</enml:DocumentSigner>

4.6 Element <NotaryCertificates> & <NotaryCertificate>

The <NotaryCertificates> element carries information about the Notarial Certificate and the Notary Public who notarized (or witnessed) the document. It appears only within a <NotarizedDocument> element but not in a <WitnessedDocument> element (since witnessed documents do not carry a notarial certificate).

The <NotaryCertificates> element is a container-element, whose sole purpose is to organize a collection of <NotaryCertificate> elements inside itself.

The <NotaryCertificate> element carries the actual information about the notarial certificate, representing a unique notarization event, and about the Notary Public himself/herself.

Note: The <NotaryCertificates> may also appear within propriety XML documents, as a sub-element of documents that are not of NotarizedDocumentType, but which are deemed eNotarized because they have undergone the requisite legal process of electronic notarization and carry the <NotaryCertificates> and <NotarySignatures> elements in their proprietary XML.

However, there is no assurance that applications that implement only the the <NotaryCertificates> and <NotarySignatures> elements within proprietary XML are inter-operable, since those applications must also understand the proprietary XML of the enclosing document to verify the eNotarized document.

Applications that implement the OASIS-specified <NotarizedDocument> and <WitnessedDocument> elements, however, are expected to inter-operate, since these two elements are standardized through this specification.

<xsd:complexType name="NotaryCertificatesType">
<xsd:sequence>
<xsd:element
name="NotaryCertificate"
type="enml:NotaryCertificateType"
minOccurs="1"
maxOccurs="unbounded">
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="NotaryCertificateType">
<xsd:sequence>
<xsd:element
name="CertificateContent"
type="enml:NotaryCertificateContentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotaryPublic"
type="enml:NotaryPublicType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="required"/>
</xsd:complexType>

The <NotaryCertificates> element is of type NotaryCertificatesType, defined in the ENML schema, while the <NotaryCertificate> element is of the NotaryCertificateType,

There MUST be exactly ONE <NotaryCertificates> element in a <NotarizedDocument> element. The <NotaryCertificates> element MUST contain at least ONE <NotaryCertificate> element, but may contain an unbounded (unlimited) number of <NotaryCertificate> elements as needed.

The <NotaryCertificate> element consists of a sequence of two children elements and one ID attribute:

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Example 1 – A <NotaryCertificates> element with one <NotaryCertificate> element:

<enml:NotaryCertificates>
<enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-1222640980-0ef2d548e82b637a0568fc1c4e69e2eb896acfc083fdefb82e24a05cab840f54">
<enml:CertificateContent>
<enml:NotarizationType>
Acknowledgment
</enml:NotarizationType>
<enml:NotarizationDate>
2007-02-07T15:19:17-08:00
</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>
State of California
County of Santa Clara

On February 07 2007, before me Arshad Noor, personally
appeared John Doe, who proved to me on the basis of
satisfactory evidence to be the person whose name is
subscribed to the within instrument and acknowledged to
me that he executed the same in his authorized capacity,
and that by his signature on the instrument the person,
or the entity upon behalf of which the person acted,
executed the instrument.

I certify under PENALTY OF PERJURY under the laws of the
State of California that the foregoing paragraph is true
and correct.

WITNESS my hand and official seal.
</enml:StatutoryContent>
</enml:CertificateContent>

<enml:NotaryPublic>
<enml:NotaryName>
<enml:PersonGivenName>Arshad</enml:PersonGivenName>
<enml:PersonSurName>Noor</enml:PersonSurName>
</enml:NotaryName>
<enml:NotaryCommissionNumber>
1565986
</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
</enml:NotaryCertificate>
</enml:NotaryCertificates>

Example 2– A <NotaryCertificates> element with three <NotaryCertificate> elements in it (many details have been removed for brevity). Each <NotaryCertificate> represents a unique notarization event of the same document:

<enml:NotaryCertificates>


<enml:NotaryCertificate Id="NotaryCertificate-US-CA-.....>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificate>

<enml:NotaryCertificate Id="NotaryCertificate-US-CA-.....>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificate>

<enml:NotaryCertificate Id="NotaryCertificate-US-NJ-.....>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificate>

</enml:NotaryCertificates>

4.7 Element <NotarySignatures> & <NotarySignature>

The <NotarySignatures> element carries information about the Notarial Certificate and the Notary Public who notarized (or witnessed) the document.

The <NotarySignatures> element is a container-element, whose sole purpose is to organize a collection of either <ds:Signature> or <NotarySignature> elements, which carry the actual information about the Notary's signature, inside itself. Each signature element represents a unique notarization event.

Note: The <NotarySignatures> element may also appear within propriety XML documents, as a sub-element of documents that are not of NotarizedDocumentType, but which are deemed eNotarized because they have undergone the requisite legal process of electronic notarization and carry the <NotaryCertificates> and <NotarySignatures> elements in their proprietary XML.

<xsd:choice>
<xsd:element
ref="ds:Signature"
minOccurs="1"
maxOccurs="unbounded"/>

<xsd:element
name="NotarySignature"
type="xsd:anyType"
minOccurs="1"
maxOccurs="unbounded"/>
</xsd:choice>

The <NotarySignaturesType> element is of type NotarySignaturesType, defined in the ENML schema.

There MUST be exactly ONE <NotarySignatures> element in either a <NotarizedDocument> or a <WitnessedDocument> element. The <NotarySignatures> element MUST contain at least ONE <ds:Signature> or <NotarySignature> element, but may contain an unbounded (unlimited) number of either element as needed.

The <NotarySignatures> element consists of one child elements and one ID attribute:

Please see Section 3.12 for a note on the use of XPath in <ds:Signature> elements within ENML.

The <NotarySignature> element of type xsd:anyType are for those situations where the software implementation of ENML chooses NOT to use any specific signing technology, and represents the Notary's signature with simple text (or similar representations).

As the type implies, this element does not mandate what content may be placed in it, but it is strongly recommended that implementers use meaningful text (sch as “Signed by Howard Jones”, or “/S=Howard Jones” or similar well-known and accepted norms of electronic signatures) to represent the Notary's signature.

Please note the informative appendix on “ENML Security Implications” at the end of this document for an understanding of security issues within ENML.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Example 1 – A <NotarySignatures> element with one <ds:Signature> using a symmetric cryptographic key. The signature has signed one Manifest enclosed within the Object element and contains four (4) References pointing to one SignedDocument, two DocumentSigners and one NotaryCertificate. The signature uses the HMAC-SHA1 cryptographic algorithm; the symmetric key is identified with a KeyName of “10514-1-123” and can be retrieved from the URL defined in the RetrievalMethod element:

<enml:NotarySignatures>
<ds:Signature>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
<ds:Reference Type="http://www.w3.org/2000/09/xmldsig#Manifest" URI="#Manifest-US-CA-1565986-1222641281">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>MtGcQfervxf/b3xvrPEstt0h1fg=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
09fbf143326bb09beefabe8d84094ee14c5eee8c
</ds:SignatureValue>

<ds:KeyInfo>
<ds:KeyName>10514-1-123</ds:KeyName>
<ds:RetrievalMethod URI="http://skms.somecompany.com/symkeyServlet/getsymkey"/>
</ds:KeyInfo>

<ds:Reference URI="#SignedDocument-US-CA-1565986-1222646484-
546e0248b7e7f52a4427880d3efb84557746e691556e0d37bb92fe1f2ad7fd0b">
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>W4DupJioi0mM7aG+N1qiNLtqvsk=</ds:DigestValue>
</ds:Reference>

<ds:Reference URI="#DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>Yx5JkTS0ZxaM0uEpm/SxmSRSgAw=</ds:DigestValue>
</ds:Reference>

<ds:Reference URI="#DocumentSigner-US-CA-1565986-1222643179-ca44f9fcc8950e9ad42959c725f2e31073f20b7058b777b2aa2d21f1830006dc">
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>M0uEpmYx5JkTS0Zxa/SxmSRSgAw=</ds:DigestValue>
</ds:Reference>

<ds:Reference URI="#NotaryCertificate-US-CA-1565986-1222643229-
1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>+w49wI2IZOiUOVSx7L0fQp1nO30=</ds:DigestValue>
</ds:Reference>
</ds:Manifest>
</ds:Object>
</ds:Signature>
</enml:NotarySignatures>

Example 2 – A <NotarySignatures> element with one <ds:Signature> using an asymmetric cryptographic key. The signature has References pointing to one SignedDocument, DocumentSigner and NotaryCertificate. The signature uses the RSA-SHA1 cryptographic algorithm; the public-key is identified with the X509 digital certificate:

<enml:NotarySignatures>
<ds:Signature Id="Signature-US-CA-1565986-1222649290-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>

<ds:Reference URI="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>3b3Bd7TGR/niVS+d3WbnLReFK+g=</ds:DigestValue>
</ds:Reference>

<ds:Reference URI="#DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>275ded60801633b0dd38d2e57ef3cd98eeb58de5</ds:DigestValue>
</ds:Reference>

<ds:Reference URI="#NotaryCertificate-US-CA-1565986-1222643229-
1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>275ded60801633b0dd38d2e57ef3cd98eeb58de5</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>

<ds:SignatureValue>RVLpQofvWPK2mkmmL1mQW5cxqgmciNUa6MuAKA71qq/NKhIu9ilN6TnAN7EwxNTkFpc5CBFbje4M7sbcdzzF1A==</ds:SignatureValue>
<ds:KeyInfo>
<ds:X509Data>

<ds:X509Certificate>
MIIDfDCCAmSgAwIBAgIIAe/AvliGc3AwDQYJKoZIhvcNAQELBQAwZzEmMCQGA1UEAxMdU3Ryb25n
S2V5IERFTU8gU3Vib3JkaW5hdGUgQ0ExJDAiBgNVBAsTG0ZvciBTdHJvbmdLZXkgREVNTyBVc2Ug
T25seTEXMBUGA1UEChMOU3Ryb25nQXV0aCBJbmMwHhcNMDYwNzI1MTcxMDMwWhcNMDcwNzI1MTcy
MDMwWjBtMREwDwYKCZImiZPyLGQBARMBMjEZMBcGA1UEAxMQUE9TIFJlZ2lzdGVyIDIyMjEkMCIG
A1UECxMbRm9yIFN0cm9uZ0tleSBERU1PIFVzZSBPbmx5MRcwFQYDVQQKEw5TdHJvbmdBdXRoIElu
YzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAyAmxMZhYA8wHJ4UE4b61s51JVWe4Fygj4MCf
U7LA3JhpUS4TlX0XFWqrcmltLOiVG7YBFarJFluBFJW2X6q8FuvUprv4V9nJrgiwAPtkiRyIx96n
qKXIxkUlQ4idlEg1AZI9dEdf4Y5cqBBCygPYnBoTudglM7R47AjR4nr4ks8CAwEAAaOBqTCBpjAO
BgNVHQ8BAf8EBAMCBLAwHQYDVR0OBBYEFOIOrWrZo0LdBRLVncRAwLBqVZpCMB8GA1UdIwQYMBaA
FPTYwEHoJG4iFVHRnt2EWxGluAQVMBgGA1UdIAQRMA8wDQYLKwYEAdISg30BBAEwOgYDVR0fBDMw
MTAvoC2gK4YpaHR0cDovL2RlbW8uc3Ryb25na2V5Lm9yZy9kZW1vLXN1Yi1jYS5jcmwwDQYJKoZI
hvcNAQELBQADggEBACK05PtvZD4WPglOe+EHUiApzFyCdRzf0pFZtxRwG9lR1PZUWUjmwTNfGFsL
S6kyoHgUfVa5fpT1EU1mXUB/Lmo3hFGyprZjfmD7DwuBcYgmZHv7yHrmGOMIOXjFTACvHpM0vOce
hVx2e4VE0yhBLu/ldH9awGGDp6Bk2XzxqQcs8y6ZzOXZAnPgKQZdjbFKERSsy/d1D8pk5baBk4bd
Zh568OcaUrbm9ZReRVTVaY5qiQpkOU+tDrBSj/HIL6GAqegYllkz6KYCy6RVOy6iVVSjHocDqdJr
EVOR+ds6xn8mmojdlERrILmuxiLpibPp609SfnDIxNlzLwe5g7ep3lc=
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature>
</enml:NotarySignatures>

4.8 Element <NotariesPublic> & <NotaryPublic>

The <NotariesPublic> element carries information about the Notary Public who notarized (or witnessed the signing of) the document. While it appears as a child element of the <NotaryCertificate> element in the <NotarizedDocument> element , it appears as a direct child of the <WitnessedDocument> element (since witnessed documents do not carry a notarial certificate).

The <NotariesPublic> element is a container-element, whose sole purpose is to organize a collection of <NotaryPublic> elements inside itself.

The <NotaryPublic> element carries the actual information about the Notary Public himself/herself who either notarized or witnessed the signing of an electronic document.

<xsd:element name="NotariesPublic" minOccurs="1" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="NotaryPublic"
type="enml:NotaryPublicType"
minOccurs="1"
maxOccurs="unbounded">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:complexType name="NotaryPublicType">
<xsd:sequence>
<xsd:element
name="NotaryName"
type="enml:PersonNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotaryCommissionNumber"
type="enml:NotaryCommissionNumberType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotaryCommissionExpiryDate"
type="enml:DateTimeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:choice>
<xsd:element
name="NotaryInternationalJurisdiction"
type="enml:InternationalAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotaryUSJurisdiction"
type="enml:USAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:choice>

<xsd:element
name="NotaryBondNumber"
type="enml:NotaryBondNumberType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotaryVerificationURI"
type="xsd:anyURI"
minOccurs="0"
maxOccurs=”unbounded”>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="optional"/>
</xsd:complexType>

The <NotariesPublic> element is an anonymous element defined in the ENML schema, while the <NotaryPublic> element is of the NotaryPublicType,

There MUST be exactly ONE <NotariesPublic> element in either a <NotarizedDocument> or <WitnessedDocument> element. The <NotariesPublic> element MUST contain at least ONE <NotaryPublic> element, but may contain an unbounded (unlimited) number of <NotaryPublic> elements as needed.

The <NotaryPublic> element consists of a sequence of six (6) children elements and one ID attribute:

The <NotaryUSJurisdiction> element is of the type USAddressType defined in the ENML schema, and is specified in Section 4.24.

Note: The posting of a bond by a Notary Public, before they may perform their official duties, is a requirement in some US states. Since it is not a mandatory requirement, this element is declared to be optional.

The <NotaryBondNumber> element is specified in Section 4.25.

Note: Currently there are no known locations in the US where such information can be verified programmatically and securely. However, it is anticipated that as eNotarized documents get adopted, these services will become necessary and common, to verify the authenticity of a Notary Public signing a Notarized or Witnessed document.

Please see Section 4.56 for a discussion of the Processing Rule for ID attributes within ENML.

Example 1 – A <NotariesPublic> element with one <NotaryPublic> element, as defined within a <WitnessedDocument> (<NotarizedDocument> elements only have the <NotaryPublic> element and do not carry the <NotariesPublic> element):

<enml:WitnessedDocument>
<enml:SignedDocuments>....</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotariesPublic>
<enml:NotaryPublic Id="NotaryPublic-US-CA-1565986-1222644533-
4c8e1a0eff954439fef46b8694ca8641ae64a16790d7504b6dcc69014d9bd624">
<enml:NotaryName>
<enml:PersonGivenName>Arshad</enml:PersonGivenName>
<enml:PersonSurName>Noor</enml:PersonSurName>
</enml:NotaryName>
<enml:NotaryCommissionNumber>1565986</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
</enml:NotariesPublic>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:WitnessedDocument>

Example 2 – A <NotaryPublic> element, defined within a <NotaryCertificate> element of a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>....</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>...</enml:CertificateContent>
<enml:NotaryPublic Id="NotaryPublic-US-CA-1565986-1222644533-
4c8e1a0eff954439fef46b8694ca8641ae64a16790d7504b6dcc69014d9bd624">
<enml:NotaryName>
<enml:PersonGivenName>Arshad</enml:PersonGivenName>
<enml:PersonSurName>Noor</enml:PersonSurName>
</enml:NotaryName>
<enml:NotaryCommissionNumber>1565986</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
</enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.9 Element <Document>

The <Document> element of type DocumentType from the ENML schema, is used to carry the contents of the notarized, or witnessed for signature, document. The <Document> element is always embedded inside a <SignedDocument> element, and does not stand on its own.

<xsd:element
name="Document"
type="enml:DocumentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="DocumentType">
<xsd:simpleContent>
<xsd:extension base="xsd:base64Binary">
<xsd:attribute name="Id" type="xsd:ID" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>

There MUST be exactly ONE <Document> element inside a <SignedDocument> element. However, the <Document> element may itself contain as many pages as XML technology will permit.

The contents of the <Document> element MUST always be base64Binary encoded. This permits any type of document to be notarized: graphics images, scanned-images of printed documents, word-processing documents, reports generated from application software, ZIP files and even XML-encoded documents.

Some software products, such as OpenOffice, Microsoft Office and similar products, create rich-content documents, but store them in XML format using a specific XML schema of their choice. A single rich-content document may contain many files, all stored in XML format. Such related XML files are archived into a ZIP archive and given a product-specific extension, such as *.odf, *.xlsx, etc.

If an application expects to notarize or witness the signing of such rich-content documents in ENML, the application must base64-encode the binary archived file first, and embed the resultant text into the <Document> element, to be compliant with this standard.

<enml:NotarizedDocument>
<enml:SignedDocuments>
<enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222640886-.....">
<enml:Document>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
ZwdhbFhNTCBlTm90YXJpemF0aW9uIDEuMCBTcGVjaWZpY2F0aW9uCgogIDA5IERl
Y2VtYmVyIDIwMDcgQWxsIFJpZ2h0cyBSZXNlcnZlZC4KCiAgVGhpcyBkb2N1bWVu
dCBhbmQgdHJhbnNsYXRpb25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5p
c2hlZCB0byBvdGhlcnMsIAogIGFuZCBkZXJpdmF0aXZlIHdvcmtzIHRoYXQgY29t
bWVudCBvbiBvciBvdGhlcndpc2UgZXhwbGFpbiBpdCBvciBhc3Npc3QgaW4gaXRz
CiAgaW1wbGVtZW50YXRpb24gbWF5IGJlIHByZXBhcmVkLCBjb3BpZWQsIHB1Ymxp
c2hlZCBhbmQgZGlzdHJpYnV0ZWQsIGluIHdob2xlIG9yCiAgaW4gcGFydCwgd2l0
aG91dCByZXN0cmljdGlvbiBvZiBhbnkga2luZCwgcHJvdmlkZWQgdGhhdCB0aGUg
YWJvdmUgY29weXJpZ2h0CiAgbm90aWNlIGFuZCB0aGlzIHBhcmFncmFwaCBhcmUg
aW5jbHVkZWQgb24gYWxsIHN1Y2ggY29waWVzIGFuZCBkZXJpdmF0aXZlIHdvcmtz
LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
</enml:Document>
<enml:DocumentMIMEType>....</enml:DocumentMIMEType>
<enml:DocumentComments>....</enml:DocumentComments>
</enml:SignedDocument>
</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

Example 2– A base64-encoded document in a <WitnessedDocument>. Note that the only difference between examples 1 and 2 is that example 2 carries a <NotariesPublic> element instead of the <NotaryCertificates> element.

<enml:WitnessedDocument>
<enml:SignedDocuments>
<enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222640886-.....">
<enml:Document>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
ZwdhbFhNTCBlTm90YXJpemF0aW9uIDEuMCBTcGVjaWZpY2F0aW9uCgogIDA5IERl
Y2VtYmVyIDIwMDcgQWxsIFJpZ2h0cyBSZXNlcnZlZC4KCiAgVGhpcyBkb2N1bWVu
dCBhbmQgdHJhbnNsYXRpb25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5p
c2hlZCB0byBvdGhlcnMsIAogIGFuZCBkZXJpdmF0aXZlIHdvcmtzIHRoYXQgY29t
bWVudCBvbiBvciBvdGhlcndpc2UgZXhwbGFpbiBpdCBvciBhc3Npc3QgaW4gaXRz
CiAgaW1wbGVtZW50YXRpb24gbWF5IGJlIHByZXBhcmVkLCBjb3BpZWQsIHB1Ymxp
c2hlZCBhbmQgZGlzdHJpYnV0ZWQsIGluIHdob2xlIG9yCiAgaW4gcGFydCwgd2l0
aG91dCByZXN0cmljdGlvbiBvZiBhbnkga2luZCwgcHJvdmlkZWQgdGhhdCB0aGUg
YWJvdmUgY29weXJpZ2h0CiAgbm90aWNlIGFuZCB0aGlzIHBhcmFncmFwaCBhcmUg
aW5jbHVkZWQgb24gYWxsIHN1Y2ggY29waWVzIGFuZCBkZXJpdmF0aXZlIHdvcmtz
LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
</enml:Document>
<enml:DocumentMIMEType>....</enml:DocumentMIMEType>
<enml:DocumentMIMETypeComments>....</enml:DocumentMIMETypeComments>
<enml:DocumentComments>....</enml:DocumentComments>
</enml:SignedDocument>
</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotariesPublic>....</enml:NotariesPublic>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:WitnessedDocument>

4.10 Element <DocumentMIMEType> & <SignedDocumentMIMEType>

The <DocumentMIMEType> element of type SignedDocumentMIMEType from the ENML schema, is used to describe the contents of the notarized, or witnessed for signature, document. The <DocumentMIMEType> element is always embedded inside a <SignedDocument> element, and does not stand on its own.

The <SignedDocumentMIMEType> element is of the xsd:token type from XML Schema, and consists of a list of enumerated tokens that describe the most popular file-content types. This element provides a hint to receiving applications on the type of content that was notarized and how to process it upon parsing the ENML.

<xsd:element
name="DocumentMIMEType"
type="enml:SignedDocumentMIMEType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="SignedDocumentMIMEType">
<xsd:restriction base="xsd:token">
<xsd:enumeration value="application/other"/>
<xsd:enumeration value="application/pdf"/>
<xsd:enumeration value="application/postscript"/>
<xsd:enumeration value="application/rtf"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.chart"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.formula"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.graphics"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.image"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.presentation"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.spreadsheet"/>
<xsd:enumeration value="application/vnd.oasis.opendocument.text"/>
<xsd:enumeration value="application/xml"/>
<xsd:enumeration value="application/zip"/>
<xsd:enumeration value="image/gif"/>
<xsd:enumeration value="image/jpeg"/>
<xsd:enumeration value="image/png"/>
<xsd:enumeration value="text/plain"/>
<xsd:enumeration value="text/xml"/>
<xsd:enumeration value="video/mpeg"/>
<xsd:enumeration value="video/mp4"/>
</xsd:restriction>
</xsd:simpleType>

There MUST be exactly ONE <DocumentMIMEType> element inside a <SignedDocument> element.

The content of the <DocumentMIMEType> element MUST be from the list of enumerated tokens described in the <SignedDocumentMIMEType> element. The following MIME-types are currently recognized for the <SignedDocumentMIMEType> element, by this specification:

MIME-type	Document Content Type
application/other	Any content not defined in this enumerated list
application/pdf	Portable Document Format
application/postscript	PostScript
application/rtf	Rich Text Format
application/vnd.oasis.opendocument.chart	OASIS OpenDocument Chart document
application/vnd.oasis.opendocument.formula	OASIS OpenDocument Formula document
application/vnd.oasis.opendocument.graphics	OASIS OpenDocument Graphics document
application/vnd.oasis.opendocument.image	OASIS OpenDocument Image document
application/vnd.oasis.opendocument.presentation	OASIS OpenDocument Presentation document
application/vnd.oasis.opendocument.spreadsheet	OASIS OpenDocument Spreadsheet document
application/vnd.oasis.opendocument.text	OASIS OpenDocument Text document
application/xml	eXtensible Markup Language in an application-specific format
application/zip	ZIP Archive
image/gif	Graphics Interchange Format image file
image/jpeg	Joint Photographic Expert Group image file
image/png	Portable Network Graphics image file
text/plan	Plain ASCII Text
text/xml	eXtensible Markup Language in plain ASCII text format
video/mpeg	Motion video in the Moving Picture Experts Group format
video/mp4	Motion video in the MPEG-4 format

If a document's content can be specified in more than one MIME-type, the application MUST use the most specific MIME-type that will render the contents in their true form. For example, a document created by OpenOffice Writer uses the MIME-type “application/vnd.oasis.opendocument.text”. However, the document, which is really a collection of smaller files containing content, style, settings, etc. and “zipped” into a ZIP archive, can also be characterized with the MIME-type “application/zip”.

While the document can be “read” by a ZIP-archive utility, and subsequently, by many XML tools and word-processors, the application that most closely renders the content in its “true form” is OpenOffice. As such, the ENML must use the MIME-type “application/vnd.oasis.opendocument.text” in the <DocumentMIMEType> element. This provides the receiver with the most specific instructions on how to render the contents correctly with the most appropriate tool or application.

Example 1 – A <WitnessedDocument> with “application/pdf” type content in the <Document>:

.....

LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
</enml:Document>
<enml:DocumentMIMEType>application/pdf</enml:DocumentMIMEType>
<enml:DocumentComments>....</enml:DocumentComments>
</enml:SignedDocument>
</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotariesPublic>....</enml:NotariesPublic>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:WitnessedDocument>

Example 2– A <NotarizedDocument> with “image/gif” type content in the <Document>:

<enml:NotarizedDocument>
<enml:SignedDocuments>
<enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222640886-.....">
<enml:Document>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
ZwdhbFhNTCBlTm90YXJpemF0aW9uIDEuMCBTcGVjaWZpY2F0aW9uCgogIDA5IERl
Y2VtYmVyIDIwMDcgQWxsIFJpZ2h0cyBSZXNlcnZlZC4KCiAgVGhpcyBkb2N1bWVu
dCBhbmQgdHJhbnNsYXRpb25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5p
c2hlZCB0byBvdGhlcnMsIAogIGFuZCBkZXJpdmF0aXZlIHdvcmtzIHRoYXQgY29t
bWVudCBvbiBvciBvdGhlcndpc2UgZXhwbGFpbiBpdCBvciBhc3Npc3QgaW4gaXRz
CiAgaW1wbGVtZW50YXRpb24gbWF5IGJlIHByZXBhcmVkLCBjb3BpZWQsIHB1Ymxp
c2hlZCBhbmQgZGlzdHJpYnV0ZWQsIGluIHdob2xlIG9yCiAgaW4gcGFydCwgd2l0
aG91dCByZXN0cmljdGlvbiBvZiBhbnkga2luZCwgcHJvdmlkZWQgdGhhdCB0aGUg
YWJvdmUgY29weXJpZ2h0CiAgbm90aWNlIGFuZCB0aGlzIHBhcmFncmFwaCBhcmUg
aW5jbHVkZWQgb24gYWxsIHN1Y2ggY29waWVzIGFuZCBkZXJpdmF0aXZlIHdvcmtz
LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
</enml:Document>
<enml:DocumentMIMEType>image/gif</enml:DocumentMIMEType>
<enml:DocumentMIMETypeComments>....</enml:DocumentMIMETypeComments>
<enml:DocumentComments>....</enml:DocumentComments>
</enml:SignedDocument>
</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.11 Element <DocumentMIMETypeComments>

The element <DocumentMIMETypeComments> of type xsd:String, is used to provide a hint to the receiving application, on how to process the document content if the <DocumentMIMEType> is not explicit (as when this element might contain the MIME-type “application/other”).

<xsd:element name="DocumentMIMETypeComments" minOccurs="0" maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1024"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

The <DocumentMIMETypeComments> element is an optional element; however, when used, there SHALL be only one <DocumentMIMETypeComments> element within a <Document> element.

The <DocumentMIMETypeComments> element may contain alphanumeric text, but is restricted to a length of 1,024-characters including white-space. The white-space must be preserved by XML-parsers and applications during processing.

Example 1 – A <NotarizedDocument> with a <DocumentMIMETypeComments> element in the <Document>, indicating that the content is a Bank Draft created with an application called XYZ, version 1.2.3:

4.12 Element <DocumentComments>

The element <DocumentComments> of type xsd:String, is used to provide any human-readable comments to Relying Parties about the notarized or witnessed document. Applications implementing ENML, and that possess a User Interface (UI) that might display ENML content to them, are responsible for display the contents of the <DocumentComments> element.

<xsd:element name="DocumentComments" minOccurs="0" maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1024"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

The <DocumentComments> element is an optional element; however, when used, there SHALL be only one <DocumentComments> element within a <Document> element.

The <DocumentComments> element may contain alphanumeric text, but is restricted to a length of 1,024-characters including white-space. The white-space must be preserved by XML-parsers and applications during processing.

Example 1 – A <NotarizedDocument> with a <DocumentComments> element in the <Document>:

<enml:NotarizedDocument>
<enml:SignedDocuments>
<enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222640886-.....">
<enml:Document>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
ZwdhbFhNTCBlTm90YXJpemF0aW9uIDEuMCBTcGVjaWZpY2F0aW9uCgogIDA5IERl
LgogIEhvd2V2ZXIsIHRoaXMgZG9jdW1lbnQgaXRzZWxmIG1heSBub3QgYmUgbW9k
aWZpZWQgaW4gYW55IHdheSwgc3VjaCBhcyBieQogIHJlbW92aW5nIHRoZSBjb3B5
ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
</enml:Document>
<enml:DocumentMIMEType>application/other</enml:DocumentMIMEType>
<enml:DocumentMIMETypeComments>
Bank Draft created with application XYZ Version 1.2.3
</enml:DocumentMIMETypeComments>
<enml:DocumentComments>
While the bank issued the Draft, there is a legitimate question
about the viability of the issuing bank.
</enml:DocumentComments>
</enml:SignedDocument>
</enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.13 Element <SignerName>

The <SignerName> element, of the type PersonNameType defined in the ENML schema, carries the full name of a document signer. If there are multiple document signers, there would be multiple <DocumentSigner> elements, and each one would have its own <SignerName> element to identify the signer.

<xsd:element
name="SignerName"
type="enml:PersonNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="PersonNameType">
<xsd:sequence>

<xsd:element
name="PersonPrefixName"
type="enml:PersonPrefixNameType"
minOccurs="0"
maxOccurs=”1”/>

<xsd:choice>
<xsd:sequence>
<xsd:element
name="PersonFirstName"
type="enml:PersonGivenNameType"
minOccurs="1"
maxOccurs="1"/>
<xsd:element
name="PersonMiddleName"
type="enml:PersonMiddleNameType"
minOccurs="0"
maxOccurs=”1”/>
<xsd:element
name="PersonLastName"
type="enml:PersonSurNameType"
minOccurs="0"
maxOccurs=”1”/>
</xsd:sequence>

<xsd:sequence>
<xsd:element
name="PersonGivenName"
type="enml:PersonGivenNameType"
minOccurs="1"
maxOccurs="1"/>
<xsd:element
name="PersonMiddleName"
type="enml:PersonMiddleNameType"
minOccurs="0"
maxOccurs=”1”/>
<xsd:element
name="PersonSurName"
type="enml:PersonSurNameType"
minOccurs="0"
maxOccurs=”1”/>
</xsd:sequence>
</xsd:choice>

<xsd:element
name="PersonSuffixName"
type="enml:PersonSuffixNameType"
minOccurs="0"
maxOccurs=”1”/>

<xsd:element
name="PersonMaidenName"
type="enml:PersonMaidenNameType"
minOccurs="0"
maxOccurs=”1”/>

<xsd:element
name="PersonFullName"
type="enml:PersonFullNameType"
minOccurs="0"
maxOccurs=”1”/>

</xsd:sequence>
</xsd:complexType>

Example 1 – A <SignerName> using the US-based convention within a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>
<enml:DocumentSigner>
<enml:SignerName>
<enml:PersonFirstName>John</enml:PersonFirstName>
<enml:PersonMiddleName>Q</enml:PersonMiddleName>
<enml:PersonLastName>Doe</enml:PersonLastName>
<enml:PersonFullName>John Q Doe</enml:PersonFullName>
</enml:SignerName>
<enml:SignerSignature>...</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

<enml:SignerName>
<enml:PersonPrefixName>Dr.</enml:PersonPrefixName>
<enml:PersonFirstName>John</enml:PersonFirstName>
<enml:PersonMiddleName>Q</enml:PersonMiddleName>
<enml:PersonLastName>Doe</enml:PersonLastName>
<enml:PersonSuffixName>Jr.</enml:PersonSuffixName>
<enml:PersonFullName>Dr. John Q. Doe Jr.</enml:PersonFullName>
</enml:SignerName>

<enml:SignerName>
<enml:PersonPrefixName>Mrs.</enml:PersonPrefixName>
<enml:PersonGivenName>Marie</enml:PersonGivenName>
<enml:PersonSurName>Antoinette-Givenchy</enml:PersonSurName>
<enml:PersonMaidenName>Antoinette</enml:PersonMaidenName>
<enml:PersonFullName>Mrs. Marie Antoinette-Givenchy</enml:PersonFullName>
</enml:SignerName>

4.14 Element <SignerTitle>

The element <SignerTitle>, of type PersonTitleType defined in the ENML schema, allows the ENML to carry the official designation of the document-signer when the document-signer signs the electronic document in his/her official capacity in a business transaction.

<xsd:element
name="SignerTitle"
type="enml:PersonTitleType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonTitleType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="256"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

When used in a <DocumentSigner> element, this is an optional element; when used in an <ApostilleContent> element, it is required. Regardless of when it is used, there SHALL be only one <SignerTitle> element within the <DocumentSigner> or the <ApostilleContent> element.

The PersonTitleType uses the xsd:String as the base type, and permits a title of up to 256-characters, preserving any white-spaces within the title-content.

Example 1 – A <SignerTitle> using the US-based convention within a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>
<enml:DocumentSigner ID=...>
<enml:SignerName>...</enml:SignerName>
<enml:SignerTitle>Loan Officer</enml:SignerTitle>
<enml:SignerSignature>...</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

Example 2 – An example of an <ApostillizedDocument> with a <SignerTitle> element.

4.15 Element <SignerInternationalAddress>

The element <SignerInternationalAddress>, of type InternationalAddressType defined in the ENML schema, is used to carry the physical postal address of a document-signer based outside the USA.

The <SignerInternationalAddress> element is an optional one, but when present, there SHALL be only one <SignerInternationalAddress> element within the <DocumentSigner> element.

Schema Definition:

<xsd:element
name="SignerInternationalAddress"
type="enml:InternationalAddressType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="InternationalAddressType">
<xsd:sequence>
<xsd:element
name="StreetAddress1"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="StreetAddress2"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="State"
type="enml:InternationalStateType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="PostalCode"
type="enml:InternationalPostalCodeType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="Country"
type="enml:CountryType"
minOccurs="1"
maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>

The <SignerInternationalAddress> element is composed of a sequence of the following elements:

Example 1 – A <SignerInternationalAddress> within a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>
<enml:DocumentSigner>
<enml:SignerName>....</enml:SignerName>
<enml:SignerTitle>....</enml:SignerTitle>
<enml:SignerInternationalAddress>
<enml:City>Utrecht</enml:City>
<enml:County>Utrecht</enml:County>
<enml:Country>Netherlands</enml:Country>
</enml:SignerInternationalAddress>
<enml:SignerIdentificationMethod>....</enml:SignerIdentificationMethod>
<enml:SignerSignature>...</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

<enml:SignerInternationalAddress>
<enml:StreetAddress1>490 Sussex Drive</enml:StreetAddress1>
<enml:City>Ottawa</enml:City>
<enml:State>Ontario</enml:State>
<enml:PostalCode>K2P 2N2</enml:PostalCode>
<enml:Country>Canada</enml:Country>
</enml:SignerInternationalAddress>

4.16 Element <SignerUSAddress>

The element <SignerUSAddress>, of type USAddressType defined in the ENML schema, is used to carry the physical postal address of a document-signer based in the USA.

The <SignerUSAddress> element is an optional one, but when present, there SHALL be only one <SignerUSAddress> element within the <DocumentSigner> element.

<xsd:element
name="SignerUSAddress"
type="enml:USAddressType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="USAddressType">
<xsd:sequence>
<xsd:element
name="StreetAddress1"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="StreetAddress2"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="USState"
type="enml:USStateCodeType"
minOccurs="1"
maxOccurs="1"/>

<xsd:element
name="USZipCode"
type="enml:USZipCodeType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="Country"
type="enml:CountryTypeUSA"
minOccurs="1"
maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>

The <SignerUSAddress> element is composed of a sequence of the following elements:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>
<enml:DocumentSigner>
<enml:SignerName>....</enml:SignerName>
<enml:SignerTitle>....</enml:SignerTitle>
<enml:SignerUSAddress>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:SignerUSAddress>
<enml:SignerIdentificationMethod>....</enml:SignerIdentificationMethod>
<enml:SignerSignature>...</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

<enml:SignerUSAddress>
<enml:StreetAddress1>23 Autumn Drive</enml:StreetAddress1>
<enml:City>Basking Ridge</enml:City>
<enml:County>Middlesex</enml:County>
<enml:USState>NJ</enml:USState>
<enml:USZipCode>07920</enml:USZipCode>
<enml:Country>USA</enml:Country>
</enml:SignerUSAddress>

4.17 Element <SignerIdentificationMethod>

The element <SignerIdentificationMethod>, of type PersonIdentificationMethodType defined in the ENML schema, is used to describe how the document-signer identified himself/herself to the Notary Public at the time of the notarization or witnessing act. The element does not specify what specific document was produced or any identification number of the document (for privacy reasons), but merely indicates what method of identification was used to assure the Notary Public of the signer's identity.

<xsd:element
name="SignerIdentificationMethod"
type="enml:PersonIdentificationMethodType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonIdentificationMethodType">
<xsd:restriction base="xsd:token">
<xsd:enumeration
value="Produced Government-issued Identification Document"/>
<xsd:enumeration value="Personally Known to Credible Witnesses"/>
<xsd:enumeration value="Personally Known to Notary Public"/>
</xsd:restriction>
</xsd:simpleType>

The <SignerIdentificationMethod> element is an optional element, but when present, there SHALL be only one <SignerIdentificationMethod> element within the <DocumentSigner> element.

The PersonIdentificationMethodType uses the xsd:Token as the base type, and requires that, when present, the content of this element be one of the three specified identification methods:

Note: These choices currently reflect US-based law for notarization of documents. However, it is anticipated to include support for international law as representation from other countries provide input to the OASIS eNotarization Technical Committee.

Example 1 – A <SignerIdentificationMethod> within a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>
<enml:DocumentSigner>
<enml:SignerName>...</enml:SignerName>
<enml:SignerTitle>Loan Officer</enml:SignerTitle>
<enml:SignerIdentificationMethod>
Personally Known to Notary Public
</enml:SignerIdentificationMethod>
<enml:SignerSignature>...</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.18 Element <SignerSignature>

The <SignerSignature> element of type xsd:anyType from the XML Schema definition, allows the ENML to carry a document signer's signature in situations where the software implementation of ENML does NOT use any cryptographic signature, and represents the signer's signature as simple text (or similar representations).

<xsd:element
name="SignerSignature"
type="xsd:anyType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

There SHALL be only one <SignerSignature> element within the <DocumentSigner> element. As the type implies, this element does not mandate what content may be placed in it, but it is strongly recommended that implementers use meaningful text (sch as “Signed by John Doe”, or “/S=John Doe” or similar well-known and accepted norms of electronic signatures) to represent the signer's signature.

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>
<enml:DocumentSigner>
<enml:SignerName>...</enml:SignerName>
<enml:SignerTitle>Loan Officer</enml:SignerTitle>
<enml:SignerIdentificationMethod>....</enml:SignerIdentificationMethod>
<enml:SignerSignature>
Signed by John Doe
</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>
<enml:NotaryCertificates>....</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.19 Element <CertificateContent>

The <CertificateContent> element of the type NotaryCertificateContentType from the ENML schema, carries details about the notarization act, such as the type of notarization, the date of notarization, location and the required legal content for the notarial certificate.

It is important to note that the <WitnessedDocument> element does not contain a <NotaryCertificate> element, and as such, does not contain a <CertificateContent> element.

<xsd:element
name="CertificateContent"
type="enml:NotaryCertificateContentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="NotaryCertificateContentType">
<xsd:sequence>
<xsd:element
name="NotarizationType"
type="enml:NotarizationActType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotarizationDate"
type="enml:DateTimeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:choice>
<xsd:element
name="NotarizationInternationalLocation"
type="enml:InternationalAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="NotarizationUSLocation"
type="enml:USAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:choice>

<xsd:element
name="StatutoryContent"
type="xsd:anyType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:complexType>

There MUST be exactly ONE <CertificateContent> element within the <NotaryCertificate> element.

The next sub-element represents the physical location where the notarization act executed within an ENML-marked document. However, depending on the geographical location – either an international or US-based location - this element must be a choice of either the <NotarizationInternationalLocation> or the <NotarizationUSLocation> element, respectively. It is the responsibility of the application generating the ENML-marked document to choose the appropriate element based on the jurisdiction of the notarization act.

When present, there MUST be exactly ONE <NotarizationInternationalLocation> or <NotarizationUSLocation> element in a <CertificateContent> element.

Example 1 – An example of a <CertificateContent> element specifying that the notarization act was an Acknowledgment, that took place on February 07, 2007 in Santa Clara County of California, US. The element also contains the legal content required for an Acknowledgment in the state of California:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>.... </enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-02-07T15:19:17-08:00</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>
State of California
County of Santa Clara

I certify under PENALTY OF PERJURY under the laws of the
State of California that the foregoing paragraph is true
and correct.

WITNESS my hand and official seal.
</enml:StatutoryContent>
</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.20 Element <NotaryName>

The <NotaryName> element, of the type PersonNameType defined in the ENML schema, carries the full name of a Notary Public who either notarized or witnessed the signing of, the ENML-marked document. If there are multiple notarizations performed on the same document, there must be multiple <NotaryPublic> elements, and each one would have its own <NotaryName> element to identify the Notary Public.

<xsd:element
name="NotaryName"
type="enml:PersonNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="PersonNameType">
<xsd:sequence>

<xsd:element
name="PersonPrefixName"
type="enml:PersonPrefixNameType"
minOccurs="0"
maxOccurs=”1”/>

<xsd:element
name="PersonSuffixName"
type="enml:PersonSuffixNameType"
minOccurs="0"
maxOccurs=”1”/>

<xsd:element
name="PersonMaidenName"
type="enml:PersonMaidenNameType"
minOccurs="0"
maxOccurs=”1”/>

<xsd:element
name="PersonFullName"
type="enml:PersonFullNameType"
minOccurs="0"
maxOccurs=”1”/>

</xsd:sequence>
</xsd:complexType>

Example 1 – A <NotaryName> using the US-based convention within a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>
<enml:NotaryName>
<enml:PersonFirstName>Arshad</enml:PersonFirstName>
<enml:PersonLastName>Noor</enml:PersonLastName>
<enml:PersonFullName>Arshad Noor</enml:PersonFullName>
</enml:NotaryName>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
<enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

<enml:NotaryName>
<enml:PersonPrefixName>Mr.</enml:PersonPrefixName>
<enml:PersonFirstName>John</enml:PersonFirstName>
<enml:PersonMiddleName>Q</enml:PersonMiddleName>
<enml:PersonLastName>Doe</enml:PersonLastName>
<enml:PersonSuffixName>Esq.</enml:PersonSuffixName>
<enml:PersonFullName>Mr. John Q. Doe Esq.</enml:PersonFullName>
</enml:NotaryName>

<enml:NotaryName>
<enml:PersonPrefixName>Mrs.</enml:PersonPrefixName>
<enml:PersonGivenName>Marie</enml:PersonGivenName>
<enml:PersonSurName>Antoinette-Givenchy</enml:PersonSurName>
<enml:PersonFullName>Mrs. Marie Antoinette-Givenchy</enml:PersonFullName>
</enml:NotaryName>

4.21 Element <NotaryCommissionNumber>

The <NotaryCommissionNumber> element of the type NotaryCommissionNumberType from the ENML schema, provides the official Commission number issued by the authority of a jurisdiction in which the Notary Public may perform his/her official duties. However, it should be noted that some US states do not use an official Commission number to identify a unique Notary Public within their state.

<xsd:element
name="NotaryCommissionNumber"
type="enml:NotaryCommissionNumberType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="NotaryCommissionNumberType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

The optional <NotaryCommissionNumber> element permits the use of any alphanumeric character, to a maximum length of 255 characters, preserving white-space characters in its representation. When present, there MUST be exactly ONE <NotaryCommissionNumber> element inside a <NotaryPublic> element.

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>
<enml:NotaryName>....</enml:NotaryName>
<enml:NotaryCommissionNumber>
1565986
</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
<enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.22 Element <NotaryCommissionExpiryDate>

The <NotaryCommissionExpiryDate> element is used to identify the date and time when the official commission of the Notary Public who notarized, or witnessed the signing of, the ENML-marked document, expires. It also specifies the time-zone in which this time falls.

<xsd:element
name="NotaryCommissionExpiryDate"
type="enml:DateTimeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="DateTimeType">
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>

The <NotaryCommissionExpiryDate> element of the type DateTimeType from the ENML schema, requires a date in the following format:

where CCYY denotes the 4-digit calendar year, MM denotes the 2-digit month of the year and DD denotes the 2-digit day-of-month; the “T” is a fixed value; hh denotes the hour of day in 24-hour format, mm denotes the minute of the hour and ss denotes the second within the minute. The time-zone may be specified either with a fixed “Z” which then implies that the preceding time is specified in Coordinated Universal Time (UTC), or it may be specified with the number of hours and minutes ahead or behind UTC, with a + or – sign respectively. There MUST be exactly ONE <NotaryCommissionExpiryDate> element within a <NotaryPublic> element.

Since the expiration date of a notary's commission is usually specified by date, the time value of this element is always assumed to be 23:59:59 – the time at the last second of the specified date in its time-zone.

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>
<enml:NotaryName>....</enml:NotaryName>
<enml:NotaryCommissionNumber>....</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2007-02-27T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
<enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.23 Element <NotaryInternationalJurisdiction>

The element <NotaryInternationalJurisdiction>, of type InternationalAddressType defined in the ENML schema, is used to specify the legal jurisdiction in which the Notary Public, based outside the USA, is authorized to carry out his/her official duties. For Notaries who perform their official duties within the USA, the <NotaryUSJurisdiction> element must be used (see the next section). Software implementing ENML must choose the appropriate element based on the physical jurisdiction of the Notary Public and the notarization.

There MUST be exactly one <NotaryInternationalJurisdiction> element within the <NotaryPublic> element when it is chosen.

<xsd:element
name="NotaryInternationalJurisdiction"
type="enml:InternationalAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="InternationalAddressType">
<xsd:sequence>
<xsd:element
name="StreetAddress1"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="StreetAddress2"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="State"
type="enml:InternationalStateType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="PostalCode"
type="enml:InternationalPostalCodeType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="Country"
type="enml:CountryType"
minOccurs="1"
maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>

The <NotaryInternationalJurisdiction> element is composed of a sequence of the following elements:

Example 1 – A <NotaryInternationalJurisdiction> within a <NotarizedDocument>:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>
<enml:NotaryName>....</enml:NotaryName>
<enml:NotaryCommissionNumber>....</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryInternationalJurisdiction>
<enml:County>Utrecht</enml:County>
<enml:Country>Netherlands</enml:Country>
</enml:NotaryInternationalJurisdiction>
</enml:NotaryPublic>
<enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.24 Element <NotaryUSJurisdiction>

The element <NotaryUSJurisdiction>, of type USAddressType defined in the ENML schema, is used to specify the legal jurisdiction in which the Notary Public, based inside the USA, is authorized to carry out his/her official duties. For Notaries who perform their official duties outside the USA, the <NotaryInternationalJurisdiction> element must be used (see the previous section). Software implementing ENML must choose the appropriate element based on the physical jurisdiction of the Notary Public and the notarization.

There MUST be exactly one <NotaryUSJurisdiction> element within the <NotaryPublic> element when it is chosen.

<xsd:element
name="NotaryUSJurisdiction"
type="enml:USAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="USAddressType">
<xsd:sequence>
<xsd:element
name="StreetAddress1"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="StreetAddress2"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="USState"
type="enml:USStateCodeType"
minOccurs="1"
maxOccurs="1"/>

<xsd:element
name="USZipCode"
type="enml:USZipCodeType"
minOccurs="0"
maxOccurs="1"/>

<xsd:element
name="Country"
type="enml:CountryTypeUSA"
minOccurs="1"
maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>

The <NotaryUSJurisdiction> element is composed of a sequence of the following elements:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>
<enml:NotaryName>....</enml:NotaryName>
<enml:NotaryCommissionNumber>....</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
<enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

<enml:NotaryUSJurisdiction>
<enml:StreetAddress1>10846 Via San Marino</enml:StreetAddress1>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>United States of America</enml:Country>
</enml:NotaryUSJurisdiction>

4.25 Element <NotaryBondNumber>

The <NotaryBondNumber> element of the type NotaryBondNumberType from the ENML schema, provides the serial number of the Bond posted by the Notary Public before starting to perform his/her official duties. Such a bond is required in many US states and is public information. This number is typically issued by the insurance company that underwrites the Bond. However, since not all jurisdictions require a bond, this element is optional.

<xsd:element
name="NotaryBondNumber"
type="enml:NotaryBondNumberType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="NotaryBondNumberType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

The optional <NotaryBondNumber> element permits the use of any alphanumeric character, to a maximum length of 255 characters, preserving white-space characters in its representation. When present, there MUST be exactly ONE <NotaryBondNumber> element inside a <NotaryPublic> element.

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>....</enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:NotaryCertificate>
<enml:CertificateContent>....</enml:CertificateContent>
<enml:NotaryPublic>
<enml:NotaryName>....</enml:NotaryName>
<enml:NotaryCommissionNumber>....</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
<enml:NotaryBondNumber>ABC-12345</enml:NotaryBondNumber>
</enml:NotaryPublic>
<enml:NotaryCertificate>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.26 Element <PersonPrefixName>

The <PersonPrefixName> element allows the ENML to carry the prefix of a document-signer's or Notary's name. This is not the same as the document-signer's or Notary's title, which has its own element.

The optional <PersonPrefixName> element of the PersonPrefixNameType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 32-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="PersonPrefixName"
type="enml:PersonPrefixNameType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonPrefixNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.27 Element <PersonFirstName> & <PersonGivenName>

The <PersonFirstName> and the <PersonGivenName> elements carry the first- or given-name (depending on the local convention where the notarization is being performed) of a document-signer's or Notary's name. Only one of these elements MUST be chosen by the software implementing ENML.

These required elements of the PersonGivenNameType from the ENML schema, use the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 32-characters for the element, while preserving all white-space characters within their content.

<xsd:element
name="PersonFirstName"
type="enml:PersonGivenNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="PersonGivenName"
type="enml:PersonGivenNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonGivenNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.28 Element <PersonMiddleName>

The <PersonMiddleName> element allows the ENML to carry the middle-name or middle-initial of a document-signer's or Notary's name.

The optional <PersonMiddleName> element of the PersonMiddleNameType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 32-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="PersonMiddleName"
type="enml:PersonMiddleNameType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonMiddleNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.29 Element <PersonLastName> & <PersonSurName>

The <PersonLastName> and the <PersonSurName> elements carry the last- or surname (depending on the local convention where the notarization is being performed) of a document-signer's or Notary's name. Only one of these elements MUST be chosen by the software implementing ENML.

These required elements of the PersonSurNameType from the ENML schema, use the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within their content.

<xsd:element
name="PersonLastName"
type="enml:PersonSurNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="PersonSurName"
type="enml:PersonSurNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonSurNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.30 Element <PersonSuffixName>

The <PersonSuffixName> element allows the ENML to carry the suffix of a document-signer's or Notary's name. This is not the same as the document-signer's or Notary's title, which has its own element.

The optional <PersonSuffixName> element of the PersonSuffixNameType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 32-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="PersonSuffixName"
type="enml:PersonSuffixNameType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonSuffixNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.31 Element <PersonMaidenName>

The <PersonMaidenName> element allows the ENML to carry the maiden-name (unmarried last-name or surname) of a document-signer's or Notary's name, where necessary.

Note: While this author does not know of any requirement for this within US Notary laws, given that maiden-names may be used in some parts of the world as a custom, this optional element is made available in the schema.

The optional <PersonMaidenName> element of the PersonMaidenNameType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="PersonMaidenName"
type="enml:PersonMaidenNameType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonMaidenNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.32 Element <PersonFullName>

The <PersonFullName> element allows the ENML to carry the full name – which includes the prefix, the first- or given-name, middle-name, last- or surname and suffix - of a document-signer's or Notary's name in a single element.

While it is possible for software to construct the full name of the document-signer or the Notary Public using the component elements described earlier, carrying the full-name of the person in ENML can save many software products a fair amount of processing time during verifications, for display on screens and for printing on reports. It is provided as a convenience rather than a requirement.

The optional <PersonFullName> element of the PersonFullNameType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 256-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="PersonFullName"
type="enml:PersonFullNameType"
minOccurs="0"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonFullNameType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="256"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.33 Element <StreetAddress1>

The <StreetAddress1> element allows the ENML to carry the first line of the street address of a physical location for a document-signer or a Notary Public.

The optional <StreetAddress1> element of the StreetAddressType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="StreetAddress1"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="StreetAddressType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.34 Element <StreetAddress2>

The <StreetAddress2> element allows the ENML to carry the second line of the street address of a physical location for a document-signer or a Notary Public.

The optional <StreetAddress2> element, also of the StreetAddressType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="StreetAddress2"
type="enml:StreetAddressType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="StreetAddressType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.35 Element <City>

The <City> element allows the ENML to carry the name of the city of the street address for a document-signer or a Notary Public.

The optional <City> element, also of the CityType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="City"
type="enml:CityType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="CityType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.36 Element <County>

The <County> element allows the ENML to carry the name of the county or municipality of the street address for a document-signer or a Notary Public. While the <County> element is optional within an international address, it is a required element for notarized or witnessed documents with US-based addresses. This is because Notaries in the US are commissioned by county within a State. While they may perform their official duties outside their county within their state, they must indicate the name of their county in notarized, or witnessed for signature, documents.

The <County> element, also of the CountyType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="County"
type="enml:CountyType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

Schema Definition (for US addresses/jurisdictions):

<xsd:element
name="County"
type="enml:CountyType"
minOccurs="1"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="CountyType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.37 Element <State>

The <State> element allows the ENML to carry the name of the state or province of the street address for a document-signer or a Notary Public in an international location; for US-based locations, the appropriate element is <USState>. While the <State> element is optional within an international address, it is a required element for notarized or witnessed documents with US-based addresses.

The <State> element, also of the InternationalStateType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="State"
type="enml:InternationalStateType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="InternationalStateType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.38 Element <PostalCode>

The <PostalCode> element allows the ENML to carry the postal code of the street address for a document-signer or a Notary Public in an international location; for US-based locations, the appropriate element is <USZipCode>.

The optional <PostalCode> element, of the InternationalPostalCodeType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="PostalCode"
type="enml:InternationalPostalCodeType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="InternationalPostalCodeType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.39 Element <Country> (International)

The <Country> element allows the ENML to carry the name of an international country, of the street address for a document-signer or a Notary Public.

The required <Country> element is of the CountryType from the ENML schema for an international location, and of the CountryTypeUSA for a US-based location. The CountryType uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="Country"
type="enml:CountryType"
minOccurs="1"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="CountryType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

4.40 Element <USState>

The <USState> element allows the ENML to carry the name of the state or territory of the street address for a document-signer or a Notary Public in a US-based location. For international locations, the appropriate element is <State>.

The required <USState> element, of the USStateCodeType from the ENML schema, uses the xsd:token type from the XML Schema Definition as the base type, with a restriction to choose one of restricted set of enumerations. The enumerations are highlighted in the Schema Definition below; the annotations from the schema-definition has been left in-place to avoid duplicating the explanation.

There MUST be exactly ONE <USState> element with any element that uses a US-based address in ENML.

<xsd:element
name="USState"
type="enml:USStateCodeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="USStateCodeType">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">
A code list that enumerates the states of the USA.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="AA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">
Armed Forces Americas (except Canada)
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AE">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">
Armed Forces Africa, Canada, Europe, Middle East
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AK">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">ALASKA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AL">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">ALABAMA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AP">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">Armed Forces Pacific
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AR">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">ARKANSAS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AS">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">AMERICAN SAMOA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AZ">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">ARIZONA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">CALIFORNIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CO">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">COLORADO
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CT">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">CONNECTICUT
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DC">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">DISTRICT OF COLUMBIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DE">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">DELAWARE
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FL">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">FLORIDA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FM">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">
FEDERATED STATES OF MICRONESIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">GEORGIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GU">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">GUAM
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="HI">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">HAWAII
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="IA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">IOWA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ID">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">IDAHO
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="IL">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">ILLINOIS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="IN">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">INDIANA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="KS">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">KANSAS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="KY">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">KENTUCKY
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">LOUISIANA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MASSACHUSETTS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MD">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MARYLAND
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ME">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MAINE
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MH">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MARSHALL ISLANDS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MI">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MICHIGAN
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MN">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MINNESOTA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MO">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MISSOURI
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MP">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">
NORTHERN MARIANA ISLANDS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MS">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MISSISSIPPI
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MT">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">MONTANA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NC">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NORTH CAROLINA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ND">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NORTH DAKOTA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NE">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NEBRASKA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NH">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NEW HAMPSHIRE
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NJ">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NEW JERSEY
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NM">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NEW MEXICO
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NV">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NEVADA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NY">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">NEW YORK
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="OH">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">OHIO
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="OK">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">OKLAHOMA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="OR">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">OREGON
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">PENNSYLVANIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PR">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">PUERTO RICO
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PW">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">PALAU
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RI">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">RHODE ISLAND
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SC">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">SOUTH CAROLINA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SD">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">SOUTH DAKOTA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="TN">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">TENNESSEE
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="TX">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">TEXAS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="UT">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">UTAH
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="VA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">VIRGINIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="VI">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">VIRGIN ISLANDS
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="VT">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">VERMONT
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="WA">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">WASHINGTON
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="WI">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">WISCONSIN
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="WV">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">WEST VIRGINIA
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="WY">
<xsd:annotation>
<xsd:documentation xml:lang="en-US">WYOMING
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>

4.41 Element <USZipCode>

The <USZipCode> element allows the ENML to carry the postal code of the street address for a document-signer or a Notary Public in a US-based location; for international locations, the appropriate element is <PostalCode>.

The optional <USZipCode> element, of the USZipCodeType from the ENML schema, uses the xsd:string type from the XML Schema Definition as the base type, with a restriction that indicates that the zip-code may either be one of the following:

<xsd:element
name="USZipCode"
type="enml:USZipCodeType"
minOccurs="0"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="USZipCodeType">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{5}|\d{5}-\d{4}"/>
</xsd:restriction>
</xsd:simpleType>

4.42 Element <Country> (USA)

The <Country> element allows the ENML to carry the name of the country of the street address for a document-signer or a Notary Public.

In the case of the USA, the required <Country> element is of the CountryTypeUSA from the ENML schema; for an international location it is of the CountryType. The CountryTypeUSA uses the xsd:token type from the XML Schema Definition as the base type, with a restriction to choose one of two restricted enumerations. The enumerations are highlighted in the Schema Definition below.

There MUST be exactly ONE <Country> element within an element that uses a US-based address in ENML.

<xsd:element
name="Country"
type="enml:CountryTypeUSA"
minOccurs="1"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="CountryTypeUSA">
<xsd:restriction base="xsd:token">
<xsd:enumeration value="USA"/>
<xsd:enumeration value="United States of America"/>
</xsd:restriction>
</xsd:simpleType>

The two valid examples of the use of the <Country> element for US-based addresses (within ENML) are :

4.43 Element <NotarizationType>

The <NotarizationType> element, of the type NotarizationActType defined in the ENML schema, identifies the type of notarization acts that is described within the <NotarizedDocument>.

<xsd:element
name="NotarizationType"
type="enml:NotarizationActType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="NotarizationActType">
<xsd:restriction base="xsd:token">
<xsd:enumeration value="Acknowledgment"/>
<xsd:enumeration value="Attestation"/>
<xsd:enumeration value="CertifiedCopy"/>
<xsd:enumeration value="Jurat"/>
<xsd:enumeration value="Other"/>
</xsd:restriction>
</xsd:simpleType>

The NotarizationActType is an enumerated list of xsd:token types from the XML Schema Definition, and consists of a choice of one the following tokens:

There MUST be exactly ONE <NotarizationType> element within a <CertificateContent> element.

Example 1 – An example of a <NotarizationType> element specifying that the notarization act was an Acknowledgment:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>.... </enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-02-07T15:19:17-08:00</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>
State of California
County of Santa Clara

I certify under PENALTY OF PERJURY under the laws of the
State of California that the foregoing paragraph is true
and correct.

4.44 Element <NotarizationDate>

The <NotarizationDate> element is used to identify the date and time of the notarization or witnessing act. It is the date and time the <NotarizedDocument> or <WitnessedDocument> was issued.

<xsd:element
name="NotarizationDate"
type="enml:DateTimeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="DateTimeType">
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>

The <NotarizationDate> element of the type DateTimeType from the ENML schema, requires a date in the following format:

There MUST be exactly ONE <NotarizationDate> element within a <CertificateContent> element.

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>.... </enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-01-27T13:01:05-08:00</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>...</enml:StatutoryContent>
</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.45 Element <NotarizationInternationalLocation>

The element <NotarizationInternationalLocation>, of type InternationalAddressType defined in the ENML schema, is used to carry the name of the physical location outside the USA where the <NotarizedDocument> was issued.

When used, there SHALL be only one <NotarizationInternationalLocation> element within the <NotarizedDocument> element. While issuers of <NotarizedDocument> are permitted to use as many elements as required from the InternationalAddressType, only the <Country> element is mandatory.

Schema Definition:

<xsd:element
name="NotarizationInternationalLocation"
type="enml:InternationalAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>.... </enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-02-07T15:19:17-08:00</enml:NotarizationDate>
<enml:NotarizationInternationalLocation>
<enml:StreetAddress1>490 Sussex Drive</enml:StreetAddress1>
<enml:City>Ottawa</enml:City>
<enml:State>Ontario</enml:State>
<enml:PostalCode>K2P 2N2</enml:PostalCode>
<enml:Country>Canada</enml:Country>
</enml:NotarizationInternationalLocation>
<enml:StatutoryContent>...</enml:StatutoryContent>
</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.46 Element <NotarizationUSLocation>

The element <NotarizationUSLocation>, of type USAddressType defined in the ENML schema, is used to identify the name of the physical location inside the USA where the <NotarizedDocument> was issued.

When used, there SHALL be only one <NotarizationUSLocation> element within the <NotarizedDocument> element. While issuers of <NotarizedDocument> are permitted to use as many elements as required from the USAddressType, only the <County>, <State> and <Country> elements are mandatory.

<xsd:element
name="NotarizationUSLocation"
type="enml:USAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

Example 1 – An example of a <NotarizationUSLocation> element that shows additional elements from the USAddressType in addition to the required sub-elements:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>.... </enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-02-07T15:19:17-08:00</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:StreetAddress1>10846 Via San Marino</enml:StreetAddress1>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>...</enml:StatutoryContent>
</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

Example 2 – An example of a <NotarizationUSLocation> element with minimum required sub-elements:

<enml:NotarizedDocument>
<enml:SignedDocuments>.... </enml:SignedDocuments>
<enml:DocumentSigners>.... </enml:DocumentSigners>
<enml:NotaryCertificates>
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-02-07T15:19:17-08:00</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>...</enml:StatutoryContent>
</enml:CertificateContent>
<enml:NotaryPublic>....</enml:NotaryPublic>
</enml:NotaryCertificates>
<enml:NotarySignatures>....</enml:NotarySignatures>
</enml:NotarizedDocument>

4.47 Element <ApostilleContent>

The <ApostilleContent> element of the ApostilleContentType, carries information about the apostille – the certified document issued by a competent authority for a jurisdiction, certifying the signature of the public official who signed the embedded document: either a <NotarizedDocument> or <WitnessedDocument>.

Schema Definition:

<xsd:element
name="ApostilleContent"
type="enml:ApostilleContentType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="ApostilleContentType">
<xsd:sequence>
<xsd:element
name="IssuingCountry"
type="enml:CountryType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="ApostilleNumber"
type="enml:ApostilleNumberType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="ApostilleDate"
type="enml:DateTimeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:choice>
<xsd:element
name="IssuedAtInternationalLocation"
type="enml:InternationalAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="IssuedAtUSLocation"
type="enml:USAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:choice>

<xsd:element
name="SignerTitle"
type="enml:PersonTitleType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="StatutoryContent"
minOccurs="1"
maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:token">
<xsd:enumeration
value="(Convention de La Haye du 5 octobre 1961)"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

<xsd:element
name="DocumentSigningOfficialName"
type="enml:PersonNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="DocumentSigningOfficialTitle"
type="enml:PersonTitleType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:element
name="DocumentSigningOfficialSeal"
type="enml:ApostilleSealType"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
<xsd:attribute name="Id" type="xsd:ID" use="required"/>
</xsd:complexType>

There MUST be exactly ONE <ApostilleContent> element in an <ApostillizedDocument> element.

The <ApostilleContent> element consists of a sequence of nine children elements and one ID attribute, all of which are required.

This element of type ApostilleNumberType, identifies the unique number of the apostille from the issuing-country. This number is, typically, determined by the competent authority of the jurisdiction issuing the apostille.

While each country is permitted to use numbers of its choice, the ENML specification recommends using the Processing Rule for ENML ID-types (Section 4.x) for this element. The advantage of doing so ensures a unique <ApostilleNumber> without the need to reference any other element. If this Processing Rule is not used, applications must qualify the <ApostilleNumber> with the <IssuingCountry> element to ensure uniqueness. There MUST be exactly ONE <ApostilleNumber> element in an <ApostilleContent> element.

The <ApostilleNumber> element is specified in Section 4.49.

This element of type DateTimeType, identifies the date, time and time-zone of the apostille from the issuing-country. There MUST be exactly ONE <ApostilleDate> element in an <ApostilleContent> element.

The <ApostilleDate> element is specified in Section 4.50.

This element represents the physical location where the apostille was issued. Depending on the geographical location – either an international or US-based location - this element must be a choice of either the <IssuedAtInternationalLocation> or the <IssuedAtUSLocation> element, respectively. It is the responsibility of the application generating the ENML-marked document to choose the appropriate element based on the jurisdiction of the certificate-issuer

There MUST be exactly ONE <IssuedAtInternationalLocation> or <IssuedAtUSLocation> element in an <ApostilleContent> element.

The <SignerTitle> element of PersonTitleType indicates who signed the apostille, thus certifying the signature of the public-official in the embedded <NotarizedDocument> or <WitnessedDocument>.

There MUST be exactly ONE <SignerTitle> element in a <ApostilleContent> element.

Please see Section 4.53 for a discussion of the Processing Rule for ID attributes within ENML.

Example 1 – An example of an <ApostillizedDocument> element issued in the USA:

Example 2 – An example of an <ApostillizedDocument> element issued in Canada:

<enml:ApostillizedDocument>
<enml:NotarizedDocument>.... </enml:NotarizedDocument>
<enml:ApostilleContent Id="ApostilleContent-CA-ON-XVL65986-1226972923-89e89c11cac335b3d7c1030f78ffca5527cbd4cc61479fc88526c38e01d912a5">
<enml:IssuingCountry>Canada</enml:IssuingCountry>
<enml:ApostilleNumber>
ApostilleNumber-CA-ON-XVL65986-1226971821-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4
</enml:ApostilleNumber>
<enml:ApostilleDate>2008-11-17T12:13:14-08:00</enml:ApostilleDate>
<enml:IssuedAtInternationalLocation>
<enml:City>Ottawa</enml:City>
<enml:State>Ontario</enml:State>
<enml:Country>Canada</enml:Country>
</enml:IssuedAtInternationalLocation>
<enml:SignerTitle>
Secretary of State, State of Ontario
</enml:SignerTitle>
<enml:StatutoryContent>
(Convention de La Haye du 5 octobre 1961)
</enml:StatutoryContent>
<enml:DocumentSigningOfficialName>
<enml:PersonFirstName>Giacomo</enml:PersonFirstName>
<enml:PersonLastName>Puccini</enml:PersonLastName>
</enml:DocumentSigningOfficialName>
<enml:DocumentSigningOfficialTitle>
Notary Public
</enml:DocumentSigningOfficialTitle>
<enml:DocumentSigningOfficialSeal>
<enml:TextSeal>
Notary Public, State of Ontario
</enml:TextSeal>
</enml:DocumentSigningOfficialSeal>
</enml:ApostilleContent>
<ds:Signature>....</ds:Signature>
</enml:ApostillizedDocument>

4.48 Element <IssuingCountry>

The <IssuingCountry> element carries the name of the country issuing an <ApostillizedDocument>.

The required <IssuingCountry> element is of the CountryType from the ENML schema. The CountryType uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="IssuingCountry"
type="enml:CountryType"
minOccurs="1"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="CountryType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="64"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

Example 1 – An example of an <ApostillizedDocument> with an <IssuingCountry> element.

4.49 Element <ApostilleNumber>

The <ApostilleNumber> element carries the unique certificate number of the <ApostillizedDocument>.

The required <ApostilleNumber> element is of the ApostilleNumberType from the ENML schema. The ApostilleNumberType uses the xsd:string type from the XML Schema Definition as the base type, with a restriction to allow up a maximum of 64-characters for the element, while preserving all white-space characters within its content.

<xsd:element
name="ApostilleNumber"
type="enml:ApostilleNumberType"
minOccurs="1"
maxOccurs="1"/>
</xsd:element>

<xsd:simpleType name="ApostilleNumberType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1024"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

Example 1 – An example of an <ApostillizedDocument> with an <ApostilleNumber> element. This example uses the ENML Processing Rule derived value (highly recommended):

4.50 Element <ApostilleDate>

The <ApostilleDate> element is used to identify the date and time when the electronic <ApostillizedDocument> was issued. It also specifies the time-zone where the apostille is signed.

The <ApostilleDate> element of the type DateTimeType from the ENML schema, requires a date in the following format:

where CCYY denotes the 4-digit calendar year, MM denotes the 2-digit month of the year and DD denotes the 2-digit day-of-month; the “T” is a fixed value; hh denotes the hour of day in 24-hour format, mm denotes the minute of the hour and ss denotes the second within the minute. The time-zone may be specified either with a fixed “Z” which then implies that the preceding time is specified in Coordinated Universal Time (UTC), or it may be specified with the number of hours and minutes ahead or behind UTC, with a + or – sign respectively. There MUST be exactly ONE <ApostilleDate> element within a <ApostillizedDocument> element.

<xsd:element
name="ApostilleDate"
type="enml:DateTimeType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="DateTimeType">
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>

Example 1 – An example of an <ApostillizedDocument> with an <ApostilleDate> element.

4.51 Element <IssuedAtInternationalLocation>

The element <IssuedAtInternationalLocation>, of type InternationalAddressType defined in the ENML schema, is used to carry the name of the physical location outside the USA where the <ApostillizedDocument> was issued.

When used, there SHALL be only one <IssuedAtInternationalLocation> element within the <ApostillizedDocument> element. While issuers of <ApostillizedDocument> are permitted to use as many elements as required from the InternationalAddressType, only the <Country> element is mandatory. Based on current conventions, this is sufficient for an <ApostillizedDocument>.

Schema Definition:

<xsd:element
name="IssuedAtInternationalLocation"
type="enml:InternationalAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

Example 1 – An example of an <ApostillizedDocument> with an <IssuedAtInternationalLocation> element. The <City> and <State> elements are not mandatory for an <ApostillizedDocument>, but are shown here as an example of additional elements that can be included in the <IssuedAtInternationalLocation> element:

<enml:ApostillizedDocument>
<enml:NotarizedDocument>.... </enml:NotarizedDocument>
<enml:ApostilleContent Id="ApostilleContent-CA-ON-XVL65986-1226972923-89e89c11cac335b3d7c1030f78ffca5527cbd4cc61479fc88526c38e01d912a5">
<enml:IssuingCountry>Canada</enml:IssuingCountry>
<enml:ApostilleNumber>
ApostilleNumber-CA-ON-XVL65986-1226971821-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4
</enml:ApostilleNumber>
<enml:ApostilleDate>2008-11-17T12:15:23-05:00</enml:ApostilleDate>
<enml:IssuedAtInternationalLocation>
<enml:City>Ottawa</enml:City>
<enml:State>Ontario</enml:State>
<enml:Country>Canada</enml:Country>
</enml:IssuedAtInternationalLocation>
<enml:SignerTitle>
Secretary of State, State of Ontario
</enml:SignerTitle>
<enml:StatutoryContent>
(Convention de La Haye du 5 octobre 1961)
</enml:StatutoryContent>
<enml:DocumentSigningOfficialName>
<enml:PersonFirstName>Giacomo</enml:PersonFirstName>
<enml:PersonLastName>Puccini</enml:PersonLastName>
</enml:DocumentSigningOfficialName>
<enml:DocumentSigningOfficialTitle>
Notary Public
</enml:DocumentSigningOfficialTitle>
<enml:DocumentSigningOfficialSeal>
<enml:TextSeal>
Notary Public, State of Ontario
</enml:TextSeal>
</enml:DocumentSigningOfficialSeal>
</enml:ApostilleContent>
<ds:Signature>....</ds:Signature>
</enml:ApostillizedDocument>

4.52 Element <IssuedAtUSLocation>

The element <IssuedAtUSLocation>, of type USAddressType defined in the ENML schema, is used to carry the name of the physical location inside the USA where the <ApostillizedDocument> was issued.

When used, there SHALL be only one <IssuedAtUSLocation> element within the <ApostillizedDocument> element. While issuers of <ApostillizedDocument> are permitted to use as many elements as required from the USAddressType, only the <City>, <State> and <Country> elements are mandatory. Based on current conventions, this is more than sufficient for an US-issued <ApostillizedDocument>.

<xsd:element
name="IssuedAtUSLocation"
type="enml:USAddressType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

Example 1 – An example of an <ApostillizedDocument> with an <IssuedAtUSLocation> element. The <County> and <State> elements are not mandatory for an <ApostillizedDocument>, but are necessary for an USAddressType and are included here:

4.53 Element <DocumentSigningOfficialName>

The <DocumentSigningOfficialName> element, of the type PersonNameType defined in the ENML schema, carries the full name of a Notary Public who either notarized or witnessed the signing of the embedded document within the <ApostillizedDocument>.

<xsd:element
name="DocumentSigningOfficialName"
type="enml:PersonNameType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

Example 1 – An example of an <ApostillizedDocument> with an <DocumentSigningOfficialName> element.

4.54 Element <DocumentSigningOfficialTitle>

The <DocumentSigningOfficialTitle> element, of the type PersonTitleType defined in the ENML schema, carries the official title of the Notary Public who either notarized or witnessed the signing of the embedded document within the <ApostillizedDocument>.

<xsd:element
name="DocumentSigningOfficialTitle"
type="enml:PersonTitleType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:simpleType name="PersonTitleType">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="256"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>

Example 1 – An example of an <ApostillizedDocument> with an <DocumentSigningOfficialTitle> element.

4.55 Element <DocumentSigningOfficialSeal>

The <DocumentSigningOfficialSeal> element, of the type ApostilleSealType defined in the ENML schema, carries the official seal of the Notary Public who either notarized or witnessed the signing of the embedded document within the <ApostillizedDocument>.

<xsd:element
name="DocumentSigningOfficialSeal"
type="enml:ApostilleSealType"
minOccurs="1"
maxOccurs="1">
</xsd:element>

<xsd:complexType name="ApostilleSealType">
<xsd:choice>
<xsd:element name="TextSeal">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1024"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

<xsd:element
name="X509CertificateSeal"
type="xsd:base64Binary">
</xsd:element>
</xsd:choice>
</xsd:complexType>

The <DocumentSigningOfficialSeal> element may consist of a choice of one the following elements:

This element carries an electronic image of the seal of the public-official who signed the embedded <NotarizedDocument> or <WitnessedDocument>. The content in this element MUST be Base64-encoded GIF seal image. If used, there MUST be exactly ONE <GIFImageSeal> element in an <DocumentSigningOfficialSeal> element

This element carries an electronic image of the seal of the public-official who signed the embedded <NotarizedDocument> or <WitnessedDocument>. The content in this element MUST be Base64-encoded JPEG seal image. If used, there MUST be exactly ONE <JPEGImageSeal> element in an <DocumentSigningOfficialSeal> element.

This element carries an electronic image of the seal of the public-official who signed the embedded <NotarizedDocument> or <WitnessedDocument>. The content in this element MUST be Base64-encoded PNG seal image. If used, there MUST be exactly ONE <PNGImageSeal> element in an <DocumentSigningOfficialSeal> element.

This element carries the Bse64-encoded X509-compliant digital certificate seal of the public-official who signed the embedded <NotarizedDocument> or <WitnessedDocument>. If used, there MUST be exactly ONE <X509CertificateSeal> element in an <DocumentSigningOfficialSeal> element.

There MUST be exactly ONE <DocumentSigningOfficialSeal> element within an <ApostilleContent> element.

Example 1 – An example of an <ApostillizedDocument> with a <TextSeal> in an <DocumentSigningOfficialSeal> element.

Example 2 – An example of an <ApostillizedDocument> with a <X509CertificateSeal> in an <DocumentSigningOfficialSeal> element.

<enml:ApostillizedDocument>
<enml:NotarizedDocument>.... </enml:NotarizedDocument>
<enml:ApostilleContent Id="ApostilleContent-US-CA-1565986-1226972923-89e89c11cac335b3d7c1030f78ffca5527cbd4cc61479fc88526c38e01d912a5">
<enml:IssuingCountry>United States of America</enml:IssuingCountry>
<enml:ApostilleNumber>
ApostilleNumber-US-CA-1565986-1226971821-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4
</enml:ApostilleNumber>
<enml:ApostilleDate>2008-11-17T15:45:28-08:00</enml:ApostilleDate>
<enml:IssuedAtUSLocation>
<enml:County>Sacramento</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:IssuedAtUSLocation>
<enml:SignerTitle>
Secretary of State, State of California
</enml:SignerTitle>
<enml:StatutoryContent>
(Convention de La Haye du 5 octobre 1961)
</enml:StatutoryContent>
<enml:DocumentSigningOfficialName>
<enml:PersonFirstName>Arshad</enml:PersonFirstName>
<enml:PersonLastName>Noor</enml:PersonLastName>
</enml:DocumentSigningOfficialName>
<enml:DocumentSigningOfficialTitle>
Notary Public
</enml:DocumentSigningOfficialTitle>
<enml:DocumentSigningOfficialSeal>
<enml:X509CertificateSeal>
MIIDfDCCAmSgAwIBAgIIAe/AvliGc3AwDQYJKoZIhvcNAQELBQAwZzEmMCQGA1UEAxMdU3Ryb25n
S2V5IERFTU8gU3Vib3JkaW5hdGUgQ0ExJDAiBgNVBAsTG0ZvciBTdHJvbmdLZXkgREVNTyBVc2Ug
T25seTEXMBUGA1UEChMOU3Ryb25nQXV0aCBJbmMwHhcNMDYwNzI1MTcxMDMwWhcNMDcwNzI1MTcy
MDMwWjBtMREwDwYKCZImiZPyLGQBARMBMjEZMBcGA1UEAxMQUE9TIFJlZ2lzdGVyIDIyMjEkMCIG
A1UECxMbRm9yIFN0cm9uZ0tleSBERU1PIFVzZSBPbmx5MRcwFQYDVQQKEw5TdHJvbmdBdXRoIElu
YzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAyAmxMZhYA8wHJ4UE4b61s51JVWe4Fygj4MCf
U7LA3JhpUS4TlX0XFWqrcmltLOiVG7YBFarJFluBFJW2X6q8FuvUprv4V9nJrgiwAPtkiRyIx96n
qKXIxkUlQ4idlEg1AZI9dEdf4Y5cqBBCygPYnBoTudglM7R47AjR4nr4ks8CAwEAAaOBqTCBpjAO
BgNVHQ8BAf8EBAMCBLAwHQYDVR0OBBYEFOIOrWrZo0LdBRLVncRAwLBqVZpCMB8GA1UdIwQYMBaA
FPTYwEHoJG4iFVHRnt2EWxGluAQVMBgGA1UdIAQRMA8wDQYLKwYEAdISg30BBAEwOgYDVR0fBDMw
MTAvoC2gK4YpaHR0cDovL2RlbW8uc3Ryb25na2V5Lm9yZy9kZW1vLXN1Yi1jYS5jcmwwDQYJKoZI
hvcNAQELBQADggEBACK05PtvZD4WPglOe+EHUiApzFyCdRzf0pFZtxRwG9lR1PZUWUjmwTNfGFsL
S6kyoHgUfVa5fpT1EU1mXUB/Lmo3hFGyprZjfmD7DwuBcYgmZHv7yHrmGOMIOXjFTACvHpM0vOce
hVx2e4VE0yhBLu/ldH9awGGDp6Bk2XzxqQcs8y6ZzOXZAnPgKQZdjbFKERSsy/d1D8pk5baBk4bd
Zh568OcaUrbm9ZReRVTVaY5qiQpkOU+tDrBSj/HIL6GAqegYllkz6KYCy6RVOy6iVVSjHocDqdJr
EVOR+ds6xn8mmojdlERrILmuxiLpibPp609SfnDIxNlzLwe5g7ep3lc=
</enml:X509CertificateSeal>
</enml:DocumentSigningOfficialSeal>
</enml:ApostilleContent>
<ds:Signature>....</ds:Signature>
</enml:ApostillizedDocument>

4.56 Processing Rule for ID attributes within ENML

To ensure that the <Signature>, <SignerSignature>, <NotarySignature> and <ApostilleSignature> elements refer to the precise elements being signed within the ENML-based document, ENML has chosen to explicitly identify those elements being signed through <Reference> elements in the different signature elements. Additionally, since the <NotarizedDocument> and the <WitnessedDocument> elements may appear within an <ApostillizedDocument>, it is necessary for these elements to also carry a unique ID value.

The identification is accomplished through the mandatory use of the ID attribute (of the xsd:ID type from the XML Schema Definition) for the following required elements in ENML-based documents:

Given that there may be millions of eNotarized, eWitnessed and eApostillized documents, it is critical that documents not duplicate the value of the ID attribute for these elements.

ENML, therefore, requires that conforming implementations MUST generate the value of the ID attribute using the following algorithm for seven (7) of the above-mentioned eight (8) elements. It is only recommended for the <ApostilleNumber> element, but not mandated.

While the above algorithm cannot absolutely guarantee that the value generated for the ID attribute will be unique, it is the contention of this TC that the probability of values being identical for different eNotarized, eWitnessed or eApostillized document are extremely low.

Example 1 – This example shows a <SignedDocument> that has the following ID attribute value. In this example, the:

- SignedDocument refers to the name of the element (step 1);
- US refers to the 2-character [ISO-3166-1] country code for the USA (step 3);
- CA refers to the 2-character state abbreviation for California within the US (step 5);
- 1565986 refers to the unique Commission number of the Notary Public notarizing this document (step 7);
- 1222646651 refers to the epoch time at the time of generating this value (step 9);
- c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4 refers to the
SHA-256 message digest of the <SignedDocument> element (step 11);

Note: The SHA-256 digest is not necessarily cryptographically valid for this element; it is shown here as an illustration of what the ID value might look like applying this processing rule.

<enml:SignedDocuments>
<enml:SignedDocument Id="SignedDocument-US-CA-1565986-1222646651-c4e7f79729ad7da392d3a18023243532a0e30067350d4698974d5a2e7bd09ee4">
<enml:Document>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KCjwhLS0KICBM
ZwdhbFhNTCBlTm90YXJpemF0aW9uIDEuMCBTcGVjaWZpY2F0aW9uCgogIDA5IERl
Y2VtYmVyIDIwMDcgQWxsIFJpZ2h0cyBSZXNlcnZlZC4KCiAgVGhpcyBkb2N1bWVu
dCBhbmQgdHJhbnNsYXRpb25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5p
c2hlZCB0byBvdGhlcnMsIAogIGFuZCBkZXJpdmF0aXZlIHdvcmtzIHRoYXQgY29t
bWVudCBvbiBvciBvdGhlcndpc2UgZXhwbGFpbiBpdCBvciBhc3Npc3QgaW4gaXRz ICAgICAtLT4KICAgICAKPC94c2Q6c2NoZW1hPgo=
</enml:Document>
<enml:DocumentMIMEType>application/xml</enml:DocumentMIMEType>
<enml:DocumentComments>Property Deed</enml:DocumentComments>
</enml:SignedDocument>
</enml:SignedDocuments>

Example 2 – This example shows a <DocumentSigner> that has the following ID attribute value. In this example, the:

- DocumentSigner refers to the name of the element (step 1);
- US refers to the 2-character [ISO-3166-1] country code for the USA (step 3);
- CA refers to the 2-character state abbreviation for California within the US (step 5);
- 1565986 refers to the unique Commission number of the Notary Public notarizing this document (step 7);
- 1222643107 refers to the epoch time at the time of generating this value (step 9);
- f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7 refers to the
SHA-256 message digest of the <DocumentSigner> element (step 11);

Note: The SHA-256 digest is not necessarily cryptographically valid for this element; it is shown here as an illustration of what the ID value might look like applying this processing rule.

<enml:DocumentSigners>
<enml:DocumentSigner Id="DocumentSigner-US-CA-1565986-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
<enml:SignerName>
<enml:PersonFirstName>John</enml:PersonFirstName>
<enml:PersonLastName>Doe</enml:PersonLastName>
</enml:SignerName>
<enml:SignerIdentificationMethod>
Produced Government-issued Identification Document
</enml:SignerIdentificationMethod>
<enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>

Example 3 – This example shows a <NotaryCertificate> that has the following ID attribute value. In this example, the:

- NotaryCertificate refers to the name of the element (step 1);
- US refers to the 2-character [ISO-3166-1] country code for the USA (step 3);
- CA refers to the 2-character state abbreviation for California within the US (step 5);
- 1565986 refers to the unique Commission number of the Notary Public notarizing this document (step 7);
- 1222643229 refers to the epoch time at the time of generating this value (step 9);
- 1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f refers to the
SHA-256 message digest of the <DocumentSigner> element (step 11);

Note: The SHA-256 digest is not necessarily cryptographically valid for this element; it is shown here as an illustration of what the ID value might look like applying this processing rule.

<enml:NotaryCertificates>
<enml:NotaryCertificate Id="NotaryCertificate-US-CA-1565986-1222643229-
1963a865f3516996f711936045ced816a0fccd4aca57c6807a1c44f9b98a1e5f">
<enml:CertificateContent>
<enml:NotarizationType>Acknowledgment</enml:NotarizationType>
<enml:NotarizationDate>2007-01-27T15:45:28-08:00</enml:NotarizationDate>
<enml:NotarizationUSLocation>
<enml:City>Cupertino</enml:City>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotarizationUSLocation>
<enml:StatutoryContent>
State of California
County of Santa Clara

On January 27 2008, before me Arshad Noor, personally
appeared John Doe and Jane Doe, who proved to me on the
basis of satisfactory evidence to be the persons whose
names are subscribed to the within instrument and
acknowledged to me that they executed the same in their
authorized capacity, and that by their signature on the
instrument the persons, or the entity upon behalf of
which the persons acted, executed the instrument.

I certify under PENALTY OF PERJURY under the laws of the
State of California that the foregoing paragraph is true
and correct.

WITNESS my hand and official seal.
</enml:StatutoryContent>
</enml:CertificateContent>

<enml:NotaryPublic>
<enml:NotaryName>
<enml:PersonGivenName>Arshad</enml:PersonGivenName>
<enml:PersonSurName>Noor</enml:PersonSurName>
</enml:NotaryName>
<enml:NotaryCommissionNumber>1565986</enml:NotaryCommissionNumber>
<enml:NotaryCommissionExpiryDate>
2009-04-29T23:59:59-08:00
</enml:NotaryCommissionExpiryDate>
<enml:NotaryUSJurisdiction>
<enml:County>Santa Clara</enml:County>
<enml:USState>CA</enml:USState>
<enml:Country>USA</enml:Country>
</enml:NotaryUSJurisdiction>
</enml:NotaryPublic>
</enml:NotaryCertificate>
</enml:NotaryCertificates>

Example 4 – This example shows a <DocumentSigner> that has the following ID attribute value. In this example, the:

- DocumentSigner refers to the name of the element (step 1);
- BB refers to the 2-character [ISO-3166-1] country code for the Barbados (step 3);
- KI refers to the first 2-characters of the city name (Kingston) when there is no state abbreviation
available (step 5);
- HowardQJones refers to the full-name of the NotaryPublic, concatenated with no spaces between
the name, and with the first letter of each part of the name capitalized, when there is no
unique Commission number of the Notary Public notarizing this document is available (step 7);
- 1222643107 refers to the epoch time at the time of generating this value (step 9);
- f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7 refers to the
SHA-256 message digest of the <DocumentSigner> element (step 11);

Note: The SHA-256 digest is not necessarily cryptographically valid for this element; it is shown here as an illustration of what the ID value might look like applying this processing rule.

<enml:DocumentSigners>
<enml:DocumentSigner Id="DocumentSigner-BB-KI-HowardQJones-1222643107-f91b09f20bfa099beb6b1cb493dfdd9571c3edac5c23fa36aace2afd6d273fd7">
<enml:SignerName>
<enml:PersonFirstName>John</enml:PersonFirstName>
<enml:PersonLastName>Doe</enml:PersonLastName>
</enml:SignerName>
<enml:SignerIdentificationMethod>
Produced Government-issued Identification Document
</enml:SignerIdentificationMethod>
<enml:SignerSignature>Signed by John Doe</enml:SignerSignature>
</enml:DocumentSigner>
</enml:DocumentSigners>

5 Conformance

An implementation conforms to this specification if it satisfies all of the MUST, REQUIRED or SHALL level requirements defined within this specification. An ENML Node MUST NOT use the XML namespace identifier for this specification (listed in the Title section under Declared Namespace(s)) unless it is compliant with this specification.

This specification references a number of other specifications (see the table above). In order to comply with this specification, an implementation MUST implement the portions of referenced specifications necessary to comply with the required provisions of this specification. Additionally, the implementation of the portions of the referenced specifications that are specifically cited in this specification MUST comply with the rules for those portions as established in the referenced specification.

Additionally normative text within this specification takes precedence over normative outlines, which in turn take precedence over the XML Schema [XML Schema Part 1, Part 2] descriptions. That is, the normative text in this specification further constrains the schema part of this specification; and this specification contains further constraints on the elements defined in referenced schemas.

If an OPTIONAL message is not supported, then the implementation SHOULD Fault just as it would for any other unrecognized/unsupported message. If an OPTIONAL message is supported, then the implementation MUST satisfy all of the MUST and REQUIRED sections of the message.

The following individuals have participated in the creation of this specification and are gratefully acknowledged

The OASIS LegalXML eNotary TC has determined that it is useful to standardize on the structure and content of error and informational messages within ENML so that implementations and their users are clear about the problem they are dealing with eNotarized documents.

Structure

The following structure is proposed for ENML-based messages. The message will consist of a three-part string, with each part separated from the others by a hyphen (“-”). The 3-part message consists of the following:

Thus, an ENML error message might look like the following: ENML-ERR-NNNNN; and an ENML informational message might look like the following: ENML-MSG-NNNNN

Five-digit Codes

The 5-digit integer is divided into the following groups to ensure consistency amongst implementations:

ENML Standard Code-ranges

The 5-digit code range reserved for OASIS LegalXML eNotary TC ENML standards use will be reserved as follows:

Code-range	Reserved for
00001 - 00099	Authentication related errors and messages
00100 - 00199	Authorization related errors and messages
00200 - 00299	Cryptographic-module related errors and messages
00300 - 00399	Notarized Document related errors and messages
00400 - 00499	Witnessed Document related errors and messages
00500 - 00599	Apostillized Document related errors and messages
00600 - 00699	Signed Documents related errors and messages
00700 - 00799	Document Signers related errors and messages
00800 - 00899	Notary Certificates related errors and messages
00900 - 00999	Notaries Public related errors and messages
01000 - 01099	Notary Signatures related errors and messages
01100 - 01199	Miscellaneous errors and messages
01200 - 10000	Future OASIS LegalXML eNotary TC use

Note: The {0} symbol at the end of each message is a placeholder for a parameter that can be used by implementations for adding additional information pertaining to the error. The additional information will be useful to administrators and software developers in helping them focus on the part of the system where the underlying problem has manifested itself.

Authentication ERROR Codes (00001 - 00099)

Authorization ERROR Codes (00100 - 00199)

Code	Message
ENML-ERR-00001	Authentication failure – invalid signature: {0}
ENML-ERR-00002	Authentication failure – invalid status: {0}
ENML-ERR-00003	Authentication failure – unverifiable certificate: {0}
ENML-ERR-00004	Authentication failure – expired certificate: {0}
ENML-ERR-00005	Authentication failure – revoked certificate: {0}
ENML-ERR-00006	Authentication failure – revoked certificate issuer: {0}
ENML-ERR-00007	Authentication failure – missing certificate: {0}
ENML-ERR-00008	Authentication failure – missing certificate keyUsage: {0}
ENML-ERR-00009	Authentication failure – missing certificate crlDistributionPoint: {0}
ENML-ERR-00010	Authentication failure – missing certificate authorityInfoAccess: {0}
ENML-ERR-00011	Authentication failure – invalid certificate Subject DN: {0}
ENML-ERR-00012	Authentication failure – invalid certificate Validity: {0}
ENML-ERR-00013	Authentication failure – invalid certificate keyUsage: {0}
ENML-ERR-00014	Authentication failure – invalid certificate crlDistributionPoint: {0}
ENML-ERR-00015	Authentication failure – invalid certificate authorityInfoAccess: {0}
ENML-ERR-00016	Authentication failure – unreachable certificate crlDistributionPoint: {0}
ENML-ERR-00017	Authentication failure – unreachable certificate authorityInfoAccess: {0}
ENML-ERR-00099	Authentication failure – other authentication error: {0}

Code	Message
ENML-ERR-00101	Authorization failure – invalid signature: {0}
ENML-ERR-00102	Authorization failure – invalid status: {0}
ENML-ERR-00103	Authorization failure – invalid requester: {0}
ENML-ERR-00104	Authorization failure – invalid request: {0}
ENML-ERR-00105	Authorization failure – invalid identifier: {0}
ENML-ERR-00106	Authorization failure – invalid policy: {0}
ENML-ERR-00107	Authorization failure – invalid role: {0}
ENML-ERR-00108	Authorization failure – invalid application: {0}
ENML-ERR-00109	Authorization failure – invalid date: {0}
ENML-ERR-00110	Authorization failure – invalid day: {0}
ENML-ERR-00111	Authorization failure – invalid time: {0}
ENML-ERR-00112	Authorization failure – invalid use: {0}
ENML-ERR-00113	Authorization failure – unauthorized access: {0}
ENML-ERR-00114	Authorization failure – unauthorized date: {0}
ENML-ERR-00115	Authorization failure – unauthorized day: {0}
ENML-ERR-00116	Authorization failure – unauthorized time: {0}
ENML-ERR-00117	Authorization failure – unauthorized use: {0}
ENML-ERR-00199	Authorization failure – other authorization error: {0}

Cryptographic-module ERROR Codes (00200 - 00299)

Code	Message
ENML-ERR-00201	Cryptographic-module failure – invalid signature: {0}
ENML-ERR-00202	Cryptographic-module failure – invalid status: {0}
ENML-ERR-00203	Cryptographic-module failure – invalid cryptographic provider: {0}
ENML-ERR-00204	Cryptographic-module failure – invalid algorithm: {0}
ENML-ERR-00205	Cryptographic-module failure – invalid initialization vector: {0}
ENML-ERR-00206	Cryptographic-module failure – invalid padding: {0}
ENML-ERR-00207	Cryptographic-module failure – invalid key-size: {0}
ENML-ERR-00208	Cryptographic-module failure – invalid password or PIN: {0}
ENML-ERR-00209	Cryptographic-module failure – missing cryptographic provider: {0}
ENML-ERR-00210	Cryptographic-module failure – missing cryptographic module: {0}
ENML-ERR-00211	Cryptographic-module failure – missing password or PIN: {0}
ENML-ERR-00212	Cryptographic-module failure – missing private key: {0}
ENML-ERR-00213	Cryptographic-module failure – missing digital certificate: {0}
ENML-ERR-00214	Cryptographic-module failure – missing certificate chain: {0}
ENML-ERR-00215	Cryptographic-module failure – failed to sign: {0}
ENML-ERR-00216	Cryptographic-module failure – failed to verify: {0}
ENML-ERR-00217	Cryptographic-module failure – failed to encrypt: {0}
ENML-ERR-00218	Cryptographic-module failure – failed to decrypt: {0}
ENML-ERR-00219	Cryptographic-module failure – failed to digest (hash): {0}
ENML-ERR-00220	Cryptographic-module failure – failed to generate key: {0}
ENML-ERR-00299	Cryptographic-module failure – other cryptographic-module error: {0}

Notarized Document ERROR Codes (00300 - 00399)

Code	Message
ENML-ERR-00301	Notarized Document failure – invalid signature: {0}
ENML-ERR-00302	Notarized Document failure – invalid status: {0}
ENML-ERR-00303	Notarized Document failure – invalid ID attribute: {0}
ENML-ERR-00304	Notarized Document failure – invalid content: {0}
ENML-ERR-00305	Notarized Document failure – missing ID attribute: {0}
ENML-ERR-00306	Notarized Document failure – missing content: {0}
ENML-ERR-00399	Notarized Document failure – other Notarized Document error: {0}

Witnessed Document ERROR Codes (00400 - 00499)

Code	Message
ENML-ERR-00401	Witnessed Document failure – invalid signature: {0}
ENML-ERR-00402	Witnessed Document failure – invalid status: {0}
ENML-ERR-00403	Witnessed Document failure – invalid ID attribute: {0}
ENML-ERR-00404	Witnessed Document failure – invalid content: {0}
ENML-ERR-00405	Witnessed Document failure – missing ID attribute: {0}
ENML-ERR-00406	Witnessed Document failure – missing content: {0}
ENML-ERR-00499	Witnessed Document failure – other Witnessed Document error: {0}

Apostillized Document ERROR Codes (00500 - 00599)

Code	Message
ENML-ERR-00501	Apostillized Document error - invalid signature: {0}
ENML-ERR-00502	Apostillized Document error - invalid status: {0}
ENML-ERR-00503	Apostillized Document error - invalid ID attribute: {0}
ENML-ERR-00504	Apostillized Document error - invalid Notarized Document: {0}
ENML-ERR-00505	Apostillized Document error - invalid Witnessed Document: {0}
ENML-ERR-00506	Apostillized Document error - invalid Issuing Country: {0}
ENML-ERR-00507	Apostillized Document error - invalid Apostille Number: {0}
ENML-ERR-00508	Apostillized Document error - invalid Apostille Date: {0}
ENML-ERR-00509	Apostillized Document error - invalid International Location: {0}
ENML-ERR-00510	Apostillized Document error - invalid US Location: {0}
ENML-ERR-00511	Apostillized Document error - invalid Signer Title: {0}
ENML-ERR-00512	Apostillized Document error - invalid Statutory Content: {0}
ENML-ERR-00513	Apostillized Document error - invalid Document Signing Official Name: {0}
ENML-ERR-00514	Apostillized Document error - invalid Document Signing Official Title: {0}
ENML-ERR-00515	Apostillized Document error - invalid Document Signing Official Seal: {0}
ENML-ERR-00516	Apostillized Document error - missing ID attribute: {0}
ENML-ERR-00517	Apostillized Document error - missing Notarized Document: {0}
ENML-ERR-00518	Apostillized Document error - missing Witnessed Document: {0}
ENML-ERR-00519	Apostillized Document error - missing Issuing Country: {0}
ENML-ERR-00520	Apostillized Document error - missing Apostille Number: {0}
ENML-ERR-00521	Apostillized Document error - missing Apostille Date: {0}
ENML-ERR-00522	Apostillized Document error - missing International Location: {0}
ENML-ERR-00523	Apostillized Document error - missing US Location: {0}
ENML-ERR-00524	Apostillized Document error - missing Signer Title: {0}
ENML-ERR-00525	Apostillized Document error - missing Statutory Content: {0}
ENML-ERR-00526	Apostillized Document error - missing Document Signing Official Name: {0}
ENML-ERR-00527	Apostillized Document error - missing Document Signing Official Title: {0}
ENML-ERR-00528	Apostillized Document error - missing Document Signing Official Seal: {0}
ENML-ERR-00599	Apostillized Document error - other Apostillized Document error: {0}

Signed Documents ERROR Codes (00600 - 00699)

Code	Message
ENML-ERR-00601	Signed Documents error - invalid signature: {0}
ENML-ERR-00602	Signed Documents error - invalid status: {0}
ENML-ERR-00603	Signed Documents error - invalid ID attribute: {0}
ENML-ERR-00604	Signed Documents error - invalid Document: {0}
ENML-ERR-00605	Signed Documents error - invalid Document MIME Type: {0}
ENML-ERR-00606	Signed Documents error - invalid Document MIME Type Comments: {0}
ENML-ERR-00607	Signed Documents error - invalid Document Comments: {0}
ENML-ERR-00608	Signed Documents error - missing ID attribute: {0}
ENML-ERR-00609	Signed Documents error - missing Document: {0}
ENML-ERR-00610	Signed Documents error - missing Document MIME Type: {0}
ENML-ERR-00611	Signed Documents error - missing Document MIME Type Comments: {0}
ENML-ERR-00612	Signed Documents error - missing Document Comments: {0}
ENML-ERR-00699	Signed Documents error - other error: {0}

Document Signers ERROR Codes (00700 - 00799)

Notary Certificates ERROR Codes (00800 - 00899)

Code	Message
ENML-ERR-00701	Document Signers error - invalid signature: {0}
ENML-ERR-00702	Document Signers error - invalid status: {0}
ENML-ERR-00703	Document Signers error - invalid ID attribute: {0}
ENML-ERR-00704	Document Signers error - invalid Signer Name: {0}
ENML-ERR-00705	Document Signers error - invalid Signer Title: {0}
ENML-ERR-00706	Document Signers error - invalid International Address: {0}
ENML-ERR-00707	Document Signers error - invalid US Address: {0}
ENML-ERR-00708	Document Signers error - invalid Identification Method: {0}
ENML-ERR-00709	Document Signers error - invalid Signature: {0}
ENML-ERR-00710	Document Signers error - invalid Signed Info: {0}
ENML-ERR-00711	Document Signers error - invalid Signature Value: {0}
ENML-ERR-00712	Document Signers error - invalid Key Info: {0}
ENML-ERR-00713	Document Signers error - invalid Object: {0}
ENML-ERR-00714	Document Signers error - missing ID attribute: {0}
ENML-ERR-00715	Document Signers error - missing Signer Name: {0}
ENML-ERR-00716	Document Signers error - missing Signer Title: {0}
ENML-ERR-00717	Document Signers error - missing International Address: {0}
ENML-ERR-00718	Document Signers error - missing US Address: {0}
ENML-ERR-00719	Document Signers error - missing Identification Method: {0}
ENML-ERR-00720	Document Signers error - missing Signature: {0}
ENML-ERR-00721	Document Signers error - missing Signed Info: {0}
ENML-ERR-00722	Document Signers error - missing Signature Value: {0}
ENML-ERR-00723	Document Signers error - missing Key Info: {0}
ENML-ERR-00724	Document Signers error - missing Object: {0}
ENML-ERR-00799	Document Signers error - other error: {0}

Code	Message
ENML-ERR-00801	Notary Certificates error - invalid signature: {0}
ENML-ERR-00802	Notary Certificates error - invalid status: {0}
ENML-ERR-00803	Notary Certificates error - invalid ID attribute: {0}
ENML-ERR-00804	Notary Certificates error - invalid Notarization Type: {0}
ENML-ERR-00805	Notary Certificates error - invalid Notarization Date: {0}
ENML-ERR-00806	Notary Certificates error – invalid International Location: {0}
ENML-ERR-00807	Notary Certificates error - invalid US Location: {0}
ENML-ERR-00808	Notary Certificates error - invalid Statutory Content: {0}
ENML-ERR-00809	Notary Certificates error - missing ID attribute: {0}
ENML-ERR-00810	Notary Certificates error - missing Notarization Type: {0}
ENML-ERR-00811	Notary Certificates error - missing Notarization Date: {0}
ENML-ERR-00812	Notary Certificates error – missing International Location: {0}
ENML-ERR-00813	Notary Certificates error - missing US Location: {0}
ENML-ERR-00814	Notary Certificates error – missing Statutory Content: {0}
ENML-ERR-00899	Notary Certificates error - other error: {0}

Notaries Public ERROR Codes (00900 - 00999)

Code	Message
ENML-ERR-00901	Notaries Public error - invalid signature: {0}
ENML-ERR-00902	Notaries Public error - invalid status: {0}
ENML-ERR-00903	Notaries Public error - invalid ID attribute: {0}
ENML-ERR-00904	Notaries Public error - invalid Name: {0}
ENML-ERR-00905	Notaries Public error - invalid Commission Number: {0}
ENML-ERR-00906	Notaries Public error - invalid Commission Expiry Date: {0}
ENML-ERR-00907	Notaries Public error - invalid International Jurisdiction: {0}
ENML-ERR-00908	Notaries Public error - invalid US Jurisdiction: {0}
ENML-ERR-00909	Notaries Public error - invalid Bond Number: {0}
ENML-ERR-00910	Notaries Public error - invalid Verification URI: {0}
ENML-ERR-00911	Notaries Public error - missing ID attribute: {0}
ENML-ERR-00912	Notaries Public error - missing Name: {0}
ENML-ERR-00913	Notaries Public error - missing Commission Number: {0}
ENML-ERR-00914	Notaries Public error - missing Commission Expiry Date: {0}
ENML-ERR-00915	Notaries Public error - missing International Jurisdiction: {0}
ENML-ERR-00916	Notaries Public error - missing US Jurisdiction: {0}
ENML-ERR-00917	Notaries Public error - missing Bond Number: {0}
ENML-ERR-00918	Notaries Public error - missing Verification URI: {0}
ENML-ERR-00999	Notaries Public error - other error: {0}

Notary Signatures ERROR Codes (01000 - 01099)

Code	Message
ENML-ERR-01001	Notary Signatures error - invalid signature: {0}
ENML-ERR-01002	Notary Signatures error - invalid status: {0}
ENML-ERR-01003	Notary Signatures error - invalid ID attribute: {0}
ENML-ERR-01004	Notary Signatures error - invalid Signed Info: {0}
ENML-ERR-01005	Notary Signatures error - invalid Signature Value: {0}
ENML-ERR-01006	Notary Signatures error - invalid Key Info: {0}
ENML-ERR-01007	Notary Signatures error - invalid Object: {0}
ENML-ERR-01008	Notary Signatures error - missing ID attribute: {0}
ENML-ERR-01008	Notary Signatures error - missing Signed Info: {0}
ENML-ERR-01010	Notary Signatures error - missing Signature Value: {0}
ENML-ERR-01011	Notary Signatures error - missing Key Info: {0}
ENML-ERR-01012	Notary Signatures error - missing Object: {0}
ENML-ERR-01099	Notary Signatures error - other error: {0}

Miscellaneous ERROR Codes (01100 – 01199)

Code	Message
ENML-ERR-01101	Miscellaneous error - invalid signature: {0}
ENML-ERR-01102	Miscellaneous error - invalid status: {0}
ENML-ERR-01103	Miscellaneous error – SOAP layer error: {0}
ENML-ERR-01104	Miscellaneous error - network layer error: {0}
ENML-ERR-01105	Miscellaneous error – database layer error: {0}
ENML-ERR-01106	Miscellaneous error – epoch time error: {0}
ENML-ERR-01199	Miscellaneous error - other miscellaneous error: {0}

Vendors who choose to implement ENML will be able to apply for a unique block of 1,000 code numbers to be assigned for their exclusive use within their implementation of the ENML protocol. They may choose to use these numbers for messages related to their implementation, in addition to the Standard ENML Codes & Messages.

In order to receive this unique block of code-numbers, the Vendor must use the following process:

Version	Date	Author	Notes
DRAFT 1	November 2, 2008	Arshad Noor	Initial version
DRAFT 2	December 1, 2008	Arshad Noor	Includes ApostillizedDocument and supporting elements, Appendices C, E and F
DRAFT 2.1	December 8, 2008	Arshad Noor	Minor corrections to Glossary to correct typographic errors and some descriptions
DRAFT 2.2	December 16, 2008	Arshad Noor	Removed Appendix D related to XPath Removed section 4.57 related to XPath Added section 3.12 with a cautionary (non-normative) note on the use of XPath within ENML Minor correction to the description of ENML in the Introduction.