If we want a unique tag choice, it’s “status” type relation, ok?
But the default text when empty is “Select status”.
Status is just the “technical type”, not the data!
If I want a “Origin” relation for an object (a person, a bottle, etc), the “Select status” is incomprehensible.
Or the author of a book (without using objects) : I need status type but I don’t want “Select status”.
Please, change that for something like “Select value” (because yes, it’s always a value!)
I don’t understand your request.
Typically in programming, if you have a list that has several options, the filed that is of that type list will either: by default have no value, or, take the first option as default value
I don’t understand how having a default value of ‘select value’ is better than having a default value of ‘select status’. Seems like splitting hair to me
Perhaps you can explain it better. Words like ‘Status is a ‘technical type’’ is hard to understand - your meaning. Cheers
You’ve read it wrong: I don’t want a default value (which has no raison d’être, an unfilled relationship is simply empty of any value).
Typically in a user interface, when the user is asked to select a value, we say “select zip code” for a list of zip codes, or “select category” for a list of categories, or “select color” for a color. Or “select a tag” in this forum when you have to choose e tag for your new post 
. In short, you get the idea.
The problem here is that for a color list, you end up with “select status”. This is bad information for the user, and should be avoided (UX level).