Great. Thanks Jim. From: James E Cabral <
jec@mtgmc.com> Sent: Wednesday, October 17, 2018 10:40 PM To: Othon, Enrique <
Enrique.Othon@tylertech.com>;
legalxml-courtfiling@lists.oasis-open.org Subject: RE: cardinality question Enrique, I’ve started a WD38 incorporating that fixes the bad hyperlinks in PRD02 and will incorporate changes from the public review. That version will include these fixes as well. __ Jim Cabral 502 509-4532 From:
legalxml-courtfiling@lists.oasis-open.org <
legalxml-courtfiling@lists.oasis-open.org > on behalf of James E Cabral <
jec@mtgmc.com > Sent: Tuesday, October 9, 2018 10:11:42 PM To: Othon, Enrique;
legalxml-courtfiling@lists.oasis-open.org Subject: [legalxml-courtfiling] RE: cardinality question Enrique, Unfortunately, we’ll now need to hold off changes until after the public review. __ 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: Tuesday, October 9, 2018 2:10:38 PM To:
legalxml-courtfiling@lists.oasis-open.org Subject: [legalxml-courtfiling] cardinality question I know this is bad timing as we just approved public review… As I was building the code off of the latest working draft I noticed the wrapper for some of the operations still have FilingMessage with a maxOccurs=”1” I know Philip had sent an email to the group some time back in May about it. Would it be possible to change FilingMessage to unbounded for the following types below? Also NotifyFilingReviewCompleteMessage and NotifyDocketingCompleteMessage. 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