Currently, ReadConcern is implemented as an enum. The spec explicitly defines it as an object with a single level field, however. This might be so that future fields could be added to ReadConcern in addition to level, similar to how WriteConcern has several fields.

As implemented, adding any new fields would be a breaking change to the driver's enum based implementation, but if it were implemented as a struct, doing so would not be.