Content deleted Content added
m Grammar: removed the word "sometimes". My reasoning: storing XML (in the form of an "XML database") in XML format is not a "sometimes" activity (AFAIK). Thus I reworded the sentence more accurately, and concisely. |
m →Rationale for XML in databases: Grammatical (logic): For example, XML may be used in databases, however, in the context of an "XML database"; XML is itself a database format, rather than being explicitely used in databases. Just like SQL is not in itself a database. I will verify my reasoning with a citation: https://risingwave.com/blog/mastering-database-format-a-comprehensive-guide/ |
||
Line 4:
An '''XML database''' is a [[data persistence]] software system that allows data to be specified, and stored, in [[XML]] format. This data can be [[XQuery|queried]], transformed, exported and returned to a calling system. XML databases are a flavor of [[document-oriented database]]s which are in turn a category of [[NoSQL]] database.
== Rationale for XML
There are a number of reasons to directly specify data in XML or other document formats such as [[JSON]]. For XML in particular, they include:<ref name=nicola2010>{{cite web|last1=Nicola|first1=Matthias|title=5 Reasons for Storing XML in a Database|url=http://nativexmldatabase.com/2010/09/28/5-reasons-for-storing-xml-in-a-database/|website=Native XML Database|access-date=17 March 2015|date=28 September 2010}}</ref>
<ref name=feldman2013>{{cite conference|last1=Feldman|first1=Damon|title=Moving from Relational Modeling to XML and MarkLogic Data Models|url=http://www.marklogic.com/resources/slides-moving-from-relational-modeling-to-xml-and-marklogic-data-models/resource_download/presentations/|conference=MarkLogic World|conference-url=http://world.marklogic.com/|date=11 April 2013|access-date=17 March 2015}}</ref>
| |||