more DDB spec updates

git-svn-id: https://svn.code.sf.net/p/gphoto/code/trunk/libgphoto2@9178 67ed7778-7388-44ab-90cf-0a291f65f57c

1 files changed, 6 insertions, 1 deletions

diff --git a/tests/ddb/README.ddb b/tests/ddb/README.ddb
index 3c35e390b..7a0348526 100644
--- a/tests/ddb/README.ddb
+++ b/tests/ddb/README.ddb
@@ -132,7 +132,9 @@ What would need to be done to go into production with this:
 
    One solution to the problem could be a directory structure like
 
-      /etc/libgphoto2.d/libgphoto2.ddb # the devices we ship
+      /etc/libgphoto2.d/camlib-agfa.ddb # the devices from the agfa camlib
+      /etc/libgphoto2.d/camlib-canon.ddb # the devices from the canon camlib
+      /etc/libgphoto2.d/camlib-ptp2.ddb # the devices from the ptp2 camlib
       /etc/libgphoto2.d/foo.ddb # devices the user got from somewhere
       /etc/libgphoto2.d/bar.ddb # devices the user got from somewhere
 
@@ -141,6 +143,9 @@ What would need to be done to go into production with this:
 
  * The DDB device names should be Unicode strings.
 
+ * There must be structured information on device names, e.g. the
+   vendor must be readable without parsing strings.
+
  * Store other device information in the DDB which may be of interest
    for a libgphoto2 frontend, e.g.
     - thumbnail images of the devices themselves.