190 likes | 361 Views
Contents: Overview What is XML? Mapping rules A simple class Association of low multiplicity Association of high multiplicity Hierachy Intermediate conclusion XML as a bridge - Exporting from MS-Access - Importing into FastObjects The XML reality. XML model. XML Database. XML:
E N D
Contents: • Overview • What is XML? • Mapping rules • A simple class • Association of low multiplicity • Association of high multiplicity • Hierachy • Intermediate conclusion • XML as a bridge • - Exporting from MS-Access • - Importing into FastObjects • The XML reality
XML model XML Database XML: Just an additional path in the data modelling flow chart?
Each XML document (a database?) … • is a (long) string (stored in a text file) • consists of • a header (conc. XML version and character set) • (if necessary:) a reference to a structure definition file • data (= a „mixture“ of tags and content) • Content and all tags (!) can be defined by the user. • Structure information can be generated automatically on the basis of the • XML documents. (-> first: create data and second: generate the structure)
This is the begin tag of an object Mapping of a simple class and here is the corresponding end tag An object A set of objects The corresponding document type definition (DTD) (a class definition) indicating „many; at least one“
Mapping of an association of low multiplicity Mapping multiplicity 0..*
XML Schema: just another DDL Again: mapping multiplicity 0..*
A client („Kunde“) element based on this DTD is as follows: Remark: This mapping rule differs from the corresponding one in The Book.
Who‘s gonna use these concepts? Nobody. Nowadays data is stored in network or relational databases, but isn‘t stored in XML databases/documents. So, what‘s left (for XML)?
XML as a bridge between heterogeneous databases [so-called Message-oriented middleware (MOM) architecture]
Exporting a simple relation as part of an MS-Access database
Importing an XML document into a FastObjects database (screen shot)
Conclusions: • The XML path is just another path in data modelling, but it is of no importance in industry. Native XML database systems won‘t have a commercial future. • Import/export of data will be done on an XML basis. All database systems (will) offer interfaces for that basis.
Reality The XML reality Relational Database (e.g. Access) Network Database (e.g. UDS) Object- oriented Database (e.g. POET) XML data model XML- DB XML document