A data definition and mapping language
Communications of the ACM
Introduction to “feature analysis of generalized data base management systems”
Communications of the ACM
A relational model of data for large shared data banks
Communications of the ACM
An approach to Stored Data Definition and Translation
SIGFIDET '72 Proceedings of 1972 ACM-SIGFIDET workshop on Data description, access and control
A developmental model for data translation
SIGFIDET '72 Proceedings of 1972 ACM-SIGFIDET workshop on Data description, access and control
An approach to implementing a relational data management system
SIGFIDET '74 Proceedings of the 1974 ACM SIGFIDET (now SIGMOD) workshop on Data description, access and control
The relational data management system: A perspective
SIGFIDET '74 Proceedings of the 1974 ACM SIGFIDET (now SIGMOD) workshop on Data description, access and control
Interactive support for non-programmers: The relational and network approaches
SIGFIDET '74 Proceedings of the 1974 ACM SIGFIDET (now SIGMOD) workshop on Data description, access and control: Data models: Data-structure-set versus relational
Schema analysis for database restructuring
ACM Transactions on Database Systems (TODS)
Computer Communication Networks: Approaches, Objectives, and Performance Considerations
ACM Computing Surveys (CSUR)
Conversion technology, an assessment
ACM SIGMIS Database
Issues in distributed data base management systems: a technical overview
VLDB '78 Proceedings of the fourth international conference on Very Large Data Bases - Volume 4
| Hi-index | 0.00 |
Experience with data translation over the last two years has resulted in a definite set of requirements for the normalized representation of data when used as an intermediate form during the process. The logical requirements pertain to the ability to represent a class of data structures including networks. The implementation requirements include the specification of two physical representations termed as the Restructurer Internal Form and the Interchange Form.Recent investigations with the Normal Forms of the relational model have shown that1. they satisfy the logical requirements2. a complete normalization to the third Normal Form requires excessive dependency data and results in reducing the restructuring operation to an identity transformation.3. normalization is not conducive to localizing the restructuring operations in the translator4. the first Normal Form used as a vehicle for translation poses problems with specification of keys and in handling networks.To alleviate the difficulties of normalization, a Modified Normal Form, similar to the First Normal Form, was designed and investigated. On the basis of the accessing, manipulation and processing requirements in the current model of data translation, it is concluded that a software system must be designed to work with the relational Normal Forms and their modified versions.