[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [legalxml-courtfiling] JXDDS Person Object
These comments and the "pseudo-code" examples were very helpful. I know the object-oriented "pseudo-code" examples were just basic illustrations. How might "party" and "person" be incorporated into them? Thanks, Rolly Chambers ----- Original Message ----- From: "Durham, Shane (LNG-CL)" <Shane.Durham@lexisnexis.com> To: "'Poindexter, Gary W'" <gpoindexter@kpmg.com>; "Durham, Shane (LNG-CL)" <Shane.Durham@lexisnexis.com>; "Court Filing List" <legalxml-courtfiling@lists.oasis-open.org> Sent: Monday, September 23, 2002 2:02 PM Subject: RE: [legalxml-courtfiling] JXDDS Person Object <snip> > > > > Example: Please bear with my psuedo-code. > > Instead of having structures like this (as we do now): > > "Case-12 (id-1)" > "Gary (id-2) ( plaintiff-of (id-1) ) " > "Shane (id-3) ( respondant-of (id-1) ) " > > We should have: > "Case 12 (id-1) (participant-list: plaintiff-(id-2) respondant-(id-3) " > "Gary (id-2) " > "Shane (id-3) " > > > In this way, with parents keeping track of their children, the actors can be > related to more than one parent. And, those actors could have different > parent-specific-relationships to each parent. > > For example: in the same XML message, an actor might have a relationship to > a case, and a different relationship to a filing. > > "Case 12 (id-1) (participant-list: plaintiff-(id-2) respondant-(id-3) " > "Gary (id-2) " > "Shane (id-3) " > "Filing 5 (id-4) (participant-list: filer-(id-3) " >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC