Semi-structured Database Design
XML database design
From a requirements document, a database designer distills the real world constraints and designs a database schema. While the design process for structured data is well defined, the design process for semi-structured data is not as well understood. What is a “good” design for semi-structured databases that captures real world constraints, prevents data redundancy and update anomalies, and allows typical queries to execute quickly?
There was a lot of research into the design of relational databases in the 1970s, and it was found that the design of relational databases involves a trade off between the speed of execution of queries and the updating anomalies caused by maintaining redundant data when updates occur. During logical schema design normalization algorithms are used to reduce redundancy, and during physical design to improve performance some redundancy may be reintroduced, views can be created over the schema, and...
- 2.Brandin C. Information modeling with XML. In A. Chaudhri, A. Raschid, and R. Zicari (ed.). XML data management. Addison-Wesley: Boston, 2003,p. 3–17.Google Scholar
- 3.Bray T, Paoli J, Sperberg-McQueen CM. Extensible markup language (XML) 1.0. 2nd edn. 2000.Google Scholar
- 7.Nestorov S, Abiteboul S, Motwani R. Extracting schema from semistructured data. In: Proceedings of the ACM SIGMOD International Conference on Management of Data; 1995. p. 295–306.Google Scholar
- 8.Thompson HS, Beech D, Maloney M, Mendelson N, editors. XML schema part 1: structures. 2001. http://www.w3.org/TR/xmlschema-1.
- 10.Yu C, Jagadish HV. Efficient discovery of XML data redundancies. In: Proceedings of the 32nd International Conference on Very Large Data Bases; 2006. p. 103–14.Google Scholar