Schema Translation - Information Systems Reengineering, Integration and Normalization - page 122

(/(0(173DWLHQWB5HFRUGV3DWLHQW!
(/(0(173DWLHQW5HFRUGB)ROGHU!
(/(0(175HFRUGB)ROGHU0HGLFDOB5HFRUG!
(/(0(170HGLFDOB5HFRUG(037<!
$77/,673DWLHQW+.,'&'$7$5(48,5('!
$77/,673DWLHQW3DWLHQWB1DPH&'$7$5(48,5('!
$77/,673DWLHQW&RXQWU\B&RGH&'$7$5(48,5('!
$77/,675HFRUGB)ROGHU)ROGHUB1R&'$7$5(48,5('!
$77/,675HFRUGB)ROGHU/RFDWLRQ&'$7$5(48,5('!
$77/,675HFRUGB)ROGHU+.,'&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG0HGLFDOB5HFB1R&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG&UHDWHB'DWH&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG6XEB7\SH&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG)ROGHUB1R&'$7$5(48,5('!
Step 2.2—Mapping Weak Entity into Content Model
It is not applicable in this step.
Step 2.3—Mapping Participation into Content Model
The relationship between the entities Patient and the Record Folder is total partici-
pation. The relationship between the entities Record Folder and the Medical Record
is also in total participation. Therefore, the content model of the XML schema is
translated as shown below. Notice that all foreign keys in relational schema will not
be mapped into XML DTD because they will be represented in containment or ID
and IDREF.
Listing 2 Translated XML Schema for relations Patient, Record_Folder, and
Medical_Record:
(/(0(173DWLHQW5HFRUGB)ROGHU!
(/(0(175HFRUGB)ROGHU0HGLFDOB5HFRUG!
(/(0(170HGLFDOB5HFRUG(037<!
$77/,673DWLHQW+.,'&'$7$5(48,5('!
$77/,673DWLHQW3DWLHQWB1DPH&'$7$5(48,5('!
$77/,673DWLHQW&RXQWU\B&RGH&'$7$5(48,5('!
$77/,675HFRUGB)ROGHU)ROGHUB1R&'$7$5(48,5('!
$77/,675HFRUGB)ROGHU/RFDWLRQ&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG0HGLFDOB5HFB1R&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG&UHDWHB'DWH&'$7$5(48,5('!
$77/,670HGLFDOB5HFRUG6XEB7\SH&'$7$5(48,5('!
Step 2.4—Mapping Cardinality into Content Model
The relationship between entities Borrower and entity Record_Folder is in many-
to-many cardinality. It is because a borrower can borrow many record folders and
a record folder can be borrowed by many borrowers. In this many-to-many cardi-