This position paper presents a set of design principles for ontology engineering for model-driven applications. Ontologies sometimes need to be translated into less expressive languages and be used by software developers with limited ontology experience. In such scenarios, one may wish to refrain from using OWL features or design patterns that increase interpretation or software implementation complexity. I introduce practical considerations inherent in those scenarios, and discuss their modeling consequences.