Each configuration schema has its own set of metadata, in addition to the metadata associated with each configuration option. There are three kinds of schema metadata: Common, backend-specific, and custom metadata. Common metadata is comprised of pre-defined keys not specific to a backend, and do not have a common prefix. Backend-specific metadata is comprised of pre-defined keys with a common prefix: the name property of the backend. Custom metadata follows the convention of message headers [1] and desktop file keys [2], in that they MUST begin with the prefix X-.
Here is the list of common metadata keys:
Here is the list of backend-specific metadata keys:
All of this metadata is stored in the group DEFAULT. Here is an example of what that section might look like:
[DEFAULT]
single_instance = false
GConf.base_path = /non/standard-prefix
[1] | RFC 822, Section 4.7.5 |
[2] | Desktop Entry Specification: Extending the format |