Maybe some more contact fields
Stuart K. Bingë
omicron-list at mighty.co.za
Fri Jul 16 01:17:56 CEST 2004
On Friday, 16 July 2004 00:29, David Faure wrote:
> On Thursday 15 July 2004 22:24, Stuart K. Bingë wrote:
> > On Thursday, 15 July 2004 21:16, David Faure wrote:
> > > * Geographical information:
> > > latitude, longtitude (floating point numbers)
> > Horde can support this (well not yet, but I've added these in in the
> > past, and subsequently removed them due to lack of interest - they are
> > easy to re-add).
> Maybe because you didn't implement a nifty world map where the user can
> click to define a latitude & longitude? The editor in the KDE addressbook
> looks pretty cool :-) (note that I'm not commenting on the usefulness here
> > > * Logo (it's a picture, just like the photo used for <picture>, I'm
> > > not sure what people use it for though...)
> > >
> > > * Sound (the sound data will be stored in an additional attachment,
> > > much like the picture. I guess it can be any sound file that the sound
> > > system supports, e.g. wav, mp3, ogg...)
> > Can't support these, however.
> OK, I'll use kde-specific tags for those then... Should I use <logo> and
> <sound> or should I prefix those tags somehow, like <k-logo> <k-sound>?
> IMHO they're pretty non-ambiguous so I prefer not prefixing the tag names,
> so that another client or tool can implement support for e.g. sound without
> feeling that they're doing something kde-specific.
> OTOH maybe we should mark all non-compliant tags like x-logo x-sound
> to make clear they're extensions, like in many standards.
I like the x- idea - at some point we can then bring some of these extensions
into the format, if they're generic enough to be used between clients (as
they should be if they're using x- instead of k-, o- or h-).
I think Outlook supports the logo, but I could be wrong. Joon should be up in
like 3 hours so he can tell you then.
> > > The rest is probably not worth sharing (or quite difficult to share) :
> > >
> > > * IM address - that's a single field but it has also been extended to a
> > > much more complete list of IM addresses (for ICQ, AIM, Yahoo, etc.)
> > I can add support for this into Horde, as a plain text field. Unless this
> > is some funny URL select-box type thingy?
> We have two things. An old plain text field, which I suppose will disappear
> in KDE 4. The real thing is more complex.
> It's a list of items, each item specifies
> - a protocol (aim, gadu, icq, irc, jabber, msg, sms, yahoo ...)
> - an address
> - a context (any, work or home)
> It's possible to define multiple addresses for the same protocol, with
> identical or different contexts.
> So I guess the proper XML representation of it would be
> <address>123456</address> <!-- no idea how an aim address
> looks like :) --> <context>work</context>
Hmm. Perhaps that would be a bit much for Horde :-)
> > > * Crypto settings (allowed protocols, preferred openpgp and smime
> > > encryption keys, and whether to always sign/never sign/ask sign etc.)
> > Horde has the following fields that relate to this:
> > "PGP Public Key"
> > "S/MIME Public Certificate"
> > which are both multi-line text fields.
> Oh. I assume they are supposed to contain the full public key?
> In KDE we only store the fingerprint, gpg knows how to go from that to
> the full public key. We could of course store the full public key in there
> in theory, but I don't really want to be writing crypto code in the xml
> resource :)
I'm not sure how these things work actually, I've just seen them there. If gpg
can work with the fingerprint in Kontact then it should be the same in Horde,
if gpg is hooked up properly to handle S/MIME, etc, within Horde. Unless
there's some magic going on between Kontact/GPG? I'll need to do some
Code Fusion cc.
Office: +27 11 673 0411
Mobile: +27 83 298 9727
Email: s.binge at codefusion.co.za
Tailored email solutions; Kolab specialists.
More information about the Kolab-format