In the literature, ontology change management systems (OCMS) are direct implementation of the concept of “change management” stated by reference (Klein, 2004). Ontology change management combines ontol- ogy evolution and versioning features to manage ontol- ogy changes and their impacts. Since 2007, many works have combined ontology evolution and versioning into ontology change management systems (OCMS). The evolution subject has been massively studied in these works. They especially addressed the consistence issue for the application of changes on the ontology. These proposals constituted a consequent background for ontology change management but they did not take into account certain specificities of ontologies. One of them is the fact that ontologies are decen- tralized data Rajugan (2006). It means that multiple versions of the same ontology evolution are bound to exist over the Web and must be supported. It implies that ontology chronological evolution is not enough to manage ontologies. Actually, managing different paral- lel versions of a same ontology would bridge this gap. Another characteristic is that ontologies are meant to grow during their lifecycle and may become too large to be used in its original scale by potential ap- plications. Indeed, ontology development implies a dynamic and incremental process starting from the creation of a brute ontology, which has to be revised and refined (Djedidi, 2009). Refinement often leads to the improvement of the ontology level of detail corresponding to the addition of new elements to its conceptualization. Therefore the ontology size may in- crease after each refinement iteration, with no guaranty that the ontology is still manageable by applications and understandable by humans. In the literature, ontology views have been defined to bridge this ontology size issue and improve ontology reusability. Several definitions and implementations of ontology views have been studied in the Ontology View Management specific research field. However no agreement was found. Nevertheless, a view generally is a subset specification on an ontology, which allows to extract a manageable portion of the ontology capable to be used and queried by applications like the whole ontology. The resulting sub-ontology can be generated not only as a sub-graph of the ontology but also as an independent ontology, itself being a new interpreta- tion of the domain. It can be considered as a new parallel version of the actual ontology validating the decentralized quality of ontologies. From the different approaches studied in this article, can be deduced four types of view specification and implementation: query language based, subset extraction based, rule based and other views specifications based on hybrid techniques. This article aims at giving an overall state of the art on ontology views, their objectives, their different implementations and use, the corresponding advantages and lacks, and finally defining the future research directions to take in the context of Ontology Change Management.