[October 02, 2000] "The OXCI (Open XML Court Interface) initiative was founded in March 2000 with the intent of developing an open source version of an Electronic Filing Manager (EFM). Developers may find benefit in looking at the Architectural Proposal or in participating in OXCI. Comments on the document should be sent to the author, Richard Himes. OXCI is not formally affiliated with Legal XML, but it is devoted to developing Legal XML standards-compliant software and does have members who belong to Legal XML." OXCI has been set up as a SourceForge project.
References:
Open XML Court Interface (OXCI) Architecture Proposal. Document version: 1.0. Author: Richard Himes. Abstract: "This document is a draft proposal for an approach to the design of the Open XML Court Interface (OXCI). It is submitted as a seed for comments so that the design group can discuss and agree on a general methodology." Excerpts: "... OXCI will serve as the Electronic Filing Manager (EFM) module [in the diagram]; EFP is the electronic filing provider. It represents the client (attorney) side of electronic filing. The EFP wraps the filing(s) in a Legal XML envelope and transmits it to the EFM. There can be many EFP systems communicating with a particular EFM. The method of transmission is unspecified, but could be via e-mail, HTTP, FTP, or other means. An EFP must submit filings using the Legal XML Court Filing data format standard. The CMS is the case management system. It represents the court side of electronic filing. There will probably be only one CMS per EFM, but theoretically, the EFM could distribute filings to multiple CMS systems in a state or region. The CMS is responsible for accepting or rejecting a filing. Other standard CMS functions (docketing, reporting, workflow, etc.) are outside the scope of this specification...Objects will be defined based on UML (Unified Modeling Language) constructs and the OMG IDL (Object Management Group Interface Definition Language.) IDL will occasionally be augmented with sample Java implementations for clarification... The only visible portion for systems using this object is that it contains a function called submitCourtFiling that accepts a CourtFiling object and returns a Confirmation object. Thus, we only know how to invoke this function, and what we can expect in return. The CourtFiling and Confirmation objects, of course, will represent the corresponding XML documents defined in the Electronic Court Filing standard. In actuality, what is received at the court server is a message in LegalEnvelope format, which may contain a CourtFiling element. Thus, there is another level of processing that has been omitted in this discussion for sake of simplicity. All of these system objects will need to access portions of the CourtFiling XML elements. To facilitate this access, each element in the XML document should be defined as an object. All XML elements will be derived from an OxciElement, which implements the DOM interface Element..." [cache]
Open XML Court Interface on SourceForge [OXCI 'Product work for LegalXML Court Filing standard']
Related resources:
