Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

John Stokes

dblp:12/2192 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1997
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 2

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
2 papers
Database theory · 38% Data models and query languages · 24% Data integration and cleaning · 19%

Topics — the 5 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed and cloud data management
federated database
0.011997
Designing the Reengineering Services for the DOK Federated Database System · ICDE 1997
Database theory
normalization
0.011997
Object Normal Forms and Dependency Constraints for Object-Oriented Schemata · ACM Trans. Database Syst. 1997
Data models and query languages
object-oriented data model
0.011997
Object Normal Forms and Dependency Constraints for Object-Oriented Schemata · ACM Trans. Database Syst. 1997
Data integration and cleaning
schema mapping
0.011997
Designing the Reengineering Services for the DOK Federated Database System · ICDE 1997
Data models and query languages › object-oriented data model
object-oriented schema
0.011997
Object Normal Forms and Dependency Constraints for Object-Oriented Schemata · ACM Trans. Database Syst. 1997

Methods — techniques the papers use, named apart from their topics

schema analysis · 0.0iterative restructuring · 0.0functional dependency extension · 0.0correlation analysis · 0.0
YearPublicationVenuePosition
1997 Designing the Reengineering Services for the DOK Federated Database System
abstract
Addresses the design of the reengineering service for the DOK (Distributed Object Kernel) federated database. This service allows the hiding of the heterogeneity of databases involved in a federation by generating object-oriented representations from their corresponding schemata. We propose a complete methodology that supports the identification and the translation of both the explicit and implicit information. The identification of object-oriented constructs is performed by classifying a relational schema into different categories of relations, namely base, dependent and composite relations. The main difficulty in designing the reengineering service relies on the distinction between the different types of relationships amongst classes. Our approach deals with this problem by analysing relations according two types of correlation: (i) the degree of correlation between the external and primary keys, and (ii) the degree of correlation between sets of tuples in the relations. Examining these correlations uncovers implicit relationships contained as well-hidden classes in a relational schema.
Zahir Tari, John Stokes
ICDE2
1997 Object Normal Forms and Dependency Constraints for Object-Oriented Schemata
abstract
We address the development of a normalization theory for object-oriented data models that have common features to support objects. We first provide an extension of functional dependencies to cope with the richer semantics of relationships between objects, called path dependency, local dependency, and global dependency constraints. Using these dependency constraints, we provide normal forms for object-oriented data models based on the notions of user interpretation (user-specified dependency constraints) and object model . In constrast to conventional data models in which a normalized object has a unique interpretation, in object-oriented data models, an object may have many multiple interpretations that form the model for that object. An object will then be in a normal form if and only if the user's interpretation is derivable from the model of the object. Our normalization process is by nature iiterative, in which objects are restructured until their models reflect the user's interpretation.
Zahir Tari, John Stokes, Stefano Spaccapietra
ACM Trans. Database Syst.2