[Openicc] configuration namespace outline

[Kai-Uwe Behrmann]

Hello,

in preparation of modularising the Oyranos configurations and after some 
discussions with Markus Raab from Elektra, I want discuss a key name 
scheme to apply to a global namespace. This will allow applications to 
share default colour settings outside of Oyranos in a standard way and to 
share as well plug-in settings for the Oyranos library.


The idea is to comply to Elektra naming schemes and be extensible to other 
data bases too like XML files or possibly the JSON format suggested by 
Graeme.
Elektra keys are ordered like paths, and thus separated by a slash. The 
top level entry is something like "sw" for application specific things. In 
order to get colour stuff recognised, I would suggest to use a top level 
category "colour" for system wide colour management settings in Elektra. 
Elektra has even a layer above to feature a user/system distinction, but 
it shall not matter here. This is the Elektra specific part.
In Oyranos I call this the top part of a configuration path.
Top:         the top section for the Elektra data base; e.g.
              "colour"
              "sw"

The following generic part is to create paths and keys based on the 
following arrangement. Each element has to be appended:

Domain:      a hint about the standard the keys adhere to; e.g.
              "openicc.org" (not available),
              "freedesktop.org" or
              "oyranos.org" for specific things
Type:        tell about a roughly classification; e.g.
              "default" for default settings
              "colour" for a colour conversion CMM
Application: a real application or a group for standard settings; e.g.
              "profile"
              "lcms"
Option:      the actual value; e.g.
              "editing_xyz"
              "preserve_black"


This would lead to the following path + key:
a standard Rgb editing space:
   "colour/freedesktop.org/default/profile/editing_rgb"

for a plug-in or application setting:
   "sw/oyranos.org/colour/lcms/preserve_black"

The actual value is then to be associated to the key.


A detailed proposal would have to walk after a while to xdg.


kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org