Not all field names are easily human readable.
Having a setting at the data layer would allow a user to set the field label ONCE and have the label propagate to all instances of the field on any layout.
Rule should be that if label/alias exists that it supersedes the standard label.
Manual label editing on a layout should take precedence over anything just like it is now.
Furthermore if the label could be a calculation then the label could be very flexible and programmatically responsive.
Possible extensions are:
1. Create FieldLables and FieldLabel design functions
2. Get(ActiveFieldLabel) function.
3. Field label could also be returned with the schema definitions available via ExecuteSQL()