I say "should" because its omission allows the script to continue functioning in the event that a read-only property becomes read-write. Conceptually, the writability of a property should not be a consideration for .get()ing the value (get being a read operation), which is another reason to leave it off. Functionally, setting should fail in both cases, (again, the expected result), thus you will never see a set with that property listed to begin with. The only purpose it serves is then as a purely antiquated "Hungarian" notation meant to instruct the reader as to the nature of the property, which is better expressed by the error trying to set it would create, or by the documentation which already states "This is a read-only property." However, I allow for the possibility that you feel differently, as usual. =D