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

Masaaki Tsubaki

dblp:95/100 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
0since 2021 · last 1979
—ORCID · none

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

Databases, data management, data science and information retrieval · 3 · 2 first-author

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 system architecture and tuning · 54% Data models and query languages · 46%

Topics — the 2 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Database system architecture and tuning
data independence
0.011975
Multi-Level Data Model in DPLS - Database, Dynamic Program Control & Open-Ended Pol Support · VLDB 1975
Data models and query languages
relational model
0.011977
Self-Descriptive Relational Data Base · VLDB 1977
YearPublicationVenuePosition
1979 Distributed Multi-Database Environment with a Supervisory Data Dictionary Database
Masaaki Tsubaki, Ryosuke Hotaka
ER1
1977 Self-Descriptive Relational Data Base
Ryosuke Hotaka, Masaaki Tsubaki
VLDB2
1975 Multi-Level Data Model in DPLS - Database, Dynamic Program Control & Open-Ended Pol Support
abstract
A multi-level or three-level data model is introduced in DPLS -- Database, Dynamic Program Control and Open-Ended POL Support. The first ievel is logically the highest "Information Structure Model" where "Entity, Attribute and Value" are the bases for formalizing information. A logical database is composed of as many logical subfiles as the number of defined entity types. The second level is the "Data Structure Model" where the logical subfiles are broken down into physical subfiles in consideration of unused space, redundancy, variable length data, access efficiency, security, integrity, maintenance, etc. A physical subfile is a collection of stored records with the simplest rectangular form. The third level is the "Storage Structure Model" where physical subfiles are given the required number of pages in the data sets. These clearly separated three-level data representations produce a high degree of data independence and storage device independence, which support system designers with orthogonal system decomposition.
Masaaki Tsubaki
VLDB1