Users generally know Google Talk, Ovi Chat, etc. by their brand, not as Jabber or XMPP. Here is a proposed Account property used to indicate this: http://people.freedesktop.org/~wjt/telepathy-spec-service/spec/Account.html#org.freedesktop.Telepathy.Account.Service
And here is the branch!
I have updated the branch to make Service rw, and add a restriction flag.
12:01 wjt | i wonder whether it should instead be read-write so
that Empathy can migrate Facebook and Google Talk
accounts to have that property set appropriately
12:01 smcv | wjt: read-write but with a flag in A.I.Storage for
"actually, no"? :-)
12:02 fledermaus | I was going to say.
12:02 wjt | exactly
If we or others will use them in object paths or filenames (very likely), then they should have a restricted format; my vote would be /[_A-Za-z][_A-Za-z0-9]+/ or /[A-Za-z][-A-Za-z0-9]+/.
If there's a chance that we might use values of Service in object paths, then it may be worth having their naming convention be like "google_talk".
And updated again to have the same naming rules as protocol names, and to add lj-talk to the well-known list.
(For the record, the reason GConf was mentioned is that poking GConf via libmissioncontrol was the official way to change parameters in Mission Control 4; there was no D-Bus representation at all.)
Merged; will be in 0.19.8. Thanks!