Content deleted Content added
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/ |
I reworded the sentence into what (I believe) is a more articulate explanation. My changes may not be semantically similar to the original intent. Please correct or revise as appropriate.. |
||
Line 7:
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>
* An enterprise may have numerous XML documents with similar data, but dispersed in different XML formats. Conglomerating this data into a singular, standardized XML database structure will avoid compatability issues
* Data may need to be exposed or ingested as XML, so using another format such as relational forces double-modeling of the data
* XML is very well suited to parse data, deeply nested data and mixed content (such as text with embedded markup tags)
| |||