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: cardinality question



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.






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)











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