Which is the ubiquitous language that determinates the need of a version property in the order entity?

[ComptonAlvaro]

I have seen in the optimistic concurrency example, that in the entities there is a property for the version. But I have the following doubt.

Which is the ubuquitous language that determinates the need of this property? It is hard to imagine how the domain experts talk about version of entity. I can imagine they talk about conditions like an order can have only 5 lines, or the total amount has to be less than X total, or the customer has to be accepted to can create orders... but I don't see how that experts will tell, we have to take care about concurrency, we need a version for entities. For me, it seems that it is more suitable for the repository, for example, that is who can check in the SaveChanges() if is the same version and if not, throw and exception that will be handle by the consumer (in the application layer).

Thanks.