Page History

...

• avoid redundancy or noise (no dialog. prefix, ...)
• avoid conflicts (but allow them - on purpose - for labels that are actually meant to be the same in most situations)
• be consistent (this part is hard - sometimes we prefix with module name, sometimes with app, sometimes with nothing)

Note: as the dialog names usually follow the pattern moduleName:dialogNameWithinTheModule, the <dialog-name> part of the keys mentioned bellow is in fact <module-name>.<dialog-name-within-the-module> (as the ':' character cannot be part of a key).

Field labels: – optional fallback to a key without a .label suffix to make things less verbose

...

<dialog-name>.<tab-name>.label (or .tablabel for explicitness?)

Dialog (Form) labels:

<dialog-name>.label

<dialog-name>

Action labels:

 99% of our dialogs have the same save/cancel actions. Those should be defaults. Labels should still be overridable on a dialog-per-dialog basis.

...