This document was last revised or approved by the OASIS Electronic Court Filing TC on the above date. The level of approval is also listed above. Check the "Latest stage" location noted above for possible later revisions of this document. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=4bbf9c9f-bd29-4adb-afab-018dc7d3f220 .

TC members should send comments on this document to the TC's email list. Others should send comments to the TC's public comment list, after subscribing to it by following the instructions at https://groups.oasis-open.org/communities/community-home?CommunityKey=8b8e7de9-6bec-49ae-a1bb-018dce26009c .

This document is provided under the RF on Limited Terms Mode of the OASIS IPR Policy, the mode chosen when the Technical Committee was established. For information on whether any patents have been disclosed that may be essential to implementing this document, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the TC's web page (https://www.oasis-open.org/committees/legalxml-courtfiling/charter.php).

Note that any machine-readable content (Computer Language Definitions) declared Normative for this Work Product is provided in separate plain text files. In the event of a discrepancy between any such plain text file and display content in the Work Product's prose narrative document(s), the content in the separate plain text file prevails.

Key words:

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] and [RFC8174] when, and only when, they appear in all capitals, as shown here.

Citation format:

When referencing this document, the following citation format should be used:

[ecf-v5.01-errata01]

Electronic Court Filing v5.01 Errata 01. Edited by James Cabral, Gary Graham, Cassidy Stokes. DD Month 2025. OASIS Committee Specification Draft 01. https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/errata01/ecf-v5.01-errata01-csd01.html . Latest stage: https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/ecf-v5.01.html.

Notices:

Distributed under the terms of the OASIS IPR Policy, [https://www.oasis-open.org/policies-guidelines/ipr/]. For complete copyright information please see the full Notices section in an Appendix below.

Table of Contents

1 Introduction. 4

1.1 Changes from earlier Versions. 4

1.2 Glossary. 4

1.2.1 Definitions of terms. 4

1.2.2 Acronyms and abbreviations. 4

1.2.3 Document conventions. 4

2 Section Title. 5

2.1 Level 2 section title. 5

2.1.1 Level 3 section title. 5

2.1.1.1 Level 4 section title. 5

2.1.1.1.1 Level 5. 5

3 Conformance. 6

Appendix A. References. 7

A.1 Normative References. 7

A.2 Informative References. 8

Appendix B. Security and Privacy Considerations. 9

Appendix C. Acknowledgments. 10

C.1 Special Thanks. 10

C.2 Participants. 10

Appendix D. Revision History. 11

Appendix E. Example Title. 12

E.1 Subsidiary section. 12

E.1.1 Sub-subsidiary section. 12

E.1.1.1 Sub-sub-subsidiary section. 12

E.1.1.1.1 Sub-sub-sub-subsidiary section. 12

Appendix F. Notices. 13

1 Approved Errata for ECF Core 5.01

· Following are the approved errata to the Electronic Court Filing v5.01 Committee Specification. All references schemas are provided with the [ECF-v5.01] specification.

1.1 Reference to ecf:CasePartySelfRepresentationIndicator

In Section 6.5 Case Participant Rules, replace the second paragraph with the following:

The CaseParticipantRoleCode.gc code list defines the allowed values for ecf:CaseParticipantRoleCode and includes columns indicating which code values are valid in combination with each role element. If ecf:CaseParticipantRoleCode is provided, the code value MUST be in the CaseParticipantRoleCode.gc code list and the code list column matching the role element MUST have the value “true”. Parties not represented by an attorney should be represented with ecf:CaseParty with a ecf:CasePartySelfRepresentationIndicator value of “true”.

1.2 Case Participant Rules Example

In Section 6.5 Case Participant Rules, replace the non-normative example with the following

<nc:Case>

<nc:CaseTitleText>Jane Doe vs. John Doe </nc:CaseTitleText>

<j:CaseAugmentation>

…

<j:CaseOfficial>

<nc:RoleOfPerson structures:id=”Person1”>

…

<nc:PersonName>

<nc:PersonGivenName>James</nc:PersonGivenName>

<nc:PersonMiddleName>Q.</nc:PersonMiddleName>

<nc:PersonSurName>Quigley</nc:PersonSurName>

</nc:PersonName>

…

<ecf:PersonAugmentation>

…

<ecf:CaseParticipantRoleCode>Guardian</ecf:CaseParticipantRoleCode>

…

</ecf:PersonAugmentation>

</nc:RoleOfPerson>

</j:CaseOfficial>

</j:CaseAugmentation>

<ecf:CaseAugmentation>

<ecf:CaseTrackingID>

<nc:IdentificationID>23456ABC </nc:IdentificationID>

</ecf:CaseTrackingID>

<j:CaseNumberText>23456ABC </j:CaseNumberText>

</ecf:CaseAugmentation>

</nc:Case>

1.3 CaseParticipantRole Code List

In the schema folder, replace CaseParticipantRoleCode.gc with CaseParticipantRoleCode-roles.gc.

2 Conformance

This document does not provide any additional conformance requirements beyond those already defined in the [ECF-v5.01] specification.

Appendix A. References

This appendix contains the normative and informative references that are used in this document.

While any hyperlinks included in this appendix were valid at the time of publication, OASIS cannot guarantee their long-term validity.

A.1 Normative References

The following documents are referenced in such a way that some or all of their content constitutes requirements of this document.

[RFC2119]

Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.

[RFC8174]

Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.

[ECF-v5.01]

A.2 Informative References

The following referenced documents are not required for the application of this document but may assist the reader with regard to a particular subject area.

[RFC3552]

Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, July 2003, <https://www.rfc-editor.org/info/rfc3552>.

Appendix B. Acknowledgments

B.1 Special Thanks

Substantial contributions to this document from the following individuals are gratefully acknowledged:

Gary Graham, Arizona Supreme Court

B.2 Participants

The following individuals were members of this Technical Committee during the creation of this document and their contributions are gratefully acknowledged:

James Cabral, Individual Member

Eric Eastman, InfoTrack US

Ryan Foley, i3-ImageSoft LLC

Gary Graham, Arizona Supreme Court

Geoge Knecht, InfoTrack US

Mark Leong, Arizona Supreme Court

Enrique Othon, Tyler Technologies, Inc.

Dallas Powell, Tybera Development Group

Jim Price, Arizona Supreme Court

Brock Rogers, File & ServeXpress

Cassidy Stokes, Tybera Development Group

David Sturdivant, Tyler Technologies Inc.

Patrick Wallace, Tyler Technologies, Inc.

Charlie Wilson, Tyler Technologies, Inc.

Appendix C. Revision History

Revisions made since the initial stage of this numbered Version of this document may be tracked here.

Revision	Date	Editor	Changes Made
1.0	2025-06-26	James Cabral	Initial version.

Appendix D. Notices

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website: [https://www.oasis-open.org/policies-guidelines/ipr/].

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

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

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS AND ITS MEMBERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THIS DOCUMENT OR ANY PART THEREOF.

As stated in the OASIS IPR Policy, the following three paragraphs in brackets apply to OASIS Standards Final Deliverable documents (Committee Specifications, OASIS Standards, or Approved Errata).

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

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

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

The name "OASIS" is a trademark of OASIS, the owner and developer of this document, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, documents, while reserving the right to enforce its marks against misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark/ for above guidance.