Well - it depends on if you think most people will be holding a job and going to school at the same time and giving them equal primary-ness. When you ask people their occupation they would usually tell you "student with a side job" or "software engineer but i'm taking some classes" in which case they would still have a primary organization (the school in the former and the job in the latter).
I think that was the thinking behind it - does that sound alright? If not, we should definitely start a thread on the spec list to talk about it. - Cassie On Sun, Aug 31, 2008 at 1:25 AM, Ian Boston <[EMAIL PROTECTED]> wrote: > I have been updating the Db Implementation of the SPI from v.7/.8 to 0.8.1 > and I have noticed something. > > In organization like in ListEntry types, there is a Primary field. The doc > appears to say that there must be only a single Primary per set indicating > that is the primary of the set. However Person.getOrganization() will > contain both Organizations of type job and school (see > Orgnaization.getType()), and so, should probably contain upto 2 primary = > true entries. > > This doesn't cause a problem with the datamodel, but it does represent > tension in the specification or documentation. > > There are a number of other areas where the requirements for multiple types > and single primary entry generates tension. > Perhaps it needs to be stated one primary per type in a list, which > potentially is 2 or more in a single list like Person.getOrganization() ? > > > Ian >
