Jump to content

XML database

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Gregburd (talk | contribs) at 12:18, 21 July 2009 (→Implementations). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

An XML database is a data persistence software system that allows data to be stored in XML format. This data can then be queried, exported and serialized into the desired format.

Two major classes of XML database exist:

  1. XML-enabled: these map all XML to a traditional database (such as a relational database), accepting XML as input and rendering XML as output. This term implies that the database does the conversion itself (as opposed to relying on middleware).
  2. Native XML (NXD): the internal model of such databases depends on XML and uses XML documents as the fundamental unit of storage, which are, however, not necessarily stored in the form of text files.

Rationale for XML in databases

O'Connell (2005, 9.2) gives one reason for the use of XML in databases: the increasingly common use of XML for data transport, which has meant that "data is extracted from databases and put into XML documents and vice-versa". It may prove more efficient (in terms of conversion costs) and easier to store the data in XML format .

Native XML databases

The term "native XML database" (NXD) can lead to confusion. Many NXDs do not function as standalone databases at all, and do not really store the native (text) form.

The formal definition from the XML:DB initiative states that a native XML database:[1]

  • Defines a (logical) model for an XML document — as opposed to the data in that document — and stores and retrieves documents according to that model. At a minimum, the model must include elements, attributes, PCDATA, and document order. Examples of such models include the XPath data model, the XML Infoset, and the models implied by the DOM and the events in SAX 1.0.
  • Has an XML document as its fundamental unit of (logical) storage, just as a relational database has a row in a table as its fundamental unit of (logical) storage.
  • Need not have any particular underlying physical storage model. For example, NXDs can use relational, hierarchical, or object-oriented database structures, or use a proprietary storage format (such as indexed, compressed files).

Additionally, many XML databases provide a logical model of grouping documents, called "collections". Databases can set up and manage many collections at one time. In some implementations, a hierarchy of collections can exist, much in the same way that an operating system's directory-structure works.

All XML databases now support at least one form of querying syntax. Minimally, just about all of them support XPath for performing queries against documents or collections of documents. XPath provides a simple pathing system that allows users to identify nodes that match a particular set of criteria.

In addition to XPath, many XML databases support XSLT as a method of transforming documents or query-results retrieved from the database. XSLT provides a declarative language written using an XML grammar. It aims to define a set of XPath filters that can transform documents (in part or in whole) into other formats including Plain text, XML, HTML, or PDF.

Not all XML databases support XQuery to perform querying. XQuery includes XPath as a node-selection method, but extends XPath to provide transformational capabilities. Users sometimes refer to its syntax as "FLWOR" (pronounced 'Flower') because the flow may include the following statements: 'For', 'Let', 'Where', 'Order' and 'Return'.

Some XML databases support an API called the XML:DB API (or XAPI) as a form of implementation-independent access to the XML datastore. In XML databases, XAPI resembles ODBC and JDBC as used with relational databases.

Databases known to support XML:DB API (XAPI)

The following XML databases are known to provide an implementation of the XML:DB API defined by the XML:DB Initiative.

XML Database License Support Notes
Apache XIndice Open source, free Yes XIndice Version 1.1 released 9 May 2007
BaseX Open source, free Yes Supported since version 4.2
Gemfire Enterprise Commercial Yes
DOMSafeXML Commercial Yes
eXist Open source, free Yes TransactionService (ACID Transactions) not supported
MonetDB/XQuery Open source, free Yes
myXMLDB Open source, free Yes Works on top of MySQL; seems to have been discontinued long ago.
OZONE Open source, free Yes 100% support including TransactionService (ACID). Appears inactive. Latest release Nov. 2005.
Sedna Open source, free Yes 100% support, including TransactionService (ACID).
Software AG's Tamino Commercial Partial Lacks update support, XUpdateQueryService.

Implementations

References

  1. ^ http://xmldb-org.sourceforge.net/faqs.html

External references

Retrieved from "https://en.wikipedia.org/w/index.php?title=XML_database&oldid=303323379"