Hi Horst, thanks for this. I will add this to the current list of proposals. I agree that the suggested 5 keys are enough for a person's record in a healthcare application considering that healthcare apps are not telephone directories.
I have 5 numbers (purely coincidential to the above) and in my workplace i have a maximum of 12 (no kidding) plus an occassional beeper number. Best regards, elpidio On Saturday 01 May 2004 03:22, Calle Hedberg wrote: > For this concrete simple example: > > 1.) reality is that people have none to many phone numbers. I, for example, > have 6 that are relevant to my person. > 2.) Such telephone numbers usually require an attribute to tell which > number to use for what purpose. > > Hence, the ideal mapping to a XML-RPC compatible data type would be a > "dictionary list" (list of key:value pairs) like (simplified for > readability) > <phone> > <location = "home"> 1234567 </location> > <location = "work"> 2345678 </location> > <location = "mobile private"> 1234567 </location> > <location = "mobile work"> 1234567 </location> > <location = "fax"> 1234567 </location> > </phone> > > A remote procedure call would then be provided to retrieve > all phone numbers belonging to an individual. > > Due to the substantial call overhead and inherent redundancy of XML-RPC, > you > would always try to anticipate further queries in your return values, hence > you would not just query for "fax number" but simply for all phone numbers > and parse the returned structure on the client side. > > Horst
