OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

legalxml-courtfiling message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: SHA256 hash for documents

Haha, we may want to clarify that in the specification, eh Gary?  😊



Philip Baughman
Senior Software Engineering Manager, eSolutions
P: 972.713.3770 ext: 113406



From: James E Cabral <jec@mtgmc.com>
Sent: Friday, December 21, 2018 12:44 PM
To: Baughman, Philip <Philip.Baughman@tylertech.com>; legalxml-courtfiling (legalxml-courtfiling@lists.oasis-open.org) <legalxml-courtfiling@lists.oasis-open.org>
Subject: RE: SHA256 hash for documents




Itâs been a long time since we talked about hashes but my recollection is that, regardless of whether we return the final documents, we wanted the all MDEs to receive the hashes for document integrity purposes.  That is, by returning the hash of the accepted documents to the FilingReview and FilingAssembly MDEs, we provide the clerk and/or filer a way to detect a future modification of the document in the court record system.


If I understand your description of the Tyler implementation, the hash is applied in the FilingReview MDE and received by the CourtRecord MDE in docketing.  As long as it is still returned to the FilingAssembly MDE in the NotifyFilingReviewComplete message, I think weâre good.


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: Thursday, December 20, 2018 7:19:22 PM
To: legalxml-courtfiling (legalxml-courtfiling@lists.oasis-open.org)
Subject: [legalxml-courtfiling] SHA256 hash for documents


Greeting TC members.


In follow-up tasks out of our face-to-face last week, I propose a slight adjustment to the following within the ECF 5 specification.  Problem at hand: Within the Tyler implementation, the FRMDE is responsible for document stamping, therefore the CRMDE does not pass documents back to our EFM.  Hence, no need for a document hash below.




The Court Record MDE MUST invoke the NotifyDocketingComplete operation on the Filing Review MDE that invoked a RecordDocketing operation as a callback message to indicate whether the filing was accepted or rejected by the court record system.  If the Court Record MDE rejected the filing, an explanation MUST be provided.  If the Court Record MDE accepts the filing, the docketing information (e.g. date and time the document was entered into the court record, judge assigned, document identifiers,  nc:DocumentFileControlID, and next court event scheduled) MUST be provided.  The operation MAY return the docketed documents or links to the documents.  If either is returned then it MUST also include the [FIPS 180-2] SHA 256 document hash.  The Filing Review MDE responds synchronously with an cbrn:MessageStatus to acknowledge the callback message.






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

P: 972.713.3770 ext: 113406



Tyler Technologies

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]