A preference set is a container of various preference settings declaring
the choices, desires, course of actions, or customizations per actor, group,
or scope. A preference set captures the related properties for some
functional area.
Preference set naming guidelines
- A names must use alpha-numeric ASCII characters only and must not include spaces
- Special characters are discouraged; preference set names may be used as
keys in resource bundles for internationalization
- A name must clearly indicate usage
- A name must be in init caps with the first letter of each word in uppercase
- A name should preferably avoid a 'Preferences' suffix
- A name can be up to 64 characters long; smaller is better
- A preference set can only extend from another with the same name (or template)
- The number of preference sets per profile must be small; use property naming
effectively to further organize preferences
Below are examples in XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.