Like API docs, I don't think a wiki is appropriate for this - what would be great is a tool which would allow application developers to document DBus APIs the way they document their C APIs, in the source code. You can also have the DBus calls documented through the "register" calls they make to listen on the bus, and be able to query the bus for the complete possible API, the way GIMP plug-ins work - this is what DFeet does. We could then parse all the register calls in the source code & generate HTML pages directly from the sources. I looked into this some time ago, but there doesn't appear to be an easy way to do this (yet). Perhaps David Greaves could share how he generated the Phone Control docs? I believe he did them by hand, with DFeet. Dave.