<?xml version="1.0" encoding="UTF-8"?>
<!--
     Electronic Court Filing Version 5.01
     Committee Specification Draft 01
     23 May 2022
     Copyright (c) OASIS Open 2022. All Rights Reserved.
     Source: https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/examples/
     Latest version of narrative specification: https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/ecf-v5.01.html
     TC IPR Statement: https://www.oasis-open.org/committees/legalxml-courtfiling/ipr.php
-->
<!--Sample XML file generated by XMLSpy v2018 sp1 (http://www.altova.com)-->
<wrappers:ServeFilingRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:structures="http://release.niem.gov/niem/structures/4.0/" xmlns:nc="http://release.niem.gov/niem/niem-core/4.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/6.1/" xmlns:ecf="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/ecf" xmlns:filing="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/filing" xmlns:payment="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/payment" xmlns:wrappers="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/wrappers" xsi:schemaLocation="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/wrappers ../schema/wrappers.xsd">
	<filing:FilingMessage xsi:schemaLocation="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/filing ../schema/filing.xsd">
		<!-- The nc:DocumentIdentification element below is a Message Identifier (see section 6.2.5), in this circumstance, assigned by the FAMDE. -->
		<nc:DocumentIdentification>
			<nc:IdentificationID>0d58f2a0-fffe-42df-85ee-801d34c07c0d</nc:IdentificationID>
			<nc:IdentificationCategoryDescriptionText>messageID</nc:IdentificationCategoryDescriptionText>
			<nc:IdentificationSourceText>FilingAssembly</nc:IdentificationSourceText>
			<!-- Per 6.2.4 the originating MDE for each identifier SHOULD be identified in nc:IdentificationSourceText (above) with a value from
				 MajorDesignElementTypeCode.gc -->
		</nc:DocumentIdentification>
		<ecf:SendingMDELocationID>
			<nc:IdentificationID>http://example.com/efsp1</nc:IdentificationID>
		</ecf:SendingMDELocationID>
		<ecf:ServiceInteractionProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-5.0</ecf:ServiceInteractionProfileCode>
		<j:CaseCourt>
			<nc:OrganizationIdentification>
				<!-- content reference for a court organization -->
				<nc:IdentificationID>harris:dc</nc:IdentificationID>
			</nc:OrganizationIdentification>
		</j:CaseCourt>
		<!-- nc:DocumentPostDate below contains the timestamp of the request -->
		<nc:DocumentPostDate>
			<nc:DateTime>2008-07-07T13:47:42.0Z</nc:DateTime>
		</nc:DocumentPostDate>
		<ecf:ElectronicServiceInformation>
			<ecf:ReceivingMDELocationID>
				<nc:IdentificationID>http://example.com/efsp2</nc:IdentificationID>
			</ecf:ReceivingMDELocationID>
			<ecf:ReceivingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-5.0</ecf:ReceivingMDEProfileCode>
			<!-- ecf:ServiceRecipientID identifies who was served electronically. see section 6.2.10 -->
			<!-- The ServiceRecipientID below corresponds to an entity belonging to a firm in the Tyler implementation -->
			<ecf:ServiceRecipientID>
				<nc:IdentificationID>69395710-70B5-4C52-9DF3-F8C6A59A710C</nc:IdentificationID>
			</ecf:ServiceRecipientID>
		</ecf:ElectronicServiceInformation>
		<filing:FilingConnectedDocument structures:id="Document2">
			<nc:DocumentDescriptionText>Exhibit</nc:DocumentDescriptionText>
			
			<!-- nc:DocumentEffectiveDate is the docketing date (see UML definition in niem-mapping.csv, copied below).  
				 UML defintion: "the date and time of day on which an entry in the docket or register of action in the court 
				 CMS was completed for a filing" -->
				 
			<!-- As such, and since this document has not yet been docketed, use of this element (i.e. nc:DocumentEffectiveDate) in
				 this context (i.e. ReviewDocketingRequest) is not appropriate. 
				 Element nc:DocumentEffectiveDate must not appear in ReviewFilingRequest. -->
			<!--	<nc:DocumentEffectiveDate>	-->
	
			<!-- The defintion for nc:DocumentFileControlID is: "An identifier applied to a document to locate it within a file control system." -->
			<!-- Bullet 2 in section 6.2.6 Document Identifiers states: 
				 "nc:DocumentFileControlID is a reference to a unique document in the Court Record system and is assigned by the Court Record MDE.
				 The values for this element MUST be unique within a court." --> 
				 
			<!-- After consideration by an ECF TC work group, it was concluded that the usage below in which nc:DocumentFileControlID contains a filename
				 as file system document identifier by the submitter in the FAMDE is not appropriate. -->
			<!--
			<nc:DocumentFileControlID>Exhibits.docx</nc:DocumentFileControlID>
			-->
			<!-- The Document Identifier below is assigned by the FAMDE -->
			<nc:DocumentIdentification>
				<nc:IdentificationID>1</nc:IdentificationID>
				<nc:IdentificationSourceText>FilingAssembly</nc:IdentificationSourceText>
			</nc:DocumentIdentification>
			
			<nc:DocumentSequenceID>2</nc:DocumentSequenceID>
			<ecf:DocumentAugmentation>
				<ecf:DocumentRendition>
					<nc:DocumentIdentification/>
					<!--ecf:DocumentSignature>
						<ecf:SignatureAugmentation>
							<xmlsig:Signatures xmlns:xmlsig="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0 ../ecf-v3.0-xmlsig.xsd">
								<xmlsig:Signature>
									<xmlsig:SignerName>Jane Doe</xmlsig:SignerName>
									<xmlsig:SignedDate>2008-07-07</xmlsig:SignedDate>
									<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
										<ds:SignedInfo Id="foobar">
											<ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
											<ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
											<ds:Reference>
												<ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
												<ds:DigestValue>j6lwx3rvEPO0vKtMup4NbeVu8nk=</ds:DigestValue>
											</ds:Reference>
										</ds:SignedInfo>
										<ds:SignatureValue>UjBsR09EbGhjZ0dTQUxNQUFBUUNBRU1tQ1p0dU1GUXhEUzhi</ds:SignatureValue>
										<ds:KeyInfo>
											<ds:X509Data>
												<ds:X509SubjectName>CN=John Smith,O=ABC Inc.,ST=Seattle,C=WA</ds:X509SubjectName>
												<ds:X509Certificate>UjBsR09EbGhjZ0dTQUxNQUFBUUNBRU1tQ1p0dU1GUXhEUzhi</ds:X509Certificate>
											</ds:X509Data>
										</ds:KeyInfo>
									</ds:Signature>
								</xmlsig:Signature>
							</xmlsig:Signatures>
						</ecf:SignatureAugmentation>
						<ecf:SignatureProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileCode>
					</ecf:DocumentSignature-->
					<nc:Attachment structures:id="Attachment2">
						<nc:BinaryDescriptionText>Adobe Acrobat</nc:BinaryDescriptionText>
						<!-- nc:BinaryDescriptionText (above) should be 'a description of a binary object'. -->
						<!-- nc:BinaryFormatText (below) should contain the MIME type. See 5.2.2  values defined in BinaryFormatText.gc -->
						<nc:BinaryFormatText>application/pdf</nc:BinaryFormatText>
						<nc:BinaryURI>cid://Payload2</nc:BinaryURI>
						<nc:BinarySizeValue>32000</nc:BinarySizeValue>
					</nc:Attachment>
				</ecf:DocumentRendition>
				<ecf:RedactionRequiredIndicator>false</ecf:RedactionRequiredIndicator>
				<ecf:SpecialHandlingInstructionsText>Please verify TCN</ecf:SpecialHandlingInstructionsText>

				<!-- nc:DocumentAssociation identifies Filing1 (complaint) as this document's parent document -->
				<nc:DocumentAssociation>
					<nc:PrimaryDocument structures:ref="Filing1" xsi:nil="true"/>
					<ecf:DocumentAssociationAugmentation>
						<!-- ecf:DocumentRelatedCode value must come from DocumentRelatedCode.gc -->
						<ecf:DocumentRelatedCode>parent</ecf:DocumentRelatedCode>
					</ecf:DocumentAssociationAugmentation>
				</nc:DocumentAssociation>
			</ecf:DocumentAugmentation>
		</filing:FilingConnectedDocument>
		
		<filing:FilingLeadDocument structures:id="Filing1">
			<!-- nc:DocumentEffectiveDate is the docketing date (see UML definition in niem-mapping.csv, copied below). 
				 UML defintion: "the date and time of day on which an entry in the docket or register of action in the court 
				 CMS was completed for a filing" -->
			<!-- As such, and since this document has not yet been docketed, use of this element (i.e. nc:DocumentEffectiveDate) in this context 
				 (i.e. ReviewDocketingRequest) is not appropriate, i.e. Element nc:DocumentEffectiveDate must not appear in ReviewFilingRequest. -->
			<!--	<nc:DocumentEffectiveDate>	-->

			<!-- This is an external reference for the document assigned by the FAMDE. --> 
			<nc:DocumentIdentification>
				<nc:IdentificationID>2</nc:IdentificationID>
				<nc:IdentificationSourceText>FilingAssembly</nc:IdentificationSourceText>
			</nc:DocumentIdentification>
			
			<nc:DocumentSequenceID>1</nc:DocumentSequenceID>
			<nc:DocumentTitleText>This is a complaint</nc:DocumentTitleText>
			<ecf:DocumentAugmentation>
				<ecf:DocumentRendition>
					<nc:DocumentIdentification/>
					<nc:Attachment structures:id="Attachment1">
						<nc:BinaryDescriptionText>Adobe Acrobat</nc:BinaryDescriptionText>
						<nc:BinaryFormatText>application/pdf</nc:BinaryFormatText>
						<nc:BinaryURI>cid://Payload3</nc:BinaryURI>
						<nc:BinarySizeValue>32000</nc:BinarySizeValue>
					</nc:Attachment>
				</ecf:DocumentRendition>
				<ecf:RedactionRequiredIndicator>false</ecf:RedactionRequiredIndicator>
				<!-- ecf:RegisterActionDescriptionCode below contains the Filing code for 'Complaint' as provided by Court Policy. -->
				<!-- The Tyler implementation only requires RegisterActionDescriptionCode in the FilingLeadDocument -->
				<ecf:RegisterActionDescriptionCode>COMPLT</ecf:RegisterActionDescriptionCode>
			</ecf:DocumentAugmentation>
		</filing:FilingLeadDocument>
		
		<nc:Case xmlns:civil="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/civil" xsi:schemaLocation="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/civil ../schema/civil.xsd">
			<j:CaseAugmentation>
				<j:CaseCourt>
					<nc:OrganizationIdentification>
						<nc:IdentificationID>harris:dc</nc:IdentificationID>
					</nc:OrganizationIdentification>
				</j:CaseCourt>				
			</j:CaseAugmentation>
			<ecf:CaseAugmentation>
				<ecf:CaseNewIndicator>false</ecf:CaseNewIndicator>
				<!-- ecf:CaseTrackingID below contains the unique identifier for the case being filed into -->
				<ecf:CaseTrackingID>
					<nc:IdentificationID>19395710-70B5-4C52-9DF3-F8C6A59A710B</nc:IdentificationID>
				</ecf:CaseTrackingID>
			</ecf:CaseAugmentation>
			<civil:CaseAugmentation>
				<civil:AmountInControversy>
					<nc:Amount>1000</nc:Amount>
				</civil:AmountInControversy>
				<civil:ReliefTypeCode/>
				<ecf:CauseOfActionCode/>
			</civil:CaseAugmentation>
		</nc:Case>
	</filing:FilingMessage>	
	
	<payment:PaymentMessage xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xsi:schemaLocation="https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.01/payment ../schema/payment.xsd">
		<cac:Address/>
		<cac:AllowanceCharge>
			<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
			<cbc:Amount currencyID="USD">100.00</cbc:Amount>
			<cac:TaxCategory>
				<cbc:Percent>.0625</cbc:Percent>
				<cac:TaxScheme/>
			</cac:TaxCategory>
			<cac:TaxTotal>
				<cbc:TaxAmount currencyID="USD">.06</cbc:TaxAmount>
			</cac:TaxTotal>
			<cac:PaymentMeans>
				<cbc:PaymentMeansCode/>
				<!-- PaymentID below contains the identifier for the payment account -->
				<cbc:PaymentID>e74adb9f-f3fd-4a18-ad2b-662001ae97fa</cbc:PaymentID>
			</cac:PaymentMeans>
		</cac:AllowanceCharge>
		<payment:CorrectedPaymentIndicator>false</payment:CorrectedPaymentIndicator>
		<payment:Payer/>
	</payment:PaymentMessage>
</wrappers:ServeFilingRequest>
