Re: [Openefm-development] Re: OpenEFM question

[Jason V. C. <ja...@va...>]

Quoth Jeremiah Jahn, on Wed, 02 Mar 2005 16:06:06 -0600:

> Is there some sample (legal)XML for each of the four transceiver
> methods between the EFP and the EFM? 

First I should make clear the state of this code base.  Last December, I
started revising OpenEFM for a new project in Sacramento, CA.  I made a
rough draft of the requirements and sent that to the man in charge for
review.  I also started changing the code itself, having been told the
project was hot.  I haven't heard from anyone involved since then, and
the whole project is now stalled.  So the code in CVS is currently
unstable, if it runs at all, and you should opt for one of the releases.
 None of which, unfortunately, is built around these methods:

> addParty()
> addCase()
> addDocument()
> transmit()

This is the new 2GEFS interface, basically, that I have BEGUN
integrating into OpenEFM.  The calls to addParty() and such are still on
our drawing board.  Previous versions of OpenEFM are based on an
all-at-once filing submission interface, where one message contained all
parties and documents for the case filing; and that's still pretty much
the way the software is coded.

So we have no samples of our own in this new format.  However, I was
sent a handful of XML samples for the 2GEFS "Request-response" API, that
seems to be what you're looking at.  These are in the repository, under
"./sample/2GEFS".

> My Understanding of these is that they they will include the documents
> with them that PDF whatever that init a new case or party.

That was quite a sentence, Mr. Jahn.  If I understand you, when an
'addDocument()' message is sent, it will contain the binary data.  I
believe it is to be BASE-64 encoded within the XML.

> Guess I would just like to see some example use cases for the
> communication points of the app.

No use cases yet, as far as I know.  I'm busy these days with a
different project, so I don't expect anything to be done with OpenEFM
soon, unless by another company (it IS open source).

--Jason

--
In 2010, Microsoft Windows will be a quantum processing emulation layer
for a 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for
an 8-bit operating system written for a 4-bit processor by a 2-bit
company that can't stand 1 bit of competition.