What if you had a "Display Name" that could be changed, and have the element that is the 'natural key' like a GUID that can be seen but not changed? By default they could be the same, but if you wanted to rename the datatype or dataname (for logical association, sorting, grouping) it wouldn't impact the natural key which would only be defined once at creation
Yep, we do this with the DataSources's, the benefit of the natural key is that it handles duplicates or overlapping definitions better, where-as the guid approach needs to handle that itself; although renaming or changing attributes are detached from its id. Its something we are likely to come back to in future.