Previous | Table of contents | Next
In order to guide the overall Interoperability related activities within CEOS, a framework was proposed and developed. Five areas have been identified as critical ‘factors’ needed to move towards greater interoperability of EO data and services.
Each factor has several components and are summarized as below.
| Factor | Description |
|---|---|
| Vocabulary (Semantics) | The (narrow) semantic aspect refers to the naming and meaning of data elements. It includes developing, harmonizing, and maintaining vocabularies and schemata supporting provision, exchange, and analysis of data, and ensures that terms and data elements are understood in the same way by all communicating parties |
| Architecture | Architecture describes the organizational structure of concepts, processes, and assets, including data and workflows. It comprises of the structural aspects of models and standards that govern the collection, storage, arrangement, integration, and use of data |
| Interface (Accessibility) | Data exchange protocols, and application interfaces. These provide the means necessary to access and exchange data. |
| Quality | References are data and schemes that are used as benchmarks for (observational) data comparison or analysis. This could include instances such as geographic locations, product numbers, or official (authoritative) data and statistics. |
| Policy | Legal frameworks, policy and strategies regulating the relation between the different stakeholders. |
The factors together will cover all aspects that play a role in enabling interoperability of data and services. Design criteria for the factors are cohesion, independence, and modularity. Cohesion (internally) is accomplished by grouping them according to specific knowledge and competences required to tackle the respective issues. This ‘separation of concerns’ known from system engineering should ensure that the individual aspects are addressed in the most adequate way by experts of the respective fields without having to deal with the complexity of the entire system all the time. Independence means that specific (fundamental) aspects (e.g. data formats) should be proprietary to one factor. In this way parallel or duplicate solution development can be avoided. Modularity must ensure that all factors together build a functional ensemble in which it is clear which covers what and how they all work together.
The interoperability factors assemble certain, hopefully related, competencies that should be dwelled on whenever interoperability is desired or required in a project or process. Most CEOS activities are targeted at enhancing interoperability, they all should scrutinize their work with respect to the framework factors.