Articles of level

There are many benefits of using XML on the Web :
Simplicity

Information coded in XML is easy to read and understand, plus it can be processed easily by computers.

Openness

XML is a W3C standard, endorsed by software industry market leaders.

Extensibility

There is no fixed set of tags. New tags can be created as they are needed.

From a start tag to end tag everything you see in a XML document, is XML element. It can contain other elements, attributes and texts.

 XSLT: Extensible Stylesheet Language Transformation to know about XSLT, we should have the basic idea of following.
There are three languages in XSL family,
XSL Transformations(XSLT): XML language for transforming XML Documents.
XSl  Formatting Objects (XSL-FO):XML language for specifying the visual formatting of an XML document.
XML Path Language (XPATH): a non XML language used by XSLT, and also available for use in non-XSLT contexts, for addressing the parts on an XML document.

All white-space, including line breaks, TAB characters, and normal spaces, even between ?structural? elements where no text can ever appear, is passed by the parser unchanged to the application (browser, formatter, viewer, converter, etc), identifying the context in which the white-space was found (element content, data content, or mixed content, if this information is available to the parser, eg from a DTD or Schema). This means it is the applications responsibility to decide what to do with such space, not the parser:
► insignificant white-space between structural elements (space which occurs where only element content is allowed, ie between other elements, where text data never occurs) will get passed to the application (in SGML this white-space gets suppressed, which is why you can put all that extra space in HTML documents and not worry about it)
► significant white-space (space which occurs within elements which can contain text and markup mixed together, usually mixed content or PCDATA) will still get passed to the application exactly as under SGML. It is the application responsibility to handle it correctly.
The parser must inform the application that white-space has occurred in element content, if it can detect it. (Users of SGML will recognize that this information is not in the ESIS, but it is in the Grove.)

The XML specification only stipulates the syntax for XML. Accordingly, the following XML related technologies play an important role in actually using XML:

  • DOM (Document Object Model)
  • SAX (Simple API for XML)

It depends. Clearly the X in AJAX stands for XML, but several AJAX proponents are quick to point out that nothing in AJAX, per se, precludes using other types of payload, such as, JavaScript, HTML, or plain text. 
XML - Web Services and AJAX seem made for one another. You can use client-side API for downloading and parsing the XML content from RESTful Web Services. (However be mindful with some SOAP based Web Services architectures the payloads can get quite large and complex, and therefore may be inappropriate with AJAX techniques.) 
Plain Text - In this case server-generated text may be injected into a document or evaluated by client-side logic. 
JavaScript - This is an extension to the plain text case with the exception that a server-side component passes a fragment of JavaScript including JavaScript object declarations. Using the JavaScript eval () function you can then create the objects on the client. JavaScript Object Notation (JSON), which is a JavaScript object based data exchange specification, relies on this technique. 
HTML - Injecting server-generated HTML fragments directly into a document is generally a very effective AJAX technique. However, it can be complicated keeping the server-side component in sync with what is displayed on the client. Mashup is a popular term for creating a completely new web application by combining the content from disparate Web Services and other online API. 

One solution that you can use to handle the session timeout errors is using JSON or XML format as output for your AJAX requests.

Here are a few reasons for using XML - 

  • XML can be used to describe and identify information accurately and unambiguously, in a way that computers can be programmed to understand.
  • XML allows documents which are all the same type to be created consistently and without structural errors, because it provides a standardized way of describing, controlling, or allowing//disallowing particular types of document structure. [Note that this has absolutely nothing whatever to do with formatting, appearance, or the actual text content of your documents, only the structure of them.
  • XML provides a robust and durable format for information storage and transmission. Robust because it is based on a proven standard, and can thus be tested and verified; durable because it uses plain-text file formats which will outlast proprietary binary ones.
  • XML provides a common syntax for messaging systems for the exchange of information between applications. Previously, each messaging system had its own format and all were different, which made inter-system messaging unnecessarily messy, complex, and expensive. If everyone uses the same syntax it makes writing these systems much faster and more reliable.

You can use Visual Studio to work faster and more efficiently when you write, navigate, and debug your code. There are some tricks which is helpful to every programmer-

Need Help? Contact Us.

Log in

*
*

Forgot password?

*

New User

*
*
*
*