From: Simon McVittie <simon.mcvittie@collabora.co.uk>
Date: Tue, 17 May 2011 16:05:39 +0000 (+0100)
Subject: Formally define a unique connection name and a well-known bus name
X-Git-Tag: dbus-1.5.10~55^2~7
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fc87e251bc717b4fb58c15b77a5bbecfa94f9ad6;p=thirdparty%2Fdbus.git

Formally define a unique connection name and a well-known bus name
---

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 8207810e7..18caac180 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -1214,16 +1214,17 @@
         <title>Bus names</title>
         <para>
           Connections have one or more bus names associated with them.
-          A connection has exactly one bus name that is a unique connection
-          name. The unique connection name remains with the connection for
-          its entire lifetime.
+          A connection has exactly one bus name that is a <firstterm>unique
+            connection name</firstterm>. The unique connection name remains
+          with the connection for its entire lifetime.
           A bus name is of type <literal>STRING</literal>,
           meaning that it must be valid UTF-8. However, there are also
           some additional restrictions that apply to bus names 
           specifically:
           <itemizedlist>
             <listitem><para>Bus names that start with a colon (':')
-                character are unique connection names.
+                character are unique connection names. Other bus names
+                are called <firstterm>well-known bus names</firstterm>.
                 </para>
             </listitem>
             <listitem><para>Bus names are composed of 1 or more elements separated by