:PRIA_DOCUMENT_v2_4_1.XSD
|
|
- Annabel Stevens
- 6 years ago
- Views:
Transcription
1 <xs:schema xmlns:mismo=" xmlns:xs=" elementformdefault="qualified" attributeformdefault="unqualified"> <xs:documentation>================================================================== ============ Title : PRIA DOCUMENT v2.4.1 Zero Delta Schema File Name :PRIA_DOCUMENT_v2_4_1.XSD ELE Version : Creation Date : Modification Date : Modification Date : =============================================================================== Copyright 2006 Property Records Industry Association (PRIA) All rights reserved. PRIA Copyright Notice, Disclaimer and End-User License Version 1.1 November 2003 (the PRIA License or the License ) This document or software (the Work ) is published by the Property Records Industry Association ( PRIA ). Copyright 2006 by PRIA (collectively or individually, a Licensor ). All rights reserved. Subject to this License, Licensor hereby grants any user of this document or software ( Licensee ) a worldwide, royalty-free, irrevocable, perpetual, non-exclusive license to reproduce the Work in copies, to prepare proprietary derivative works based upon the Work, to distribute copies of the Work to the public by sale or other transfer of ownership, and to display the Work publicly. If the Work is software published by PRIA as codes in source and binary form, the License includes the right for Licensee to distribute copies of, and use, the codes in source and binary forms, with or without modification. Any distribution of copies of the Work, or of a derivative work based upon the Work, shall reproduce verbatim the above copyright notice, the entire text of this License and the entire disclaimer below under the following header: This document includes works developed by PRIA and some of its contributors, subject to PRIA License, Version 1.1 November 2003 published at or any subsequent applicable version of such License. Any software application developed by Licensee based upon the Work shall include the following notice in its end user documentation and in its codes: This software product includes software or other works developed by PRIA and some of its contributors, subject to PRIA License, Version 1.1 November 2003 published at or any subsequent applicable version of such License. Upon publication of a derivative work, Licensee shall inform PRIA of such publication and address to PRIA a copy of Licensee s derivative work and any relevant documentation. PRIA is a trade name of the Property Records Industry Association. No derivative work or altered versions of a Work by Licensee may be trademarked or labeled in reference to PRIA or any of its trademark(s) or service mark(s) without PRIA s prior written approval. No reference to PRIA or any of its trademarks by Licensee shall imply endorsement of Licensee s activities and products. DISCLAIMER: THIS WORK IS PROVIDED AS IS. PRIA, THE COPYRIGHT HOLDER, THE AUTHORS OF THIS WORK AND ANY STANDARD -SETTING BODY CONTRIBUTORS TO THIS WORK MAKE NO REPRESENTATIONS OR WARRANTIES (i) EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT; (ii) THAT THE CONTENTS OF SUCH WORK ARE FREE FROM ERROR OR SUITABLE FOR ANY PURPOSE; NOR THAT IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD-PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. IN NO EVENT WILL PRIA, THE COPYRIGHT HOLDER. ANY AUTHOR OF THIS WORK, OR THE STANDARD-SETTING BODY CONTRIBUTORS TO THIS WORK BE LIABLE TO ANY PARTY FOR ANY DIRECT, INDIRECT, SPECIAL Page 1
2 OR CONSEQUENTIAL DAMAGES FOR ANY USE OF THIS WORK, INCLUDING, WITHOUT LIMITATION, ANY LOST PROFITS, BUSINESS INTERRUPTION, LOSS OF PROGRAMS OR OTHER DATA ON YOUR INFORMATION HANDLING SYSTEM OR OTHERWISE, EVEN IF PRIA, THE COPYRIGHT HOLDER AND/OR ANY AUTHORS AND/OR ANY STANDARD-SETTING BODY CONTRIBUTORS TO THIS WORK ARE EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ==============================================================================</xs:d ocumentation> <xs:include schemalocation="mismo_signature_type.xsd"/> <xs:element name="pria_document" type="pria_document_type"/> <xs:complextype name="pria_authorized_representative_type"> <xs:sequence> <xs:element name="contact_detail" type="pria_contact_detail_type" minoccurs="0"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>the name of the person or entity designated as the authorized representative for the party.</xs:documentation> <mismo:context>authorized Representative</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>authorized Representative Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_titledescription" type="xs:string"> <xs:documentation>the title of the authorized representative.</xs:documentation> <mismo:context>authorized Representative</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>authorized Representative Title Description</mismo:LDD_NAME> Page 2
3 <xs:attribute name="authorizedtosignindicator" type="pria_mismoindicatortype"> <xs:documentation>this indicator is set to be true when the authorized representative can sign for the party.</xs:documentation> <mismo:datatype>boolean</mismo:datatype> <mismo:context>authorized Representative</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>authorized To Sign Indicator</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_bill_to_party_type"> <xs:sequence> <xs:element name="preferred_response" type="pria_preferred_response_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="non_person_entity_detail" type="pria_non_person_entity_detail_type"/> <xs:element name="contact_detail" type="pria_contact_detail_type"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>the unparsed name of the party to whom fees are billed.</xs:documentation> <mismo:ldd_name>bill To Party Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_streetaddress" type="xs:string"> <xs:documentation>the street address of the party to whom fees are billled.</xs:documentation> Page 3
4 <mismo:ldd_name>bill To Party Street Address</mismo:LDD_NAME> <xs:attribute name="_streetaddress2" type="xs:string"> <xs:documentation>the second line of the street address of the party to whom fees are billled.</xs:documentation> <mismo:ldd_name>bill To Party Street Address 2</mismo:LDD_NAME> <xs:attribute name="_city" type="xs:string"> <xs:documentation>the city in which the address of the party to whom fees are billled is located.</xs:documentation> <mismo:ldd_name>bill To Party City</mismo:LDD_NAME> <xs:attribute name="_state" type="xs:string"> <xs:documentation>the state in which the address of the party to whom fees are billled is located.</xs:documentation> Page 4
5 <mismo:ldd_name>bill To Party State</mismo:LDD_NAME> <xs:attribute name="_postalcode" type="xs:string"> <xs:documentation>the postal code (zip code in US) of the address of the party to whom fees are billled is located. Zip code may be either 5 or 9 digits.</xs:documentation> <mismo:ldd_name>bill To Party Postal Code</mismo:LDD_NAME> <xs:attribute name="_county" type="xs:string"> <xs:documentation>the county in which the address of the party to whom fees are billled is located.</xs:documentation> <mismo:ldd_name>bill To Party County</mismo:LDD_NAME> <xs:attribute name="_country" type="xs:string"> <xs:documentation>the country in which the address of the party to whom fees are billled is located.</xs:documentation> Page 5
6 <mismo:ldd_name>bill To Party Country</mismo:LDD_NAME> <xs:attribute name="_countrycode" type="xs:string"> <xs:documentation>the country code in which the address of the party to whom fees are billled is located.</xs:documentation> <mismo:ldd_name>bill To Party Country Code</mismo:LDD_NAME> <xs:attribute name="nonpersonentityindicator" type="pria_mismoindicatortype"> <xs:documentation>when true, indicates that the party is a non person entity.</xs:documentation> <mismo:datatype>boolean</mismo:datatype> <mismo:context>beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer, Escrow Paid To</mismo:CONTEXT> <mismo:process_area>application</mismo:process_area> <mismo:ldd_name>non Person Entity Indicator</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple Bill To Parties are included this indicates the order in which they should appear on the document</xs:documentation> Page 6
7 <mismo:ldd_name>bill To Party Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="_titledescription" type="xs:string"> <xs:documentation>the title of the party to whom fees are billled.</xs:documentation> <mismo:ldd_name>bill To Party Title Description</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_consideration_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_amount" type="pria_mismomoney"> <xs:documentation>amount of the consideration</xs:documentation> <mismo:datatype>money</mismo:datatype> <mismo:ldd_name>consideration Amount</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple forms of consideration are included, this indicates the order in which they should be listed</xs:documentation> Page 7
8 <mismo:ldd_name>consideration Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="_type" type="pria_considerationtypeenumerated"> <xs:documentation>description of the consideration or money amount of the document. (Not necessarily the mortgage amount)</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:ldd_name>consideration Type</mismo:LDD_NAME> <xs:attribute name="_typeotherdescription" type="xs:string"> <xs:documentation>a description of a CONSIDERATION type not included in the enumerated list</xs:documentation> <mismo:ldd_name>consideration Type Other Description</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_contact_detail_type"> <xs:sequence> <xs:element name="contact_point" type="pria_contact_point_type" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_name" type="xs:string"> <xs:documentation>the name of an individual acting as a contact for a party to the loan.</xs:documentation> <mismo:context>contact Page 8
9 Detail</mismo:CONTEXT> ordering</mismo:process_area> PRIA_DOCUMENT_v2_4_1 <mismo:process_area>service <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> <mismo:process_area>application</mismo:process_area> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>servicing Transfer</mismo:PROCESS_AREA> <mismo:process_area>investor Reporting</mismo:PROCESS_AREA> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>contact Detail Name</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_contact_point_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_preferenceindicator" type="pria_mismoindicatortype"> <xs:documentation>this indicator is set to be true when the particular contacts Contact Point (i.e. phone number) is preferred over any others.</xs:documentation> <mismo:datatype>boolean</mismo:datatype> <mismo:context>contact Point</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> Delivery</mismo:PROCESS_AREA> <mismo:process_area>secondary <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Page 9 <mismo:process_area>servicing <mismo:process_area>investor
10 Reporting</mismo:PROCESS_AREA> PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>contact Point Preference Indicator</mismo:LDD_NAME> <xs:attribute name="_roletype" type="pria_contactpointroletypeenumerated"> <xs:documentation>this element sets the type of role (i.e. Home, Work or Mobile) used for the Contact Point Type (Phone, Fax, ).</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>contact Point</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> Delivery</mismo:PROCESS_AREA> <mismo:process_area>secondary <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Reporting</mismo:PROCESS_AREA> <mismo:process_area>servicing <mismo:process_area>investor <mismo:ldd_name>contact Point Role Type</mismo:LDD_NAME> <xs:attribute name="_type" type="pria_contactpointtypeenumerated"> <xs:documentation>this datum sets the Type (Phone, Fax, , Other) used for the Contact Point Value.</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>contact Point</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> Delivery</mismo:PROCESS_AREA> <mismo:process_area>secondary <mismo:process_area>servicing</mismo:process_area> Page 10
11 <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Reporting</mismo:PROCESS_AREA> <mismo:process_area>servicing <mismo:process_area>investor <mismo:ldd_name>contact Point Type</mismo:LDD_NAME> <xs:attribute name="_typeotherdescription" type="xs:string"> <xs:documentation>a free-form text field used to describe the Contact Point if Other is selected as the Contact Point Type.</xs:documentation> <mismo:context>contact Point</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> Delivery</mismo:PROCESS_AREA> <mismo:process_area>secondary <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Reporting</mismo:PROCESS_AREA> <mismo:process_area>servicing <mismo:process_area>investor <mismo:ldd_name>contact Point Type Other Description</mismo:LDD_NAME> <xs:attribute name="_value" type="xs:string"> <xs:documentation>this is the actual value (Phone, Fax, , Other) of the Contact Point Type.</xs:documentation> <mismo:context>contact Point</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> Page 11
12 <mismo:process_area>flood</mismo:process_area> Delivery</mismo:PROCESS_AREA> <mismo:process_area>secondary <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Reporting</mismo:PROCESS_AREA> <mismo:process_area>servicing <mismo:process_area>investor <mismo:ldd_name>contact Point Value</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_document_type"> <xs:sequence> <xs:element name="grantor" type="pria_grantor_type" maxoccurs="unbounded"/> <xs:element name="grantee" type="pria_grantee_type" maxoccurs="unbounded"/> <xs:element name="property" type="pria_property_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="parties" type="pria_parties_type"/> <xs:element name="execution" type="pria_execution_type"/> <xs:element name="mortgage_consideration" type="pria_mortgage_consideration_type" minoccurs="0"/> <xs:element name="consideration" type="pria_consideration_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="recordable_document" type="pria_recordable_document_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="signatory" type="mismo_signature_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="notary" type="pria_notary_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="recording_endorsement" type="pria_recording_endorsement_type" minoccurs="0"/> <xs:element name="embedded_file" type="pria_embedded_file_type" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_code" type="xs:string"> <xs:documentation>abbreviated code used by recorder in indexing software. Specific to County document is being recorded in</xs:documentation> Page 12
13 <mismo:ldd_name>pria Document Code</mismo:LDD_NAME> <xs:attribute name="documentnonrecordableindicator" type="pria_mismoindicatortype"> <xs:documentation>an indicator that this document is included in the electronic package but is not to be recorded by the County</xs:documentation> <mismo:datatype>boolean</mismo:datatype> <mismo:ldd_name>documentnonrecordable Indicator</mismo:LDD_NAME> <xs:attribute name="priaversionidentifier" type="xs:string"> <xs:documentation>the PRIA DOCUMENT version</xs:documentation> <mismo:ldd_name>pria Version Identifier</mismo:LDD_NAME> <xs:attribute name="_uniqueidentifier" type="xs:string"> <xs:documentation>a unique system-assigned identifier (such as an audit trail number) to each document.</xs:documentation> Page 13
14 <mismo:ldd_name>pria Document Unique Identifier</mismo:LDD_NAME> <xs:attribute name="recordabledocumentsequenceidentifier" type="xs:string"> <xs:documentation>identifier used to indicate the position of a document within a sequence of documents.</xs:documentation> <mismo:context>recordable Document</mismo:CONTEXT> <mismo:ldd_name>recordable Document Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="recordabledocumenttype" type="pria_recordabledocumenttypeenumerated"> <xs:documentation>the type of document that is to be recorded.</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>recordable Document</mismo:CONTEXT> <mismo:ldd_name>recordable Document Type</mismo:LDD_NAME> <xs:attribute name="recordabledocumenttypeotherdescription" type="xs:string"> <xs:documentation>the description of type of document when the Recordable Document Type enumerated value selected is Other.</xs:documentation> <mismo:context>recordable Document</mismo:CONTEXT> <mismo:ldd_name>recordable Document Type Page 14
15 Other Description</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_embedded_file_type"> <xs:sequence> <xs:element name="document" type="pria_document_type" minoccurs="0"/> </xs:sequence> <xs:attribute name="id" type="xs:string"/> <xs:attribute name="embeddedfiletype" type="xs:string"> <xs:documentation>type of file embedded in signature</xs:documentation> <mismo:ldd_name>file Type</mismo:LDD_NAME> <xs:attribute name="embeddedfileversion" type="xs:string"> <xs:documentation>the version number for the embedded file</xs:documentation> <mismo:ldd_name>file Version</mismo:LDD_NAME> <xs:attribute name="embeddedfilename" type="xs:string"> <xs:documentation>the name of the embedded file</xs:documentation> Page 15
16 <mismo:ldd_name>file Name</mismo:LDD_NAME> <xs:attribute name="fileencodingtype" type="xs:string"/> <xs:attribute name="filedescription" type="xs:string"> <xs:documentation>provides additional information about the embedded file, such as the software version that generated the file.</xs:documentation> <mismo:ldd_name>file Description</mismo:LDD_NAME> <xs:attribute name="mimetype" type="xs:string"> <xs:documentation>indicates the Multipurpose Internet Mail Extensions type of the data in the DOCUMENT container. A registered list of these types is available at ion> <mismo:context>embedded File, Preferred Response</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> <mismo:process_area>mi</mismo:process_area> <mismo:ldd_name>mime Type</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_execution_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> Page 16
17 <xs:attribute name="_date" type="pria_mismodatetime"> <xs:documentation>the date documents were signed (executed).</xs:documentation> <mismo:datatype>date/time</mismo:datatype> <mismo:context>execution</mismo:context> <mismo:ldd_name>execution Date</mismo:LDD_NAME> <xs:attribute name="_city" type="xs:string"> <xs:documentation>the name of the city where documents were signed (executed).</xs:documentation> <mismo:context>execution</mismo:context> <mismo:ldd_name>execution City</mismo:LDD_NAME> <xs:attribute name="_county" type="xs:string"> <xs:documentation>the name of the county where documents were signed (executed).</xs:documentation> <mismo:context>execution</mismo:context> <mismo:ldd_name>execution County</mismo:LDD_NAME> <xs:attribute name="_state" type="xs:string"> <xs:documentation>the name of the state where Page 17
18 documents were signed (executed).</xs:documentation> <mismo:context>execution</mismo:context> <mismo:ldd_name>execution State</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_external_file_type"> <xs:sequence/> <xs:attribute name="id" type="xs:string"/> <xs:attribute name="fileencodingtype" type="xs:string"/> <xs:attribute name="filedescription" type="xs:string"/> <xs:attribute name="mimetype" type="xs:string"> <xs:documentation>indicates the Multipurpose Internet Mail Extensions type of the data in the DOCUMENT container. A registered list of these types is available at ion> <mismo:context>embedded File, Preferred Response</mismo:CONTEXT> <mismo:process_area>service ordering</mismo:process_area> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>flood</mismo:process_area> <mismo:process_area>mi</mismo:process_area> <mismo:ldd_name>mime Type</mismo:LDD_NAME> <xs:attribute name="uri" type="xs:anyuri"/> <xs:attribute name="pagecount" type="pria_mismonumeric"/> <xs:attribute name="signaturesequenceidentifier" type="xs:string"/> </xs:complextype> <xs:complextype name="pria_grantee_alias_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_firstname" type="xs:string"> Page 18
19 GRANTEE</xs:documentation> PRIA_DOCUMENT_v2_4_1 <xs:documentation>alternate first name of the <mismo:ldd_name>grantee Alias First Name</mismo:LDD_NAME> <xs:attribute name="_middlename" type="xs:string"> <xs:documentation>alternate middle name (or initial) of the GRANTEE</xs:documentation> <mismo:ldd_name>grantee Alias Middle Name</mismo:LDD_NAME> <xs:attribute name="_lastname" type="xs:string"> <xs:documentation>alternate last name of the GRANTEE</xs:documentation> <mismo:ldd_name>grantee Alias Last Name</mismo:LDD_NAME> <xs:attribute name="_namesuffix" type="xs:string"> <xs:documentation>suffix or Lineage of the alternate name of the GRANTEE (ie: Jr, Sr, III)</xs:documentation> Page 19
20 PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>grantee Alias Name Suffix</mismo:LDD_NAME> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>alternate unparsed name of the GRANTEE</xs:documentation> <mismo:ldd_name>grantee Alias Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple GRANTEE ALIAS's are included this indicates the order in which they should appear on the document</xs:documentation> <mismo:ldd_name>grantee Alias Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="aliastype" type="pria_aliastypeenumerated"> <xs:documentation>a description of the type of ALIAS</xs:documentation> Page 20
21 PRIA_DOCUMENT_v2_4_1 <mismo:datatype>enumerated</mismo:datatype> <mismo:ldd_name>alias Type</mismo:LDD_NAME> <xs:attribute name="aliastypeotherdescription" type="xs:string"> <xs:documentation>a description of an ALIAS type not included in the enumerated list</xs:documentation> <mismo:ldd_name>alias Type Other Description</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_grantee_type"> <xs:sequence> <xs:element name="_alias" type="pria_grantee_alias_type" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_streetaddress" type="xs:string"> <xs:documentation>the unstructured (Unparsed) street address of the Grantee (e.g., 123 Main Street).</xs:documentation> <mismo:ldd_name>grantee Street Address</mismo:LDD_NAME> <xs:attribute name="_streetaddress2" type="xs:string"> <xs:documentation>the unstructured (Unparsed) street address 2nd division of the Grantee (e.g., Unit 1223).</xs:documentation> Page 21
22 PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>grantee Street Address 2</mismo:LDD_NAME> <xs:attribute name="_city" type="xs:string"> <xs:documentation>the city in which the Grantee is located.</xs:documentation> <mismo:ldd_name>grantee City</mismo:LDD_NAME> <xs:attribute name="_state" type="xs:string"> <xs:documentation>the state in which the Grantee is located.</xs:documentation> <mismo:ldd_name>grantee State</mismo:LDD_NAME> <xs:attribute name="_postalcode" type="xs:string"> <xs:documentation>the postal code (zip code in the US) of the Grantee. Zip code may be either 5 or 9 digits.</xs:documentation> Page 22
23 PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>grantee Postal Code</mismo:LDD_NAME> <xs:attribute name="_county" type="xs:string"> <xs:documentation>the county in which the Grantee is located.</xs:documentation> <mismo:ldd_name>grantee County</mismo:LDD_NAME> <xs:attribute name="_country" type="xs:string"> <xs:documentation>the name of the country in which the Grantee resides.</xs:documentation> <mismo:ldd_name>grantee Country</mismo:LDD_NAME> <xs:attribute name="_firstname" type="xs:string"> <xs:documentation>the first name of the GRANTEE</xs:documentation> Page 23
24 <mismo:ldd_name>grantee First Name</mismo:LDD_NAME> <xs:attribute name="_middlename" type="xs:string"> <xs:documentation>the middle name (or initial) of the GRANTEE</xs:documentation> <mismo:ldd_name>grantee Middle Name</mismo:LDD_NAME> <xs:attribute name="_lastname" type="xs:string"> <xs:documentation>the last name of the GRANTEE</xs:documentation> <mismo:ldd_name>grantee Last Name</mismo:LDD_NAME> <xs:attribute name="_namesuffix" type="xs:string"> <xs:documentation>the suffix or lineage of the GRANTEE (ie: Jr, Sr, III)</xs:documentation> Page 24
25 <mismo:ldd_name>grantee Name Suffix</mismo:LDD_NAME> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>the unparsed name of the GRANTEE</xs:documentation> <mismo:ldd_name>grantee Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_capacitydescription" type="xs:string"> <xs:documentation>the capacity in which the GRANTEE is acting (ie: Power of Attorney, Trustee)</xs:documentation> <mismo:ldd_name>grantee Capacity Description</mismo:LDD_NAME> <xs:attribute name="maritalstatustype" type="pria_maritalstatustypeenumerated"> <xs:documentation>the marital status of the party as disclosed by the party</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>borrower</mismo:context> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> Page 25
26 <mismo:process_area>aus</mismo:process_area> <mismo:process_area>servicing Transfer</mismo:PROCESS_AREA> <mismo:ldd_name>marital Status Type</mismo:LDD_NAME> <xs:attribute name="nonpersonentityindicator" type="pria_mismoindicatortype"> <xs:documentation>when true, indicates that the party is a non person entity.</xs:documentation> <mismo:datatype>boolean</mismo:datatype> <mismo:context>beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer, Escrow Paid To</mismo:CONTEXT> <mismo:process_area>application</mismo:process_area> <mismo:ldd_name>non Person Entity Indicator</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple GRANTEE's are included this indicates the order in which they should appear on the document</xs:documentation> <mismo:ldd_name>grantee Sequence Identifier</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_grantor_alias_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_firstname" type="xs:string"> <xs:documentation>alternate first name of the GRANTOR</xs:documentation> Page 26
27 PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>grantor Alias First Name</mismo:LDD_NAME> <xs:attribute name="_middlename" type="xs:string"> <xs:documentation>alternate middle name (or initial) of the GRANTOR</xs:documentation> <mismo:ldd_name>grantor Alias Middle Name</mismo:LDD_NAME> <xs:attribute name="_lastname" type="xs:string"> <xs:documentation>alternate last name of the GRANTOR</xs:documentation> <mismo:ldd_name>grantor Alias Last Name</mismo:LDD_NAME> <xs:attribute name="_namesuffix" type="xs:string"> <xs:documentation>suffix or Lineage of the alternate name of the GRANTOR (ie: Jr, Sr, III)</xs:documentation> Page 27
28 PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>grantor Alias Name Suffix</mismo:LDD_NAME> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>alternate unparsed name of the GRANTOR</xs:documentation> <mismo:ldd_name>grantor Alias Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple GRANTOR ALIAS's are included this indicates the order in which they should appear on the document</xs:documentation> <mismo:ldd_name>grantor Alias Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="aliastype" type="pria_aliastypeenumerated"> <xs:documentation>a description of the type of ALIAS</xs:documentation> Page 28
29 <mismo:datatype>enumerated</mismo:datatype> <mismo:ldd_name>alias Type</mismo:LDD_NAME> <xs:attribute name="aliastypeotherdescription" type="xs:string"> <xs:documentation>a description of an ALIAS type not included in the enumerated list</xs:documentation> <mismo:ldd_name>alias Type Other Description</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_grantor_type"> <xs:sequence> <xs:element name="_alias" type="pria_grantor_alias_type" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_streetaddress" type="xs:string"> <xs:documentation>the unstructured (Unparsed) street address of the Grantor (e.g., 123 Main Street).</xs:documentation> <mismo:ldd_name>grantor Street Address</mismo:LDD_NAME> <xs:attribute name="_streetaddress2" type="xs:string"> <xs:documentation>the unstructured (Unparsed) street address 2nd division of the Grantor (e.g., Unit 1223).</xs:documentation> Page 29
30 PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>grantor Street Address 2</mismo:LDD_NAME> <xs:attribute name="_city" type="xs:string"> <xs:documentation>the city in which the Grantor is located.</xs:documentation> <mismo:ldd_name>grantor City</mismo:LDD_NAME> <xs:attribute name="_state" type="xs:string"> <xs:documentation>the state in which the Grantor is located.</xs:documentation> <mismo:ldd_name>grantor State</mismo:LDD_NAME> <xs:attribute name="_postalcode" type="xs:string"> <xs:documentation>the postal code (zip code in the US) of the Grantor. Zip code may be either 5 or 9 digits.</xs:documentation> Page 30
31 <mismo:ldd_name>grantor Postal Code</mismo:LDD_NAME> <xs:attribute name="_county" type="xs:string"> <xs:documentation>the county in which the Grantor is located.</xs:documentation> <mismo:ldd_name>grantor County</mismo:LDD_NAME> <xs:attribute name="_country" type="xs:string"> <xs:documentation>the name of the country in which the Grantor resides.</xs:documentation> <mismo:ldd_name>grantor Country</mismo:LDD_NAME> <xs:attribute name="_firstname" type="xs:string"> <xs:documentation>the first name of the GRANTOR</xs:documentation> Page 31
32 <mismo:ldd_name>grantor First Name</mismo:LDD_NAME> <xs:attribute name="_middlename" type="xs:string"> <xs:documentation>the middle name (or initial) of the GRANTOR</xs:documentation> <mismo:ldd_name>grantor Middle Name</mismo:LDD_NAME> <xs:attribute name="_lastname" type="xs:string"> <xs:documentation>the last name of the GRANTOR</xs:documentation> <mismo:ldd_name>grantor Last Name</mismo:LDD_NAME> <xs:attribute name="_namesuffix" type="xs:string"> <xs:documentation>the suffix or lineage of the GRANTOR (ie: Jr, Sr, III)</xs:documentation> Page 32
33 <mismo:ldd_name>grantor Name Suffix</mismo:LDD_NAME> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>the unparsed name of the GRANTOR</xs:documentation> <mismo:ldd_name>grantor Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_capacitydescription" type="xs:string"> <xs:documentation>the capacity in which the GRANTOR is acting (ie: Power of Attorney, Trustee)</xs:documentation> <mismo:ldd_name>grantor Capacity Description</mismo:LDD_NAME> <xs:attribute name="maritalstatustype" type="pria_maritalstatustypeenumerated"> <xs:documentation>the marital status of the party as disclosed by the party</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>borrower</mismo:context> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Page 33 <mismo:process_area>servicing
34 Transfer</mismo:PROCESS_AREA> PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>marital Status Type</mismo:LDD_NAME> <xs:attribute name="nonpersonentityindicator" type="pria_mismoindicatortype"> <xs:documentation>when true, indicates that the party is a non person entity.</xs:documentation> <mismo:datatype>boolean</mismo:datatype> <mismo:context>beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer, Escrow Paid To</mismo:CONTEXT> <mismo:process_area>application</mismo:process_area> <mismo:ldd_name>non Person Entity Indicator</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple GRANTOR's are included this indicates the order in which they should appear on the document</xs:documentation> <mismo:ldd_name>grantor Sequence Identifier</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_mortgage_consideration_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="helocinitialadvanceamount" type="pria_mismomoney"> <xs:documentation>the amount of money that a borrower receives at closing in a HELOC transaction.</xs:documentation> Page 34
35 <mismo:process_area>aus</mismo:process_area> PRIA_DOCUMENT_v2_4_1 <mismo:datatype>money</mismo:datatype> <mismo:context>heloc</mismo:context> <mismo:ldd_name>heloc Initial Advance Amount</mismo:LDD_NAME> <xs:attribute name="originalloanamount" type="pria_mismomoney"> <xs:documentation>amount of the Mortgage as stated on the original note</xs:documentation> <mismo:datatype>money</mismo:datatype> <mismo:context>mortgage Terms, Original Loan</mismo:CONTEXT> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>servicing Transfer</mismo:PROCESS_AREA> <mismo:process_area>secondary Pricing</mismo:PROCESS_AREA> <mismo:ldd_name>original Loan Amount</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_non_person_entity_detail_type"> <xs:sequence> <xs:element name="authorized_representative" type="pria_authorized_representative_type" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_organizationtype" type="pria_nonpersonentitydetailorganizationtypeenumerated"> <xs:documentation>the description of the entity type of the party or organization.</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>non Person Entity Detail-Beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer</mismo:CONTEXT> Page 35
36 <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>non Person Entity Detail Organization Type</mismo:LDD_NAME> <xs:attribute name="_organizationtypeotherdescription" type="xs:string"> <xs:documentation>the description of the Organization Type when Other is selected as the option from the enumerated list.</xs:documentation> <mismo:context>non Person Entity Detail-Beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>non Person Entity Detail Organization Type Other Description</mismo:LDD_NAME> <xs:attribute name="_organizedunderthelawsofjurisdictionname" type="xs:string"> <xs:documentation>the name and type of jurisdiction under which the party as an entity is organized and under whose authority the party as an entity operates.</xs:documentation> <mismo:context>non Person Entity Detail-Beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>non Person Entity Detail Organized Under The Laws Of Jurisdiction Name</mismo:LDD_NAME> Page 36
37 <xs:attribute name="_successorclausetextdescription" type="xs:string"> <xs:documentation>the description used as the Successor Clause for the non person entity, i. e. Its successors and/or assigns.</xs:documentation> <mismo:context>non Person Entity Detail-Beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>non Person Entity Detail Successor Clause Text Description</mismo:LDD_NAME> <xs:attribute name="_taxidentificationnumberidentifier" type="xs:string"> <xs:documentation>the Tax Identification Number assigned to the non person entity.</xs:documentation> <mismo:context>non Person Entity Detail-Beneficiary, Borrower, Closing Agent, Investor, Lender, Loss Payee, Mortgage Broker, Payee, Assign To, Assign From, Seller, Trustee, Servicer</mismo:CONTEXT> <mismo:process_area>aus</mismo:process_area> <mismo:ldd_name>non Person Entity Detail Tax Identification Number Identifier</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_notary_certificate_signer_identification_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_description" type="xs:string"> <xs:documentation>the description of the type of identification provided by the party signing before the notary, e.g. drivers license and state of issuance.</xs:documentation> <mismo:context>notary Certificate Signer Page 37
38 Identification</mismo:CONTEXT> PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>notary Certificate Signer Identification Description</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple forms of identificaiton are presented, this indicates the order in which they should appear in the document</xs:documentation> <mismo:ldd_name>notary Certificate Signer Identification Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="_type" type="pria_notarycertificatesigneridentificationtypeenumerated"> <xs:documentation>the type of identification provided by the party signing before the notary.</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>notary Certificate Signer Identification</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signer Identification Type</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_notary_certificate_type"> <xs:sequence> <xs:element name="_signer_identification" type="pria_notary_certificate_signer_identification_type" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>if more than one certificate is Page 38
39 used, this indicates the order in which they should appear on the document</xs:documentation> <mismo:ldd_name>notary Certificate Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="_signerfirstname" type="xs:string"> <xs:documentation>the first name of the party signing before the notary.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signer First Name</mismo:LDD_NAME> <xs:attribute name="_signermiddlename" type="xs:string"> <xs:documentation>the middle name of the party signing before the notary.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signer Middle Name</mismo:LDD_NAME> <xs:attribute name="_signerlastname" type="xs:string"> <xs:documentation>the last name of the party signing before the notary.</xs:documentation> <mismo:context>notary Page 39
40 Certificate</mismo:CONTEXT> PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>notary Certificate Signer Last Name</mismo:LDD_NAME> <xs:attribute name="_signernamesuffix" type="xs:string"> <xs:documentation>the name suffix of the party signing before the notary.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signer Name Suffix</mismo:LDD_NAME> <xs:attribute name="_signerunparsedname" type="xs:string"> <xs:documentation>the unparsed name of the party signing before the notary.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signer Unparsed Name</mismo:LDD_NAME> <xs:attribute name="_signercompanyname" type="xs:string"> <xs:documentation>the company name of the party signing before the notary.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> Page 40
41 <mismo:ldd_name>notary Certificate Signer Company Name</mismo:LDD_NAME> <xs:attribute name="_signertitledescription" type="xs:string"> <xs:documentation>the title of the party signing before the notary.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signer Title Description</mismo:LDD_NAME> <xs:attribute name="_signingdate" type="pria_mismodatetime"> <xs:documentation>the date the notary performs the notarial act and signs the document.</xs:documentation> <mismo:datatype>date/time</mismo:datatype> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:process_area>sec</mismo:process_area> <mismo:ldd_name>notary Certificate Signing Date</mismo:LDD_NAME> <xs:attribute name="_signingcounty" type="xs:string"> <xs:documentation>the county in which the notary performs the notarial act.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signing County</mismo:LDD_NAME> Page 41
42 <xs:attribute name="_signingstate" type="xs:string"> <xs:documentation>the state in which the notary performs the notarial act.</xs:documentation> <mismo:context>notary Certificate</mismo:CONTEXT> <mismo:ldd_name>notary Certificate Signing State</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_notary_type"> <xs:sequence> <xs:element name="_certificate" type="pria_notary_certificate_type" minoccurs="0" maxoccurs="unbounded"/> <xs:element name="signatory" type="mismo_signature_type" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_commissionbondnumberidentifier" type="xs:string"> <xs:documentation>the identifying commission bond number of the notary.</xs:documentation> <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Commission Bond Number Identifier</mismo:LDD_NAME> <xs:attribute name="_commissionnumberidentifier" type="xs:string"> <xs:documentation>the identifying commission number assigned to the notary.</xs:documentation> <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Commission Number Page 42
43 Identifier</mismo:LDD_NAME> <xs:attribute name="_commissionexpirationdate" type="pria_mismodatetime"> <xs:documentation>the expiration date of the notary's commission.</xs:documentation> <mismo:datatype>date/time</mismo:datatype> <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Commission Expiration Date</mismo:LDD_NAME> <xs:attribute name="_commissionstate" type="xs:string"> <xs:documentation>the state in which notary is commissioned.</xs:documentation> <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Commission State</mismo:LDD_NAME> <xs:attribute name="_commissioncounty" type="xs:string"> <xs:documentation>the county in which the notary is commissioned.</xs:documentation> <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Commission County</mismo:LDD_NAME> <xs:attribute name="_commissioncity" type="xs:string"> <xs:documentation>the city where the notary is commissioned.</xs:documentation> Page 43
44 PRIA_DOCUMENT_v2_4_1 <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Commission City</mismo:LDD_NAME> <xs:attribute name="_priaversionidentifier" type="xs:string"> <xs:documentation>the version of the PRIA NOTARY DTD used</xs:documentation> <mismo:ldd_name>pria Version Identifier</mismo:LDD_NAME> <xs:attribute name="_sequenceidentifier" type="xs:string"> <xs:documentation>when multiple notaries are utilized, this indicates the order in which they should appear in the document</xs:documentation> <mismo:ldd_name>notary Sequence Identifier</mismo:LDD_NAME> <xs:attribute name="_titledescription" type="xs:string"> <xs:documentation>the title or position of the notary.</xs:documentation> <mismo:context>notary</mismo:context> Page 44
45 <mismo:ldd_name>notary Title Description</mismo:LDD_NAME> <xs:attribute name="_unparsedname" type="xs:string"> <xs:documentation>the unparsed name of the notary.</xs:documentation> <mismo:context>notary</mismo:context> <mismo:ldd_name>notary Unparsed Name</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_parcel_identification_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_type" type="pria_parcelidentificationtypeenumerated"> <xs:documentation>specifies other parcel identification types besides Assessors Parcel identifiers that are used by taxing authorities or others to identify a parcel of property.</xs:documentation> <mismo:datatype>enumerated</mismo:datatype> <mismo:context>parcel Identification</mismo:CONTEXT> <mismo:ldd_name>parcel Identification Type</mismo:LDD_NAME> <xs:attribute name="_typeotherdescription" type="xs:string"> <xs:documentation>a free-form text field used to describe the parcel identification if Other is selected as the Parcel Identification Type.</xs:documentation> <mismo:context>parcel Page 45
46 Identification</mismo:CONTEXT> PRIA_DOCUMENT_v2_4_1 <mismo:ldd_name>parcel Identification Type Other Description</mismo:LDD_NAME> <xs:attribute name="_identifier" type="xs:string"> <xs:documentation>a free-form text field used to hold the actual identification value of the type specified by Parcel Identification Type.</xs:documentation> <mismo:context>parcel Identification</mismo:CONTEXT> <mismo:ldd_name>parcel Identification Identifier</mismo:LDD_NAME> </xs:complextype> <xs:complextype name="pria_parsed_street_address_type"> <xs:sequence/> <xs:attribute name="_id" type="xs:id"/> <xs:attribute name="_streetname" type="xs:string"> <xs:documentation>the street name component of an address without any direction or quadrant indicators or street suffixes.</xs:documentation> <mismo:context>parsed Street Address</mismo:CONTEXT> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> <mismo:process_area>servicing Page 46
47 <mismo:ldd_name>parsed Street Address Street Name</mismo:LDD_NAME> <xs:attribute name="_directionprefix" type="xs:string"> <xs:documentation>the Direction Prefix address component that appears before the Street Name. (N, S, E, W, NW, SW, NE, SE).</xs:documentation> <mismo:context>parsed Street Address</mismo:CONTEXT> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> <mismo:process_area>servicing <mismo:ldd_name>parsed Street Address Direction Prefix</mismo:LDD_NAME> <xs:attribute name="_directionsuffix" type="xs:string"> <xs:documentation>the Direction Suffix address component that appears after the Street Name. (N, S, E, W, NW, SW, NE, SE).</xs:documentation> <mismo:context>parsed Street Address</mismo:CONTEXT> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Page 47 <mismo:process_area>servicing
48 <mismo:ldd_name>parsed Street Address Direction Suffix</mismo:LDD_NAME> <xs:attribute name="_streetsuffix" type="xs:string"> <xs:documentation>the street suffix or street type component of an address (ST, AV, BV, CT, DR, PL, etc.) Use U.S. Postal Service approved abbreviations.</xs:documentation> <mismo:context>parsed Street Address</mismo:CONTEXT> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> <mismo:process_area>servicing <mismo:ldd_name>parsed Street Address Street Suffix</mismo:LDD_NAME> <xs:attribute name="_housenumber" type="xs:string"> <xs:documentation>the house number address component.</xs:documentation> <mismo:context>parsed Street Address</mismo:CONTEXT> <mismo:process_area>credit Reporting</mismo:PROCESS_AREA> <mismo:process_area>secondary Delivery</mismo:PROCESS_AREA> <mismo:process_area>servicing</mismo:process_area> <mismo:process_area>aus</mismo:process_area> Transfer</mismo:PROCESS_AREA> Page 48 <mismo:process_area>servicing
The Models of erecording A Continuum of Electronic Recording Updated
2501 Aerial Center Parkway, Suite 103, Morrisville, NC 27560 877.997.7742 The Models of erecording A Continuum of Electronic Recording Updated Adopted by the PRIA Board on August 27, 2013 http://www.pria.us
More informationLevel of Assurance Authentication Context Profiles for SAML 2.0
2 3 4 5 Level of Assurance Authentication Context Profiles for SAML 2.0 Draft 01 01 April 2008 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Specification URIs: This
More informationSDLC INTELLECTUAL PROPERTY POLICY
SDLC INTELLECTUAL PROPERTY POLICY Last Revised: 11/14/17 1. Introduction. This Intellectual Property Policy ( Policy ) governs intellectual property rights of the SDL Consortium ( SDLC ) and its Members
More informationBar Code Discovery. Administrator's Guide
Bar Code Discovery Administrator's Guide November 2012 www.lexmark.com Contents 2 Contents Overview...3 Configuring the application...4 Configuring the application...4 Configuring Bar Code Discovery...4
More informationUsing Inventory Export Guide
Introducing Inventory Import and Export XML Using Inventory Export Guide To Manage Your Inventory Data Version 1.0 ADD TO CART XML API GUIDE 5/28/13 PAGE 1 Copyright 2013 Shopatron, Inc. Using Inventory
More informationCA File Master Plus. Release Notes. Version
CA File Master Plus Release Notes Version 9.0.00 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for
More informationOracle B2B 11g Technical Note. Technical Note: 11g_005 Attachments. Table of Contents
Oracle B2B 11g Technical Note Technical Note: 11g_005 Attachments This technical note lists the attachment capabilities available in Oracle B2B Table of Contents Overview... 2 Setup for Fabric... 2 Setup
More informationIETF TRUST. Legal Provisions Relating to IETF Documents. February 12, Effective Date: February 15, 2009
IETF TRUST Legal Provisions Relating to IETF Documents February 12, 2009 Effective Date: February 15, 2009 1. Background The IETF Trust was formed on December 15, 2005, for, among other things, the purpose
More informationIETF TRUST. Legal Provisions Relating to IETF Documents. Approved November 6, Effective Date: November 10, 2008
IETF TRUST Legal Provisions Relating to IETF Documents Approved November 6, 2008 Effective Date: November 10, 2008 1. Background The IETF Trust was formed on December 15, 2005, for, among other things,
More informationSYNDICATING HIERARCHIES EFFECTIVELY
SDN Contribution SYNDICATING HIERARCHIES EFFECTIVELY Applies to: SAP MDM 5.5 Summary This document introduces hierarchy tables and a method of effectively sending out data stored in hierarchy tables. Created
More informationPanasonic Audio Player 2 User Guide
Panasonic Audio Player 2 User Guide ASIO is a trademark and software of Steinberg Media Technologies GmbH. Overview Panasonic Audio Player 2 is simple GUI audio player software for Windows and Mac OS with
More informationMessages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.
May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which
More informationIntellectual Property Rights Notice for Open Specifications Documentation
[MS-SSISPARAMS-Diff]: Intellectual Property Rights tice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats,
More informationCertification Test Plan SSRF Conformance for OpenSSRF Software v Document WINNF-14-S-0023
Certification Test Plan SSRF Conformance for OpenSSRF Software v3.1.0 Document WINNF-14-S-0023 Version V1.0.0 10 February 2015 TERMS, CONDITIONS & NOTICES This document has been prepared by the Open SSRF
More informationTechnics Audio Player User Guide
Technics Audio Player User Guide Overview Technics Audio Player is simple GUI audio player software for Windows and Mac OS with high-resolution audio data processing capabilities. When connected to Technics
More informationEcma International Policy on Submission, Inclusion and Licensing of Software
Ecma International Policy on Submission, Inclusion and Licensing of Software Experimental TC39 Policy This Ecma International Policy on Submission, Inclusion and Licensing of Software ( Policy ) is being
More informationOracle Hospitality OPERA Exchange Interface Profile Lookup Vendor Specification. May 2018
Oracle Hospitality OPERA Exchange Interface Profile Lookup Vendor Specification May 2018 Copyright 2004, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation
More informationTERMS OF SERVICE AGREEMENT
TERMS OF SERVICE AGREEMENT LAST REVISION: [Date-Month-Year] PLEASE READ THIS TERMS OF SERVICE AGREEMENT CAREFULLY. BY USING THIS WEBSITE OR ORDERING PRODUCTS FROM THIS WEBSITE YOU AGREE TO BE BOUND BY
More information[MS-KPS-Diff]: Key Protection Service Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-KPS-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationEcma International Policy on Submission, Inclusion and Licensing of Software
Ecma International Policy on Submission, Inclusion and Licensing of Software Experimental TC39 Policy This Ecma International Policy on Submission, Inclusion and Licensing of Software ( Policy ) is being
More informationAdditional License Authorizations for HPE OneView for Microsoft Azure Log Analytics
Additional License Authorizations for HPE OneView for Microsoft Azure Log Analytics Product Use Authorizations This document provides Additional License Authorizations for HPE OneView for Microsoft Azure
More informationTS SIGNATURE VALIDATION REPORT
TS 119 102 2 SIGNATURE VALIDATION REPORT An introduction Presented by Peter Lipp for the esignature and eseal validation workshop, Jan 10 2018 Agenda Scope Relation to EN 319 102 1 Approach Report structure
More information[MS-SSISPARAMS-Diff]: Integration Services Project Parameter File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSISPARAMS-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for
More informationMERIDIANSOUNDINGBOARD.COM TERMS AND CONDITIONS
MERIDIANSOUNDINGBOARD.COM TERMS AND CONDITIONS Introduction This document sets forth the terms and conditions ("Terms and Conditions") governing your use of the MeridianHealth.com Web site ("Web Site")
More informationThe Travel Tree Terms and Conditions
The Travel Tree Terms and Conditions Please read the following Terms & Conditions carefully before using this site. Use of this site indicates acceptance of these Terms and Conditions. The following terms
More informationIntroduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML
Introduction Syntax and Usage Databases Java Tutorial November 5, 2008 Introduction Syntax and Usage Databases Java Tutorial Outline 1 Introduction 2 Syntax and Usage Syntax Well Formed and Valid Displaying
More informationDomain Hosting Terms and Conditions
Domain Hosting Terms and Conditions Preamble This document may be augmented or replaced by relevant sections of other parts of our Agreement, and should be read in conjunction with other supporting documents,
More informationMyCreditChain Terms of Use
MyCreditChain Terms of Use Date: February 1, 2018 Overview The following are the terms of an agreement between you and MYCREDITCHAIN. By accessing, or using this Web site, you acknowledge that you have
More informationOCTOSHAPE SDK AND CLIENT LICENSE AGREEMENT (SCLA)
OCTOSHAPE SDK AND CLIENT LICENSE AGREEMENT (SCLA) This is a License Agreement (the "Agreement") for certain code (the Software ) owned by Akamai Technologies, Inc. ( Akamai ) that is useful in connection
More informationOracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On
Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On Configuration Guide E84772-01 Last Update: Monday, October 09, 2017 Oracle Utilities Opower Energy Efficiency Web Portal -
More informationFONT SOFTWARE END USER LICENSE AGREEMENT. We recommend that you print this Font Software End User License Agreement for further reference.
FONT SOFTWARE END USER LICENSE AGREEMENT We recommend that you print this Font Software End User License Agreement for further reference. This Font Software End User License Agreement (the Agreement )
More informationLOGO LICENSE AGREEMENT(S) CERTIPORT AND IC³
LOGO LICENSE AGREEMENT(S) CERTIPORT AND IC³ EXHIBIT B-2 LICENSEE: Address: Attention: Phone: Fax: Email: Account #: CERTIPORT LOGO LICENSE AGREEMENT Authorized Testing Centers This Logo License Agreement
More informationConfiguring LDAP and Single Sign-On
Service Pack 3 Configuring LDAP and Single Sign-On Nuance Management Server Administrator Guide Page 1 Table of Contents Table of Contents...2 Creating Single Sign-On user accounts... 4 Implementing EHR
More informationHitachi ID Identity and Access Management Suite TRIAL USE LICENSE AGREEMENT. between
between Hitachi ID Systems, Inc. (hereinafter referred to as "HIDS", "we" and/or "us") and LICENSEE (see below) (hereinafter referred to as "LICENSEE" and/or "you".) (Please complete ALL fields below by
More informationOracle Technology Network Developer License Terms for Java Card Classic Edition and Java Card Connected Edition Software Development Kits
Oracle Technology Network Developer License Terms for Java Card Classic Edition and Java Card Connected Edition Software Development Kits Export Controls Export laws and regulations of the United States
More informationsaml requesting attributes v1.1 wd01 Working Draft January 2016 Standards Track Draft Copyright OASIS Open All Rights Reserved.
Standards Track Draft Copyright OASIS Open 2015. All Rights Reserved. Page 1 of 10 SAML v2.0 Protocol Extension for Requesting Attributes in AuthnRequest Version 1.1 Working Draft 02 19 January 2016 Technical
More informationApple Inc. itunes 10 and QuickTime 7 Bundling Agreement (University CD Distribution) Licensee (Institution Name): Individual to Contact:
Apple Inc. itunes 10 and QuickTime 7 Bundling Agreement (University CD Distribution) Please complete, sign and mail this agreement to: APPLE INC. Software Licensing Department 12545 Riata Vista Circle
More informationEMPLOYER CONTRIBUTION AGREEMENT
EMPLOYER CONTRIBUTION AGREEMENT This Employer Contribution Agreement ( Agreement ) is entered into by and between, your successors and assigns ( You ) and Oracle America, Inc. ( Oracle ) as of the date
More informationDomain Names & Hosting
Domain Names & Hosting 1 The following terms and conditions apply to the domain registration Service: 1.1 You acknowledge and recognize that the domain name system and the practice of registering and administering
More informationSite Impact Policies for Website Use
Site Impact Policies for Website Use Thank you for visiting the Site Impact website (the Website ). We have set up some ground rules to ensure protection of our rights and yours. Site Impact reserves the
More informationINCLUDING MEDICAL ADVICE DISCLAIMER
Jordan s Guardian Angels Terms and Conditions of Use INCLUDING MEDICAL ADVICE DISCLAIMER Your use of this website and its content constitutes your agreement to be bound by these terms and conditions of
More informationQNB Bank-ONLINE AGREEMENT
This is an Agreement between you and QNB Bank ("QNB"). It explains the rules of your electronic access to your accounts through QNB Online. By using QNB-Online, you accept all the terms and conditions
More informationDEMO MANUAL DC2645A LTC MHz to 9GHz High Linearity I/Q Demodulator with Wideband IF Amplifier DESCRIPTION BOARD PHOTO
DESCRIPTION Demonstration circuit 2645A showcases the LTC 5594 300MHz to 9GHz high linearity I/Q demodulator with wideband IF amplifiers. The USB serial controller, DC590B, is required to control and configure
More informationEnhanced Serial Peripheral Interface (espi) ECN
Enhanced Serial Peripheral Interface (espi) ECN Engineering Change Notice TITLE Clarify OOB packet payload DATE 10 January 2014 AFFECTED DOCUMENT espi Base Specification Rev 0.75 DISCLOSURE RESTRICTIONS
More informationLIST RENTAL CONTRACT
LIST RENTAL CONTRACT After execution of this Contract and upon receipt of order(s) from List Enduser or their list broker that is acceptable to MSLA INTERNATIONAL and contractual affiliates ( List Owners
More informationCMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION
CMS SOAP CLIENT SOFTWARE REQUIREMENTS SPECIFICATION CONTENTS 1. Introduction 1.1. Purpose 1.2. Scope Of Project 1.3. Glossary 1.4. References 1.5. Overview Of Document 2. Overall Description 2.1. System
More informationAhnLab Software License Agreement
AhnLab Software License Agreement IMPORTANT - READ CAREFULLY BEFORE USING THE SOFTWARE. This AhnLab Software License Agreement (this "Agreement") is a legal agreement by and between you and AhnLab, Inc.
More informationORGANIZEFOR PETITION PLATFORM ColorOfChange MOVEMENT-BUILDING PARTNERSHIP PROGRAM TERMS OF SERVICE
ORGANIZEFOR PETITION PLATFORM ColorOfChange MOVEMENT-BUILDING PARTNERSHIP PROGRAM TERMS OF SERVICE These Terms of Service ( TOS ) apply to organizations that have applied for and been accepted to participate
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-ASCNTC]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationMQ Port Scan Installation and Operation Manual
MQ Port Scan Installation and Operation Manual Capitalware Inc. Unit 11, 1673 Richmond Street, PMB524 London, Ontario N6G2N3 Canada sales@capitalware.com http://www.capitalware.com MQPS Installation and
More informationStewart Title Guaranty Company
Stewart Title Guaranty Company Landtech provides built-in integration with Stewart Title Guaranty Company s web based underwriter service. This enables you to access their web based service from within
More informationextensible Name Language (xnl) Specifications and Description Document
extensible Name Language (xnl) Specifications and Description Document CHANGE HISTORY Status Version Date Author Summary of Changes Draft 1.0 1 March 2001 CIQ-TC Initial Draft Draft 1.1 17 May 2001 CIQ-TC
More informationCustomer Market Results Interface (CMRI) For RC Interface Specification. Version: 1.0.0
Customer Market Results Interface (CMRI) For RC Interface Specification Version: 1.0.0 November 1, 2018 Revision History Date Version Description 11/01/2018 1.0.0 Initial document release Page 2 of 10
More informationTerms of Use. Changes. General Use.
Terms of Use THESE TERMS AND CONDITIONS (THE TERMS ) ARE A LEGAL CONTRACT BETWEEN YOU AND SPIN TRANSFER TECHNOLOGIES ( SPIN TRANSFER TECHNOLOGIES, STT, WE OR US ). THE TERMS EXPLAIN HOW YOU ARE PERMITTED
More informationAutomotive Append - Version 1.0.0
Automotive Append - Version 1.0.0 WSDL: http://ws.strikeiron.com/autoappend?wsdl Product Web Page: http://www.strikeiron.com/data-enrichment/automotive-append/ Description: StrikeIron s Automotive Append
More informationOracle Technology Network Developer License Terms for Java Card Classic Edition and Java Card Connected Edition Specifications
Oracle Technology Network Developer License Terms for Java Card Classic Edition and Java Card Connected Edition Specifications Export Controls Export laws and regulations of the United States and any other
More informationINCOME FOR LIFE MODEL Sign Up Form Please complete this form and fax it to:
INCOMEFORLIFEMODEL SignUpForm Pleasecompletethisformandfaxitto:781-730-0706 AgentInformation Name CompanyName Address City State Zip BrokerDealerandDisclosureInformation IamaRegisteredRepresentativeYes
More informationEnd User License Agreement
End User License Agreement Kyocera International, Inc. ( Kyocera ) End User License Agreement. CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS ( AGREEMENT ) BEFORE USING OR OTHERWISE ACCESSING THE SOFTWARE
More informationMile Terms of Use. Effective Date: February, Version 1.1 Feb 2018 [ Mile ] Mileico.com
Mile Terms of Use Effective Date: February, 2018 Version 1.1 Feb 2018 [ Mile ] Overview The following are the terms of an agreement between you and MILE. By accessing, or using this Web site, you acknowledge
More informationOracle Binary Code License Agreement for Java Secure Sockets Extension for Connected Device Configuration 1.0.2
Oracle Binary Code License Agreement for Java Secure Sockets Extension 1.0.3 for Connected Device Configuration 1.0.2 ORACLE AMERICA, INC. ("ORACLE"), FOR AND ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND
More informationfontseek.info outofthedark.xyz
Gza Seminegra 116 pt Gza Seminegra 102 pt Blitz Script 52 pt fontseek.info outofthedark.xyz 1 OWNERSHIP OF PRODUCT AND COPYRIGHT OUT OF THE DARK Print page 1 / 2 a The digital files downloaded to your
More informationTechnical requirements
ANNEX 1: TECHNICAL REQUIREMENTS Technical requirements 1. Introduction... 2 2. Overview of the import formalities section of the market access database... 2 2.1. Architecture... 2 2.2. The dataset... 2
More informationBar Code Discovery. Administrator's Guide
Bar Code Discovery Administrator's Guide September 2016 www.lexmark.com Contents 2 Contents Overview... 3 Optimizing bar code detection...4 Optimizing bar code detection...4 Configuring the application...5
More informationELECTRONIC RECORDING MEMORANDUM OF UNDERSTANDING
ELECTRONIC RECORDING MEMORANDUM OF UNDERSTANDING THIS MEMORANDUM OF UNDERSTANDING, dated, is between Caldwell County, North Carolina ( COUNTY ), and COMPANY ) with offices at. Caldwell County desires to
More informationerwin Data Modeler Creating Custom Mart Reports Using a Reporting Tool Release 9.7
erwin Data Modeler Creating Custom Mart Reports Using a Reporting Tool Release 9.7 This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred
More informationVSC-PCTS2003 TEST SUITE TIME-LIMITED LICENSE AGREEMENT
VSC-PCTS2003 TEST SUITE TIME-LIMITED LICENSE AGREEMENT Notes These notes are intended to help prospective licensees complete the attached Test Suite Time-Limited License Agreement. If you wish to execute
More informationCertification Test Requirements for Conformance with the Standard Spectrum Resource Format (SSRF) Document WINNF-14-S-0022
Certification Test Requirements for Conformance with the Standard Spectrum Resource Format (SSRF) Document WINNF-14-S-0022 Version V2.0.0 10 Feburary 2015 TERMS, CONDITIONS & NOTICES This document has
More informationUpgrading MYOB BankLink Notes (desktop)
Upgrading MYOB BankLink Notes (desktop) Contents Upgrading MYOB BankLink Notes (desktop)...4 Upgrading MYOB BankLink Notes using the automatic upgrade 4 Upgrading MYOB BankLink Notes when asked to upgrade
More informationVMware vcenter Log Insight Manager. Deployment Guide
VMware vcenter Log Insight Manager Deployment Guide VERSION: 6.0 UPDATED: JULY 2016 Copyright Notices Copyright 2002-2016 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP Technologies
More informationpython Roll: Users Guide 5.5 Edition
python Roll: Users Guide 5.5 Edition python Roll: Users Guide : 5.5 Edition Published May 08 2012 Copyright 2012 The copyright holder, and UC Regents Table of Contents Preface...iv 1. Installing the python
More informationELECTRONIC RECORDING MEMORANDUM OF UNDERSTANDING
ELECTRONIC RECORDING MEMORANDUM OF UNDERSTANDING THIS MEMORANDUM OF UNDERSTANDING, dated, is between the Davie County North Carolina Register of Deeds office ( COUNTY ), and ( COMPANY ) with offices located
More informationEvaluation Board User Guide UG-302
Evaluation Board User Guide UG-302 One Technology Way P.O. Box 9106 Norwood, MA 02062-9106, U.S.A. Tel: 781.329.4700 Fax: 781.461.3113 www.analog.com Evaluation Board for the ADM2491E ±8 kv Signal Isolated,
More informationQUARTZ LEGAL TERMS AND CONDITIONS
QUARTZ LEGAL TERMS AND CONDITIONS 1. USE OF THIS WEBSITE: The Quartz vodka website is owned and operated by Ungava Spirits Co. Ltd. (collectively hereafter "Site Owner"). Your use of this website is subject
More informationRSA Two Factor Authentication
RSA Two Factor Authentication Feature Description VERSION: 6.0 UPDATED: JULY 2016 Copyright Notices Copyright 2002-2016 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP Technologies
More information4. Save as expressly set out herein no license is granted in respect of any intellectual property rights vested in F1000 or other third parties.
Legal information The website F1000.com is operated by Faculty of 1000 Limited, a company registered in England and Wales with Company Number 3739756, with registered offices at Middlesex House, 34-42
More informationIf the firmware version indicated is earlier than the "Version 1.06", please update the unit s firmware.
STEP 1. Check the current firmware version Panasonic recommends that you update the firmware in your SC-C70 if the firmware version indicated is older than the version being offered. Please check the current
More informationOracle Binary Code License Agreement for the Java SE Platform Products and JavaFX
Oracle Binary Code License Agreement for the Java SE Platform Products and JavaFX ORACLE AMERICA, INC. ("ORACLE"), FOR AND ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES UNDER COMMON CONTROL,
More informationCERTIFIED MAIL LABELS TERMS OF USE and PRIVACY POLICY Agreement
CERTIFIED MAIL LABELS TERMS OF USE and PRIVACY POLICY Agreement Welcome to Certified Mail Envelopes and Certified Mail Labels web sites (the Site ) a website, trademark and business name owned and operated
More informationPaperless Closer 2.5 Instructions. I. Place an Order Using ATG Paperless Closer. 1. Login: Go to
Paperless Closer 2.5 Instructions I. Place an Order Using ATG Paperless Closer 1. Login: Go to http://resource.atgf.com 2. At the login enter your user name and password Do not use dash, in your password
More informationPacket Trace Guide. Packet Trace Guide. Technical Note
Packet Trace Guide Technical Note VERSION: 2.0 UPDATED: JANUARY 2016 Copyright Notices Copyright 2002-2016 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP Technologies logo
More informationSplunk. Splunk. Deployment Guide
Deployment Guide VERSION: 1.0 UPDATED: JULY 2016 Copyright Notices Copyright 2002-2016 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP Technologies logo are registered trademarks
More informationUS Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Service Data Objects (SDO) DFED Sample Application README Copyright IBM Corporation, 2012, 2013 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract
More informationPTC Integrity 10.7 Web Services Reference
PTC Integrity 10.7 Web Services Reference PTC Integrity 10.7 Web Services Reference Copyright 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation
More informationData Bus Client Interface Manager Interface Control Document
SunGuide SM : Data Bus Client Interface Manager Interface Control Document SunGuide-DB-CIM-ICD-1.0.0 Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee
More informationServerStatus Installation and Operation Manual
ServerStatus Installation and Operation Manual Capitalware Inc. Unit 11, 1673 Richmond Street, PMB524 London, Ontario N6G2N3 Canada sales@capitalware.com http://www.capitalware.com ServerStatus Installation
More informationSUPPORT MATRIX. HYCU OMi Management Pack for Citrix
HYCU OMi Management Pack for Citrix : 2.0 Product release date: October 2017 Document release data: April 2018 Legal notices Copyright notice 2014-2018 HYCU. All rights reserved. This document contains
More informationFLUENDO GENERIC EULA
FLUENDO GENERIC EULA FLUENDO S.A. Avenida Diagonal 579, 8th floor 08014 Barcelona Spain 1 END USER LICENSE AGREEMENT (EULA) FLUENDO LICENSE AGREEMENT BY FLUENDO, S.A. ( FLUENDO ) IMPORTANT - READ CAREFULLY
More informationSIMS TERMS AND CONDITIONS OF USE AGREEMENT
SIMS TERMS AND CONDITIONS OF USE AGREEMENT 1. These Terms and Conditions ("the Terms and Conditions") govern your ("the User") use of the Website and Web application and the information thereon, known
More information1. License Grant; Related Provisions.
IMPORTANT: READ THIS AGREEMENT CAREFULLY. THIS IS A LEGAL AGREEMENT BETWEEN AVG TECHNOLOGIES CY, Ltd. ( AVG TECHNOLOGIES ) AND YOU (ACTING AS AN INDIVIDUAL OR, IF APPLICABLE, ON BEHALF OF THE INDIVIDUAL
More informationUSB-IF Product Order Form
USB-IF Product Order Form Please use the following information to select the test hardware from the USB-IF estore. USB 3.1 (10 GT/s) Type-C Electrical Test Fixture Kit The USB 3.1 USB (10 GT/s) Type-C
More informationQosPolicyHolder:1 Erratum
Erratum Number: Document and Version: Cross References: Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to the service document QosPolicyHolder:1 This Erratum has
More informationBCDC 2E, 2012 (On-line Bidding Document for Stipulated Price Bidding)
BCDC 2E, 2012 (On-line Bidding Document for Stipulated Price Bidding) CLAUSE 13 ON-LINE BIDDING 13.1 ON-LINE BIDDING.1 Definitions: Owner means the party and/or their agent designated to receive on-line
More informationBBPS API Sepcifications
BBPS API Sepcifications v11.0 BBPS API Sepcifications v11.0 Page 1 Table of Contents 1 Bill Fetch Request 4 Sample Bill Fetch Request API 4 Bill Fetch Request Tag Details 5 Bill Fetch Request XSD 6 2 Bill
More informationTHIS IS A CONTRACT BETWEEN YOU AND VEC (Village Emergency Center).
Terms and Conditions VEC Entity Terms and Conditions Updated: 01/22/18 GO TO THE EMERGENCY ROOM OF A LOCAL HOSPITAL OR DIAL 911 IMMEDIATELY IN THE EVENT OF AN EMERGENCY. THIS IS A CONTRACT BETWEEN YOU
More informationAvast Customer & Technical Support Policy
Avast Customer & Technical Support Policy PLEASE READ THE TERMS AND CONDITIONS OF THIS SUPPORT POLICY ( SUPPORT POLICY ). THIS SUPPORT POLICY IS PROVIDED BY AVAST SOFTWARE s.r.o., A COMPANY DULY ORGANIZED
More informationEnd User License Agreement
End User License Agreement This End User License Agreement ( EULA ) is a legal agreement between the end-user Customer of Gigamon hardware and software products ( Customer ) and Gigamon Inc. ( Gigamon
More informationDistributed Intelligent Capture. Integration Guide
Distributed Intelligent Capture Integration Guide July 2014 www.lexmark.com Contents 2 Contents Overview... 3 Getting started... 4 Understanding the integration process... 4 Configuring the engines...
More informationAutomated Load Forecast System (ALFS) For RC Interface Specification
Automated Load Forecast System (ALFS) For RC Interface Specification Version: 1.0 October 22, 2018 Revision History Date Version Description 10/23/2018 1.0 Initial document release related to the Load
More informationMetadata for SAML 1.0 Web Browser Profiles
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Metadata for SAML 1.0 Web Browser Profiles Working Draft 00, 12 November 2002 Document identifier: draft-sstc-saml-meta-data-00 Location:
More informationInstalling the Shrew Soft VPN Client
Windows Install Installing the Shrew Soft VPN Client ShrewVPNWindows201211-01 Global Technology Associates 3505 Lake Lynda Drive Suite 109 Orlando, FL 32817 Tel: +1.407.380.0220 Fax. +1.407.380.6080 Email:
More information