Draft CSB CSO API documentation version 0.0.2
https://cso.jag.apis.gov.bc.ca
Overview
This is a working draft API Specification for CSB CSO.
The proposed API is based on (borrows from the concepts of) the ECF 4.01 specifications for the Legal-XML Electronic Court Filing (ECF). However it does not follow the recommendations of the ECF specification to the letter and is therefore not compatible and/or interoperable with any other existing ECF implementation; nor is it intended to be.
This draft constitutes what is considered to be a minimum implementation of the ECF specification. All of the Major Design Elements (MDEs) and Operations (represented as Components, Resources, and Methods or Patterns) are included in the documentation for completeness. Those that are not being used for this implementation are marked as Not Implemented.
The proposed implementation differs from the ECF specifications and recommendations in several aspects:
- It is implemented as a RESTful API, which has been based on the Web Services Service Interaction Profile 2.1 Specification.
- This initial implementation utilizes the XML schemas and examples defined in the ECF specification for example purposes only. The intent is to translate the messages and schemas into JSON.
Scope
The intent of this specification is similar to that of the ECF specifications in that it describes components needed to develop an electronic court filing system.
Basic familiarity with the ECF Specification is assumed.
This initial draft has been developed to provide a foundation to support discussion, feedback, collaboration, and the further design and development work needed to develop the API for it’s intended purpose in the CSB-eFiling system. It is not intended to be a complete specification. Details will be added and changes made as discussions proceed and the design evolves.
Examples of work to be done:
- Take a closer look at how files relate to the messages and how they flow through the ECF API to see what concepts we may be able to borrow.
- Determine appropriate methods for ensuring message and document integrity (support for non-repudiation).
- Determine security implementation(s).
- Convert XML messaging structures to JSON. Requires a review of the defined message to determine what may be extracted and incorporated into the API functionality. For example, additional query and/or filter parameters.
Filing Preparation to Court Record Process Flow
Minumum Implementation
This section describes the sequence of operations in the proposed minimum implementation.
The flow involves two parties (three logical components):
- A Filer (represented by the Filer Component)
- And a Court (represented by the Registry and Court Components)
The resources and methods supporting the processes in this flow are listed below, the equivalent ECF operation for each is listed in square brackets. The business rules associated with the methods is documented as part of the description of the method itself (within the API documentation). The resources and methods listed in bold are required and MUST occur in every successful filing as long as sending and receiving components are implemented. The other operations are optional and MAY occur within a given filing:
- /Registry/Policy - Get [GetPolicy]
- /Registry/Filing - Post [ReviewFiling]
- /Court/Record - Post [RecordFiling]
- Court Webhook Filing Event [NotifyDocketingComplete]
- Registry Webhook Filing Event [NotifyFilingReviewComplete]
Sequence Diagram
Full Implementation
This section describes the sequence of operations in a full implementation. This is provided for informaiton only, as many of the resources required are not being implemented.
The flow involves three parties (four logical components):
- A Filer (represented by the Filer Component)
- A Court (represented by the Registry and Court Components)
- A Service Recipient (represented by the LegalService Component)
The resources and methods supporting the processes in this flow are listed below, the equivalent ECF operation for each is listed in square brackets. The business rules associated with the methods is documented as part of the description of the method itself (within the API documentation). The resources and methods listed in bold are required and MUST occur in every successful filing as long as sending and receiving components are implemented. The other operations are optional and MAY occur within a given filing:
- /Registry/Policy - Get [GetPolicy]
- /Court/ServiceInformation - Get [GetServiceInformation, Not Implemented]
- /Registry/Filing/Fees - Get [GetFeesCalculation, Not Implemented]
- /Registry/Filing - Post [ReviewFiling]
- /LegalService/Serve - Post [ServeFiling, Not Implemented]
- /Court/Record - Post [RecordFiling]
- Court Webhook Filing Event [NotifyDocketingComplete]
- Registry Webhook Filing Event [NotifyFilingReviewComplete]
- At any point during or after posting a filing for review, if the filing is accessible, a party MAY access information through the following operations;
- /Registry/Filing - Get [GetFilingList, Not Implemented]
- /Registry/Filing/{caseTrackingID}/Status - Get [GetFilingStatus, Not Implemented]
- At any point after receiving an event from the the Registry Webhook, if the case is accessible, a party MAY access information through the following operations;
- /Court/Case - Get [GetCaseList, Not Implemented]
- /Court/Case/{caseID} - Get [GetCase, Not Implemented]
- /Court/Case/{caseID}/Documents/{documentID} - Get [GetDocument, Not Implemented]
Sequence Diagram
Filer (Filer Component)
Summary
The Filer is a REQUIRED logical component within the system which is equivalent/analogous to the Filing Assembly MDE from the ECF specification; which enables a filer to create a filing message for submission to a court, and for service on other parties in the case, returning a response from the court to the filer. It is not listed as a resource component as it does not implement any concrete API resources, it simply needs to provide a Webhook endpoint in order to conform to the patterns set forth.
This component is responsible for interacting with:
- The Registry in order to submit case files for review and filing with the Court.
- Optionally (Not Implemented), with the Court to request case files and documents.
- Optionally (Not Implemented), with the LegalService in order to distribute case files to other legal parties.
Registry Webhook
This component MUST implement a Webhook endpoint in order to receive asynchronous events from the Registry. This endpoint is equivalent/analogous to the NotifyFilingReviewComplete operation provided by the Filing Assembly MDE from the ECF specification. The payloads posted to the endpoint provide similar information to that of the NotifyFilingReviewCompleteMessage parameter of the NotifyFilingReviewComplete operation.
This endpoint must be able to accept the following event payloads:
- Payment Accepted/Rejected - A message indicating the payment for the filing was either accepted, or rejected and why.
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
Implementation
Along with the required Webhook(s) the Filer MUST implement the following.
Generates Messages:
- Court Policy Query Message
- Core Filing Message
Performs Activities:
- Gets the court policy from the Registry; /Registry/Policy - Get
- Submits filings to the Registry for review and recording with the Court; /Registry/Filing - Post
Court Registry Component
Summary
The Registry is a REQUIRED logical component within the system which is equivalent/analogous to the Filing Review MDE from the ECF specification; which enables a court to receive and review a filing message and prepare the contents for recording in its case management and document management systems, sending a response concerning the filing to the Filer (Filing Assembly MDE). It also enables filers to obtain court-specific policies regarding electronic filing and to check on the status of a filing.
This component is responsible for interacting with:
- The Filer in its process of submitting case files for review and filing with the Court.
- The Court to subnit case files and documents.
Court Webhook
This component MUST implement a Webhook endpoint in order to receive asynchronous events from the Court. This endpoint is equivalent/analogous to the NotifyDocketingComplete operation provided by the Filing Review MDE from the ECF specification. The payloads posted to the endpoint provide similar information to that of the RecordDocketingCallbackMessage parameter of the NotifyDocketingComplete operation.
This endpoint must be able to accept the following event payloads:
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
Registry Webhook
This componet interacts with the Filer component asynchronously through Webhooks. It expects the Filer to implement an endpoint that will receive the following event payloads:
- Payment Accepted/Rejected - A message indicating the payment for the filing was either accepted, or rejected and why
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
If the clerk rejects the filings or the Registry receives an event from the Court, the Registry MUST post an event to the Filer's Webhook endpoint as an asynchronous response indicating whether the filing was accepted and filed with the court record system. From the ECF specification, and left here for discussion... The operation MAY return the filed documents or links to the documents, but MUST include the [FIPS 180-2] SHA 256 document hash, a condensed representation of a document intended to protect document integrity.
If the filing included a payment, and the filing was accepted by the clerk and court record system, a receipt for the payment MUST be included in the operation.
Implementation
Along with the required Webhook(s) the Registry MUST implement the following.
Generates Messages:
- Court Policy Response Message
- Record Docketing Message
- Filing Event Messages
Performs Activities:
- Submits filings to the Court; /Court/Record - Post
- Notifies the Filer of filing related events through the Registry Webhook
Implement Functionality For:
- /Registry/Policy - Get
- /Registry/Filing - Post
Summary
The Registry is a REQUIRED logical component within the system which is equivalent/analogous to the Filing Review MDE from the ECF specification; which enables a court to receive and review a filing message and prepare the contents for recording in its case management and document management systems, sending a response concerning the filing to the Filer (Filing Assembly MDE). It also enables filers to obtain court-specific policies regarding electronic filing and to check on the status of a filing.
This component is responsible for interacting with:
- The Filer in its process of submitting case files for review and filing with the Court.
- The Court to subnit case files and documents.
Court Webhook
This component MUST implement a Webhook endpoint in order to receive asynchronous events from the Court. This endpoint is equivalent/analogous to the NotifyDocketingComplete operation provided by the Filing Review MDE from the ECF specification. The payloads posted to the endpoint provide similar information to that of the RecordDocketingCallbackMessage parameter of the NotifyDocketingComplete operation.
This endpoint must be able to accept the following event payloads:
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
Registry Webhook
This componet interacts with the Filer component asynchronously through Webhooks. It expects the Filer to implement an endpoint that will receive the following event payloads:
- Payment Accepted/Rejected - A message indicating the payment for the filing was either accepted, or rejected and why
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
If the clerk rejects the filings or the Registry receives an event from the Court, the Registry MUST post an event to the Filer's Webhook endpoint as an asynchronous response indicating whether the filing was accepted and filed with the court record system. From the ECF specification, and left here for discussion... The operation MAY return the filed documents or links to the documents, but MUST include the [FIPS 180-2] SHA 256 document hash, a condensed representation of a document intended to protect document integrity.
If the filing included a payment, and the filing was accepted by the clerk and court record system, a receipt for the payment MUST be included in the operation.
Implementation
Along with the required Webhook(s) the Registry MUST implement the following.
Generates Messages:
- Court Policy Response Message
- Record Docketing Message
- Filing Event Messages
Performs Activities:
- Submits filings to the Court; /Court/Record - Post
- Notifies the Filer of filing related events through the Registry Webhook
Implement Functionality For:
- /Registry/Policy - Get
- /Registry/Filing - Post
The Filer MAY obtain a court’s machine-readable court policy at any time. The Registry returns the machine-readable court policy in a synchronous response. The content of the machine readable court policy is simular to that described in Section 2.4.2 of the ECF specification. This step may be omitted if the Filer already has the current court policy.
get /Registry/Policy
Get the court's machine-readable court policy. This method is equivalent/analogous to the GetPolicy operation from the ECF specification.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CourtPolicyQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="CourtPolicyQueryMessageType">
<xsd:annotation>
<xsd:documentation>A request for a court's Court Policy.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="CourtPolicyQueryMessage" type="CourtPolicyQueryMessageType">
<xsd:annotation>
<xsd:documentation>A request for a court's Court Policy.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CourtPolicyQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyQueryMessage-4.0 ../xsd/message/ECF-4.0-CourtPolicyQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
</CourtPolicyQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyResponseMessage-4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:digsig="http://www.w3.org/2000/09/xmldsig#" xmlns:mde="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MajorDesignElementNameCode-4.0" xmlns:operation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:OperationNameCode-4.0" xmlns:a="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:AppInfo-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CourtPolicyResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:AppInfo-4.0" schemaLocation="../common/ECF-4.0-AppInfo.xsd"/>
<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="../common/xmldsig-core-schema.xsd"/>
<xsd:simpleType name="CaseTypeCodeSimpleType">
<xsd:annotation>
<xsd:documentation>A type of court case.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:normalizedString">
<xsd:enumeration value="Appellate">
<xsd:annotation>
<xsd:documentation>Appellate case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Bankruptcy">
<xsd:annotation>
<xsd:documentation>Bankruptcy case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Citation">
<xsd:annotation>
<xsd:documentation>Citation case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Civil">
<xsd:annotation>
<xsd:documentation>Civil case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Criminal">
<xsd:annotation>
<xsd:documentation>Criminal case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Domestic">
<xsd:annotation>
<xsd:documentation>Domestic case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Juvenile">
<xsd:annotation>
<xsd:documentation>Juvenile case type</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="CaseTypeCodeType">
<xsd:annotation>
<xsd:documentation>A type of court case.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="CaseTypeCodeSimpleType">
<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="CourtCodelistType">
<xsd:annotation>
<xsd:documentation>A Genericode list of valid codes for an element in a particular court to be substituted for an ECF element.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element ref="ECFElementName"/>
<xsd:element ref="EffectiveDate"/>
<xsd:element ref="ExpirationDate" minOccurs="0"/>
<xsd:element ref="CourtCodelistURI"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CourtExtensionType">
<xsd:annotation>
<xsd:documentation>A schema that defines a court-specific data structure to be substituted for an ECF element.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element ref="ECFElementName"/>
<xsd:element ref="CourtExtensionURI"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CourtPolicyQueryMessageType">
<xsd:annotation>
<xsd:documentation>A request for a court's Court Policy.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:CaseFilingType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CourtPolicyResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a request for a court's Court Policy.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="PolicyVersionID"/>
<xsd:element ref="PolicyLastUpdateDate"/>
<xsd:element ref="RuntimePolicyParameters"/>
<xsd:element ref="DevelopmentPolicyParameters"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="DevelopmentPolicyParametersType">
<xsd:annotation>
<xsd:documentation>Within Court Policy, the policies that are accessed by a person or organization developing an applications or configuring an application to interact with a court for the purpose of structuring the interactions with that court. This information is needed once and is not accessed dynamically while interacting with the court.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element ref="URLAttachmentSupportedIndicator"/>
<xsd:element ref="AcceptDocumentsRequiringFeesIndicator"/>
<xsd:element ref="AcceptConfidentialFilingsIndicator"/>
<xsd:element ref="AcceptMultipleLeadDocumentsIndicator"/>
<xsd:element ref="MaximumAllowedAttachmentSize" minOccurs="0"/>
<xsd:element ref="MaximumAllowedMessageSize" minOccurs="0"/>
<xsd:element ref="SupportedMessageProfileCode" maxOccurs="unbounded"/>
<xsd:element ref="SupportedSignatureProfileCode" maxOccurs="unbounded"/>
<xsd:element ref="SupportedOperationName" maxOccurs="unbounded"/>
<xsd:element ref="SupportedCaseType" maxOccurs="unbounded"/>
<xsd:element ref="CourtExtension" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="FilingFeesMayBeApplicableIndicator"/>
<xsd:element ref="EffectiveDate"/>
<xsd:element ref="ExpirationDate" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="MajorDesignElementNameCodeSimpleType">
<xsd:annotation>
<xsd:documentation>Name of a major design element.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:normalizedString">
<xsd:enumeration value="CourtRecord">
<xsd:annotation>
<xsd:documentation>CourtRecord MDE</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FilingAssembly">
<xsd:annotation>
<xsd:documentation>FilingAssembly MDE</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FilingReview">
<xsd:annotation>
<xsd:documentation>FilingReview MDE</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Service">
<xsd:annotation>
<xsd:documentation>Service MDE</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="MajorDesignElementNameCodeType">
<xsd:annotation>
<xsd:documentation>Name of a major design element.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="MajorDesignElementNameCodeSimpleType">
<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="OperationNameSimpleType">
<xsd:annotation>
<xsd:documentation>Name of an MDE operation.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:normalizedString">
<xsd:enumeration value="GetFeesCalculation">
<xsd:annotation>
<xsd:documentation>GetFeesCalculation query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetCase">
<xsd:annotation>
<xsd:documentation>GetCase query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetCaseList">
<xsd:annotation>
<xsd:documentation>GetFeesCaseList query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetDocument">
<xsd:annotation>
<xsd:documentation>GetDocument query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetFilingList">
<xsd:annotation>
<xsd:documentation>GetFilingList query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetFilingStatus">
<xsd:annotation>
<xsd:documentation>GetFilingStatus query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetPolicy">
<xsd:annotation>
<xsd:documentation>GetPolicy query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GetServiceInformation">
<xsd:annotation>
<xsd:documentation>GetServiceInformation query</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NotifyFilingReview">
<xsd:annotation>
<xsd:documentation>NotifyFilingReview message</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NotifyDocketing">
<xsd:annotation>
<xsd:documentation>NotifyDocketing message</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RecordFiling">
<xsd:annotation>
<xsd:documentation>RecordFiling message</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ReviewFiling">
<xsd:annotation>
<xsd:documentation>ReviewFiling message</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ServeFiling">
<xsd:annotation>
<xsd:documentation>ServeFiling message</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="OperationNameType">
<xsd:annotation>
<xsd:documentation>Name of an MDE operation.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="OperationNameSimpleType">
<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="PublicKeyInformationType">
<xsd:annotation>
<xsd:documentation>Symmetric or asymmetric keys used to encrypt and decrypt, or verify signed messages or documents exchanged with the court.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element ref="digsig:KeyInfo" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RuntimePolicyParametersType">
<xsd:annotation>
<xsd:documentation>Within Court Policy, the policies that are accessed dynamically by applications interacting with a court.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element ref="PublicKeyInformation" minOccurs="0"/>
<xsd:element ref="CourtCodelist" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="AcceptDocumentsRequiringFeesIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether the court will accept electronic filing of documents requiring filing fees.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AcceptConfidentialFilingsIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether the court will accept electronic filing of documents for which the filer requests confidential or sealed treatment by the court.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AcceptMultipleLeadDocumentsIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Does court accept placing multiple lead documents in a single message</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CourtCodelist" type="CourtCodelistType">
<xsd:annotation>
<xsd:documentation>A Genericode list of valid codes for an element in a particular court to be substituted for an ECF element. The 'code' column of the codelist includes the allowed values.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CourtCodelistURI" type="nc:IdentificationType">
<xsd:annotation>
<xsd:documentation>A URI reference to a court-specific codelist defined in Genericode.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CourtExtension" type="CourtExtensionType">
<xsd:annotation>
<xsd:documentation>A schema that defines a court-specific data structure to be substituted for an ECF element..</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CourtExtensionURI" type="nc:IdentificationType">
<xsd:annotation>
<xsd:documentation>A URI reference to a court-specific extension.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CourtPolicyResponseMessage" type="CourtPolicyResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a request for a court's Court Policy.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DevelopmentPolicyParameters" type="DevelopmentPolicyParametersType">
<xsd:annotation>
<xsd:documentation>Within Court Policy, the policies that are accessed by a person or organization developing an applications or configuring an application to interact with a court for the purpose of structuring the interactions with that court. This information is needed once and is not accessed dynamically while interacting with the court.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ECFElementName" type="nc:TextType">
<xsd:annotation>
<xsd:documentation>The name of an ECF element to be substituted by a court-specific codelist or extension.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EffectiveDate" type="nc:DateType">
<xsd:annotation>
<xsd:documentation>The date on which a court code list or extension became or will become allowed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ExpirationDate" type="nc:DateType">
<xsd:annotation>
<xsd:documentation>The date on which a court code list or extension was or will be terminated.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="FilingFeesMayBeApplicableIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicates whether fees may be required for some filings.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="GetFeesCalculationSupportedIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicates whether the e-filing system supports the GetFeesCalculation query.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="GetCaseListSupportedIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicates whether the e-filing system supports the GetCaseList query.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MajorDesignElementNameCode" type="MajorDesignElementNameCodeType">
<xsd:annotation>
<xsd:documentation>Name of a major design element.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MaximumAllowedAttachmentSize" type="nc:MeasureType">
<xsd:annotation>
<xsd:documentation>The maximum allowed attachment size, in bytes. Does not appear if there is no maximum.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MaximumAllowedMessageSize" type="nc:MeasureType">
<xsd:annotation>
<xsd:documentation>Maximum allowed size of the Court Filing Message Stream, in bytes. Does not appear if there is no maximum.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PolicyLastUpdateDate" type="nc:DateType">
<xsd:annotation>
<xsd:documentation>The date on which a court's Court Policy was last revised.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PolicyVersionID" type="nc:IdentificationType">
<xsd:annotation>
<xsd:documentation>The version of court policy reported by this message. Up to the court to define the format of this, and describe in human-readable court policy.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PublicKeyInformation" type="PublicKeyInformationType">
<xsd:annotation>
<xsd:documentation>Symmetric or asymmetric keys used to encrypt and decrypt, or verify signed messages or documents exchanged with the court.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="RuntimePolicyParameters" type="RuntimePolicyParametersType">
<xsd:annotation>
<xsd:documentation>Within Court Policy, the policies that are accessed dynamically by applications interacting with a court.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SupportedCaseType" type="CaseTypeCodeType">
<xsd:annotation>
<xsd:documentation>A structure containing indicators that signal support by the e-filing system for each ECF case type.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SupportedMessageProfileCode" type="nc:TextType">
<xsd:annotation>
<xsd:documentation>A message profile approved for use by the OASIS LegalXML Member Section Electronic Court Filing Technical Committee that is supported by this court.</xsd:documentation>
<xsd:appinfo>
<a:CourtPolicyDefinedCodeIndicator>true</a:CourtPolicyDefinedCodeIndicator>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SupportedOperationName" type="OperationNameType">
<xsd:annotation>
<xsd:documentation>Name of an MDE operation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SupportedSignatureProfileCode" type="nc:TextType">
<xsd:annotation>
<xsd:documentation>A signature profile approved for use by the OASIS LegalXML Member Section Electronic Court Filing Technical Committee that is supported by this court.</xsd:documentation>
<xsd:appinfo>
<a:CourtPolicyDefinedCodeIndicator>true</a:CourtPolicyDefinedCodeIndicator>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="URLAttachmentSupportedIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Whether court allows attachments via remote URLs.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CourtPolicyResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CourtPolicyResponseMessage-4.0 ../xsd/message/ECF-4.0-CourtPolicyResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<PolicyVersionID>
<nc:IdentificationID>1</nc:IdentificationID>
</PolicyVersionID>
<PolicyLastUpdateDate>
<nc:DateTime>2008-08-01T14:20:00.0Z</nc:DateTime>
</PolicyLastUpdateDate>
<RuntimePolicyParameters>
<CourtCodelist>
<ECFElementName>j:RegisterActionDescriptionText</ECFElementName>
<EffectiveDate>
<nc:Date>2008-08-01</nc:Date>
</EffectiveDate>
<CourtCodelistURI>
<nc:IdentificationID>https://courts.wa.gov:8000/codes/docketcodes</nc:IdentificationID>
</CourtCodelistURI>
</CourtCodelist>
</RuntimePolicyParameters>
<DevelopmentPolicyParameters>
<URLAttachmentSupportedIndicator>true</URLAttachmentSupportedIndicator>
<AcceptDocumentsRequiringFeesIndicator>true</AcceptDocumentsRequiringFeesIndicator>
<AcceptConfidentialFilingsIndicator>true</AcceptConfidentialFilingsIndicator>
<AcceptMultipleLeadDocumentsIndicator>true</AcceptMultipleLeadDocumentsIndicator>
<MaximumAllowedAttachmentSize>
<nc:MeasureText>10000000</nc:MeasureText>
<nc:MeasureUnitText>byte</nc:MeasureUnitText>
</MaximumAllowedAttachmentSize>
<MaximumAllowedMessageSize>
<nc:MeasureText>100000000</nc:MeasureText>
<nc:MeasureUnitText>byte</nc:MeasureUnitText>
</MaximumAllowedMessageSize>
<SupportedMessageProfileCode/>
<SupportedSignatureProfileCode/>
<SupportedOperationName>GetCase</SupportedOperationName>
<SupportedOperationName>GetCaseList</SupportedOperationName>
<SupportedOperationName>GetDocument</SupportedOperationName>
<SupportedOperationName>GetFeesCalculation</SupportedOperationName>
<SupportedOperationName>GetFilingList</SupportedOperationName>
<SupportedOperationName>GetFilingStatus</SupportedOperationName>
<SupportedOperationName>GetPolicy</SupportedOperationName>
<SupportedOperationName>GetServiceInformation</SupportedOperationName>
<SupportedOperationName>NotifyDocketing</SupportedOperationName>
<SupportedOperationName>NotifyFilingReview</SupportedOperationName>
<SupportedOperationName>RecordFiling</SupportedOperationName>
<SupportedOperationName>ReviewFiling</SupportedOperationName>
<SupportedOperationName>ServeFiling</SupportedOperationName>
<SupportedCaseType>Appellate</SupportedCaseType>
<SupportedCaseType>Bankruptcy</SupportedCaseType>
<SupportedCaseType>Citation</SupportedCaseType>
<SupportedCaseType>Civil</SupportedCaseType>
<SupportedCaseType>Criminal</SupportedCaseType>
<SupportedCaseType>Domestic</SupportedCaseType>
<SupportedCaseType>Juvenile</SupportedCaseType>
<FilingFeesMayBeApplicableIndicator>true</FilingFeesMayBeApplicableIndicator>
<EffectiveDate>
<nc:Date>2008-08-01</nc:Date>
</EffectiveDate>
</DevelopmentPolicyParameters>
</CourtPolicyResponseMessage>
Provides the resources and methods needed for a Filer to interact with the case files submitted to the Registry.
Submit a filing for review.
The Filer MUST submit a filing to the court by posting a filing request to the Registry for review. The request contains the documents and information about the case along with filing payment informaiton. The synchronous response includes the filing identifier (caseTrackingID) issued by the court, that can later be used to get information on the filing.
The Filer will also receive asynchronous events, through the Registry Webhook at various times as the request is being processed; refer to the documentaion on the Registry Webhook, in both the Filer and Registry components for details.
This method is equivalent/analogous to the ReviewFiling operation in the ECF standards.
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY query for a list of filings matching several criteria including the Filer's' identifier, the case tracking number, and the filed date within a certain time range. The Registry responds synchronously with a list of matching filings and the status of each filing.
This method is equivalent/analogous to the GetFilingList operation in the ECF standards.
post /Registry/Filing
Submit a filing for review.
The Filer MUST submit a filing to the court by posting a filing request to the Registry for review. The request contains the documents and information about the case along with filing payment informaiton. The synchronous response includes the filing identifier (caseTrackingID) issued by the court, that can later be used to get information on the filing.
The Filer will also receive asynchronous events, through the Registry Webhook at various times as the request is being processed; refer to the documentaion on the Registry Webhook, in both the Filer and Registry components for details.
This method is equivalent/analogous to the ReviewFiling operation in the ECF standards.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<!--
This schema was created specifically for the initail draft implementation of the API for the CSO project.
It is not part of the standard set of message schemas provided with the ECF specification.
This message schema is equivelant to "ReviewFilingRequestMessage" which is defined in the ECF-4.0-WebServicesProfile-Definitions.wsdl of the ecf-v4.0-webservices-v2.01-csprd02 specifications for use with the calls to ReviewFiling.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ReviewFilingRequestMessage-4.0" xmlns:core="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" xmlns:payment="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:PaymentMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ReviewFilingRequestMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>ReviewFilingRequestMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" schemaLocation="../ecf-v4.0-spec/xsd/message/ECF-4.0-CoreFilingMessage.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:PaymentMessage-4.0" schemaLocation="../ecf-v4.0-spec/xsd/message/ECF-4.0-PaymentMessage.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="ReviewFilingRequestMessageType">
<xsd:annotation>
<xsd:documentation>The structure of a Filing including any Payment Information will be documented in this section. This describes the filing transaction between the Filing Assembly MDE and the Filing Review MDE. This information will become part of the Record Filing between the Filing Review MDE and the Court Record MDE but does not necessarily describe the information that is actually stored in the Court Record.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:ElectronicFilingCallbackMessageType">
<xsd:sequence>
<xsd:element ref="core:CoreFilingMessage"/>
<xsd:element ref="payment:PaymentMessage"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ReviewFilingRequestMessage" type="ReviewFilingRequestMessageType">
<xsd:annotation>
<xsd:documentation>The structure of a Filing including any Payment Information will be documented in this section. This describes the filing transaction between the Filing Assembly MDE and the Filing Review MDE. This information will become part of the Record Filing between the Filing Review MDE and the Court Record MDE but does not necessarily describe the information that is actually stored in the Court Record.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CoreFilingMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0 ../xsd/message/ECF-4.0-CoreFilingMessage.xsd">
<nc:DocumentIdentification>
<nc:IdentificationID>123456ABC</nc:IdentificationID>
</nc:DocumentIdentification>
<nc:DocumentInformationCutOffDate>
<nc:DateTime>2008-07-07T13:47:42.0Z</nc:DateTime>
</nc:DocumentInformationCutOffDate>
<nc:DocumentPostDate>
<nc:DateTime>2008-07-07T13:47:42.0Z</nc:DateTime>
</nc:DocumentPostDate>
<nc:DocumentSubmitter>
<ecf:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>Jane Doe</nc:PersonFullName>
</nc:PersonName>
<nc:PersonOtherIdentification>
<nc:IdentificationID>tls</nc:IdentificationID>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</nc:DocumentSubmitter>
<ecf:SendingMDELocationID>
<nc:IdentificationID>91</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>MESSAGINGPROFILEID</ecf:SendingMDEProfileCode>
<criminal:CriminalCase xmlns:criminal="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CriminalCase-4.0" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CriminalCase-4.0 ../xsd/casetype/ECF-4.0-CriminalCase.xsd">
<nc:CaseTitleText>State vs. John Doe </nc:CaseTitleText>
<nc:CaseTrackingID>123456ABC</nc:CaseTrackingID>
<j:CaseAugmentation>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>1</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>Municipal Court</j:CourtName>
</j:CaseCourt>
<j:CaseRespondentParty>
<nc:EntityPersonReference s:ref="Person1"/>
</j:CaseRespondentParty>
</j:CaseAugmentation>
<ecf:CaseAugmentation>
<ecf:CaseParticipant s:id="Person1">
<ecf:EntityPerson>
<nc:PersonBirthDate>
<nc:Date>1983-01-01</nc:Date>
</nc:PersonBirthDate>
<nc:PersonEyeColorCode>BLU</nc:PersonEyeColorCode>
<nc:PersonHairColorCode>BRO</nc:PersonHairColorCode>
<nc:PersonHeightMeasure>
<nc:MeasureText>81</nc:MeasureText>
<nc:LengthUnitCode>INH</nc:LengthUnitCode>
</nc:PersonHeightMeasure>
<nc:PersonName>
<nc:PersonGivenName>John</nc:PersonGivenName>
<nc:PersonMiddleName>W.</nc:PersonMiddleName>
<nc:PersonSurName>Doe</nc:PersonSurName>
</nc:PersonName>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1234-56-789</nc:IdentificationID>
<nc:IdentificationCategoryText>DriverLicense</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
<nc:PersonPhysicalFeature/>
<nc:PersonRaceText>W</nc:PersonRaceText>
<nc:PersonSexCode>M</nc:PersonSexCode>
<nc:PersonTaxIdentification>
<nc:IdentificationID>123-45-67890</nc:IdentificationID>
</nc:PersonTaxIdentification>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode/>
<nc:ContactInformation>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>123 Main St.</nc:StreetFullText>
</nc:LocationStreet>
<nc:LocationCityName>Anytown</nc:LocationCityName>
<nc:LocationStateName>IN</nc:LocationStateName>
<nc:LocationPostalCode>12345</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
</nc:ContactInformation>
</ecf:CaseParticipant>
</ecf:CaseAugmentation>
<criminal:CaseCharge>
<j:ChargeSequenceID>
<nc:IdentificationID>1</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>455</nc:IdentificationID>
</j:StatuteCodeIdentification>
<j:StatuteDescriptionText>Resisting Law Enforcement</j:StatuteDescriptionText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>5-44-3-3(a)(1)</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</j:ChargeStatute>
<criminal:ChargeOffense>
<nc:ActivityDate>
<nc:Date>2008-07-07</nc:Date>
</nc:ActivityDate>
</criminal:ChargeOffense>
<criminal:ChargeAmendedIndicator>false</criminal:ChargeAmendedIndicator>
</criminal:CaseCharge>
<criminal:CaseCharge>
<j:ChargeSequenceID>
<nc:IdentificationID>2</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>1279</nc:IdentificationID>
</j:StatuteCodeIdentification>
<j:StatuteDescriptionText>Driving While Suspended</j:StatuteDescriptionText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>9-24-19-2</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</j:ChargeStatute>
<criminal:ChargeOffense>
<nc:ActivityDate>
<nc:Date>2008-07-07</nc:Date>
</nc:ActivityDate>
</criminal:ChargeOffense>
<criminal:ChargeAmendedIndicator>false</criminal:ChargeAmendedIndicator>
</criminal:CaseCharge>
<criminal:CaseCharge>
<j:ChargeSequenceID>
<nc:IdentificationID>3</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>1287</nc:IdentificationID>
</j:StatuteCodeIdentification>
<j:StatuteDescriptionText>9-30-5-2(a): Operating a Vehicle While Intoxicated</j:StatuteDescriptionText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>9-30-5-2(a)</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</j:ChargeStatute>
<criminal:ChargeOffense>
<nc:ActivityDate>
<nc:Date>2008-07-07</nc:Date>
</nc:ActivityDate>
</criminal:ChargeOffense>
<criminal:ChargeAmendedIndicator>false</criminal:ChargeAmendedIndicator>
</criminal:CaseCharge>
<criminal:CaseCharge>
<j:ChargeSequenceID>
<nc:IdentificationID>4</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>1140</nc:IdentificationID>
</j:StatuteCodeIdentification>
<j:StatuteDescriptionText>Operating a Vehicle with an ACE of .15 or More</j:StatuteDescriptionText>
</j:ChargeStatute>
<criminal:ChargeOffense>
<nc:ActivityDate>
<nc:Date>2008-07-07</nc:Date>
</nc:ActivityDate>
</criminal:ChargeOffense>
<criminal:ChargeAmendedIndicator>false</criminal:ChargeAmendedIndicator>
</criminal:CaseCharge>
</criminal:CriminalCase>
<FilingConfidentialityIndicator>false</FilingConfidentialityIndicator>
<FilingLeadDocument s:id="_123456ABC.app.doc">
<nc:DocumentApplicationName>Microsoft Word</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Appearance</nc:DocumentDescriptionText>
<nc:DocumentLanguageCode>eng</nc:DocumentLanguageCode>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText/>
<ecf:FilingAttorneyID/>
<ecf:FilingPartyID/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment1">
<nc:BinaryDescriptionText>application/msword</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Payload1</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</FilingLeadDocument>
<FilingConnectedDocument s:id="_123456ABC.inf.doc">
<nc:DocumentApplicationName>Microsoft Word</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Information</nc:DocumentDescriptionText>
<nc:DocumentSequenceID>1</nc:DocumentSequenceID>
<nc:DocumentLanguageCode>eng</nc:DocumentLanguageCode>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText/>
<ecf:ParentDocumentReference s:ref="_123456ABC.app.doc"/>
<ecf:FilingAttorneyID/>
<ecf:FilingPartyID/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment2">
<nc:BinaryDescriptionText>application/msword</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Payload2</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</FilingConnectedDocument>
</CoreFilingMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MessageReceiptMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MessageReceiptMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>MessageReceiptMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="MessageReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A message returned synchronously to indicate receipt by an MDE of another message. The intent is that this will serve as the synchronous reply to all MDE operations that have an additional asynchronous callback.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:CaseFilingType">
<xsd:sequence>
<xsd:element ref="j:CaseCourt"/>
<xsd:element ref="ecf:Error" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="MessageReceiptMessage" type="MessageReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A message returned synchronously to indicate receipt by an MDE of another message. The intent is that this will serve as the synchronous reply to all MDE operations that have an additional asynchronous callback.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
get /Registry/Filing
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY query for a list of filings matching several criteria including the Filer's' identifier, the case tracking number, and the filed date within a certain time range. The Registry responds synchronously with a list of matching filings and the status of each filing.
This method is equivalent/analogous to the GetFilingList operation in the ECF standards.
Query Parameters
- filerID (string)
Filter the results by the filer's identifier.
- caseTrackingID (string)
Filter the results by the case tracking number.
- filedDateTime (string)
Filter the results by date and time.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>FilingListQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="FilingListQueryMessageType">
<xsd:annotation>
<xsd:documentation>This is query to get a list of filings by Filer Identification, Case ID, and/or time period.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="nc:CaseTrackingID" minOccurs="0"/>
<xsd:element ref="nc:DocumentSubmitter" minOccurs="0"/>
<xsd:element ref="nc:DateRange" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="FilingListQueryMessage" type="FilingListQueryMessageType">
<xsd:annotation>
<xsd:documentation>This is query to get a list of filings by Filer Identification, Case ID, or time period.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<FilingListQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListQueryMessage-4.0 ../xsd/message/ECF-4.0-FilingListQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<nc:CaseTrackingID>KC2008-1001</nc:CaseTrackingID>
<nc:DocumentSubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</nc:DocumentSubmitter>
<nc:DateRange>
<nc:StartDate>
<nc:Date>2008-08-01</nc:Date>
</nc:StartDate>
<nc:EndDate>
<nc:Date>2008-08-01</nc:Date>
</nc:EndDate>
</nc:DateRange>
</FilingListQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>FilingListResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="FilingListResponseMessageType">
<xsd:annotation>
<xsd:documentation>A court's response to a FilingListQueryMessage.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="MatchingFiling" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="MatchingFilingType">
<xsd:annotation>
<xsd:documentation>A court's response to a FilingListQueryMessage.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="nc:DocumentType">
<xsd:sequence>
<xsd:element ref="nc:CaseTrackingID" minOccurs="0"/>
<xsd:element ref="ecf:FilingStatus"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="FilingListResponseMessage" type="FilingListResponseMessageType">
<xsd:annotation>
<xsd:documentation>A court's response to a FilingListQueryMessage.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MatchingFiling" type="MatchingFilingType">
<xsd:annotation>
<xsd:documentation>A filing that matches the criteria in a FilingListQueryMessage.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<FilingListResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingListResponseMessage-4.0 ../xsd/message/ECF-4.0-FilingListResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<MatchingFiling>
<nc:DocumentIdentification>
<nc:IdentificationID>1021</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilingID</nc:IdentificationCategoryText>
</nc:DocumentIdentification>
<nc:DocumentSubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</nc:DocumentSubmitter>
<nc:CaseTrackingID>KC-2008-1001</nc:CaseTrackingID>
<ecf:FilingStatus>
<nc:StatusDescriptionText>accepted without modification</nc:StatusDescriptionText>
<ecf:FilingStatusCode>accepted</ecf:FilingStatusCode>
</ecf:FilingStatus>
</MatchingFiling>
</FilingListResponseMessage>
get /Registry/Filing/Fees
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY query for the fees associated with a filing by calling this method, with a filing as a parameter. The synchronous response contains the fee calculation and, optionally, a list of the included charges. This step may be omitted if there are no fees associated with filings in the court or the calculated fees are already known.
This method is equivalent/analogous to the GetFeesCalculation operation in the ECF standards.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationQueryMessage-4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:core="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>FeesCalculationQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" schemaLocation="ECF-4.0-CoreFilingMessage.xsd"/>
<xsd:complexType name="FeesCalculationQueryMessageType">
<xsd:annotation>
<xsd:documentation>This query is a request for the total amount of court fees required for filing of one or more documents in a case. </xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="core:CoreFilingMessage"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="FeesCalculationQueryMessage" type="FeesCalculationQueryMessageType">
<xsd:annotation>
<xsd:documentation>This query is a request for the total amount of court fees required for filing of one or more documents in a case. </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<FeesCalculationQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:core="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationQueryMessage-4.0 ../xsd/message/ECF-4.0-FeesCalculationQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<nc:EntityPersonReference s:ref="Person1"/>
</ecf:QuerySubmitter>
<j:CaseCourt/>
<core:CoreFilingMessage>
<nc:DocumentIdentification>
<nc:IdentificationID>001-f786e6d6-558c-448f-b249-067002d716a0</nc:IdentificationID>
</nc:DocumentIdentification>
<nc:DocumentInformationCutOffDate>
<nc:DateTime>2007-06-06T14:20:47.0Z</nc:DateTime>
</nc:DocumentInformationCutOffDate>
<nc:DocumentPostDate>
<nc:DateTime>2007-06-06T14:20:47.0Z</nc:DateTime>
</nc:DocumentPostDate>
<nc:DocumentSubmitter>
<ecf:EntityPerson s:id="Person1">
<nc:PersonName>
<nc:PersonNamePrefixText>Mr.</nc:PersonNamePrefixText>
<nc:PersonGivenName>Jonathan</nc:PersonGivenName>
<nc:PersonMiddleName>Richard</nc:PersonMiddleName>
<nc:PersonSurName>Registrant</nc:PersonSurName>
<nc:PersonNameSuffixText>Sr.</nc:PersonNameSuffixText>
<nc:PersonFullName>John R. Registrant Sr.</nc:PersonFullName>
</nc:PersonName>
<nc:PersonOtherIdentification>
<nc:IdentificationID>AZAOCEFM-12345: jregistrant@aol.com</nc:IdentificationID>
<nc:IdentificationSourceText>AZAOCEFM: ATTORNEY</nc:IdentificationSourceText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</nc:DocumentSubmitter>
<ecf:SendingMDELocationID>
<nc:IdentificationID>AZAOCL2CEFSP</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:ElectronicServiceInformation>
<ecf:ServiceRecipientID>
<nc:IdentificationID>1031</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</ecf:ServiceRecipientID>
<ecf:ReceivingMDELocationID>
<nc:IdentificationID>https://eserviceprovider.com:8000</nc:IdentificationID>
</ecf:ReceivingMDELocationID>
<ecf:ReceivingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:ReceivingMDEProfileCode>
</ecf:ElectronicServiceInformation>
<criminal:CriminalCase xmlns:criminal="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CriminalCase-4.0" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CriminalCase-4.0 ../xsd/casetype/ECF-4.0-CriminalCase.xsd">
<nc:CaseTitleText>State of Arizona v Jack Smith</nc:CaseTitleText>
<nc:CaseTrackingID>CR070123</nc:CaseTrackingID>
<j:CaseAugmentation>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>1</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>Arizona Supreme Court</j:CourtName>
</j:CaseCourt>
<j:CaseDefendantParty>
<ecf:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John Smith</nc:PersonFullName>
</nc:PersonName>
</ecf:EntityPerson>
</j:CaseDefendantParty>
<j:CaseInitiatingAttorney>
<nc:RoleOfPersonReference s:ref="Person1"/>
<j:JudicialOfficialBarMembership>
<j:JudicialOfficialBarIdentification>
<nc:IdentificationID>23101</nc:IdentificationID>
<j:IdentificationJurisdictionNCICLISCode>AZ</j:IdentificationJurisdictionNCICLISCode>
<nc:IdentificationSourceText>State Bar of Arizona</nc:IdentificationSourceText>
</j:JudicialOfficialBarIdentification>
</j:JudicialOfficialBarMembership>
</j:CaseInitiatingAttorney>
</j:CaseAugmentation>
<ecf:CaseAugmentation>
<ecf:CaseParticipant>
<ecf:EntityPerson s:id="Person2">
<nc:PersonName>
<nc:PersonFullName>John S. Registrant Sr.</nc:PersonFullName>
</nc:PersonName>
<ecf:PersonAugmentation>
<nc:ContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6024561234</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
<nc:ContactEmailID>jregistrant@aol.com</nc:ContactEmailID>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:AddressDeliveryPointID>777</nc:AddressDeliveryPointID>
<nc:AddressSecondaryUnitText>Suite 507</nc:AddressSecondaryUnitText>
<nc:LocationStreet>
<nc:StreetPredirectionalText>W</nc:StreetPredirectionalText>
<nc:StreetName>Litigant Avenue</nc:StreetName>
</nc:LocationStreet>
<nc:LocationCityName>Flagstaff</nc:LocationCityName>
<nc:LocationCountyName>Coconino</nc:LocationCountyName>
<nc:LocationStateUSPostalServiceCode>AZ</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>89007</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
</nc:ContactInformation>
</ecf:PersonAugmentation>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode/>
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<ecf:EntityOrganization s:id="Organization1">
<nc:OrganizationName>Dewey, Cheatem and Howe</nc:OrganizationName>
<nc:OrganizationUnitName>Flagstaff Office</nc:OrganizationUnitName>
</ecf:EntityOrganization>
<ecf:CaseParticipantRoleCode/>
</ecf:CaseParticipant>
<ecf:CaseShortTitleText>State vs. Smith</ecf:CaseShortTitleText>
<ecf:PersonOrganizationAssociation>
<nc:PersonReference s:ref="Person1"/>
<nc:OrganizationReference s:ref="Organization1"/>
<ecf:EntityAssociationTypeCode>Employer</ecf:EntityAssociationTypeCode>
</ecf:PersonOrganizationAssociation>
</ecf:CaseAugmentation>
<criminal:CaseArrest>
<nc:ActivityDate>
<nc:Date>2008-04-01</nc:Date>
</nc:ActivityDate>
<criminal:Subject>
<nc:RoleOfPersonReference s:ref="Person2"/>
<ecf:PersonAugmentation/>
<criminal:PersonInCustodyIndicator>true</criminal:PersonInCustodyIndicator>
<criminal:WarrantIssuedIndicator>false</criminal:WarrantIssuedIndicator>
</criminal:Subject>
</criminal:CaseArrest>
<criminal:CaseCharge>
<j:ChargeStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>StatuteCodeBook</nc:IdentificationID>
</j:StatuteCodeIdentification>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>100</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</j:ChargeStatute>
<criminal:ChargeOffense>
<nc:ActivityDate>
<nc:Date>2008-04-01</nc:Date>
</nc:ActivityDate>
<nc:IncidentLocation>
<nc:LocationName>The Mall</nc:LocationName>
</nc:IncidentLocation>
</criminal:ChargeOffense>
<criminal:ChargeAmendedIndicator>false</criminal:ChargeAmendedIndicator>
</criminal:CaseCharge>
<criminal:ProsecutionRecommendedBailText>true</criminal:ProsecutionRecommendedBailText>
</criminal:CriminalCase>
<core:FilingConfidentialityIndicator>true</core:FilingConfidentialityIndicator>
<core:FilingLeadDocument s:id="Document1">
<nc:DocumentApplicationName>Adobe PDF</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Information</nc:DocumentDescriptionText>
<nc:DocumentStatus>
<nc:StatusDescriptionText>SEALED</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>BR03</j:RegisterActionDescriptionText>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentSignature>
<ecf:SignatureProfileID>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileID>
<ecf:Signature>
<digsig:KeyInfo xmlns:digsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://www.w3.org/2000/09/xmldsig# ../xsd/common/xmldsig-core-schema.xsd">
<digsig:KeyName>FilerPublicKey</digsig:KeyName>
</digsig:KeyInfo>
</ecf:Signature>
</ecf:DocumentSignature>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment1">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment1</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
<ecf:ColorRelevantIndicator>false</ecf:ColorRelevantIndicator>
<ecf:RedactedIndicator>false</ecf:RedactedIndicator>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</core:FilingLeadDocument>
<core:FilingConnectedDocument s:id="Document2">
<nc:DocumentApplicationName>Adobe PDF</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Appendix to Reply Brief</nc:DocumentDescriptionText>
<nc:DocumentSequenceID>1</nc:DocumentSequenceID>
<nc:DocumentStatus>
<nc:StatusDescriptionText>PUBLIC</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>AP01</j:RegisterActionDescriptionText>
<ecf:ParentDocumentReference s:ref="Document1"/>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentSignature>
<ecf:SignatureProfileID>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileID>
</ecf:DocumentSignature>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment2">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment2</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
<ecf:ColorRelevantIndicator>false</ecf:ColorRelevantIndicator>
<ecf:RedactedIndicator>false</ecf:RedactedIndicator>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</core:FilingConnectedDocument>
<core:FilingConnectedDocument s:id="Document3">
<nc:DocumentApplicationName>Adobe PDF</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Appendix to Reply Brief</nc:DocumentDescriptionText>
<nc:DocumentSequenceID>2</nc:DocumentSequenceID>
<nc:DocumentStatus>
<nc:StatusDescriptionText>PUBLIC</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>AP01</j:RegisterActionDescriptionText>
<ecf:ParentDocumentReference s:ref="Document1"/>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentSignature>
<ecf:SignatureProfileID>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileID>
</ecf:DocumentSignature>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment3">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment3</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
<ecf:ColorRelevantIndicator>false</ecf:ColorRelevantIndicator>
<ecf:RedactedIndicator>false</ecf:RedactedIndicator>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</core:FilingConnectedDocument>
</core:CoreFilingMessage>
</FeesCalculationQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationResponseMessage-4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>FeesCalculationResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" schemaLocation="http://docs.oasis-open.org/ubl/prd2-UBL-2.1/xsd/common/UBL-CommonAggregateComponents-2.1.xsd"/>
<xsd:complexType name="FeesCalculationResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a FeesCalculationQueryMessage, which may either be "0" indicating no fee is due, a currency amount indicating the fee due upon filing, or "unknown" indicating that the court's case management information system is unable to calculate the fee for the proposed filing. </xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="FeesCalculationAmount"/>
<xsd:element ref="cac:AllowanceCharge" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="FeesCalculationAmount" type="nc:AmountType">
<xsd:annotation>
<xsd:documentation>A fee or price required to submit a document. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="FeesCalculationResponseMessage" type="FeesCalculationResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a FeesCalculationQueryMessage, which may either be "0" indicating no fee is due, a currency amount indicating the fee due upon filing, or "unknown" indicating that the court's case management information system is unable to calculate the fee for the proposed filing. </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<FeesCalculationResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FeesCalculationResponseMessage-4.0 ../xsd/message/ECF-4.0-FeesCalculationResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<FeesCalculationAmount nc:currencyCode="USD">100.00</FeesCalculationAmount>
</FeesCalculationResponseMessage>
A specific case file.
get /Registry/Filing/{caseTrackingID}/Status
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
Get the status of a filing with caseTrackingID = {caseTrackingID}
The Filer MAY query the status of a filing at any point following the submission using the case tracking identifier to get the status of the selected filing.
This method is equivalent/analogous to the GetFilingStatus operation in the ECF standards.
URI Parameters
- caseTrackingID: required (string)
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>FilingStatusQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="FilingStatusQueryMessageType">
<xsd:annotation>
<xsd:documentation>This is query to get a filing’s status by Filing Number.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="nc:DocumentIdentification"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="FilingStatusQueryMessage" type="FilingStatusQueryMessageType">
<xsd:annotation>
<xsd:documentation>This is query to get a filing's status by Filer Identification, Case ID, or Filing Number.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<FilingStatusQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusQueryMessage-4.0 ../xsd/message/ECF-4.0-FilingStatusQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<nc:DocumentIdentification>
<nc:IdentificationID>1021</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilingID</nc:IdentificationCategoryText>
</nc:DocumentIdentification>
</FilingStatusQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>FilingStatusResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="FilingStatusResponseMessageType">
<xsd:annotation>
<xsd:documentation>A court's response to a FilingStatusQueryMessage.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="nc:Case" minOccurs="0"/>
<xsd:element ref="nc:DocumentIdentification" minOccurs="0"/>
<xsd:element ref="ecf:FilingStatus"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="FilingStatusResponseMessage" type="FilingStatusResponseMessageType">
<xsd:annotation>
<xsd:documentation>A court's response to a FilingStatusQueryMessage.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<FilingStatusResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:FilingStatusResponseMessage-4.0 ../xsd/message/ECF-4.0-FilingStatusResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<nc:Case>
<nc:CaseTitleText>In the Superior Courts of the State of Washington, John Smith vs. Bob Jones</nc:CaseTitleText>
<nc:CaseCategoryText>Small claims</nc:CaseCategoryText>
<nc:CaseTrackingID>1021</nc:CaseTrackingID>
</nc:Case>
<nc:DocumentIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilingID</nc:IdentificationCategoryText>
</nc:DocumentIdentification>
<ecf:FilingStatus>
<nc:StatusDescriptionText>accepted without modification</nc:StatusDescriptionText>
<ecf:FilingStatusCode>accepted</ecf:FilingStatusCode>
</ecf:FilingStatus>
</FilingStatusResponseMessage>
Court Record Component
The Court is a REQUIRED logical component within the system which is equivalent/analogous to the Court Record MDE from the ECF specification, which; Enables a court to record electronic documents and court list entries in its case management and document management systems and returns the results to the Registry. The Court also enables a Filer to obtain service information for all parties in a case, to obtain information about cases maintained in the court’s court list, register of actions and calendars, and to access documents maintained in the court’s electronic records.
Court Record Webhook
This componet interacts with the Registry component asynchronously through Webhooks. It expects the Registry to implement an endpoint that will receive the following event payloads:
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
The Court MUST post an event to the Registry 's Webhook endpoint as an asynchronous response indicating whether the filing was accepted or rejected by the court record system. If the Court rejected the filing, an explanation MUST be provided. If the Court accepts the filing, the case file information (e.g. date and time the document was entered into the court record, judge assigned, document identifiers and next court event scheduled) MUST be provided.
Implementation
The Court MUST implement the following.
Generates Messages:
- Filing event messages
Performs Activities:
- Notifies the Registry of filing related events through the Court Record Webhook
Implement Functionality For:
- /Court/Record - Post
The Court is a REQUIRED logical component within the system which is equivalent/analogous to the Court Record MDE from the ECF specification, which; Enables a court to record electronic documents and court list entries in its case management and document management systems and returns the results to the Registry. The Court also enables a Filer to obtain service information for all parties in a case, to obtain information about cases maintained in the court’s court list, register of actions and calendars, and to access documents maintained in the court’s electronic records.
Court Record Webhook
This componet interacts with the Registry component asynchronously through Webhooks. It expects the Registry to implement an endpoint that will receive the following event payloads:
- Filing Accepted/Rejected - A message indicating the filing was either accepted and registered with the court, or rejected and why.
The Court MUST post an event to the Registry 's Webhook endpoint as an asynchronous response indicating whether the filing was accepted or rejected by the court record system. If the Court rejected the filing, an explanation MUST be provided. If the Court accepts the filing, the case file information (e.g. date and time the document was entered into the court record, judge assigned, document identifiers and next court event scheduled) MUST be provided.
Implementation
The Court MUST implement the following.
Generates Messages:
- Filing event messages
Performs Activities:
- Notifies the Registry of filing related events through the Court Record Webhook
Implement Functionality For:
- /Court/Record - Post
post /Court/Record
Submit a filing to the court.
If the registry clerk reviews and accepts the filing, the Registry MUST submit the filing to the Court record. The information submitted includes information from Registry submission along with any modifications or comments made by the clerk. The Court responds synchronously with an acknowledgement of the request.
This method is equivalent/analogous to the RecordFiling operation in the ECF standards.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<!--
This schema was created specifically for the initail draft implementation of the API for the CSO project.
It is not part of the standard set of message schemas provided with the ECF specification.
This message schema is equivelant to "RecordFilingRequestMessage" which is defined in the ECF-4.0-WebServicesProfile-Definitions.wsdl of the ecf-v4.0-webservices-v2.01-csprd02 specifications for use with the calls to RecordFiling.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:RecordFilingRequestMessage-4.0" xmlns:core="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" xmlns:docket="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:RecordDocketingMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:RecordFilingRequestMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>RecordFilingRequestMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:RecordDocketingMessage-4.0" schemaLocation="../ecf-v4.0-spec/xsd/message/ECF-4.0-RecordDocketingMessage.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" schemaLocation="../ecf-v4.0-spec/xsd/message/ECF-4.0-CoreFilingMessage.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="RecordFilingRequestMessageType">
<xsd:annotation>
<xsd:documentation>Message resulting from clerk review and edit of a CoreFilingMessage. Requesting the court to file the documents.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:ElectronicFilingCallbackMessageType">
<xsd:sequence>
<xsd:element ref="docket:RecordDocketingMessage"/>
<xsd:element ref="core:CoreFilingMessage"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="RecordFilingRequestMessage" type="RecordFilingRequestMessageType">
<xsd:annotation>
<xsd:documentation>Message resulting from clerk review and edit of a CoreFilingMessage. Requesting the court to file the documents.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<RecordDocketingMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:RecordDocketingMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:RecordDocketingMessage-4.0 ../xsd/message/ECF-4.0-RecordDocketingMessage.xsd">
<nc:DocumentIdentification>
<nc:IdentificationID>001-f786e6d6-558c-448f-b249-067002d716a0</nc:IdentificationID>
</nc:DocumentIdentification>
<nc:DocumentInformationCutOffDate>
<nc:DateTime>2007-06-06T14:20:45.0Z</nc:DateTime>
</nc:DocumentInformationCutOffDate>
<nc:DocumentPostDate>
<nc:DateTime>2007-06-06T14:20:46.0Z</nc:DateTime>
</nc:DocumentPostDate>
<nc:DocumentReceivedDate>
<nc:DateTime>2007-06-06T14:20:47.0Z</nc:DateTime>
</nc:DocumentReceivedDate>
<nc:DocumentSubmitter>
<ecf:EntityPerson s:id="Person1">
<nc:PersonName>
<nc:PersonNamePrefixText>Mr.</nc:PersonNamePrefixText>
<nc:PersonGivenName>Jonathan</nc:PersonGivenName>
<nc:PersonMiddleName>Richard</nc:PersonMiddleName>
<nc:PersonSurName>Registrant</nc:PersonSurName>
<nc:PersonNameSuffixText>Sr.</nc:PersonNameSuffixText>
<nc:PersonFullName>John R. Registrant Sr.</nc:PersonFullName>
</nc:PersonName>
<nc:PersonOtherIdentification>
<nc:IdentificationID>AZAOCEFM-12345: jregistrant@aol.com</nc:IdentificationID>
<nc:IdentificationSourceText>AZAOCEFM: ATTORNEY</nc:IdentificationSourceText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</nc:DocumentSubmitter>
<ecf:SendingMDELocationID>
<nc:IdentificationID>AZAOCL2CEFSP</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>1</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>Arizona Supreme Court</j:CourtName>
</j:CaseCourt>
<nc:CaseTrackingID>AZ2000701</nc:CaseTrackingID>
<ecf:ReviewedLeadDocument s:id="Information">
<nc:DocumentApplicationName>application/pdf</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Information</nc:DocumentDescriptionText>
<nc:DocumentStatus>
<nc:StatusDescriptionText>SEALED</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>BR03</j:RegisterActionDescriptionText>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentSignature>
<ecf:SignatureProfileID>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileID>
<ecf:Signature>
<digsig:KeyInfo xmlns:digsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://www.w3.org/2000/09/xmldsig# ../xsd/common/xmldsig-core-schema.xsd">
<digsig:KeyName>FilerPublicKey</digsig:KeyName>
</digsig:KeyInfo>
</ecf:Signature>
</ecf:DocumentSignature>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment1">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment1</nc:BinaryLocationURI>
<ecf:AttachmentSequenceID>1</ecf:AttachmentSequenceID>
</ecf:DocumentAttachment>
<ecf:DocumentAttachment s:id="Attachment2">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment2</nc:BinaryLocationURI>
<ecf:AttachmentSequenceID>2</ecf:AttachmentSequenceID>
</ecf:DocumentAttachment>
<ecf:ColorRelevantIndicator>false</ecf:ColorRelevantIndicator>
<ecf:RedactedIndicator>false</ecf:RedactedIndicator>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
<ecf:DocumentHashText>23452345223445324</ecf:DocumentHashText>
<ecf:DocumentDocketID>
<nc:IdentificationID>1031</nc:IdentificationID>
</ecf:DocumentDocketID>
<ecf:SealDocumentIndicator>false</ecf:SealDocumentIndicator>
</ecf:ReviewedLeadDocument>
<ecf:ReviewedConnectedDocument s:id="Document2">
<nc:DocumentApplicationName>application/pdf</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Appendix to Reply Brief</nc:DocumentDescriptionText>
<nc:DocumentIdentification>
<nc:IdentificationID>ReplyAppendix01</nc:IdentificationID>
</nc:DocumentIdentification>
<nc:DocumentSequenceID>1</nc:DocumentSequenceID>
<nc:DocumentStatus>
<nc:StatusDescriptionText>PUBLIC</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>AP01</j:RegisterActionDescriptionText>
<ecf:ParentDocumentReference s:ref="Information"/>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentSignature>
<ecf:SignatureProfileID>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileID>
</ecf:DocumentSignature>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment3">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment3</nc:BinaryLocationURI>
<ecf:AttachmentSequenceID>3</ecf:AttachmentSequenceID>
</ecf:DocumentAttachment>
<ecf:ColorRelevantIndicator>false</ecf:ColorRelevantIndicator>
<ecf:RedactedIndicator>false</ecf:RedactedIndicator>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
<ecf:DocumentHashText>23452345223445325</ecf:DocumentHashText>
<ecf:DocumentDocketID>
<nc:IdentificationID>1032</nc:IdentificationID>
</ecf:DocumentDocketID>
<ecf:SealDocumentIndicator>false</ecf:SealDocumentIndicator>
</ecf:ReviewedConnectedDocument>
<SealCaseIndicator>false</SealCaseIndicator>
</RecordDocketingMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MessageReceiptMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MessageReceiptMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>MessageReceiptMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="MessageReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A message returned synchronously to indicate receipt by an MDE of another message. The intent is that this will serve as the synchronous reply to all MDE operations that have an additional asynchronous callback.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:CaseFilingType">
<xsd:sequence>
<xsd:element ref="j:CaseCourt"/>
<xsd:element ref="ecf:Error" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="MessageReceiptMessage" type="MessageReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A message returned synchronously to indicate receipt by an MDE of another message. The intent is that this will serve as the synchronous reply to all MDE operations that have an additional asynchronous callback.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
get /Court/Case
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY query the Court for a list of cases matching several criteria including case number, case participant, or the filed date over a specific time range. The Court responds synchronously with a list of matching cases.
This method is equivalent/analogous to the GetCaseList operation in the ECF standards.
Query Parameters
- caseID (string)
Filter the results by the case ID.
- participant (string)
Filter the results by a particular participant in the case.
- filedDateTime (string)
Filter the results by date and time.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CaseListQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="CaseListQueryMessageType">
<xsd:annotation>
<xsd:documentation>This is a query for a list of cases that match a set of criteria including case participants, case classification, case status, and date of the case was initiated.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="CaseListQueryCase" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="CaseListQueryTimeRange" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="CaseListQueryCaseParticipant" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CaseParticipantType">
<xsd:annotation>
<xsd:documentation>Placeholder for all case participants, i.e. persons or organizations playing a role in a case. This is where all actor details are expressed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="ecf:CaseParticipant"/>
<xsd:element ref="FilingSubmissionSubmitterID"/>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="CaseListQueryCase" type="nc:CaseType">
<xsd:annotation>
<xsd:documentation>Structure for general information about a case used in a query.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CaseListQueryMessage" type="CaseListQueryMessageType">
<xsd:annotation>
<xsd:documentation>This is a query for a list of cases that match a set of criteria including case participants, case classification, case status, and date of the case was initiated.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CaseListQueryTimeRange" type="nc:DateRangeType">
<xsd:annotation>
<xsd:documentation>The beginning and ending filing dates/times of cases about which information is sought in this query.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CaseListQueryCaseParticipant" type="CaseParticipantType">
<xsd:annotation>
<xsd:documentation>Information describing a participant when a query seeks information about the cases in which the person or organization is a participant.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="FilingSubmissionSubmitterID" type="nc:IdentificationType">
<xsd:annotation>
<xsd:documentation>A unique identifier assigned by the filing assembly MDE for the person who is managing the interface between the filer and the filing assembly MDE. This person will receive secondary service on behalf of the filer. This is also the serviceRecipientID for subsequent filings in this case, and asynchronous responses to this filing.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CaseListQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListQueryMessage-4.0 ../xsd/message/ECF-4.0-CaseListQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<CaseListQueryCase>
<nc:ActivityStatus>
<nc:StatusText>Active</nc:StatusText>
</nc:ActivityStatus>
<nc:CaseCategoryText>Smallclaims</nc:CaseCategoryText>
</CaseListQueryCase>
<CaseListQueryTimeRange>
<nc:StartDate>
<nc:Date>2008-08-01</nc:Date>
</nc:StartDate>
<nc:EndDate>
<nc:Date>2008-08-01</nc:Date>
</nc:EndDate>
</CaseListQueryTimeRange>
<CaseListQueryCaseParticipant>
<FilingSubmissionSubmitterID>
<nc:IdentificationID>1000</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</FilingSubmissionSubmitterID>
</CaseListQueryCaseParticipant>
</CaseListQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CaseListResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="CaseListResponseMessageType">
<xsd:annotation>
<xsd:documentation>A synchronous response to a GetCaseListQueryMessage. </xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="nc:Case" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="CaseListResponseMessage" type="CaseListResponseMessageType">
<xsd:annotation>
<xsd:documentation>A synchronous response to a GetCaseListQueryMessage. </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CaseListResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseListResponseMessage-4.0 ../xsd/message/ECF-4.0-CaseListResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<civil:CivilCase xmlns:civil="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CivilCase-4.0" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CivilCase-4.0 ../xsd/casetype/ECF-4.0-CivilCase.xsd">
<nc:ActivityStatus>
<nc:StatusText>Active</nc:StatusText>
<nc:StatusDate>
<nc:DateTime>2008-08-01T14:20:00Z</nc:DateTime>
</nc:StatusDate>
<nc:StatusDescriptionText>At trial</nc:StatusDescriptionText>
</nc:ActivityStatus>
<nc:CaseTitleText>In the Superior Courts of the State of Washington, John Smith vs. Bob Jones</nc:CaseTitleText>
<nc:CaseCategoryText>Smallclaims</nc:CaseCategoryText>
<nc:CaseTrackingID>KC-2008-1001</nc:CaseTrackingID>
<j:CaseAugmentation>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<j:CaseInitiatingParty>
<ecf:EntityPerson>
<nc:PersonName>
<nc:PersonGivenName>John</nc:PersonGivenName>
<nc:PersonSurName>Smith</nc:PersonSurName>
</nc:PersonName>
</ecf:EntityPerson>
</j:CaseInitiatingParty>
</j:CaseAugmentation>
<ecf:CaseAugmentation>
<ecf:CaseShortTitleText>Smith vs. Jones</ecf:CaseShortTitleText>
</ecf:CaseAugmentation>
<ecf:CauseOfActionCode/>
<civil:ClassActionIndicator>false</civil:ClassActionIndicator>
<civil:JuryDemandIndicator>false</civil:JuryDemandIndicator>
<civil:ReliefTypeCode/>
</civil:CivilCase>
</CaseListResponseMessage>
get /Court/Case/{caseID}
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY query the Court for information about a particular case including the case participants, court docket and calendar events. The Filer MAY also limit the amount of case detail returned from the Court by using a set of filters. The Court responds synchronously with the selected case information.
This method is equivalent/analogous to the GetCase operation in the ECF standards.
TODO: Determine the complete list of filter parameters.
URI Parameters
- caseID: required (string)
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CaseQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="CaseQueryMessageType">
<xsd:annotation>
<xsd:documentation>A message requesting a list of cases from a court's case management information system conforming to the parameter or parameters identified in the message.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="nc:CaseTrackingID"/>
<xsd:element ref="CaseQueryCriteria"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CaseQueryCriteriaType">
<xsd:annotation>
<xsd:documentation>A message requesting a list of cases from a court's case management information system conforming to the parameter or parameters identified in the message.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element ref="IncludeParticipantsIndicator"/>
<xsd:element ref="IncludeDocketEntryIndicator"/>
<xsd:element ref="IncludeCalendarEventIndicator"/>
<xsd:element ref="DocketEntryTypeCodeFilterText"/>
<xsd:element ref="CalendarEventTypeCodeFilterText"/>
<xsd:element ref="DocketEntryTimeRange" minOccurs="0"/>
<xsd:element ref="CalendarEventTimeRange" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="CalendarEventTimeRange" type="nc:DateRangeType">
<xsd:annotation>
<xsd:documentation>A filter criterion for calendar events. If present, the response should only include calendar events that fall between the from and to dates and times.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CalendarEventTypeCodeFilterText" type="nc:TextType">
<xsd:annotation>
<xsd:documentation>Filter criterion indicating that only calendar entries of a specified type are being requested.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CaseQueryCriteria" type="CaseQueryCriteriaType">
<xsd:annotation>
<xsd:documentation>Criteria limiting the case information to be returned.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CaseQueryMessage" type="CaseQueryMessageType">
<xsd:annotation>
<xsd:documentation>A message requesting a list of cases from a court's case management information system conforming to the parameter or parameters identified in the message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DocketEntryTimeRange" type="nc:DateRangeType">
<xsd:annotation>
<xsd:documentation>A filter criterion for docket entries. If present, the response should only include docket entries that fall between the from and to dates and times.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DocketEntryTypeCodeFilterText" type="nc:TextType">
<xsd:annotation>
<xsd:documentation>Filter criterion indicating that only docket entries of a specified type are being requested.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IncludeParticipantsIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicates whether requester wishes participant information to be included in the response.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IncludeDocketEntryIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicates whether requester wishes docket entry information to be included in the response.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IncludeCalendarEventIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicates whether requester wishes calendar event information to be included in the response.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CaseQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0 ../xsd/message/ECF-4.0-CaseQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<nc:CaseTrackingID>KC-2008-1001</nc:CaseTrackingID>
<CaseQueryCriteria>
<IncludeParticipantsIndicator>true</IncludeParticipantsIndicator>
<IncludeDocketEntryIndicator>true</IncludeDocketEntryIndicator>
<IncludeCalendarEventIndicator>true</IncludeCalendarEventIndicator>
<DocketEntryTypeCodeFilterText>Filings</DocketEntryTypeCodeFilterText>
<CalendarEventTypeCodeFilterText>Hearings</CalendarEventTypeCodeFilterText>
<DocketEntryTimeRange>
<nc:StartDate>
<nc:Date>2008-08-01</nc:Date>
</nc:StartDate>
<nc:EndDate>
<nc:Date>2008-08-01</nc:Date>
</nc:EndDate>
</DocketEntryTimeRange>
<CalendarEventTimeRange>
<nc:StartDate>
<nc:Date>2008-08-01</nc:Date>
</nc:StartDate>
<nc:EndDate>
<nc:Date>2008-08-01</nc:Date>
</nc:EndDate>
</CalendarEventTimeRange>
</CaseQueryCriteria>
</CaseQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseResponseMessage-4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CaseResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="CaseResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a GetCaseInformationQuery. </xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="nc:Case" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="CaseResponseMessage" type="CaseResponseMessageType">
<xsd:annotation>
<xsd:documentation>A message requesting a list of cases from a court's case management information system conforming to the parameter or parameters identified in the message.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<CaseResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseResponseMessage-4.0 ../xsd/message/ECF-4.0-CaseResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<appellate:AppellateCase xmlns:appellate="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:AppellateCase-4.0" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:AppellateCase-4.0 ../xsd/casetype/ECF-4.0-AppellateCase.xsd">
<nc:CaseTitleText>State of Arizona v Jack Smith</nc:CaseTitleText>
<nc:CaseTrackingID>CR070123</nc:CaseTrackingID>
<j:CaseAugmentation>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>1</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>Arizona Supreme Court</j:CourtName>
</j:CaseCourt>
<ecf:CaseCourtEvent>
<nc:ActivityIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
</nc:ActivityIdentification>
<nc:ActivityDate>
<nc:DateTime>2008-08-01T14:20:00.0Z</nc:DateTime>
</nc:ActivityDate>
<nc:ActivityDescriptionText>Hearing</nc:ActivityDescriptionText>
<j:CourtEventJudge>
<nc:RoleOfPersonReference s:ref="Judge1"/>
</j:CourtEventJudge>
<j:CourtEventSchedule>
<nc:ScheduleActivityText>Hearing</nc:ScheduleActivityText>
<nc:ScheduleDate>
<nc:DateTime>2008-07-30T14:20:00.0Z</nc:DateTime>
</nc:ScheduleDate>
</j:CourtEventSchedule>
<ecf:CourtEventEnteredOnDocketDate>
<nc:Date>2008-08-01</nc:Date>
</ecf:CourtEventEnteredOnDocketDate>
<ecf:CourtEventTypeCode>Initial filing</ecf:CourtEventTypeCode>
<ecf:CourtEventDocument s:id="Document1">
<nc:DocumentApplicationName>application/pdf</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Appellee's Reply Brief</nc:DocumentDescriptionText>
<nc:DocumentStatus>
<nc:StatusDescriptionText>SEALED</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>BR03</j:RegisterActionDescriptionText>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment1">
<nc:BinaryLocationURI>cid://Attachment1</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</ecf:CourtEventDocument>
</ecf:CaseCourtEvent>
<j:CaseInitiatingAttorney>
<nc:RoleOfPersonReference s:ref="Person2"/>
<j:JudicialOfficialBarMembership>
<j:JudicialOfficialBarIdentification>
<nc:IdentificationID>23101</nc:IdentificationID>
<j:IdentificationJurisdictionNCICLISCode>AZ</j:IdentificationJurisdictionNCICLISCode>
<nc:IdentificationSourceText>State Bar of Arizona</nc:IdentificationSourceText>
</j:JudicialOfficialBarIdentification>
</j:JudicialOfficialBarMembership>
</j:CaseInitiatingAttorney>
</j:CaseAugmentation>
<ecf:CaseAugmentation>
<ecf:CaseParticipant>
<ecf:EntityPerson s:id="Judge1">
<nc:PersonName>
<nc:PersonFullName>Judge Kelly Thomas.</nc:PersonFullName>
</nc:PersonName>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode/>
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<ecf:EntityPerson s:id="Person2">
<nc:PersonName>
<nc:PersonFullName>John R. Registrant Sr.</nc:PersonFullName>
</nc:PersonName>
<ecf:PersonAugmentation>
<nc:ContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6024561234</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
<nc:ContactEmailID>jregistrant@aol.com</nc:ContactEmailID>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:AddressDeliveryPointID>777</nc:AddressDeliveryPointID>
<nc:AddressSecondaryUnitText>Suite 507</nc:AddressSecondaryUnitText>
<nc:LocationStreet>
<nc:StreetPredirectionalText>W</nc:StreetPredirectionalText>
<nc:StreetName>Litigant Avenue</nc:StreetName>
</nc:LocationStreet>
<nc:LocationCityName>Flagstaff</nc:LocationCityName>
<nc:LocationCountyName>Coconino</nc:LocationCountyName>
<nc:LocationStateUSPostalServiceCode>AZ</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>89007</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
</nc:ContactInformation>
</ecf:PersonAugmentation>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode/>
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<ecf:EntityOrganization s:id="Organization1">
<nc:OrganizationName>Dewey, Cheatem and Howe</nc:OrganizationName>
<nc:OrganizationUnitName>Flagstaff Office</nc:OrganizationUnitName>
</ecf:EntityOrganization>
<ecf:CaseParticipantRoleCode/>
</ecf:CaseParticipant>
<ecf:CaseShortTitleText>State vs. Smith</ecf:CaseShortTitleText>
<ecf:PersonOrganizationAssociation>
<nc:PersonReference s:ref="Person2"/>
<nc:OrganizationReference s:ref="Organization1"/>
<ecf:EntityAssociationTypeCode>Employer</ecf:EntityAssociationTypeCode>
</ecf:PersonOrganizationAssociation>
</ecf:CaseAugmentation>
</appellate:AppellateCase>
</CaseResponseMessage>
Documents within a specific case file.
get /Court/Case/{caseID}/Documents/{documentID}
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY query the Court file a particular document from a case. The Court will respond synchronously with the requested document or instructions on how to access it.
This method is equivalent/analogous to the GetDocument operation in the ECF standards.
URI Parameters
- caseID: required (string)
- documentID: required (string)
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>DocumentQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="DocumentQueryMessageType">
<xsd:annotation>
<xsd:documentation>A request for an electronic document in the court's official record. </xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="nc:CaseTrackingID"/>
<xsd:element ref="nc:CaseDocketID"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="DocumentQueryMessage" type="DocumentQueryMessageType">
<xsd:annotation>
<xsd:documentation>A request for an electronic document in the court's official record. </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<DocumentQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentQueryMessage-4.0 ../xsd/message/ECF-4.0-DocumentQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<nc:CaseTrackingID>KC-2008-1001</nc:CaseTrackingID>
<nc:CaseDocketID>1001</nc:CaseDocketID>
</DocumentQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>DocumentResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="DocumentResponseMessageType">
<xsd:annotation>
<xsd:documentation>The court's response to a request for an electronic document in the court's official record. </xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="ecf:Document"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="DocumentResponseMessage" type="DocumentResponseMessageType">
<xsd:annotation>
<xsd:documentation>The court's response to a request for an electronic document in the court's official record. </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<DocumentResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:DocumentResponseMessage-4.0 ../xsd/message/ECF-4.0-DocumentResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<ecf:Document s:id="Document1">
<nc:DocumentApplicationName>application/pdf</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Information</nc:DocumentDescriptionText>
<nc:DocumentStatus>
<nc:StatusDescriptionText>SEALED</nc:StatusDescriptionText>
</nc:DocumentStatus>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText>BR03</j:RegisterActionDescriptionText>
<ecf:FilingAttorneyID>
<nc:IdentificationID>AZ:231001</nc:IdentificationID>
</ecf:FilingAttorneyID>
<ecf:FilingPartyID>
<nc:IdentificationID>1</nc:IdentificationID>
</ecf:FilingPartyID>
<ecf:SpecialHandlingInstructions/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentSignature>
<ecf:SignatureProfileID>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:XMLSignature-1.0</ecf:SignatureProfileID>
<ecf:Signature>
<digsig:KeyInfo xmlns:digsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://www.w3.org/2000/09/xmldsig# ../xsd/common/xmldsig-core-schema.xsd">
<digsig:KeyName>FilerPublicKey</digsig:KeyName>
</digsig:KeyInfo>
</ecf:Signature>
</ecf:DocumentSignature>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment1">
<nc:BinaryDescriptionText>application/pdf</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Attachment1</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
<ecf:ColorRelevantIndicator>false</ecf:ColorRelevantIndicator>
<ecf:RedactedIndicator>false</ecf:RedactedIndicator>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</ecf:Document>
</DocumentResponseMessage>
get /Court/ServiceInformation
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
The Filer MAY obtain the Court’s service information for all parties in an existing case at any time using the appropriate case number on the Court. The service list returned assists the filer in maintaining the filer’s service list and is not a substitute for the filer’s service list. To provide this information, the Court MUST have access to the court’s registry with all updated information about case participants. There MUST be only one such registry per court, though multiple courts MAY share the same registry. The Court responds synchronously to the Filer with a service list reflecting the most current contact information available to the court, which is necessary to complete secondary service, whether electronically or by other means.
If the court provides a Hub Service, the electronic service information returned from this query MUST include the court’s Service ID for all case participants who have one.
A party to a case is always the official target of service. In practice, the system will actually deliver to pro se litigants and to attorneys as intermediaries.
The duty to complete secondary service is upon the filer, and not the court, except when the court is the filer.
The query returns a service list current as of the transaction. No assumption can be made that the data returned by the operation will remain current for use at any future point in time.
This method is equivalent/analogous to the GetServiceInformation operation in the ECF standards.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationQueryMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>ServiceInformationQueryMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="ServiceInformationQueryMessageType">
<xsd:annotation>
<xsd:documentation>A message requesting information concerning the persons entitled to services of filings in a particular court case, together with the electronic addresses and message profiles of their Filing Assembly MDEs and their physical addresses if they are not currently using a Filing Assembly MDE.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryMessageType">
<xsd:sequence>
<xsd:element ref="nc:CaseTrackingID"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ServiceInformationQueryMessage" type="ServiceInformationQueryMessageType">
<xsd:annotation>
<xsd:documentation>A message requesting information concerning the persons entitled to services of filings in a particular court case, together with the electronic addresses and message profiles of their Filing Assembly MDEs and their physical addresses if they are not currently using a Filing Assembly MDE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<ServiceInformationQueryMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationQueryMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationQueryMessage-4.0 ../xsd/message/ECF-4.0-ServiceInformationQueryMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<ecf:QuerySubmitter>
<ecf:EntityPerson>
<nc:PersonOtherIdentification>
<nc:IdentificationID>1001</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</nc:PersonOtherIdentification>
</ecf:EntityPerson>
</ecf:QuerySubmitter>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<nc:CaseTrackingID>KC-2008-1001</nc:CaseTrackingID>
</ServiceInformationQueryMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationResponseMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>ServiceInformationResponseMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="ServiceInformationResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a serviceInformationQueryMessage, setting forth the requested information.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:QueryResponseMessageType">
<xsd:sequence>
<xsd:element ref="nc:CaseTrackingID"/>
<xsd:element ref="ServiceRecipient" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ServiceInformationResponseMessage" type="ServiceInformationResponseMessageType">
<xsd:annotation>
<xsd:documentation>The response to a serviceInformationQueryMessage, setting forth the requested information.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ServiceRecipient" type="nc:EntityType">
<xsd:annotation>
<xsd:documentation>The person or organization to be served in this case</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<ServiceInformationResponseMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationResponseMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceInformationResponseMessage-4.0 ../xsd/message/ECF-4.0-ServiceInformationResponseMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://courts.wa.gov:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ecf:Error>
<ecf:ErrorCode>0</ecf:ErrorCode>
<ecf:ErrorText>No error</ecf:ErrorText>
</ecf:Error>
<nc:CaseTrackingID>1021</nc:CaseTrackingID>
<ServiceRecipient>
<ecf:EntityPerson>
<nc:PersonName>
<nc:PersonGivenName>John</nc:PersonGivenName>
<nc:PersonSurName>Smith</nc:PersonSurName>
</nc:PersonName>
<ecf:PersonAugmentation>
<ecf:ElectronicServiceInformation>
<ecf:ServiceRecipientID>
<nc:IdentificationID>1031</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFFilerID</nc:IdentificationCategoryText>
</ecf:ServiceRecipientID>
<ecf:ReceivingMDELocationID>
<nc:IdentificationID>https://eserviceprovider.com:8000</nc:IdentificationID>
</ecf:ReceivingMDELocationID>
<ecf:ReceivingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:ReceivingMDEProfileCode>
</ecf:ElectronicServiceInformation>
<nc:ContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>55555551212</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>500 Main St.</nc:StreetFullText>
</nc:LocationStreet>
<nc:LocationCityName>Seattle</nc:LocationCityName>
<nc:LocationStateName>WA</nc:LocationStateName>
<nc:LocationPostalCode>98101</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
<nc:ContactInformationDescriptionText>Home</nc:ContactInformationDescriptionText>
</nc:ContactInformation>
</ecf:PersonAugmentation>
</ecf:EntityPerson>
</ServiceRecipient>
</ServiceInformationResponseMessage>
Legal Service Component
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
Enables a party to receive service electronically FROM other parties in the case. Note that service TO other parties in the case is performed by the Filer.
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
Enables a party to receive service electronically FROM other parties in the case. Note that service TO other parties in the case is performed by the Filer.
post /LegalService/Serve
Not implemented. Reserved for future implementation. The content and response body schemas and examples are provided for informational purposes only.
Serve case files to 3rd parties.
At approximately the same time the Filer submits the filing to the court, the Filer MAY serve the entire filing, to other parties in the case by posting the information to the service recipient. This operation MUST NOT be used to serve parties in a new case or to persons or organizations that have not yet been made party to the case. The LegalService responds synchronously with an acknowledgement that the message will be delivered to the service recipient or with an error. If the court hosts a Hub Service, the Filer MAY send post to Hub Service. The Hub Service MUST then broadcast the message to each of the LegalService's and respond synchronously with a single response to the Filer, conveying the results of each individual service transaction. If a court chooses to support electronic service, then each Filer MUST support service operations for the clients for which it provides Filer functionality.
This method is equivalent/analogous to the ServeFiling operation in the ECF standards.
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>CoreFilingMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:complexType name="CoreFilingMessageType">
<xsd:annotation>
<xsd:documentation>The structure of a Filing including any Payment Information will be documented in this section. This describes the filing transaction between the Filing Assembly MDE and the Filing Review MDE. This information will become part of the Record Docketing between the Filing Review MDE and the Court Record MDE but does not necessarily describe the information that is actually stored in the Court Record.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ecf:ElectronicFilingMessageType">
<xsd:sequence>
<xsd:element ref="nc:Case"/>
<xsd:element ref="FilingConfidentialityIndicator" minOccurs="0"/>
<xsd:element ref="FilingLeadDocument" maxOccurs="unbounded"/>
<xsd:element ref="FilingConnectedDocument" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="CoreFilingMessage" type="CoreFilingMessageType">
<xsd:annotation>
<xsd:documentation>The structure of a Filing including any Payment Information will be documented in this section. This describes the filing transaction between the Filing Assembly MDE and the Filing Review MDE. This information will become part of the Record Docketing between the Filing Review MDE and the Court Record MDE but does not necessarily describe the information that is actually stored in the Court Record.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="FilingConfidentialityIndicator" type="niem-xsd:boolean">
<xsd:annotation>
<xsd:documentation>Indicator by the filer that something in the message requires sensitive or confidential treatment. (This replaces the former "request to seal" document metadata.)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="FilingConnectedDocument" type="ecf:DocumentType">
<xsd:annotation>
<xsd:documentation>A document included in a Filing that supports the Document. This document is not separately entered on the docket or register of actions.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="FilingLeadDocument" type="ecf:DocumentType">
<xsd:annotation>
<xsd:documentation>The pleading, motion or order that is the main document in a Filing. A Document may have Attachments.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<!--
This is an example of XML following the Legal XML ECF 4.01 specification with extensions for Bankruptcy Notice specific information
nc - niem core
j - justice xml
ecf - legal xml electronic case file 4.0
ebn - extension created for electronic bankruptcy noticng elements not existing in other specifications
<BankruptcyNotice xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:Bankruptcy_Notice somelocation/Bankruptcy_Notice.xsd">
-->
<!-- -->
<CoreFilingMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CoreFilingMessage-4.0 ../xsd/message/ECF-4.0-CoreFilingMessage.xsd">
<nc:DocumentIdentification>
<nc:IdentificationID>1247-12345</nc:IdentificationID>
<!-- Bankruptcy Noticing Center generated; combination of trading partner number and serial; id's this XML document instance -->
</nc:DocumentIdentification>
<nc:DocumentPostDate>
<nc:DateTime>2010-06-06T14:20:47.0Z</nc:DateTime>
<!-- mailing date -->
</nc:DocumentPostDate>
<ecf:SendingMDELocationID>
<nc:IdentificationID>91</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>MESSAGINGPROFILEID</ecf:SendingMDEProfileCode>
<bankruptcy:BankruptcyCase xmlns:bankruptcy="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:BankruptcyCase-4.0" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:BankruptcyCase-4.0 ../xsd/casetype/ECF-4.0-BankruptcyCase.xsd">
<nc:ActivityDate>
<nc:Date>2010-01-21</nc:Date>
</nc:ActivityDate>
<!-- use for case initiation date instead of nc:CaseFiling/nc:ActivityDate -->
<nc:CaseTitleText>Bankruptcy of John Q. Public</nc:CaseTitleText>
<nc:CaseTrackingID>123456ABC</nc:CaseTrackingID>
<nc:CaseDocketID>10-1325-ABC</nc:CaseDocketID>
<!-- case number plus judges initials -->
<j:CaseAugmentation>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>113a-08</nc:IdentificationID>
<!-- combines district and office code; may need to separate -->
</nc:OrganizationIdentification>
<nc:OrganizationLocation>
<nc:LocationAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>N. Florida Avenue</nc:StreetFullText>
</nc:LocationStreet>
<!-- our addresses are not available at detail component level -->
<nc:LocationCityName>Tampa</nc:LocationCityName>
<nc:LocationStateUSPostalServiceCode>FL</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>33602</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:LocationAddress>
</nc:OrganizationLocation>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8133015137</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<j:CourtName>Middle District of Florida</j:CourtName>
</j:CaseCourt>
<j:CaseInitiatingParty>
<nc:EntityPersonReference s:ref="Debtor"/>
</j:CaseInitiatingParty>
<!--j:CaseJudge>
<nc:RoleOfPersonReference s:ref="Judge"/>
<j:CaseOfficialRoleText>Judge</j:CaseOfficialRoleText>
</j:CaseJudge-->
<j:CaseOtherEntity>
<nc:EntityPersonReference s:ref="JointDebtor"/>
</j:CaseOtherEntity>
<j:CaseOtherEntity>
<nc:EntityPersonReference s:ref="Clerk"/>
</j:CaseOtherEntity>
<j:CaseOtherEntity>
<nc:EntityPersonReference s:ref="Trustee"/>
</j:CaseOtherEntity>
<j:CaseInitiatingAttorney>
<nc:RoleOfPersonReference s:ref="Attorney"/>
<j:CaseOfficialRoleText xsi:nil="true"/>
</j:CaseInitiatingAttorney>
</j:CaseAugmentation>
<ecf:CaseAugmentation>
<!--ecf:CaseOfficial>
<ecf:CaseRepresentedPartyReference></ecf:CaseRepresentedPartyReference>
</ecf:CaseOfficial-->
<ecf:Alias>
<ecf:AliasAlternateName>Adam Public</ecf:AliasAlternateName>
<ecf:AliasAlternateNameTypeCode>aka</ecf:AliasAlternateNameTypeCode>
<nc:EntityReference s:ref="Debtor"/>
</ecf:Alias>
<ecf:Alias>
<ecf:AliasAlternateName>Eve Public</ecf:AliasAlternateName>
<ecf:AliasAlternateNameTypeCode>aka</ecf:AliasAlternateNameTypeCode>
<nc:EntityReference s:ref="JointDebtor"/>
</ecf:Alias>
<ecf:CaseParticipant>
<ecf:EntityPerson s:id="Debtor">
<nc:PersonName>
<nc:PersonFullName>John Q. Public</nc:PersonFullName>
</nc:PersonName>
<nc:PersonTaxIdentification>
<nc:IdentificationID>XXX-XX-0987</nc:IdentificationID>
<!-- will need to allow for multiple SSN and tax ids -->
</nc:PersonTaxIdentification>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode>Debtor</ecf:CaseParticipantRoleCode>
<!-- # Allowable role codes should be defined in court policy -->
<nc:ContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>2025551234</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>555 W 130th St.</nc:StreetFullText>
</nc:LocationStreet>
<!-- our addresses are not available at detail component level -->
<nc:AddressSecondaryUnitText>Suite 507</nc:AddressSecondaryUnitText>
<nc:LocationCityName>Flagstaff</nc:LocationCityName>
<nc:LocationStateUSPostalServiceCode>AZ</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>89007</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
</nc:ContactInformation>
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<ecf:EntityPerson s:id="JointDebtor">
<nc:PersonName>
<nc:PersonFullName>Mary A. Public</nc:PersonFullName>
</nc:PersonName>
<nc:PersonTaxIdentification>
<nc:IdentificationID>XXX-XX-1234</nc:IdentificationID>
<!-- will need to allow for multiple SSN and tax ids -->
</nc:PersonTaxIdentification>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode>JointDebtor</ecf:CaseParticipantRoleCode>
<!-- # Allowable role codes should be defined in court policy -->
<nc:ContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>202555123</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>555 W 130th St.</nc:StreetFullText>
</nc:LocationStreet>
<!-- our addresses are not available at detail component level -->
<nc:AddressSecondaryUnitText>Suite 507</nc:AddressSecondaryUnitText>
<nc:LocationCityName>Flagstaff</nc:LocationCityName>
<nc:LocationStateUSPostalServiceCode>AZ</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>89007</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
</nc:ContactInformation>
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<nc:EntityPerson s:id="Attorney">
<nc:PersonName>
<nc:PersonFullName>Dewey C. Him</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
<ecf:CaseParticipantRoleCode>Attorney</ecf:CaseParticipantRoleCode>
<!-- # Allowable role codes should be defined in court policy -->
<nc:ContactInformation>
<nc:ContactMailingAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>345 Lombard St.</nc:StreetFullText>
</nc:LocationStreet>
<!-- our addresses are not available at detail component level -->
<nc:AddressSecondaryUnitText>Suite 666</nc:AddressSecondaryUnitText>
<nc:LocationCityName>Tucson</nc:LocationCityName>
<nc:LocationStateUSPostalServiceCode>AZ</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>89007</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:ContactMailingAddress>
</nc:ContactInformation>
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<!--ebn:EntityPerson s:id="Judge">
<nc:PersonName><nc:PersonFullName>U. R. Honor</nc:PersonFullName></nc:PersonName>
<j:PersonNameInitialsText>URH</j:PersonNameInitialsText>
</ebn:EntityPerson-->
<ecf:EntityPerson s:id="Judge">
<nc:PersonName>
<nc:PersonFullName>U. R. Honor</nc:PersonFullName>
</nc:PersonName>
</ecf:EntityPerson>
<ecf:CaseParticipantRoleCode>Judge</ecf:CaseParticipantRoleCode>
<!-- # Allowable role codes should be defined in court policy -->
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<nc:EntityPerson s:id="Clerk">
<nc:PersonName>
<nc:PersonFullName>Ima G. Clerk</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
<ecf:CaseParticipantRoleCode>Clerk of Court</ecf:CaseParticipantRoleCode>
<!-- # Allowable role codes should be defined in court policy -->
</ecf:CaseParticipant>
<ecf:CaseParticipant>
<nc:EntityPerson s:id="Trustee">
</nc:EntityPerson>
<ecf:CaseParticipantRoleCode>Trustee</ecf:CaseParticipantRoleCode>
<!-- # Allowable role codes should be defined in court policy -->
</ecf:CaseParticipant>
</ecf:CaseAugmentation>
<bankruptcy:AssetNoticeIndicator>false</bankruptcy:AssetNoticeIndicator>
<bankruptcy:NumberOfCreditorsValueLevelCode>normalizedString</bankruptcy:NumberOfCreditorsValueLevelCode>
<bankruptcy:EstimatedAssetsValueLevelCode>normalizedString</bankruptcy:EstimatedAssetsValueLevelCode>
<bankruptcy:EstimatedDebtsValueLevelCode>normalizedString</bankruptcy:EstimatedDebtsValueLevelCode>
<bankruptcy:SmallBusinessIndicator>true</bankruptcy:SmallBusinessIndicator>
<bankruptcy:Section1121eIndicator>true</bankruptcy:Section1121eIndicator>
<bankruptcy:DebtorTypeCode>normalizedString</bankruptcy:DebtorTypeCode>
<bankruptcy:JointPetitionIndicator>true</bankruptcy:JointPetitionIndicator>
<bankruptcy:NatureOfDebtCode>normalizedString</bankruptcy:NatureOfDebtCode>
<bankruptcy:VoluntaryIndicator>true</bankruptcy:VoluntaryIndicator>
<bankruptcy:BankruptcyStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>7</nc:IdentificationID>
</j:StatuteCodeIdentification>
</bankruptcy:BankruptcyStatute>
<bankruptcy:Debtor>
<nc:EntityPersonReference s:ref="Debtor"/>
</bankruptcy:Debtor>
<!--ebn:CaseAugmentation>
<ebn:ConversionDate>
<j:ActivityDate>2010-12-21</j:ActivityDate-->
<!-- optional only if there is a conversion -->
<!--/ebn:ConversionDate>
<ebn:ObjectionDischargeDate>
<j:ActivityDate>2011-01-21</j:ActivityDate>
</ebn:ObjectionDischargeDate>
<ebn:ProofClaimDate>
<j:ActivityDate>2011-02-21</j:ActivityDate>
</enb:ProofClaimDate>
<ebn:GovProofClaimDate>
<j:ActivityDate>2010-02-21</j:ActivityDate>
</ebn:GovProofClaimDate>
<ebn:Plan13_date>
<j:ActivityDate>2010-03-21</j:ActivityDate>
</ebn:Plan13_date>
<ebn:Means>Presumption of abuse does not exist.</ebn:Means>
<ebn:PreviousChapter>13</ebn:PreviousChapter-->
<!-- optional field -->
<!--ebn:BkFormCode>9A</ebn:BkFormCode>
<ebn:notice_short_name>Chapter 7 First Meeting</notice_short_name-->
<!-- get from header record, not EDI section -->
<!--ebn:case_type>BK</ebn:case_type-->
<!-- Is this needed? could be adversary or bankruptcy case -->
<!--j:CourtAppearance>
<j:CourtAppearanceType>Section 341 Meeting</j:CourtAppearanceType>
<nc:StructuredAddress>
<nc:LocationStreet> 801 N. Florida Avenue</nc:LocationStreet-->
<!-- our addresses are not available at detail component level -->
<!--nc:LocationCityName>Tampa</nc:LocationCityName>
<nc:LocationStateUSPostalServiceCode>FL</nc:LocationStateUSPostalServiceCode>
<nc:LocationCountryFIPS10-4Code>US</nc:LocationCountryFIPS10-4Code>
<nc:LocationPostalCode>33602</nc:LocationPostalCode>
</nc:StructuredAddress>
<nc:DateTime>2010-06-06T14:20:47.0Z</nc:DateTime-->
<!-- First meeting date and time -->
<!--/j:CourtAppearance-->
<!--/ebn:CaseAugmentation-->
</bankruptcy:BankruptcyCase>
<FilingConfidentialityIndicator>false</FilingConfidentialityIndicator>
<FilingLeadDocument s:id="_123456ABC.app.doc">
<nc:DocumentApplicationName>Microsoft Word</nc:DocumentApplicationName>
<nc:DocumentDescriptionText>Bankruptcy Notice</nc:DocumentDescriptionText>
<nc:DocumentLanguageCode>eng</nc:DocumentLanguageCode>
<ecf:DocumentMetadata>
<j:RegisterActionDescriptionText/>
<ecf:FilingAttorneyID/>
<ecf:FilingPartyID/>
</ecf:DocumentMetadata>
<ecf:DocumentRendition>
<ecf:DocumentRenditionMetadata>
<ecf:DocumentAttachment s:id="Attachment1">
<nc:BinaryDescriptionText>application/msword</nc:BinaryDescriptionText>
<nc:BinaryLocationURI>cid://Payload1</nc:BinaryLocationURI>
</ecf:DocumentAttachment>
</ecf:DocumentRenditionMetadata>
</ecf:DocumentRendition>
</FilingLeadDocument>
</CoreFilingMessage>
HTTP status code 200
Body
Type: application/xml
Schema:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xsd/
-->
<!--
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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.
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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<xsd:schema xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceReceiptMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:receipt="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MessageReceiptMessage-4.0" xmlns:a="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:AppInfo-4.0" targetNamespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceReceiptMessage-4.0" version="4.0">
<xsd:annotation>
<xsd:documentation>ServiceReceiptMessage</xsd:documentation>
<xsd:appinfo>
<i:ConformantIndicator>true</i:ConformantIndicator>
</xsd:appinfo>
</xsd:annotation>
<xsd:import namespace="http://niem.gov/niem/niem-core/2.0" schemaLocation="../constraint/niem/niem-core/2.0/niem-core.xsd"/>
<xsd:import namespace="http://niem.gov/niem/structures/2.0" schemaLocation="../constraint/niem/structures/2.0/structures.xsd"/>
<xsd:import namespace="http://niem.gov/niem/appinfo/2.0" schemaLocation="../constraint/niem/appinfo/2.0/appinfo.xsd"/>
<xsd:import namespace="http://niem.gov/niem/proxy/xsd/2.0" schemaLocation="../constraint/niem/proxy/xsd/2.0/xsd.xsd"/>
<xsd:import namespace="http://niem.gov/niem/domains/jxdm/4.0" schemaLocation="../constraint/niem/domains/jxdm/4.0/jxdm.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" schemaLocation="../common/ECF-4.0-CommonTypes.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:MessageReceiptMessage-4.0" schemaLocation="ECF-4.0-MessageReceiptMessage.xsd"/>
<xsd:import namespace="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:AppInfo-4.0" schemaLocation="../common/ECF-4.0-AppInfo.xsd"/>
<xsd:complexType name="ServiceReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A synchronous response by a Filing Assembly MDE acknowledging receipt of a service message for one of its clients.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="receipt:MessageReceiptMessageType">
<xsd:sequence>
<xsd:element ref="ServiceRecipientStatus" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ServiceRecipientStatusType">
<xsd:annotation>
<xsd:documentation>A value describing the status of electronic service on a particular recipient.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="nc:StatusType">
<xsd:sequence>
<xsd:element ref="ecf:ServiceRecipientID"/>
<xsd:element ref="ServiceStatusCode"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ServiceReceiptMessage" type="ServiceReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A synchronous response by a Filing Assembly MDE acknowledging receipt of a service message for one of its clients.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ServiceRecipientStatus" type="ServiceRecipientStatusType">
<xsd:annotation>
<xsd:documentation>A value describing the status of electronic service on a particular recipient.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ServiceStatusCode" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>Status of the service as determined by the system receiving the service. Allowable values defined in ECF-4.0-ValueLevelCode.gc.</xsd:documentation>
<xsd:appinfo>
<a:CodeListReference a:CanonicalURI="urn:oasis:names:tc:legalxml-courtfiling:codelist:gc:ServiceStatusCode" a:CanonicalVersionURI="urn:oasis:names:tc:legalxml-courtfiling:codelist:gc:ServiceStatusCode-4.0" a:LocationURI="../../gc/ECF-4.0-ServiceStatusCode.gc"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:schema>
Example:<?xml version="1.0" encoding="UTF-8"?>
<!--
Electronic Court Filing Version 4.01 Plus Errata 01
OASIS Standard incorporating Approved Errata 01
14 July 2014
Copyright (c) OASIS Open 2014. All Rights Reserved.
Source: http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata01/os/xml/
-->
<ServiceReceiptMessage xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceReceiptMessage-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:ServiceReceiptMessage-4.0 ../xsd/message/ECF-4.0-ServiceReceiptMessage.xsd">
<ecf:SendingMDELocationID>
<nc:IdentificationID>https://efilingprovider.com:8000</nc:IdentificationID>
</ecf:SendingMDELocationID>
<ecf:SendingMDEProfileCode>urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-2.0</ecf:SendingMDEProfileCode>
<j:CaseCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>01</nc:IdentificationID>
</nc:OrganizationIdentification>
<j:CourtName>King County Superior Court</j:CourtName>
</j:CaseCourt>
<ServiceRecipientStatus>
<nc:StatusDate>
<nc:DateTime>2008-08-01T14:20:00.0Z</nc:DateTime>
</nc:StatusDate>
<nc:StatusDescriptionText>Service received and will be delivered.</nc:StatusDescriptionText>
<ecf:ServiceRecipientID>
<nc:IdentificationID>1031</nc:IdentificationID>
<nc:IdentificationCategoryText>ECFServiceID</nc:IdentificationCategoryText>
</ecf:ServiceRecipientID>
<ServiceStatusCode>received</ServiceStatusCode>
</ServiceRecipientStatus>
</ServiceReceiptMessage>