legalxml-courtfiling message

Subject: Maricopa County issues

From: "Cabral, James E." <JCabral@mtgmc.com>
To: <legalxml-courtfiling@lists.oasis-open.org>
Date: Thu, 11 May 2006 22:17:32 -0700

Title: Maricopa County issues

ECF TC:

Here are several issues/questions Maricopa County has raised regarding the ECF 3.0 specification.

Technical Questions

1. Currently, we provide metadata for splitting an attached document into parts/chunks in order to keep each part under a maximum attachment size. However, in the web service messaging profile, each of these attachments are still part of the same SOAP message and thus must be recombined at the receiving web server into a single HTTP POST. According to Maricopa, most web servers (e.g. ASP.NET, Apache, etc.) default at a maximum POST size of 10MB. Although the maximum POST size can usually be changed in the web server configuration, this could be an obstacle to implementation and also could raise issues in performance, etc. In any case, it seems like our metadata for splitting a document into parts are not working as intended. The question is whether should try to fix this in a future version of the web services message profile, or whether we should simply recommend that implementers increase the maximum POST size in their web server configurations?

2. Currently, we can query for filings or cases by case # or date. Should we also be able to query based on filing assembly MDE ( vendor) or filing status?

3. Can we add an indicator to the machine-readable court policy to indicate whether filings with multiple lead documents are supported?

4. How could ECF 3.0 be used or extended to support Judge Review and approval of documents, draft orders, etc.?