KnowID: Knowledge-driven Information and Data access

Overview - EER-ARM transformations: the system - Publications and dissemination - Download - Contributors


Modern information systems require the orchestration of ontologies, conceptual data modelling techniques, and efficient data management in order to provide a way to better support informed decision-making and to ensure new requirements in organisational needs are met. A major issue to realise this, is to figure out which components to design and put together to realise the 'knowledge to data' pipeline, since each component and process has trade-offs. We introduce a new knowledge-to-data architecture, which we call KnowID. It combines both recently proposed components and adds novel transformation rules between (a logic-based representation of) EER diagrams as application ontology and the Abstract Relational Model to complete the pipeline. Compared to other ontology-based data access approaches, KnowID's key distinctive architectural features are that runtime use can avail of full SQL augmented with path queries, the closed world assumption commonly used in information systems, and avouds a costly mapping layer. Its architecture is sketched in Figure 1, below.

Figure 2 of the EKAW14 paper
Figure 1. Overview of the KnowID architecture.

EER-ARM transformations: the system

A key component of the KnowID architecture is the transformation between EER and ARM. The transformation rules have been implemented recently and a basic interface added. The system itself has a modular architecture, which straightforwardly permits extension with other components of the KnowID architecture. A few screenshots are included below.

Figure 2. Screenshot after loading an EER diagram (serialised and stored as a JSON file).

Figure 3. Screenshot of the state of the interface after transforming an EER diagram into an ARM model, with the ARM figure approximating the text-based specifications of the relations.

Figure 4. Screenshot of the complete logfile after transforming the EER diagram into an ARM model.

Figure 5. Screenshot of the state of the interface after transforming an ARM model into and EER diagram.

Figure 6. Screenshot of the complete logfile after transforming the ARM diagram into an ERD.

Publications and dissemination