Hey, while it's certainly a good idea to abstract the parsing of individual properties out of the parsing routine, the right place for those functions would be properties of the property definition, not a method on the mug instance.  Even if this property only happens to ever be used for labels and not any other question types, it's still an aspect of the property and not the mug.

You could probably move `populate` to be an attribute the `appearanceControl` spec below, and then in the parsing routine, handle properties with `populate` defined.  So something like:

```
appearanceControl: {
    get: function (xmlNode) {
        return xmlNode.attr('appearance') !== 'minimal';
    }
}
```

And then in the parsing routine:

```
_.each(controlElementSpecs, function (spec, specName) {
    if (spec.get) {
        mug.controlElement[specName] = spec.get(xmlNode);
    }
}
```