Exposing members whether as public fields or through simple getter and setters goes against the original ideas of OOoriginal ideas of OO.
If you are modelling values and not objects there might be reason to model them as values.
Puristically speaking objects are about behaviour any member variable is an implementation detail and no value is part of the behaviour. So if you wish to do puristic OO every time you want to create a setter or getter, you should ask your self questions about your design seeing that the need for getters and setters (when not talking about values as oppossed to objects) is a smell that you are not modelling what the system does (behaviour) but what it is (data). A paradigm that focuses on the separation of these concepts is DCI
