OASIS LegalXML Electronic Court Filing TC
Using XML to create and transmit legal documents among attorneys, courts, litigants, and others.
Table of Contents
- ECF Quick Start Guide
- Technical Work Produced by the Committee
- Mailing Lists and Comments
On July 14, 2014, the ECF Technical Committee approved Errata 01 for ECF 4.01. More Info
On June 7, 2013, Electronic Court Filing Version 4.01 was announced as an approved OASIS standard. ECF v4.01 is a maintenance release that addresses minor schema and definition issues. More Info
ECF TC Co-Chair James Cabral has been appointed as a member of the NIEM Technical Architecture Committee (NTAC) (July 9, 2013)
The ECF TC is working with the IJIS Institute to conduct a Springboard initiative establishing a certification capability based on the ECF 4.01 standard. Organizations interested in learning more about the Springboard ECF Initiative are invited to contact Scott Serich at firstname.lastname@example.org More Info
On May 30, 2014 the IJIS Institute announced that the Georgia Administrative Office of the Courts achieved ECF 4.01 certification. More Info
Former ECF TC Chair John Greacen was presented with the OASIS Distinguished Contributor award for 2013 and inducted into the OASIS "Hall of Fame" at the OASIS 20th Anniversary reception on April 3, 2013 in Santa Clara, CA. More Info
ECF TC Co-Chair James Cabral has been elected to serve on the OASIS LegalXML Member Section Steering Committee. Mr. Cabral’s term extends through to September 2013. More Info
The most recent face-to-face meeting was held in conjunction with the NACM Conference 2014, in July. The meeting was held on July 14, 2014, in the Merriam B Meeting Room at the Westin Kierland Resort, Scottsdale, AZ. More Info
The next face-to-face meeting is planned to occur in conjunction with the Court Technology Conference (CTC) in Minneapolis, MN - September 22-24, 2015.
The OASIS Electronic Court Filing TC will develop specifications for the use of XML to create legal documents and to transmit legal documents from an attorney, party or self-represented litigant to a court, from a court to an attorney, party or self-represented litigant or to another court, and from an attorney or other user to another attorney or other user of legal documents.
ECF Quick Start Guide
To gain a simple understanding of the ECF specification, and easily understand what is required to implement ECF in your enviroment, check out the 7 Steps to Electronic Filing with Electronic Court Filing 4.0.
- Standardize integration methods in your e-Filing implementation with XML
- Integrate with any potential e-Filing Service Provider or share e-Filing data between systems or with partners
- Setup a single method of processing data related to e-Filing
- Find out how to implement legal service in your e-Filing application
In the software industry today, and especially in the global justice space, there continues to be a strong movement toward the standardization of data definition and exchange methods, and it is often the desire of administrators and technologists throughout federal, state, local, and tribal governments to apply those standards. In reality, however, it is often overwhelming to review and fully comprehend the documentation accompanying those standards. This document attempts to minimize that factor for the OASIS Electronic Court Filing (ECF) specification, and allows the reader to completely understand what is required to implement the specification in their environment ... download the quick start guide to learn more
- LegalXML Court Filing Conformance SC
- LegalXML Court Filing Document SC
- LegalXML Court Filing Outreach SC
- LegalXML Court Filing Signatures SC
3.0 Electronic Court Filing Committee Draft
3.0 ECF XML Signature Document Signature Profile Committee Draft 1.0
3.1 Electronic Court Filing Committee Draft
4.0 Electronic Court Filing Committee Draft
4.0 Web Services Service Interaction Profile
4.0 Portable Media Service Interaction Profile
4.01 Electronic Court Filing OASIS Standard Plus Errata 01
For technical assistance regarding this OASIS TC web page, contact email@example.com.
Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.