The scenario is an attribute that is decided not be used anymore in an entity, but its deletion is not a good policy at that point.
The only way to "deprecate" is adding a comment in the description, which is not a safe solution because it doesn't prevent developers to keep using it.
So there could be a property in the attribute (called Deprecated) that could grey out the field and warn about its usage in SQLs and other actions.
