China
Africa
Explore chapters and articles related to this topic
Semantic Technologies as Enabler
Published in Sarika Jain, Understanding Semantics-Based Decision Support, 2021
In the early 1970s, relational, network, and hierarchical data models (information level) were deployed, with the relational data model the most widely used for structured data even today (fifty years on) because of its simplicity and structural clarity. Hierarchical database models are used to organize data in a tree structure. Network models are an extension of hierarchical models and provide a flexible graphical representation of objects and relationships. Relational database models declaratively store data in the form of two-dimensional tables to specify data and queries. Entity-relationship models are used to describe interrelated things of interest in pictorial form, which can then be converted to the relational model—with the drawback that there is no data-manipulation language. Enhanced entity-relationship models are used to precisely reflect the constraints and properties that are found in more complex databases. While very effective at searching record content, RDBMSs are very inflexible in terms of representing arbitrary and evolving relationships between records, because of their strict adherence to tabular structure; therefore they cannot be used for cognitive knowledge-level systems, stored procedures, and binary large objects.
Hierarchical combination design of shaded-weave database for digital jacquard fabric
Published in The Journal of The Textile Institute, 2019
The hierarchy number (N) of the hierarchical design was determined by the number of repeats (R) of the base weave and the weaving-point added value (M). R and M should have a multiplicative relationship. The multiplicative relationship is an indication of the colour mixing pattern and the uniformity of colour rendering shared by weave databases with differing weaving-point added values. The hierarchy number (N) of the weave database is the number of values of M selected and is proportional to R (M = R, R/2, R/4, …, 1). When M = R, the hierarchical weave database has the fewest weaves and is assigned as the primary-level weave database. This is the basic concept for the design and combined application of the hierarchical database, and the key parameter for calculating the number of weaves in each hierarchical database. The hierarchical weave databases with the remaining M values are assigned as secondary-level, tertiary-level, … and N-level hierarchical weave databases in ascending order according to the number of weaves. Different R for the base weave produce distinct hierarchy numbers for the hierarchical weave database and for the number of weaves within the database. A larger R value yields a higher number of M values selected, thus indicating a higher hierarchy number for the weave database, as shown in Table 1.
Developing a national database of police-reported fatal road traffic crashes for road safety research and management in India
Published in International Journal of Injury Control and Safety Promotion, 2023
Arunabha Banerjee, Abhaya Jha, Basit Farooq, Dinesh Mohan, Geetam Tiwari, Kavi Bhalla, Rahul Goel
Therefore, our goal in this study was to assess, (1), the online availability and accessibility of FIRs for developing a national crash database, and (2), the extent of information available for road safety research and evaluations. We started by reviewing the government websites that provide access to FIRs for each state and union territory in India. As a case study, we downloaded the FIRs for one state, Chhattisgarh. We developed a hierarchical database that allows recording information typically included in high-quality crash databases, and tested how much of this information could be extracted from FIRs in Chhattisgarh.
A Model-View-Controller (MVC) architecture for contextual visualisation of task-based multi-dimensional energy KPIs in a manufacturing process
Published in International Journal of Ambient Energy, 2018
Nadeem Qazi, Malachy McElholm, Liam Maguire
A software framework was constructed through a combination of data visualisation pattern and Model View Controller (MVC) design pattern to implement the proposed visualisation technique discussed in the last section. A modified version of Card, Mackinlay, Schneiderman (1999) data visualisation design pattern shown in Figure 1 was used. The raw data were first collected from sensors, followed by a data transformation phase during which all raw data were saved in data tables of a hierarchical database. It was followed by a visual mapping phase during which the process hierarchy of the manufacturing processes was mapped connecting associated process occurred in the manufacturing of the product. The parent–child relationship of the process event was established in this phase through a hierarchical batch production process as shown in Figure 3(b). This visual data structure resulted from data visualisation pattern phase facilities application user to drill down through the various levels to view relevant energy and production information associated with each layer. The visual structure was then made accessible to the user through a multi-tier application developed consisting of data view, data controller and data model components. The visual mapping structure and visual analytic business logic were placed in the model component. All the requests from the user for visual analytic were handled by model component. The Controller component dispatches incoming user requests to the appropriate data analysis logic functions in the Model. The Model component retrieves or inserts the required information from the hierarchical database and passes it to the controller, which in turn sends the response to the View component. The View component renders the information following the proposed focus and context technique discussed in the last section. The Controller component was developed using Java servlet, while Java server pages (JSP) were used to display the graphical component of the View. The graphical components were developed using HTML5 as it provides platform-independent ability, which means the same application could be run on multiple devices, that is, either on desktop or mobile.