EDIT

Applied in changeset taxeditor|967f73857a25e5d92aae0450eb1363575cf26bec.

The implementation added a new section "createSection" which contains the created information. This results in a gap between created and updated section. If this is ok I would keep it like it is otherwise we need to implement it a little bit more complicated with a check in the different sections whether the created string is already available (for versionable entities) or not (for cdmBase entities).

Actually the gap does not look nice and more important it requires more scrolling when trying to read the ID and UUID information (which I use often). So I think we should try to implement it without gab. From my understanding we only need a case distinction which fills "updated" with an empty string or with "not updatable" or something. Isn't this simply 3 lines of code? Or is there something more one has to remind?

Final issue: there is still a relatively large gap before UUID for VersionableEntities:

Can this be reduced same as for CdmBase?

Once this is done we can close the ticket.

Katja Luther wrote in #note-11:

Andreas Müller wrote in #note-9:
...

But this is the same as before. Then we have to move all elements in one section.

OK, I checked against production and it is true that there is the same gap.
So if this is really not a non-brainder to fix then we can leave it as it is. It is not really important and there are more important issues to work on.
In this case feel free to close the ticket as it is.
Only if there is a really simple/non-time consuming solution to remove the gap we should try to do it