Page History

<dialog-name>.actions.<action-name>

 I introduced the .actions portion here to avoid confusion with fields; consistency would dictate having a .fields or .tabs portion for field and tabs labels too, but that would downplay the conciseness.

 for all dialog-related items, we could also use <dialog-id> and fallback to dialog-name, for further specializing.  Dialog ID is possibly currently not available; if it is, it's a single string concatenating module name and dialog name, which isn't ideal. It'd be sweet to be able to get back to module id (and app id) from a dialog.

Apps:

<app-id>.label

<app-id>.icon # because the icon might have to be localized

<app-id>.description # because a mouse-over title of the app might be interesting ?

<app-id> could be <module-id>.<app-name> or just app-name (same as for dialogs)

App launcher groups:

app-launcher.<app-group-name>.label # we use the app-launcher prefix, as if app-launcher was an app (which we should consider considering, I suppose)

Templates:

<module-name>.<template-name>.title # I think "title" is what we've been using in 4.x - we could use label for consistency, or simply name

<module-name>.<template-name> # same as above

<module-name>.<template-name>.desc # Useful in template selector

 <module-name>.<template-name> is essentially the component ID.

Page components:

<module-name>.<component-name>.title # see remark above

<module-name>.<component-name>

<module-name>.<component-name>.desc

 <module-name>.<component-name> is essentially the component ID.

Workbench columns:

<app-id>.<sub-app-name>.views.<view-name>.<column-name>

• actions in dialog
• actionbar in subapps
• workbench/<view>/columns in content apps: column names
• in workbench/view/columns, we also have formatterClass which should be locale-sensitive
• app (label in app launcher, tab)
• page templates
• page components