Data Conversion - Information Systems Reengineering, Integration and Normalization - page 167

Class Instructor

OID Inst_name SS# Inst_addr

004 A.B.Adams 415223641 White Plains

005 J.S. Fink 613557642 Brooklyn

006 A.M.Jones 452113641 Long Island

Class Section

OID SS# Stored OID Section# Lecture_hour

007 415223641 001 1 30

008 613557642 001 2 30

Class Graduate Student

OID Student# Degree_to_be

009 012888 M.Sc.

010 120008 Ph.D.

Class Student

OID Student# Student_name Sex

009 012888 Paul Chitson M

010 120008 Irene Kwan F

011 117402 John Lee M

Class Enrol

OID Stored OID Stored OID SS# Section# Year Grade

012 009 001 415223614 1 1995 A

013 010 001 613557642 2 1996 B

4.8 Data Conversion from Relational to XML Document

As the result of the schema translation in Chap. 3, we translate an EER model into
different views of XML schemas based on their selected XML view. For each trans-
lated XML schema, we can read its corresponding source relation sequentially by
embedded SQL, that is, one tuple at one time, starting a parent relation. The tuple
can then be loaded into an XML document according to the mapped XML DTD.
Then we read the corresponding child relation tuple(s), and load them into an XML
document. The procedure is to process corresponding parent and child relations in