RE: ECF 5.0 Comment Resolution Log - Item 4e

[James E Cabral <jec@mtgmc.com>]

Philip,

 

Thanks for the comment.  I’ve added to the January meeting agenda.

 

__
Jim Cabral
502 509-4532

 

---

From: legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org> on behalf of Baughman, Philip <Philip.Baughman@tylertech.com>
Sent: Wednesday, December 13, 2017 2:11:32 AM
To: legalxml-courtfiling (legalxml-courtfiling@lists.oasis-open.org)
Subject: [legalxml-courtfiling] ECF 5.0 Comment Resolution Log - Item 4e

 

The comment received from Joe Mierwa was:

I think that all example messages except for serve filing should *not* have ecf:ElectronicServiceInformation at the top of the message.

 

The Disposition reads:

Change the mapping and schema to remove ecf:ElectronicServiceInformation from request and response messages.

 

 

Tyler’s Position:

We see no harm in having ecf:ElectronicServiceInformation present for both ServeFiling and ReviewFiling. In fact, we actually leverage its presence.  That is, our solution has three possible business scenarios:

 

1. eFiling only
2. eFiling plus eService
3. eService only

 

#1 and #2 are currently implemented via the ReviewFiling operation in our ECF 4.01 certified version solution, whereas #3 is implemented via the ServeFiling operation.  Our preference is to maintain that design as it is more efficient (one call instead of two in scenario #2) as well as less complex (no need to associate two separate calls either implicitly or explicitly).

 

 

Philip Baughman
Senior Software Engineering Manager, eSolutions
Tyler Technologies, Inc. 

P: 972.713.3770 ext: 113406

www.tylertech.com