From cd279fd3c57bf60da4436c0fdc15e33735207273 Mon Sep 17 00:00:00 2001
From: Simon McVittie <simon.mcvittie@collabora.co.uk>
Date: Tue, 17 May 2011 17:06:30 +0100
Subject: [PATCH 5/9] Describe conventional naming of errors

---
 doc/dbus-specification.xml |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 6d2b26a..20b0d48 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -1304,6 +1304,17 @@
         <para>
           Error names have the same restrictions as interface names.
         </para>
+
+        <para>
+          Error names have the same naming conventions as interface
+          names, and often contain <literal>.Error.</literal>; for instance,
+          the owner of <literal>example.com</literal> might define the
+          errors <literal>com.example.MusicPlayer.Error.FileNotFound</literal>
+          and <literal>com.example.MusicPlayer.Error.OutOfMemory</literal>.
+          The errors defined by D-Bus itself, such as
+          <literal>org.freedesktop.DBus.Error.Failed</literal>, follow a
+          similar pattern.
+        </para>
       </sect3>
     </sect2>
 
-- 
1.7.5.1