Revision as of 09:12, 9 January 2025 edit CombinatoriallyPlastic (talk \| contribs) 61 edits 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.. ← Previous edit		Revision as of 09:27, 9 January 2025 edit undo CombinatoriallyPlastic (talk \| contribs) 61 edits m Reworded for conciseness Next edit →
Line 5: == Rationale for XML as a database format == ~~There are a number of reasons~~Reasons to ~~directly specify~~store data in XML ~~or other document formats such~~format as ~~[[JSON]]. For~~an XML ~~in particular, they~~database 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

XML database: Difference between revisions