XML as Databases - Advantages and Concerns - Essay Example

XML AND DATABASES XML and Databases Affiliation Table of Contents Table of Contents 2 Introduction 3 EXTENSIBLE MARKUP LANGUAGE (XML) 3 XML Features and standards 5 Organizations use XML 5 XML as Databases: Advantages and Concerns 6 Advantages and Concerns 6 Disadvantages of XML as a Database 8 Performance of XML databases 8 Slow in Data Search 8 Difficult XML database conversion 9 XML restrictions as a database 9 XML data security 10 XML security benefits 10 Implementations of XML 11 Types of XML Databases 13 XML MODELS 15 Data-centric model 15 Document-centric model 16 Hybrid model 16 XML into SQL 17 Comparison with JASON 19 Future work 20 Conclusion 21 References 21 Introduction Without a doubt, a database is a most important element of today’s web based systems. The majority of web sites use databases to store relevant information, which are used for completing daily activities. There are many ways to develop databases that have to be used on the Internet. In this scenario, XML (eXtensible Markup Language) is a relatively more fashionable arrangement for sharing data that allows web developers to build customized sites by making use of predefined tags. In XML, developers can create a link that points to several Web sites in place of a single site (Shelly, Cashman, & Vermaat, 2005). In fact, XML is a brilliant standard for expressing semi-structured information and contents on the Internet. A large number of web developers make use of this language to develop and maintain databases on the Internet. Basically, XML was not designed to be used as a database because it lacks a large number of features that are important for the databases. However, it also contains a large number of features that are contained by well-known databases. This paper presents a detailed analysis of XML with respect to its usage as a database management system. This paper presents an overview of XML and its associated concepts. This paper also discusses advantages, disadvantages and uses of XML databases. This paper also presents a brief comparison of XML with its alternative. Finally, this paper will talk about the future work. EXTENSIBLE MARKUP LANGUAGE (XML) eXtensible Markup Language (XML) is a more stylish arrangement for sharing data that facilitates web developers to develop customized tags and utilize predefined tags. In XML, developers can establish a link which points to several web sites in place of a single site. In addition, with XML, a server is able to distribute a complete record to the customer, facilitating the client to perform main part of the processing devoid of going back to the server (Shelly, Cashman, & Vermaat, 2005, p. 682). Basically, XML allows consistent depictions of data structures in order that data can be used and processed suitably by various systems instead of case-by-case processing. However, this technique of data processing is appropriate for supply chain management systems and e-commerce applications that carry out operations across corporation borders. Additionally, the XML cannot simply diminish paperwork by automating activities, but also can connect supply chains for enhanced cooperation and knowledge transfer or data sharing as well as business associates or stakeholders (Turban, Leidner, McLean, & Wetherbe, 2005, pp. 463-464). In addition, XML oriented messages can be used from back-end stores and implemented via the portal interface and back once more. Since, a portal that makes use of the XML facilitates the corporation to correspond to its customers in an improved manner, by connecting them in a virtual demand chain, where variations in customer needs and interests are directly imitated in production plans. Thus, the XML has turned out to be the common language that all portal vendors implement, because of its capability to extremely shorten the process of systems assimilation or integration. In addition, the vendors are rapidly moving to put together the benefits and facilities accessible through XML standards. For instance, Teamsite, which is Interwoven’s content management software, currently completely incorporates XML, facilitating corporations to offer content obtainable in any layout all through the corporation. Furthermore, the Hummingbird’s Enterprise Portal Suite and Sequoia Software’s XML Portal Server (XPS) also incorporate the XML standard for communication and data sharing (Turban, Leidner, McLean, & Wetherbe, 2005, pp. 463-464). XML Features and standards XML is quickly turning out to be a standard for e-commerce content. While HTML, documents oversee the demonstration of data and information in a web browser, on the other hand, XML deals with the configuration and handling of the data engaged. Thus, XML makes it practicable to save data objects that are constantly established throughout the corporations (Hoffer, Prescott, & McFadden, 2007). The procedure of standardization is itself an enormously complicated one. If one planed a standard too soon, the standard does not regard as sufficient information and is consequently not assumed. If the standard is planned excessively late, as well a lot of people will have assumed their own methods, and the standard will be unnoticed. However, a number of instances of standards that emerge too soon or too late include OSI layers, JavaScript, and rewritable DVD. In addition, the XML includes a number of these complexities by allowing a standard to build inside the circumstance of an XML format. Furthermore, absolutely, this is not an activity which can take place itself; however Xml presents wide-ranging structure as well as sets up the enormously primary steps essential for significant communication to happen (W3C, 2007). Organizations use XML XML enables the creation of customized tags. These tags can be utilized throughout the corporations, facilitating the communication, description, corroboration, and interpretation of data among applications and between corporations. Additionally, the XML has also proved its value for linking inherited information to the web, since the XML tags are employed to illustrate data as it is configured in the inherited data layup, consequently eradicating the necessity to re-arrange it (W3C, 2007). Since, XML performs the jobs of HTML to assist it in the transmission, exchange, and handling of data, however, XML is not an alternate for HTML. In addition, all the categories of content can be organized via XML, for instance, sound files and images files. Additionally, the data that need to be transferred outside the corporation should attach to broadly defined XML framework. However, inside data should be defined mainly in XML. The fashion of using XML as a constant storage arrangement is becoming increasingly common for the configuration of data and information, as a transitional database presentation, and for semantic annotation (Hoffer, Prescott, & McFadden, 2007, pp. 399-400). XML as Databases: Advantages and Concerns Advantages and Concerns Normally, XML is called a database only if it contains a huge amount of data. So XML is similar to all other files because all the files contain some data. When XML is used as a database format it offers a wide variety of benefits. One of the most important advantages of XML is that it encompasses a self-describing capability. For instance, it can define the type names of the data along with the structure, though not the semantics. In addition, it is a portable language that can support a wide variety of platforms without causing compatible issues. It offers an excellent mechanism for the data explanation. For instance, in XML data can be displayed in graph or tree structures. Though, XML is a not a complete database nor it can be used as a complete database package, however, it encompasses a large number of features and tools that are provided by a variety of database management systems. For instance, XML provides database storage mechanisms in the form of XML documents, programming interfaces such as DOM, SAX JDOM, database structure or schemas in the forms of XML Schemas, DTDs, RELAX NG, and many more, like other database manipulation languages it also provides query languages such as XPath, XQuery, XML-QL, XQL, QUILT, and so on. On the other hand, as compared to complete database management systems it lacks a large number of significant features such as, indexes, efficient storage, perfect security, data transactions and integrity, triggers, multi-user access, queries across multiple documents, and many more (Bourret, 2003). In short, an XML document can be used as a database in an environment where there is need for small amounts of data, little performance requirements, few users on the other hand, it is unable to provide a considerable support for an environment in which there are a large number of users, the need for good performance and severe data integrity requirements. One of the most important examples of an XML database where it is suitable is .ini file. This file consists of different information related to application configuration. In this scenario, it is very simple to create a small XML language as well as invent a SAX application for translating that language as compared to writing a complete parser for comma-delimited files. Additionally, with XML files, users can handle nested entries on the other hand it is very difficult to do with comma-delimited files. It cannot be treated as a database for the reason that it is written and read linearly simply when the application initiates and ends (Bourret, 2003). Some of the well-known examples of applications where an XML file can be used a database can include: browser bookmarks, personal contact lists (to store phone numbers, names, addresses, and other information) and explanations of the media files that users steal by using Napster. On the other hand, with the passage of time there have emerged a large number of affordable and easy to use database management systems such as Microsoft Access and dBASE, that is why the majority of application developers do not prefer to use XML even in the discussed examples. In conclusion, data portability is believed to be an apparent advantage of XML, and even though it cannot be perceived as a significant advantage because of the extensive accessibility of tools and software applications for serializing databases as XML (Bourret, 2003). Disadvantages of XML as a Database On the Internet, the most important use of an XML file is to exchange and encode data. The majority of web applications make use of XML for data transfers and data export between applications. However, if an XML file is used as a database then it can consume to some extent more memory than the XML text files. Though, there is not an appropriate way to design and develop an XML database however they can be developed and implemented by connecting various XML files to each other or forming a tree construction from each XML page. In reality, there are a large number of disadvantages of using XML as a database format. Some of the disadvantages of XML databases are outlined as below (Wilhite, 2015): Performance of XML databases The documents created using XML contain huge amounts of words. In addition, they will work only if all open and close markup tags are present in the document. There is need for applying data compression techniques on an XML database to make it perform faster. Moreover, there is need for a lot of information to maintain them as compared to data stored in cells for the reason that XML databases contain a huge volume of text. Slow in Data Search The most important advantage of a database is that it provides to its users an easy way of data search. On the other hand, XML lack this important feature of a database. In fact, it offers much slower searching and querying support than other databases. Actually, in order to perform the search operation on an XML database searches must examine the tags and text based information, which takes much more time than a search of data in a relational database. In view of the fact that XML databases are built from XML files by means of document trees and graphs, as a result, a search query must have to undergo all nodes and branches of the tree in order to provide the requested results. So it takes a lot of time to receive the query results. Difficult XML database conversion In view of the fact that XML is used to develop files or documents instead of databases and it is not a well-known or standard tool for developing a database hence it cause a significant problems when there is need for connecting it with other formats. In addition, due to lack of its acceptance as a database resulted in smaller number of database tools than other database applications. Additionally, XML is based on a hierarchical database structure despite the fact that the majority of databases use a relational database schema. As a result, XML databases can require restructuring before converting it into other formats. XML restrictions as a database The basic objective of XML is to allow for the free-form documents development and XML databases developed from those documents are not purposefully developed to store long-term data. In view of the fact that XML can be established with definite rules or schema but it does provide a support for implementation of definite rules. An XML database does not have a referential integrity constraint to make sure that data is stored in the same location where it was kept first for the storage, due to which data references can be misplaced. In addition, an XML document will not prompt error messages in response to a broken database reference if a document tree within the database is changed. XML data security An XML database cannot be tested for errors partly without loading the complete database because it requires the complete data set to be loaded into the database before it can be observed. Additionally, as compared to other database management systems, XML does not provide role-based security. In addition, like other databases it cannot be developed in a way to allow others to add, change or delete data. Moreover, XML databases allow us to set security authorizations through containers, and if a user is permitted to access a container, he can view all information kept by the container. Though, this security mechanism can be constricted by establishing more subcontainers as well as restraining authorizations to subcontainers, however it will increase the amount of effort required to establish, implement and maintain access control (Wilhite, 2015). XML security benefits Implementation of XML based security provides main advantage regarding the enhanced management of user data and business information security. This security based structure provides us extensive confidence regarding the online data and financial transfers. In this way we can have better and enhanced working and management over the web based structure. By means of an ever-increasing amount of people with businesses depending on the web and Internet based environment to transfer secret and sensitive data and information, security has turned out to be a hot issue. Implementation of XML based security has two main and significant advantages (Verma, 2004): Trouble free management: implementation of XML based security environment provides a huge advantage regarding the enhanced management of business. This security based structure provides us confidence regarding the business data handling and management over the web. Portable trust: XML based security structure offers a portable trust of data safety. It means that we have same standard of security in all areas of the business and other platform. This security structure provides similar outcomes on all type of platforms and security scenarios. Implementations of XML Some of the important implementations of XML is seen in the following areas (Song, 2009): No XML Security Areas Explanation 1 Banking Web based money transfer Online billing system Web based Stock management system 2 Manufacturing On the entire areas through logistics chain incorporation of suppliers as well as customers in the course of WSI Intranet systems 3 Retail Intranet systems On entire sectors in the course of logistics chain incorporation of suppliers and clientele by means of WSI Client Ecommerce corporations offering WS interfaces 4 Health Care Web based health data preservation Hospital client and business data security Intranet systems Patient Data systems integration 5 Government Governmental Intranet systems Online Tax management system Government and administration web structure 6 Electric/Water/Gas Network Companies Online bills payment Business information preservation Business Network management Remote meter reading Types of XML Databases The true native storage technique contains the data on disk that is post analyzed, while it allows the data to be accumulated in the disk separately and which is not like a stream, but it is interlinked. In addition, the true native storage gives the benefits of CLOB and BLOB, however, it furthermore provides solution to the other performance problems which are linked with BLOB, where the document is not virtualized in the form of a single connecting byte range. On the other hand, all the documents are virtualized in form of single joining byte range but the distinct joints can be displaced within this range, where there is a very low effect on other indexing and nodes. Consequently, the true native XML catalogues provide benefits as follows (IBM, 2005): The new updates create its effects only at the nodes, which are altered and the nodes’ instant antecedent, siblings plus children. The user can approach any part of the document directly, rather than a mandatory read of the overall document The process of Indexing is centered on groups instead of indexing on byte that counterbalance the document byte stream, consequently, index items should be altered merely for displaced nodes, rather than for all nodes succeeding an in-order traversal. As the storage’s basic component is a node, so the concurrency management is promising for the sub-document parts (IBM, 2005). The inherent XML data storage is provided by SQL Server by means of the xml data category. It is in the hand of the user to choose any XSD schemas among a number of XML schemas, for linking this with the column or variable of xml category. These xml schemas groups accumulate non-native XML schemas and is used for the following purposes: Authenticating the XML illustrations Inputting the XML data like it is gathered in record It is noteworthy that the groups of xml schemas are similar to a number of tables in the records. The user can develop, change and delete them. The groups of schemas itemized on the option of Create Xml Schema Collection account (Transact-SQL) are spontaneously entered into the anew generated XML schema group item. The users can input extra schemas or their parts within an already present group items in the records by inputting the Alter Xml Schema Collection (Transact-SQL) account (Microsoft Corporation, 2014; IBM, 2005). As discussed in this regard, there is a distinction made as typed and un-typed XML. Among these, the Typed XML are those xml that are amassed in variable or column and the schema is linked with, due to the fact that the schema delivers the essential information about data type for the insistence data. Such type of information is utilized by SQL Server for maximizing the data storage. The device for processing any request also employed the schema for type examination and to enhance requests as well as data amendment. Furthermore, SQL Server employs the related XML schema group for the typed xml, in order to authenticate the XML case. The catalogue or record permits the xml case to be inputted within the system along their type data, when it conforms to the schema. Or else, it discards the xml case if it does not conform to the schema. The basic role of Xml_Schema_Namespace is to regain the schema group inputted in the records. The user can also employ the XML schema group for typing the XML columns, variables, and parameters (Microsoft Corporation, 2014; IBM, 2005). XML MODELS With the two models using the XML, it usually becomes essential to import the xml within the storehouse or a record that permits further refined storage as well as the data regain when the xml is approached by a number of users. Following are the storage options discussed on the basis of needed xml usage model (Obasanjo, 2001): Data-centric model In this type of model, the data is accumulated in a related record or catalogues, where the user may wish to retrieve data in the form of xml or store it into records or both the uses. Within the first case, when the user requires to take out the XML from the record, then the middleware applications can be used, which can retract the data from record and restores as XML. The middleware applications that convert the related data into the xml and then restores, show a discrepancy extensively in terms of functionality and the way it functions. For example, ADO.NET by Microsoft delivers an XML combination to the extent that stems from requests on XML documents or SQL records can be retrieved equally through the similar API. Others such as Merants jxTransformer necessitates the user to stipulate in what way the consequences of a SQL request can be transformed to XML through more customized request, despite the fact, some like IBMs Record DOM entails the user to generate a prototype file, which comprises the SQL transforming into XML to fulfill the request. While one more method is given by DB2XML in which a default transformation of SQL into XML data occurs that could not be changed by the user. Middleware applications also show a discrepancy in the ways of refinement for the user interface that can differ from virtually non-current (interface performed through programmatically by APIs) to interface existing through a classy graphical user interactions (Obasanjo, 2001). Document-centric model Content Management Systems are basically chosen if the user requires to collect, revise and recover numerous XML documents within a common depository. This system usually encompasses a storehouse which collects a number of xml documents, a checker and also an engine delivering one or other functions (Obasanjo, 2001): Type, review and access control The capability to use again the documents in diverse designs Cooperation Web publishing amenities Backing for many different text editors (e.g. Microsoft word, adobe frame maker, etc.) Search competences and indexing Mainly, the content management system is much useful for the workflow and information flow management in the business field, where the information flow management is a crucial element and is considered to be a method for handling the formation of web content in a sectional manner, letting the web developers as well as content makers to function regardless of defending others, rather than the conventional web authoring setting. Cases of XML centered content management systems includes; Entrepid, Content@, SyCOMAX, SiberSafe, XDisect, and Frontier. Hybrid model When the both of the above discussed models are collectively used, then the best selection for the storage technique is the native xml database. It is the topic of a discussion that what exactly establishes a native XML storehouse, which has become complicated by the unclear lines seen among the XML-enabled records, native XML databases, XML servers and XML query engines. The discussion among the forum members of XML:DB mailing list results in the most comprehensible description with consensus, where they demarcated the native XML database to have an XML document being the most basic unit of storage and elaborate the model for an XML document that is to be opposite to the document, and collects and recovers the documents vased on the model. It is argued that the model should have the fundamentals, features, PCDATA, as well as the document order at least. Two examples are explained here for the purpose of elaborating the extent of functionality as well as variability which is anticipated to exist in the native XML database field (Obasanjo, 2001). First example is the Tamino advanced by Software AG. Which is a comparatively complete application, presently at version 2.3.1, which delivers the ways to stock & recover the XML documents, the interactive data, and also the interface with outside requests and resources of data. Tamino contains the web-based management interface related to the main interactive database management systems, plus it comprises the GUI implements for cooperating with the records and rewriting the schemas (Obasanjo, 2001). XML into SQL In order to put XML into SQL, the two most basic non-native techniques are the LOBs (BLOBs/ CLOBs, for instance Binary or Character Large Objects) and Shredding. There are some explanations for the bad performances of both techniques. Among these, the Shredding takes the XML documents and dispenses these documents into a cluster of tables. In the same way, the updates within the XML can also be distributed in a number of updates while the shredding technique is employed. And with this shredded storage technique, a complicated connection can be developed from a single lookup within XML. On the other hand, the LOB storage removes all these issues, however, it generates another issue, where if the user is found only a portion of the document, then there is a requirement to retrieve and manage the whole document, while such similar issues happens to the updates (Monash Research, 2005). Thus, the native storage can only be beneficial if the user is not able to meet the expense of the bad functioning clash of either the LOB storage technique, or shredding or any other available hybrid technique. It could also be beneficial, if the acquired storage techniques are performing well, but possibly it would generate excessive loads on the application development, or if any other thing happens, then single technique or both of the methods are not practical (Monash Research, 2005). There is also a good aspect regarding the native-XML storage that it would not have any drawback when the user gets the XML storage from a well reputed high-end DBMS sellers. Among these, IBM, Oracle, and Microsoft are the sellers that have developed resolutions for having a combined query analyzing, and query optimization, and they have allowed the storage to be either more or less separate. In specific words, the Oracle yet stabs the whole thing into a single data store in reality (therefore there is no support for native XML), however permits the highest level of flexibility in the way it is retrieved. Microsoft has distinct servers for all kinds of tabular data, MOLAP, and text, while similar to Sybase, it doesn’t contain universal data category extensibility, which can be shown to the customers, or take advantage of it for providing with a number of categorized data types. IBM also had extensibility the whole time like Oracle, however, it was never been much aggressive in taking advantage of it, while it has further launched a distinct server option for XML. The two companies IBM and Microsoft asserted that the management tools by themselves are smooth at adequate levels, while the DBA has a slight additional function from their offerings which would be there in a solitary server solution (Monash Research, 2005; Harold, 2008 ). The question here is that what the rudimentary idea is behind the functionality of storage. The basic idea is that the data is deposited in the name-value couples, with pointers linking parents to children. While the underground point here is the additional data which is accumulated at the node straight or in an all-embracing directory. Noticeably, there is an exchange among the update and recovery swiftness (Monash Research, 2005). Comparison with JASON Given below is the comparison of XML and JSON technology (ajaxwith, 2009; Almaer, 2007; Subbu, 2006): XML parsing is extremely generic; in this scenario we do not have to care for the types. On the other hand JSON parsing is extremely tricky. In case of developing a system code parsing through XML is a great deal cleaner than the code to parse JSON. The JSON data on the HTTP is more effective and faster as compared to XML. Assessing the JSON on JS is a great deal efficient and faster. Because of its intrinsic support on Java Script, the learning cycle as well as handling the JSON data is quicker than handling of XML through Java Script. To support WEB2.0/RIA applications, wherever there are many data transfers among the browser as well as server, it makes sense to obtain the response in JSON as well as manipulate it in the browser. JSON does not have some namespaces. JSON is not having validator. XQuery and XLink and other special facilities those are obtainable via XML but not on JSON. Future work XML technology has progressed greatly and at the present, it is aimed at providing the businesses a new technology based working that include a variety of facilities regarding the management of web based business and other communication. A new future based technology that is expected in coming few years is the SQL support XML technology. In this technology XML publishing is the logical position to initiate for the reason that it is straightforward to symbolize a SQL outcome set in XML and because consequently a lot of dynamic Web pages are fed through SQL queries. The customary approach needs programmatic contact to the result set as well as programmatic development of the Web page (Udell, 2009). The new technique turns up that dynamic Web page in a completely declarative method, by means of a SQL-to-XML query to produce an XML depiction of the data and eXtensible Stylesheet Language Transformation (XSLT) to massage the XML into the HTML carried to the browser. This structure will trim down the processing load. Here we will also require less time for results because of direct processing. The overall security structure will enhance because of the direct quarry processing and retrieval (Udell, 2009). Growing portability is also a most important revolutionary technique. The implementation of the portability in XML based document is an evolving trend. At the present all our office documents are in XML, it will turn out to be extremely simple to transform them from one layout to another. Modern version of XML that is identified as XSLT is more powerful and comprises lot of new facilities. We are expecting further enhancement those can free us from the handling of lot of different type of version handlings (Harold, 2008 ). Enhanced security implementation and safer online business handling is also a main facility that XML provides. We are expecting more safer technology in this regard that can make the overall working and handling of the data on the web easier (Samokhvalov & Eisentraut, 2007). Conclusion A database is used at the back-end of a web site in order to store data related to a web site. A large number of web applications make use of different databases to store relevant information, which are used for completing daily activities. A wide variety of tools and technologies are available to create, manage and update these databases. However, the scope of this paper was limited to the development of databases using XML. This paper has discussed important concepts associated with XML and databases. This paper has discussed the way an XML database is used. Though, an XML database is not a formal database that is developed through a database management system but it can provide a limited functionality that is contained by the databases. This paper has discussed the features and elements that differentiate XML databases from other database management systems. References ajaxwith. (2009). JSON vs XML. Retrieved 01 20, 2015, from http://www.ajaxwith.com/JSON-vs-XML.html Almaer, D. (2007, January 04). JSON vs. XML: The Debate. Retrieved January 21, 2015, from http://ajaxian.com/archives/json-vs-xml-the-debate Bourret, R. (2003, November). XML and Databases. Retrieved from http://people.cs.clemson.edu/~juan/CPSC862/XML-Databases.htm#query Codenomicon-Labs. (2009). XML Security and Fuzzing. Retrieved February 04, 2015, from http://www.codenomicon.com/labs/xml/ Harold, E. R. (2008 , Feb). The future of XML. Retrieved February 05, 2015, from http://www.ibm.com/developerworks/library/x-xml2008prevw.html Hirsch, F. (2002, November 28). Getting Started with XML Security. Retrieved February 04, 2015, from http://www.sitepoint.com/article/getting-started-xml-security/ Hoffer, J. A., Prescott, M. B., & McFadden, F. R. (2007). Modern Database Management, Eighth Edition. New York: Pearson Education, Inc. IBM. (2002, April 22). XML & Security . Retrieved February 04, 2015, from IBM.com: http://www.trl.ibm.com/projects/xml/index_e.htm IBM. (2005). The IBM approach to unified XML/relational databases. Retrieved from http://xml.coverpages.org/IBM-XML-GC34-2496.pdf Microsoft Corporation. (2014). XML Schema Collections (SQL Server). Retrieved from https://msdn.microsoft.com/en-us/library/ms187856.aspx Monash Research. (2005, November 17). Native XML storage, Part 1 (technology) . Retrieved from http://www.dbms2.com/2005/11/17/native-xml-storage-part-1-technology/ Obasanjo, D. (2001). AN EXPLORATION OF XML IN DATABASE MANAGEMENT SYSTEMS. Retrieved from http://www.25hoursaday.com/storingandqueryingxml.html Samokhvalov, N., & Eisentraut, P. (2007). The Road to the XML Type: Current and Future Developments. Retrieved February 06, 2015, from SlideShare.net: http://www.slideshare.net/petereisentraut/the-road-to-the-xml-type-current-and-future-developments Shelly, Cashman, & Vermaat. (2005). Discovering Computers 2005. Boston: Thomson Course Technology. Song, Y. (2009). The Application of XML Security Technology in E-commerce System. Second International Symposium on Electronic Commerce and Security (pp. 422-425). IEEE. Subbu. (2006, August 27). JSON vs XML. Retrieved March February 03, 2015, from Subbu.org: http://www.subbu.org/blog/2006/08/json-vs-xml The Road to the XML Type: Current and Future Developments. (2009). Retrieved February 04, 2015, from http://www.slideshare.net/petereisentraut/the-road-to-the-xml-type-current-and-future-developments Turban, E., Leidner, D., McLean, E., & Wetherbe, J. (2005). Information Technology for Management: Transforming Organizations in the Digital Economy, 4th edition (4th ed.). New York: Wiley. Udell, J. (2009). The future of XML documents and relational databases. Retrieved February 06, 2015, from http://www.infoworld.com/d/data-management/future-xml-documents-and-relational-databases-757 Verma, M. (2004, Jan 27). XML Security: The XML Key Management Specification. Retrieved February 02, 2015, from http://www.ibm.com/developerworks/xml/library/x-seclay3/ W3C. (2007, July 25). Efficient XML Interchange Measurements Note. Retrieved February 04, 2015, from http://www.w3.org/TR/2007/WD-exi-measurements-20070725/ W3C. (2009). XML Security Working Group. Retrieved February 04, 2015, from http://www.w3.org/2008/xmlsec/ Wilhite, T. (2015). Disadvantages of an XML Database. Retrieved from eHow.Com: http://www.ehow.com/list_6701942_disadvantages-xml-database.html Read More