Object paths naming conventions?

[Sander Jansen]

On Thu, Jul 17, 2008 at 4:07 PM, Havoc Pennington <hp at pobox.com> wrote:

>
> This is not appropriate because it prevents multiple dbus-exported
> objects from living in the same process. For example, say GTK+ or
> libgnome or something implements an object /org/gtk/atk that is the
> root object for accessibility. That would be namespaced to avoid
> collision with apps.
>
> Similarly, say an app implements two specs, one is the above MPRIS
> thing and another is something else like say a session management
> spec. Hopefully both specs didn't decide to use "/"
>
> Bottom line, that spec is polluting the namespace - it's as if a
> shared library had a function called "void play()" with no namespace.
> It's broken.
>
> An app can contain multiple objects, provided by distinct code
> modules. Namespacing is required.
>

Thanks for the explanation!
Wouldn't the interface name already provide the necessary namespacing?
For example my object at path "/" provides my own
org.fifthplanet.gogglesmm api and for example the "org.bluez" api?

Sander