Hi Marcel, 2010/11/23 Marcel Holtmann <mar...@holtmann.org>: >> So the aa{sv} parameter/return value would be of format: >> { >> 'name' : string, >> 'group' : string, // optional, for eg. organization >> 'hidden' : integer, // boolean value: defaults to 0 >> 'numbers' : array of dict { >> 'number' : string, >> 'category' : integer >> }, >> 'emails' : array of dict { >> 'address' : string, >> 'category' : integer >> }, >> 'voip_uris' : array of dict { >> 'uri' : string, >> 'category' : integer >> }, >> } >> >> category : enum { // like existing "enum phonebook_number_type" >> HOME, MOBILE, FAX, WORK, OTHER >> } > > this feels a bit too complicated for me. I actually don't want to > over-design this feature, but it does have to be consistent with our > other key names.
I agree, how about a strict subset of the spec, like a dict of name -> number? > To be honest, the more and more I think about this, the more my > conclusion is to not support phonebook export. It is a bad idea. It is > highly complex and it is not a feature that will be used anyway. I tend to agree. However, people seem to really want to have this export(), so we need to arrive at some reasonable conclusion here. Cheers, Aki _______________________________________________ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono