XML and JSON - Research Paper Example

XML and JSON Abstract This paper presents a detailed analysis of the XML (extensible markup language) and its standards. Additionally, this analysis and research based paper will discuss the difference between XML and JSON. This paper will also discuss the examples of how organizations use XML or JSON to meet business needs. Here I will discuss why there is a need for XML or JSON. EXTENSIBLE MARKUP LANGUAGE (XML) XML (eXtensible Markup Language) is a more stylish arrangement for sharing data that facilitates web page developers to develop customized tags and utilize predefined tags. Additionally, in XML, developers can establish a link which points to several web sites in place of a single site. Furthermore, 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). Extensible Markup Language (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 not simply can 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. In addition, the 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). JSON (JavaScript Object Notation) JavaScript Object Notation (JSON) is a simple data-interchange arrangement. Since, it is trouble-free for humans to write and read it. Additionally, it is straightforward for machines to parse and create. In addition, JSON is foundational upon a division of the ECMA-262 third Edition, December 1999, which is Standard of JavaScript Programming Language. Furthermore, JSON uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others, but it is entirely language autonomous. Thus, JSON is an ideal data-interchange language because of these characteristics. However, the JSON is a division of the object literal notation of JavaScript. Since, JSON is a division of JavaScript; it can be utilized in the language having no fuss or muss (JSON, n.d). It is helpful when writing some type of JavaScript-based application, comprising extensions (mozilla, 2009). Furthermore, the (Java-Script Object Notation) is an extremely portable data transaction format. As its arrangement is familiar natively through Java-Script, its arrangement principles are simply recognized through other C-like languages. However, the JSON is constructed on two main structures (Matt, 2006): A set of value/name pairs. In a variety of languages, this is acknowledged as record, object, structure, hash table, dictionary, associative array or keyed list. A structured list of values. In the majority programming languages, this is acknowledged as a vector, array, sequence or list. 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 (W3C, 2007). 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 (MSDN, 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 the 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 (Hoffer, Prescott, & McFadden, 2007, pp. 399-400). 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 (MSDN, 2007). Difference between XML and JSON This section outlines some differences between the 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. Concussion This paper has presented a detailed analysis of the two most popular web technologies. In this scenario I have discussed the XML and JSON. This paper has outlined the uses, technology and standards for these technologies. In addition, this paper has presented the comprehensive comparison of XML and JSON working and technology. I hope this research will offer an insight of the XML and JSON technology. References Almaer, D. (2007, January 04). JSON vs. XML: The Debate. Retrieved March 20, 2010, from http://ajaxian.com/archives/json-vs-xml-the-debate Hoffer, J. A., Prescott, M. B., & McFadden, F. R. (2007). Modern Database Management, Eighth Edition. New York: Pearson Education, Inc. JSON. (n.d). Introducing JSON. Retrieved March 25, 2010, from JSON.org: http://www.json.org/ Matt. (2006, March 29). The Case For JSON: What Is It and Why Use It? Retrieved March 25, 2010, from BorkWeb.com: http://borkweb.com/story/the-case-for-json-what-is-it-and-why-use-it Mozilla. (2009). JSON. Retrieved March 20, 2010, from https://developer.mozilla.org/en/JSON MSDN. (2007). Convergence Zones. Retrieved March 25, 2010, from http://blogs.msdn.com/mikechampion/archive/2007/01/12/convergence-zones.aspx Shelly, Cashman, & Vermaat. (2005). Discovering Computers 2005. Boston: Thomson Course Technology. Subbu. (2006, August 27). JSON vs XML. Retrieved March 26, 2010, from Subbu.org: http://www.subbu.org/blog/2006/08/json-vs-xml 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. W3C. (2007, July 25). Efficient XML Interchange Measurements Note. Retrieved March 25, 2010, from http://www.w3.org/TR/2007/WD-exi-measurements-20070725/ Read More