tree 9faf581045be955e3182b85b69dcd57aca5c6ab3
parent 57812c8902c07d9a217fc924b02c6bfeb99bf507
author Brad Bishop <bradleyb@fuzziesquirrel.com> 1462996225 -0400
committer Jeremy Kerr <jk@ozlabs.org> 1463124020 +0800

Take a stab at a proper DBUS API document.

Changed the main structure to be interface based rather than
topic based.  Each interface should have a methods, signals
properties and namespace section with a table and option free
form examples or additional overview information.  If an interface
doesn't have any properties, methods or signals those sections
can be omitted.

The namespace section outlines where objects implementing certain
interfaces are expected to be found.

There are a number of things that still need to be filled out.