Class declarations and object modeling: Correct Solution

Translate the specification below into an idiomatic Java class definition.

(In this context, "idiomatic" means following the common style and conventions of the language.)

One kind of thing that exists in our model is a Remad.
Each Remad has its own sopen, which is a list of strings. The value of sopen is specified when a Remad is created. Anyone can ask a Remad for the value of its sopen. The value of sopen for a specific Remad can never change.

Solution

public class Remad {
    private List<String> sopen;

    public Remad(List<String> sopen) {
        this.sopen = sopen;
    }

    public List<String> getSopen() {
        return sopen;
    }

    public void setSopen(List<String> sopen) {
        this.sopen = sopen;
    }
}

Things to check in your solution:

Is every public and private modifier correct?
Are the correct items static?
Are the correct items final?
Are all the variable types and method return types correct?
Are the class members in the correct order? It should be: (1) static variables, (2) instance variables, (3) constructors, (4) methods.
Do members have the correct capitalization?

Acceptable variations in the solution:

It is OK if you initialized non-static variables in the constructor instead of in the declaration. (Ask your instructor if you aren’t clear what this means.) Note that static variables must be initialized in the declaration.
It is OK if you used a slightly different but equivalent form of an expression, such as += 1 instead of ++.

Related puzzles: