RE: ReviewFilingRequestType

["Baughman, Philip" <Philip.Baughman@tylertech.com>]

Enrique is correct – it was on the agenda for May 2018 but we ran out of time so punted until June 2018.  I was not on the June call but the minutes suggest you may have skipped it, perhaps since I was not present.  Tuesday sounds good.

 

Related materials attached.

 

 

 

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

 

 

From: legalxml-courtfiling@lists.oasis-open.org [mailto:legalxml-courtfiling@lists.oasis-open.org] On Behalf Of James E Cabral
Sent: Thursday, July 05, 2018 4:00 PM
To: Othon, Enrique <Enrique.Othon@tylertech.com>; legalxml-courtfiling@lists.oasis-open.org
Subject: [legalxml-courtfiling] RE: ReviewFilingRequestType

 

Enrique,

 

I haven’t heard anything about this recently but I’ll add it to the agenda for our meeting Tuesday.

 

__
Jim Cabral
502 509-4532

 

---

From: legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org> on behalf of Othon, Enrique <Enrique.Othon@tylertech.com>
Sent: Thursday, July 5, 2018 4:05:08 PM
To: legalxml-courtfiling@lists.oasis-open.org
Subject: [legalxml-courtfiling] ReviewFilingRequestType

 

Hi Jim,

 

I know we brought it up maybe two calls back but are there any plans to change the cardinality on FilingMessage to unbounded in the wrapper?

This is so we can send in multiple filings at once.

 

<xs:complexType name="ReviewFilingRequestType">

       <xs:sequence>

              <xs:element ref="filing:FilingMessage" minOccurs="1" maxOccurs="1"/>

              <xs:element ref="payment:PaymentMessage" minOccurs="0" maxOccurs="1"/>

       </xs:sequence>

</xs:complexType>

--- Begin Message ---

• From: "Baughman, Philip" <Philip.Baughman@tylertech.com>
• To: "legalxml-courtfiling (legalxml-courtfiling@lists.oasis-open.org)" <legalxml-courtfiling@lists.oasis-open.org>
• Date: Mon, 7 May 2018 18:45:44 +0000

TC Members,

 

In a past TC meeting we (Tyler) inquired as to the proper way to represent our “multiple filings in an envelope” concept within ECF 5.  The response given was that the FilingMessage could be repeated as needed.  We checked it at the time and found this to be correct and agreed that this was a suitable method.  However, the cardinality apparently changed.

 

Based upon wd30 we see that the ReviewFiling and ServeFiling operations are set to maxOccurs=1

 

wrappers.xsd:

 

 

 

The above apparently changed between wd22 and wd23.

 

Also, we notice similar limitations to related operations (not changed since wd22 but would be problematic for us):

 

feesrequest.xsd: (GetFeesCalculation)

 

 

 

wrappers.xsd

 

 

 

 

 

 

Finally, for completeness: while docket.xsd has the RecordDocketing at maxOccurs = 1, this is not a problem as wrappers.xsd has RecordDocketingMessage unbounded so no change requested on this one.

 

docket.xsd: (RecordDocketing)

 

 

 

 

 

 

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

P: 972.713.3770 ext: 113406

www.tylertech.com

 

 

 

 

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

P: 972.713.3770 ext: 113406

www.tylertech.com

 

--- End Message ---

Attachment: ECF TC Minutes 050818.docx
Description: ECF TC Minutes 050818.docx