Re: The real world doesn't have an "other xyz", neithershould

This means that in the model for the resource (something easier to express in OWL than in XSD unless you use annotations), a specific provision needs to be bound to the property (and possibly to the type of the subject) to indicate whether the list in question is closed (only a curator to introduce new terms), privileged (certain people can add new terms that have the given relationship), or open (anyone can add new terms, with the system itself assigning keys and approving or disapproving new entries (etc.)). This means that the rendering mechanism for the user interfaces (if dynamically generated) would be responsible for adding an "Other" field and exposing a means to put together a minimally sufficient entry for that field. In the simplest case, this may be a label, but it could in fact be a fairly exhaustive form in its own right.

Thus, "Other" should not be a part of any enumerated set per se, but the "Other" mechanism should provide the means to pass the constructor information to the curator or curation systems.