XML database

Jump to navigation Jump to search

Definition

In this article, we are primarily interested in Native XML Databases, “Databases that store XML in "native" form, generally as some variant of the DOM mapped to an underlying data store. This includes the category formerly known as persistent DOM (PDOM) implementations.For data- and document-centric applications.”(R. Bourret, retrieved 17:59, 3 November 2006 (MET))

See also XQuery (the XML Query language) and Database (overview of various kinds of databases).

When do we need an XML database

Ronald Bourret (2006) summarizes the major different XML and databases scenarios:

To store and retrieve the data in data-centric documents, what kind of software you need will depend on how well structured your data is. For highly structured data, such as the white pages in a telephone book, you will need an XML-enabled database that is tuned for data storage, such as a relational or object-oriented database, and some sort of data transfer software. This may be built in to the database (in which case the database is said to be XML-enabled) or might be third-party software, such as middleware or an XML server. If your data is semi-structured, such as the yellow pages in a telephone book or health data, you have two choices. You can try to fit your data into a well-structured database, such as a relational database, or you can store it in a native XML database, which is designed to handle semi-structured data.

(R. Bourret, retrieved 17:59, 3 November 2006 (MET))

Standards

Software

Native XML databases

(just some popular free ones)

According to R. Bourret, retrieved 13:38, 24 November 2007 (MET), native XML databases differ from XML-enabled databases in three main ways:

  • Native XML databases can preserve physical structure (entity usage, CDATA sections, etc.) as well as comments, PIs, DTDs, etc.
  • Native XML databases can store XML documents without knowing their schema (DTD), assuming one even exists.
  • The only interface to the data in native XML databases is XML and related technologies (such as XQuery, XPath, the DOM) or an XML-specific API, such as the XML:DB API. XML-enabled databases, on the other hand, offer direct access to the data, such as through ODBC.

List of some XML databases:

  • eXist is a poplar and easy to use XML database and retrieval engine. Features: XQuery, XUpdate, XML:DB API, xml-rpc support, REST support, WebDav, PHP API, etc. This is the only one DKS tested sometimes in the past and it perfectly worked. Newer versions probably add lots of new features.....
  • Xindice is a native XML database. Supports XPath queries and XML:DBXUpdate. Java and has a XML-RPC API plugin. It has grown out from dbXML is a native XML database (JDK 1.3, LGPL licence). See also the Xindice Wiki at Apache for more information
  • BaseX Processing and Visualizing XML Data with a native XML Database. A Java-based XQuery processor that will create XML databases (somewhere in your home) and allow for some data visualizations with TreeMaps and Scatterplots. (April 2009)
  • Sedna is an open source XML database management system. It is a XML-native system developed from scratch in C/C++ and Scheme. Sedna is a full-featured database system that supports queries, updates, ACID transactions, security, etc. Sedna is designed to be fast, reliable and easy-to-use for production-grade applications. Apache license (free).
  • dbXML was a Native XML Database (NXD) and was developed using the Java 2 Standard Edition version 1.4. Dead project, later became Xindice and others ....
  • Oracle Berkeley DB XML. Open source, embeddable XML database with XQuery-based access to documents stored in containers and indexed based on their content. Oracle Berkeley DB XML is built on top of Oracle Berkeley DB. (broken link)

Discussion

DSchneider believes that native XML databases like eXist "will take off" in our field as soon as there are sufficient PHP APIs or maybe some XML-based authoring frameworks. For example, the eXist XML database is both a database server and a portal based on Java/Cocoon technology. This technology is not very accessible to the "bricoleur" world of education.

The advantage of an XML-database is that you can just "stick in" XML contents and then retrieve them with XQuery expressions. Native XML databases are most commonly used to store document-centric documents and that's something we may see a lot in education (e.g. descriptions of pedagogical scenarios, lesson plans, contents other than IMS Content Packaging. Adding new information structures may require writing interfaces to XQuery, but this kind of flexibility comes at a much lower price. Most of these database now support standardized XQuery Update. Lack of an updating standard was a problem that is now almost solved - 21:26, 1 November 2007 (MET)

See some discussion in the DITA article and also El-Seoud et al. (2007)

Links

  • (more needed here)
  • Yuli Vasiliev (2007), PHP Oracle Web Development: Data processing, Security, Caching, XML, Web Services, and Ajax (Paperback). ISBN-10: 1847193633. Book excepts are available at webreference.com ("XML enabled applications").
  • Elliotte Rusty Harold (2007), Native XML Databases, eXQuisite or eXcruciating?, New York PHP Users Group, Presentation slides, HTML pages - HTML 1 page

References

  • El-Seoud, Samir Abou; Hosam El-Sofany, Fayed Ghaleb, Sameh Daoud, Jihad AL Ja'am, Ahmad Hasna (2007). XML and Databases for E-Learning Applications, International Journal of Emerging Technologies in Learning (iJET), Vol 2, No 4 Abstract/PDF

Warning-noto.svg

Content of this article has been taken from EduTechWiki (en) or EduTechWiki (fr) at the date indicated in the history. DKS was the main founder and main contributor of EduTechWiki. If you cite this page you also must cite and credit EduTechWiki, according to the CC BY-NC-SA license. View the pageinfo-toolboxlink for this article.