ࡱ> `!Uce,mz\}`9HVxڍRjAfgf6 5)j xgBB-5MI¦E |E' ꅗ+V!~3im:p9l@[@ )ReQLjGS`{{3߂u;b;{yyΫ@d}{oq?XN& ∓Ճ*s\x2xu9H^靎N<]n˪bejo]f橱FT]69ON߭c4*sdlom|VE ehK;E|bMmu;u,AK,c& f0!nJLtb(C,c3ɈY(KDBTފQc(8{1'¶ϯqb9类(vmsY6N>gr|`!/"oh"Î)1|*!+=;<]/:w:N(qkI&({(1+:s.eeG[[ۛ"f9#\*QT+SW_;6V˙ՒI,xD/i+f\km!lF4x~7}QU2kټG$E÷!q:Iz`!/;=C`f(HxڝTMKQ=#hh} l )7.ԥt&!p?HЅk7..Jp2psw;Û0 桗l\I3gLy+i܄|G$?=L! gBvֳ;`Xfq"!|C(:/0Pdoѫw:m|9—~"Yϣ^}LMC"^f*u/ǿ)`UDE><ܬM1@UЉAӝ19SDKt}Np ۤjMj _ռ;rH{*PJZ"]erz2:WfB/`,7=ѤV֢W٢K$;7;dͅ v=(z    #?Picture Word.Picture.80,Microsoft Word PictureHPicture Word.Picture.80,Microsoft Word Picture SPicture Word.Picture.80,Microsoft Word PictureVPicture Word.Picture.80,Microsoft Word Picture/ 0DArialngs(0(z[ 0 DTimes New Roman(0(z[ 0  DWingdingsRoman(0(z[ 0  B .  @n?" dd@  @@``   `5   HG    () >>,,HH 5.. //**21   nryz  HH,,>>  ()    HG   ,,             _2$Uce,mz\$2$"oh"Î)UE  2 Association RelationshipORDB was introduced to improve RDB performance and has become popular because it improves the limitations of RDB such as lack of support for new types and composite data values Since ORDB has OO features, it encapsulates the static (including association relationship) as well as dynamic aspects of objects The association relationship represents a  connection between object instances. Basically, it is a reference from one object to another that provides access paths among objects in a system. The objects are connected through an association link. The link can have a specified cardinality: one-to-one, one-to-many, many-to-many6{7 8 # Related WorkBMost existing work has focused on methods to map RDB to an XML database for database interoperability. Some works still used DTD and some have used XML schema. The previous works include mapping referential integrity constraints from RDB to XML, semantic data modeling using XML schemas, hybrid database schema to map a subset of XML documents onto database structures, generic-transforming rules from the OOCM to XML schema, etc. The transformation of generalization and aggregation relationship from the XML Schema to ORDB has been done earlier as a first part of the projectCCF#$Proposed Transformation Methodology  %#((There are 3 parts of association relationships that will be transformed, one-to-one association, one-to-many association and many-to-many association The method that we use to implement the association relationship in Oracle is using object references (REF). Instead of connecting two tables through the values of the associated primary key and foreign key, this method allows one to directly connecting two tables through referencing attributeB I$One-to-One Relationship The example that is used in this section is the relationship between lecturer and office For one-to-one association relationship, it is important to determine the participation of the objects to decide location of the foreign keys in relational systemY K%One-to-One Relationship (2)The Transformation steps: 1. From the XML Schema, element with partial participation will be recognized by statement minOccurs = 0 maxOccurs = 1 . First, create an object for the one with partial participation (office) with its attributesBmd8 [  dM&One-to-One Relationship (3) .N'One-to-One Relationship (4) .O(One-to-One Relationship (5) .T)One-to-Many Relationship WThe example that is used in this section is the relationship between customer and orderXX X W+One-to-Many Relationship (2) The Transformation steps: 1. An element with a complex type in XML Schema, which does not have reference inside it, is transformed by creating an object in ORDB with all the attributes6md [,One-to-Many Relationship (3)  ]-One-to-Many Relationship (4) .^.One-to-Many Relationship (5)  a/One-to-Many Relationship (6) .X*Many-to-Many Relationship GThe example that is used is the relationship between student and courseHHc0Many-to-Many Relationship (2)  ((DThe Transformation steps: 1. All elements name that has minOccurs =  1 max Occurs =  unbounded need to be created as object in ORDB and write all its attributes6md.8  a e1Many-to-Many Relationship (3)  (( g2Many-to-Many Relationship (4) (( .i3Many-to-Many Relationship (5) (( .  Conclusion and Future WorkNIn this paper, we have investigated the transformation from XML schema to the ORDB by using Oracle 9i, emphasis the transformation of association relationship This transformation is important because people tends to eliminate the object-oriented conceptual features when they transform XML schema to the database. Our future work is being planned to investigate more transformation from XML schema to ORDB for other XML Schema features that has not been discussed in this paper. Further research should be done to create a query from XML schema to get the data from the Oracle 9i databasesd;d  O /$ <=AGJLPQRUY Z!\"_#`$b%d&f'h(j)l*n,p- ` 3fff` 3R|:33` ff` ffmo` #fT=` WXcmwnI` v^Xf̙` 3f` ff~bWf3>?" dd@,?lKd@    @ `  n?" dd@   @@``PR    @ ` `0p>>   Pv (  bT  ^  " ^  c BWC DEFy2@ IB *CN, me;>VvK W !vVJ5ka2IBIBBD@`" ^  c B>CBDEF@ >BB>B>B @`" >  c \BC)DEdFny2@ha))qWs%Fl&N Y1bQiha48@`"   c tBCDEpFzy2@ Xv02PzNPFW p(E;%N:<@`" 2  T?d?" '6 2  T?yd?",\2   T?d?"     <VvK W !vVJ5ka2IBIBBD@`" ^  c B>CBDEF@ >BB>B>B @`" >  c \BC)DEdFny2@ha))qWs%Fl&N Y1bQiha48@`"   c tBCDEpFzy2@ Xv02PzNPFW p(E;%N:<@`" 2  T?d?" '6 2  T?yd?",\2   T?d?"     <b "p b T Click to edit Master title style! !   0 " `   b W#Click to edit Master subtitle style$ $   0b "` `  \*    0b "`  b ^*   0tb "` ` b ^* H  0޽h ? 3fff___PPT10i. A+D=' = @B + 0  *(    0b   b X*   0b  y b Z* d  c $ ?5E  b  0$b  w b RClick to edit Master text styles Second level Third level Fourth level Fifth level!     S  6f   b X*   6f  y f Z* H  0xl>L ? 3380___PPT10.6K~,K0  (  x  c $ b P b x  c $b  P b   <]+D=' = @B + -K0 p\<(  \~ \ s *\(f  `}  f ~ \ s *Kf Rfc f H \ 0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +A K0 @8(  ~  s *@af  `}  f ~  s *Ćf Rfc f F P  8 r  S A ??"?P ZB  s *D(p(ZB  s *D H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0  (  ~  s *f  `}  f ~  s *Df fc f ^  6H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0 <(  ~  s *f  `}  f ~  s *lf  ` f H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +  K0 p<(  ~  s *f  `}  f ~  s *f ` ` f H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0 <(  ~  s *0f  `}  f ~  s *f   ` f H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0 y0 (  ~  s *f  `}  f ~  s *f  ` f ^  6[8 S  Sx  c &A ??"?!S ZB  s *DP@@  <\f"`P 0  5HAS   <f"`P@ 31    <|f"`p` 31 H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0  P (  ~  s *0Jf  `}  f   s *  ` f "xdJ   6b"`` Pp 8& <complexType> <sequence> <element ref= office minOccurs= 0 maxOccurs=  1 /> <element ref= lecture minOccurs= 0 maxOccurs= unbounded /> </sequence> &  b $    H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +! K0  p(  ~  s *   `}     s *  `  "xd^  6  6|&"` T& </element> <element name =  office > <attribute name =  officeid type =  string use =  required /> </element>& 0 r r;1   6)"`0   FCREATE OR REPLACE TYPE Office_T AS OBJECT (office_id VARCHAR2(10));G G, H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +1 K0 0( (  ~  s *t1  `}     s *7  `  "xd^  60  0A v 2. Create another object for the one with total participation, lecture, with the attributes and a REF that refers to office typemdxd$  6E"`0P0  H<element name =  lecture > & <attribute name =  lectureid type =  string use =  required /> <attribute name =  lectureName type =  string use =  optional />&  ,0 9 (   6`3b"` p (CREATE OR REPLACE TYPE Lecture_T AS OBJECT (lecture_id VARCHAR2 (10), lecture_name VARCHAR2 (50), lecture_office REF office_T) b   H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0 C(  ~  s *@U  `}     s *[  `  "xd^  6  0d  v F3. Lastly, we create one table for  Lecture and another one for  Office . Each table has its id as well as the constraints|md|xd  6,l"`pp aCREATE TABLE Office OF Office_T (office_id NOT NULL, PRIMARY KEY (office_id)); CREATE TABLE Lecture OF Lecture_T (lecture_id NOT NULL, PRIMARY KEY (lecture_id)); xt     H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + K0 y (  ~  s *ts  `}   ~  s *0v 0 `  ^  6[8 S  Cx  c &A  ??"?!S  ZB  s *DP@@  <x"`P 0  5HAS    <H|"`P@ 31    <D"`p` 3* H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + !K0  T(  ~  s *P  `}     s *$R  `  "xd   6ԡ"`    <xs:element name =  customer type =  customerType / > & <xs:complexType name =  customerType > & </xs:complexType>u ub    H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +y  "K0 xp0 (   ~   s *(  `}   ^   600   6\"``  <<xs:complexType name =  customerType > <xs:attribute name =  customerName type= xs:string /> <xs:attribute name =  shippingAddress type= xs:string /> <xs:attribute name =  shippingCity type= xs:string /> <xs:attribute name =  shippingState type= xs:string /> <xs:attribute name =  shippingPostalCode type= xs:integer /> </xs:complexType>& [ [L                ,   6"`  CREATE OR REPLACE TYPE Customer_T AS OBJECT (customer_id VARCHAR2 (10), customer_name VARCHAR2 (50), shipping_address VARCHAR2 (100), shipping_city VARCHAR2 (20), shipping_state VARCHAR2 (20), shipping_postalcode NUMBER)      H   0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +7 #K0 6.P(  ~  s *  `}     s *t  `  "xd^  6  0  v P2. For another element in the complex type that has reference to another element, create another object and write all the attributes. The minOccurs =  1 and maxOccurs =  unbounded in XML will be shown by using REF in Oracle(md ,  ;xdN  6P"` P@ (& <xs:sequence> <xs:element name =  order type=  orderType minOccurs=  1 max Occurs =  unbounded / > & <xs:complexType name =  orderType > &  xt    & H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + $K0 pP(  ~  s *  `}   ^  600  6("`pp 8& <xs:complexType name =  orderType > <xs:attribute name = orderID type= xs:integer /> <xs:attribute name =  orderDate type=  xs:date /> </xs:complexType>         6,"` ` ~CREATE OR REPLACE TYPE Order_T AS OBJECT (order_id VARCHAR2(10), order_date DATE, order_customer REF Customer_T) xb   H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + %K0 $(  $~ $ s *  `}    $ s *t  `  "xd^ $ 6  $ 0\  v Y3. Lastly, create a table for each type. Each table has its id as well as the constraintsZmdZxd $ 6<^b"`@ bCREATE TABLE Customer OF Customer_T (customer_id NOT NULL, PRIMARY KEY (customer_id)); CREATE TABLE Order OF Order_T (order_id NOTNULL, PRIMARY KEY (order_id)); t   H $ 0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +  K0   (  ~  s *x%  `}   ~  s *L& 0 `  ^  6b8 C  Cx  c &A ??"?C ZB  s *DO00  <4)"`0 P  < ENROLLS_IN      <l-"`O? 3*    <0"`o_ 3* H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +c &K0 bZ,(  ,~ , s * <xs:sequence> <xs:element name =  students minOccurs = 1 maxOccurs = unbounded > <xs:complexType> & <xs:element name =  course minOccurs = 1 maxOccurs =  unbounded > <xs:complexType> &          H , 0޽h ? 3f3f___PPT10i.K`>]+D=' = @B +  'K0 4D(  4~ 4 s *$_  `}   ^ 4 600 4 6_"``  F<xs:element name =  student >& <xs:attribute name = refCourseID type=  xs:string />& <xs:attribute name =  studentid type =  xs:string />& & <xs:element name =  course >& <xs:attribute name = refstudentID type=  xs:string />& <xs:attribute name =  courseid type =  xs:string />& & $ $               4 6r"`  CREATE OR REPLACE TYPE Student_T AS Object (student_id VARCHAR2 (10), student_name VARCHAR2(30)) CREATE OR REPLACE TYPE Course_T AS Object (course_id VARCHAR2(10), course_name VARCHAR2(30))        Q ]Q X    H     Q ]Q X    H     Q ]Q X    HH 4 0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + (K0 <!(  <~ < s *  `}    < s *H  `  "xd < 0X < ` T2. In the XML Schema, each element will be linked to another element by using the attribute name that refers to another element ID. For those elements create table for each of them in ORDB and add the constraints for the attributesmd xd* < 6t{b"`  & <xs:attribute name = refCourseID type=  xs:string />& & <xs:attribute name = refstudentID type=  xs:string />& 0w  wt       < 6"`4 `t eCREATE TABLE Student OF Student_T (student_id NOT NULL, PRIMARY KEY(student_id)); CREATE TABLE Course OF Course_T (course_id NOT NULL, PRIMARY KEY (order_id));  t   H < 0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + )K0 De(  D~ D s *h  `}    D s *Ȱ  `  "xd^ D 6b D 0  v 3. Create another table to keep the relationship between the two connected tables in ORDB. This table will have reference to the participating objectsmd xd; D 6"`@  MCREATE TABLE Enrolls_in (student REF Student_T, course REF Course_T);N xN>  H D 0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + *K0 <(  ~  s *  `}   ~  s *  `  H  0޽h ? 3f3f___PPT10i.K`>]+D=' = @B + 0 {s (  d  c $5E   g  s *) w   UORDB comes in late 90s to improve RDBMSs performance. It becomes popular because of the limitations of RDB, such as lack of support for new types and lack of support for composite data values that can prevent it from taking on enterprise-wide tasks. For the foreseeable future, however, most business data will continue to be stored in ORDBMS. Since ORDB has OO features, we will discuss briefly about object oriented conceptual model (OOCM). OOCM encapsulates the structural/static as well as behavioural/dynamic aspects of objects. The static aspects consist of the classes/objects and the relationship between them, namely association, inheritance, and aggregation. The dynamic aspect of the OOCM consists of generic methods and user-defined methods. We only discuss about the static aspects since this is the topic that is relevant with this paper. 8Vr ."0 H  0xl>L ? 3380___PPT10.6KpńL 0  \(   d   c $5E      s *D w   FMost existing work has focused on a methodology that has been designed to map a relational database to an XML database for database interoperability. The schema translation procedure is provided with an Extended Entity Relationship model mapped into XML schema (Fong, Pang and Bloor 2001). There are many works that explain about the mapping from relational databases to XML. Some of them still use DTD (Yang and Wang 2001) and some of them use XML schema (Mani and Muntz 2001). Since XML is rapidly emerging as the dominant standard for exchanging data on the WWW, the previous work already discussed about mapping referential integrity constraints from Relational Database to XML, semantic data modeling using XML schemas and enhancing structural mapping for XML and ORDB. In addition, the study about the use of new scalar and aggregate functions in SQL for constructing complex XML documents directly in the relational engine has been done Another research wrote about how a relevant subset of XML documents and their implied structure can be mapped onto database structures using hybrid database schema Another research come out with several generic-transforming rules from the OOCM to XML schema, with the emphasis on the transformations of generalization and aggregation relationships The transformation of generalization and aggregation relationship from the XML Schema to ORDB has been done earlier as a first part of the project . >H   0xl>L ? 3380___PPT10.6Kpń 0 /(  d  c $5E     s *n w   The popularity of XML is growing and XML schema is being widely used to describe data. XML has emerged and is gradually accepted as the standard for describing data and interchanging data between various systems and databases on the Internet. At the moment, XML offers the DTD as formalism for defining the syntax and structure of XML documents. Then XML Schema definition language as a substitution of DTD provides more rich facilities for defining and constraining the content of XML documents. With the wide acceptance of the OO conceptual models, more and more systems are initially modeled and being expressed with OO notation. This situation suggests the necessity to integrate the OO conceptual models and XML.H  0xl>L ? 3380___PPT10.6Kpń 0 -%(  d  c $5E     s * w   The goal of this work is to present a coherent way to transform the XML schema into ORDB using Oracle 9i features models. We use Oracle 9i as the ORDB since it has good and new features to implement ORDB so that it will be more efficient and effective. This research is different with a transformation from a conceptual model into ORDB because this research discusses about the transformation from XML schemas format into ORDB. This transformation is important so that all the data that are created using XML schema can be transformed to the databases using Oracle format and features. What we try to suggest here is to transform and map the XML schema and ORDB without eliminating the object relational features. xg s(  H  0xl>L ? 3380___PPT10.6Kpń  0 .&(  d  c $5E     s * w   The emphasis of this paper is only on the transformation of association relationship in order to help people conveniently and automatically generate Oracle database. The work presented in this paper is actually part of a larger research project on Transformation from XML Schema to Object-Relational Databases. This project consists of two stages: (i) transformation aggregation and inheritance relationship from XML Schema to Object-Relational Database, (ii) transformation association relationship from XML Schema to Object Relational Database. The research results from the first stage have been reported in (Widjaya, Taniar and Rahayu, 2002). In this paper, we focus on the second stage of the project.\<>(jJ FH  0xl>L ? 3380___PPT10.6Kpń# 0 4, (  d  c $5E      s * w    In the following, we use XML Schema and Oracles 9i to interpret the association relationship in OOCM There are 3 parts of association relationships that will be transformed below. First is one-to-one association, then one-to-many association and lastly, many-to-many association. The method that we use to implement the association relationship in Oracle is using object references (REF). Instead of connecting two tables through the values of the associated primary key and foreign key, this method allows one to directly connecting two tables through referencing attribute. Therefore, the associated attribute that connects the two tables is not holding a value of the primary key of the other connected table, but a reference of where the connected table is actually stored. V 1:  H  0xl>L ? 3380___PPT10.6Kpń$ 0 1)@(  d  c $5E     s * w   %We assume that one lecture can only have one office and one office can only have one lecture. For one-to-one association relationship, it is important for us to determine the participation of the objects to be able to decide location of the primary keys in relational system. There are two types of participation: total and partial participation. Total participation is when an existence of an object is totally dependent on the other object and the partial participation is when an existence of an object is partially dependent on the other object.8&:^ H  0xl>L ? 3380___PPT10.6Kpń% 0 `(  d  c $5E     s *8 w   zThe steps to transform the association relationship from XML Schema to ORDB: From the XML Schema, the total participation will be the element that has minOccurs = 0 maxOccurs = 1 next to it. Therefore, we need to create an object for the other entity before we create an object for lecture. An element named  Office can be transformed by creating an object named  Office_T in ORDB. Then, write all the attributes for this element based on the attribute s name in that complex type.*MMJM J  oH  0xl>L ? 3380___PPT10.6KpńV& 0 f(  d  c $5E     s *x w   P H  0xl>L ? 3380___PPT10.6Kpń' 0 H@(  d  c $5E   4  s * w   Create another object named  Lecture_T in ORDB and write all the attributes for  Lecture element based on the attribute s name in  Lecture complex type. The minOccurs = 0 and maxOccurs = 1 in XML means that element D can contain 0 or 1 data. In ORDB, it will be shown by using REF, so we create one attribute in  Lecture_T object named  Lecture_Office that refers to  Office_T .t z   H  0xl>L ? 3380___PPT10.6Kpń( 0 F>(  d  c $5E   2  s *P w   xLastly, we create one table for  Lecture and another one for  Office . Each table has its id and a primary key that refers to the id. Declared every id as a Not Null since it is required.H  0xl>L ? 3380___PPT10.6Kpń) 0 (  d  c $5E   z  s *$ w   The example that is used in this section is the relationship between customer and order. One customer can have many orders and one order belongs to only one customer. H  0xl>L ? 3380___PPT10.6Kpń&* 0 6(  d  c $5E     s *3 w   The last association type is many-to-many relationship. The example that we use below is the relationship between student and course. Student can enroll in many courses and one course can be enrolled by many students. H  0xl>L ? 3380___PPT10.6Kpń+ 0 | (  d  c $5E   p  s * > w   `For one to many association relationship, an element named C with a complex Type Ctype in XML schema (<xsd:element name =  C type=  Ctype >) can be transformed by creating an object named C_type in ORDB. Then, write all the attributes for this element based on the attribute s name in that complex type 11PQ 3nH  0xl>L ? 3380___PPT10.6KpńV, 0 @f(  d  c $5E     s *Q w   P H  0xl>L ? 3380___PPT10.6Kpń- 0 6.`(  d  c $5E   "  s *`d w   Since it is one-to-many relationship, there is another element (D) in the Ctype complex type under sequence compositor that refers to another table. Create another object named D_type in ORDB and write all the attributes for D element based on the attribute s name in D complex type. The minOccurs = 1 and maxOccurs = unbounded in XML means that element D should contain 1 or more data. In ORDB, it will be shown by using REF, so we create one attribute in Dtype object named D_C that refers to Ctype. tJbi  !H  0xl>L ? 3380___PPT10.6KpńV. 0  f(   d   c $5E      s *r w   P H   0xl>L ? 3380___PPT10.6Kpń/ 0 {s( (  (d ( c $5E   g ( s * w   Lastly, we create one table for C and another one for D. Each table has its id and a primary key that refers to the id. Declared every id as a Not Null since it is required H ( 0xl>L ? 3380___PPT10.6Kpń0 0 nf0(  0d 0 c $5E   Z 0 s * w   .There are three steps to transform many-to-many relationship from XML Schema to ORDB: In the XML Schema for many-to-many relationship, we can find the element name that has minOccurs =  1 max Occurs =  unbounded . Those elements need to be created as object in ORDB. Then, write all its attributes based on the attribute name under the element or all the elements between <xs:sequence> and </xs:sequence>. b       H 0 0xl>L ? 3380___PPT10.6KpńV1 0 8f(  8d 8 c $5E    8 s * w   P H 8 0xl>L ? 3380___PPT10.6Kpń2 0 f^@(  @d @ c $5E   R @ s * w   bIn the XML Schema, each element will be linked to another element by using the attribute name that refers to another element ID. For those 2 elements in XML Schema, we need to create table for each of them in ORDB. Then, write the type of its attributes (such as student_id) and declared it as a Not Null. Create its id as the primary key for that table.cc.  Q H @ 0xl>L ? 3380___PPT10.6KpńX3 0  Hh(  Hd H c $5E    H s * w   R H H 0xl>L ? 3380___PPT10.6Kpń  0  0L(  L^ L S 5E    L c $ w   #In this paper, we have investigated the transformation from XML schema to the ORDB by using Oracle 9i. We emphasis the transformation of association relationship to help people easily understand the basic object conceptual mapping that we proposed. This transformation is important because people always eliminate the object-oriented conceptual features when they transform XML schema to the database. Our research gives better solution in transformation XML Schema into ORDB rather than the XML features that Oracle 9i have. Oracle 9i can only convert all the data or query result in XML format but it does not deal with the type of database that is used, such as relational database or object oriented database, like we do. This transformation can be applied on any XML documents that use XML Schema. 8$d$" H L 0xl>L ? 3380___PPT10.R   0 `X(  XX X C 5E   f X S (f w  f  H X 0xl>L ? 3380___PPT10.RPb5 0 `/(  `d ` c $5E    ` s * w   The popularity of XML is growing and XML schema is being widely used to describe data. XML has emerged and is gradually accepted as the standard for describing data and interchanging data between various systems and databases on the Internet. At the moment, XML offers the DTD as formalism for defining the syntax and structure of XML documents. Then XML Schema definition language as a substitution of DTD provides more rich facilities for defining and constraining the content of XML documents. With the wide acceptance of the OO conceptual models, more and more systems are initially modeled and being expressed with OO notation. This situation suggests the necessity to integrate the OO conceptual models and XML.H ` 0xl>L ? 3380___PPT10.6KpńRx\ol[?gىS^VmF!d)-YMK4$̉;-T62 iHlBڀA˟/*Z!$*m Ccι>I4U)ܟ{|s{{O?zU 3(}a< f6S,)D*j\W4s+qͰɃ?q98\ DBt<3UԸ_qӞ<w!n"0;!Z]B QkiZܛ`\\tpGPWaAh?wDcG{AX?#m(P!#U2ՄFYt&"Bi5ҏTGk߂iz *Յݽq&.fƇ*=KO=Z$o?n/aA>QSrPIgH_m_:8dH_@Vflym__ ZRz.sX1cN<}p7&W6a'>p@=p ǁ ~O`]8 [~U>cLOŢ PeU ''fUt>*NaGxw$gS 38Ɏ< lxh!}c`W`j6.]mU 3 d򢒝`bGLuG.J+øl}ܘia¨N=3fá4^;CDvٛ ;[ڱ}}+ CB w [q +:lvx.,?A|3C:-:IIЂGbQq5zV b.nQǍ9YX䯩t㯆*0[S5nm8q0MaUn b)\'!ؿBO!m󭍺@~O *+X[|Y,oobm_G"6rrX/XHQ-@}dOPc_Kv=A*V!54t}Z/q>i?5JN7ֵиz7Vdi|@ ,ga <>aT=@1c%~BJRTzCrUt{|U3' fCΏa/taw\u [/P8|7Z|/4zH~teѫ] `ö7fsQo:Pf_H=;Ԫj ][KPrPKHԏS, 囜ġUQYFTg16佪\R[6!L]>[4T'tZ!..%\Ɔ}F*^拤k̼y33ܝy7߄gc6! gYpF$N#)̊zH̑R{͸of G!0 +_erm4Tn]XXοs6YI!v> ,BPyIW_G\EԸAM׌Z` R+V;6HHې#Tx']H2~@R@nT!9 At^:90{LJlE е>+X|i7[]7I=^ ݧ ʤQǑ ǰrl"44 򼔸1RqVu0vTÐ"o1^os)vOÄ1Ce#Ik-bj*)վTjH"|r <"#42C}@h15yաL J::,Yw|:ASyœ-1jjG;mQC DU"F^腽 UITp2HQc˜ĽL$Ttੴ_]r΄Td&k[J"In INN0$Hr$JǒP)[C<'uIٲJkȎsEX^+ʫ㒹9IfJcH/(okT mJmD wB־Ѓ};C 1P _g*d[ z=S 34HR d=F D[.N [R<$<y ^:jϞDtAY6jREp(p?4 |FRK)G,M著HvC^qG; CQG^1!S` sQ8 | ;'3{4g;Mz{uses߅w4ߝ֢RDPCZIR+sc9IQ}ָPr谨]Kn- 5&R;E0[|9O[Ex'[?T3fu)IC|8|g),΢t >ō׳nCkw+@|tbĤ|t|?<3>HpyugVr7sps\m Uo< vʼj>5׺1 8|= ̛72?\OH73¼Vw2ۘ3`v;|'N滘fż{0e~䋹+³//~`]_]J.PO啯s\ϫ$ӑIPBF:~E^Z$ Z+ "uyRa,-IMBO ᫁/͂>t:(^] U=wvzm9eg2'_b;yЄE2vWjr~_V)y n + OnyN #+/a w7CyOX}*Įw] ^7˨}, WOor})6p 'I3ly% 'u0]{. ȐNg%Ct>'(۟ڵ9X,x> ;a̐?⯾>ikڋS~ru<~E5sjgR-=^PEnZKM)xzdj*0aA77:>n4u:CT-p6Mn*W`Eɖt/  &< ,Zo7I6nxivJoyr8E)*߂ZCDskAA%j=-Pz j]qPkovfнBQ~^!pAZ){l4:-4 4NC$n[x0޷wM|jN@m>9cHПZ׹jN47 .e+hƻdyI㛰xReȅ>̉XR8.wnpFp^b. I*I g*grhI<\ϯ;W(|렍|kyf zqzYn: r˵kj:Q0\nkYr@fЮfK`YWaڌeѹ ׌cКQ1˿۷o_ Ac;kN䖔X/94+Xku~"2jЙrf<ɛ ~C}8kLML[_u/Cu0zJU&_8Z jU%ro|/#!^#I!ǡeZXRGGH|=a([|G+r_sq<kR.U:C 1rӴi{NPo_?^ vHpr[ʜvM>G:VC{Ba1n8#nQ@DBgBPОᣪ~:c67aX(8c=ca4j N% З4<7m>+X+ޘWt.x'$xn^VWp%At !} `o՞ ?>܋yNC4]W[`~6"c %}#^]̼sJi/U<(w-؋`˃&z_G6{@0|Q2][GY;S*X>;tOݹo}$fe N0Qɴ C3ύNhBEUmi9eS4C)3j|z%'/$2I(U2oTȟ+itUrTu&uB%3X+R $_IrKHrr!@#%kP<ԅHi݂<$9HʖU]Cvg,ZQ^IR5SCR}A)\}XPhGP*ҥ,+z.c9.nM7bHUȶBzU!fi*--d4NJTGrJM|(ZVޞqCLWHo?RPiA4'vʓ%s:Ij1(_IU, 7uB=8h9,i˄{ ctozD9BprN4cJ󴮗W=P6]xJj-*6}29F-DZ MnRj5.J,*5u<[ C<PPkQMH-SMl N+*G!ٺ$8d4$m,χ$<#m=⣋(@4 `x\klT>scpyXb00,0vM%UPC[W ѪRӊ6h?%H$U#D4QmRHC[؞3gfwzmUHy93gg*;'_.\O!h 3B i\a+.:؏< 0(*hY> 7>{=Aݧ6>hV&s4^6îa,8 I3D-]gZ욑uL E P@tP<*UdS"݁4 i:R is'YH EB XH!sh9kLz"c~~Gn#F| *>Q <- 5_nMNsa-&8#E΃b2րDYH@̵ g!{u;$O$нYU}XHe'3P郪>$3 4| 3]/Ȇlz#uև!QL/#Hc& U -CZi%5jp=\# 7\}cSO8\pCP^7| x8(>Gcqk׀;E *=)y+tR^I3 -ѵ%# Onn⇸;^-{p~= _Oe`'/lX+- _l?xPUtsSy]}xlgyO;Мa~7=i>뒉&PϔbH4~T@O,=OnӖkӰ-|Ӱ6[T'|^`,ڳkc1WsUrr6{./9,<#S-O3J/rrGN|.fWLxy_Oߞ~Cloz<'Ka'Yf<瀰'y,,E;֒D6'?;;/e,rώ"EHEZΑ~t{#tͮm 0O>7۽sWu|\N hۜBN|,Fpg,Pú]R dg,m;^'^i!8q-6Dw̜͞'T7lhxnt3&8(0&f񝛇10$eBVĎTdn=%Qܕ H=0p/NgkQxPʙrjI(tz/'ߔJ-ߞ:WJ|kk;G1l>2KPîgZ 5YZC൜54TM)|@xkK~ yvU?N;K2~Ah}=U_+zőՇKRUj$,̾Z`7J<2+[8<$v@+wNH?/ J)1|c`XЎbwۑC`/\N;ERV <;e.Sݍk#tQuyYwZe)J},jk,%R,/Fn;f,{2`×d.f(Ryjq2Qk2˲t{Ȧs;sG}ڬLw >#j)Tnz7nR`6;!.[WHV}TTn4ސB)(/{$M푇TN@LG9 J_vb:5&TuBESX& .D'#HIT5%yJRJ" )/K]ET,v % FɊ%(\H`I!"nJPQ*byˊT%Wde^_47{>Ez=UZ[5C^O7bI!ig?P@h#?^i^੄zH_Ƥ\50.Z{#ܩst'=He92܎^v\엾!#)Qf6T@'zO|S~nGQ"͑7;団VU~%.ߍr#NH%7GginL S[g}5M5 ԛm8>9H*,!w=9| N#ZoI8 >]!dW#:n%Q;,~[Jb38<2`/b8>G=/;7tw#yNɦŭ +zP{Wܒªǡ%*"$cdr80NEp˦e,83;Zp{_}5?SⰟ?=n\xP-kh9, Y[~~)ƗpH=dkQ@kl*IKk+Ln9GT"7k:&z@֩֩Ϡ>Jj5 {TmPn/iL9u;w[nOCõ UÛ?kvooLNx]{pTνw7a,!),k4MJ0B tKEB.6K1=B~ɤ OL)4A@] " TS([\mCt%F}߫ Q婣>WHYHeҽ Av Ũ ~!i6OHԡۡv:1r6 XDfcYbYkCFD~*mjeM"i#5 mqnF i3R#HLr'9?YƿJWdM4&r*s#Gr &'l9l00P 'P G9קt*X.hű-Ћ3q l]CA_TҢ\,D^]ܧ3Q係~drtlHӸqp`1f>^i @UrVkYYւX;`Ll o)tET筀%(t~r~'k7N-nǺ#hK/L ,/qf8߁ >C*X1oCy>$d~jI]%d TG2|<6%zJ%x_D1=Rx10000000000008+@^-m}W/y/g҉e Xp>Q#'42?1@NkN_h`+2mq;ۘC\u;MmEwǣ]Ѿ(@k:TƎnΕYoyL.x ^xKWGw=]eUU|YKozn[kxj/{?~qə(}^x'pGvNw93N;?݆2U7F^!ğ^Kp|ԥ70~x܇3syԾ5bf9H@ʜadTIRiiMzМfIcxż@c\xKOoW77ڎ~2'w +~N(/V܇<k^S 5{9m,/40'Fi;YZX$@Hˇ(w^IVHp'6@wC|yZJ@q2+O?º]g/0rۻ!J] wflUITCEl'vܝR.ȟA6,(<blZ+H %q:w;(Y$;$+%iJ2$Y\N ITHikyH\I-+dۚ쀬cV")ʒ)I$K(o(/edjZ^Rt/XJ\"zlMIXzt_b" C^"䮠B$){HK-%ƗFfX5eyml/DEɑ"6?#FhƵ(Ykydr}tO3a:ՋyӼEțsojGk`v&17wzv?Sz}W8 . 'uh˞f zۈaƿai xV~ru#2y2\|nH'LBo쎥D\T0_JbܽKד_c/z哲uw{ %1m1bdc|t]bg@ʐdL+_2| vY2, *#-9Rm sG=UaL׌mS?I˶e쁝?{`IG}||4 {RA}CH2fE9Է-w}cz=rkM?j~c3?@}+1S;a6jc:.)m A.ԗ>^Qrd ?^ *u# w8`~=P\hmKr?0ar' FPziI}ӃRR8"({+o.2e&7%9B@BE KMaQlETn0Yk[? pOh+'0T hp  Slide 1Eric 1Orbit1revi175iMicrosoft PowerPointP@`5M<@3K@ i GSg  )'    """)))UUUMMMBBB999|PP3f333f3333f3ffffff3f̙3ff333f333333333f33333333f33f3ff3f3f3f3333f33̙33333f333333f3333f3ffffff3f33ff3f3f3f3fff3ffffffffff3ffff̙fff3fffff3fff333f3f3ff3ff33f̙̙3̙ff̙̙̙3f̙3f333f3333f3ffffff3f̙3f3f3f333f3333f3ffffff3f̙3f3ffffffffff!___www 4'A x(xKʦ """)))UUUMMMBBB999|PP3f3333f333ff3fffff3f3f̙f3333f3333333333f3333333f3f33ff3f3f3f3333f3333333f3̙33333f333ff3ffffff3f33f3ff3f3f3ffff3fffffffff3fffffff3f̙ffff3ff333f3ff33fff33f3ff̙3f3f3333f333ff3fffff̙̙3̙f̙̙̙3f̙3f3f3333f333ff3fffff3f3f̙3ffffffffff!___www__________<<__<<<<<<<<<<<<___________<___<_<_<<<<<<<<<__________<_<<_<<<<<<<<<<<<______________<<<_<<<<<<<<<_____________<_<<___<<<<<<<<________<__<__<<<<<<<<<<<<<_______________<<_<_<<<<<<<<<____________<_<_<_<<<<<<<<<<<<______________<_<_<<<<<<<<<__________<__<_<_<<<<<<<<<<<<_____________<__<<_<<<<<<<______________<_<_<<_<<<<<<<<__<____________<_<_<<<<<<<<<<_______________<<_<<<<_<<<<<<_<________<_<__<<_<<<<<<<<___________<____<_<_<<_<<<<<____________<<_<_<<<<<<<<<<___________<_<_<_<<<<<<<<<<____________<_<_<_<<<<<<<<<____________<_<<_<<<<<<<<<__________<<_<_<_<_<<<<<_________<___<_<<<<<<<<<<_______<_<<_<_<<<<<<<<<___________<<<__<<<<<<<________<__<<<_<<<<<<<<______<_<_<_<<<<<<<<____<_<__<_<<_<<<<<<<__<____<_<<<<<<<<<<____<<<_<<<_<<<<<<<__<_<__<<_<<<<<<<<<_<__<<<<<<<<<<<____<__<<<<<<<<<<__<<<<<<<<<<<<___<_<<<<<<<<_<<_<<<<<<<<<_<<<<<<<<<<<<<_<<<<<<<<_<<<<<<<<__<<<<<<<<_<<<<<<<__<<<<<<____<<<<<___<<<<<___<<<<___<<<<__<<__<__<<<<<<<<