Question

Why xml is used to store and transport data?? Why we not use html?

Answer 1

Hey mate..
========

▪XML which extends for extensible Markup Language, is basically a meta-markup language defined by the World Wide Web Consortium in 1997.

▪It is a markup language because it uses tags surrounding text to convey information such as content or format.

▪It is also a meta language because it is used it create other languages.

▪XML was developed in order to overcome some of the difficulties associated with the HTML. One of the main problems of the HTML is that it doesn't define the structure of the document.

▪XML was created so that richly structure document can be used on the web.

▪Both XML and HTML are designed with different goals. XML was designed to store, carry and exchange data while HTML was designed to display data.

▪Thus, we come to a conclusion that HTML is not used for storing and transporting data but XML does.

Hope it helps u to some extent !! ☺

Answer 2

Answer:

You can use XML is for both, storing and transferring data.

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.XML is human readable text. Some of the characters ('<' and '>') are interpreted as keyword markers. That way it is very flexible in what you can use it for.

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.XML is human readable text. Some of the characters ('<' and '>') are interpreted as keyword markers. That way it is very flexible in what you can use it for.[EDIT]

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.XML is human readable text. Some of the characters ('<' and '>') are interpreted as keyword markers. That way it is very flexible in what you can use it for.[EDIT]For transferring data from a sender machine to a receiver machine, you would most likely have the data you want to transfer in an object.

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.XML is human readable text. Some of the characters ('<' and '>') are interpreted as keyword markers. That way it is very flexible in what you can use it for.[EDIT]For transferring data from a sender machine to a receiver machine, you would most likely have the data you want to transfer in an object.The sender serializes the object. That means it converts the object to a byte stream. This stream can be formatted in XML, SOAP (which is built on top of XML), JSON, whatever.

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.XML is human readable text. Some of the characters ('<' and '>') are interpreted as keyword markers. That way it is very flexible in what you can use it for.[EDIT]For transferring data from a sender machine to a receiver machine, you would most likely have the data you want to transfer in an object.The sender serializes the object. That means it converts the object to a byte stream. This stream can be formatted in XML, SOAP (which is built on top of XML), JSON, whatever.The receiver receives the byte stream and deserializes it to an object. This object should be equivalent to the one the sender has sent before in that it holds the same data.

You can use XML is for both, storing and transferring data.For transferring, you usually don't create a file and transfer it but send the content directly.XML is human readable text. Some of the characters ('<' and '>') are interpreted as keyword markers. That way it is very flexible in what you can use it for.[EDIT]For transferring data from a sender machine to a receiver machine, you would most likely have the data you want to transfer in an object.The sender serializes the object. That means it converts the object to a byte stream. This stream can be formatted in XML, SOAP (which is built on top of XML), JSON, whatever.The receiver receives the byte stream and deserializes it to an object. This object should be equivalent to the one the sender has sent before in that it holds the same data.The (de)serialization part can get fiddly. Therefore try to use something that already works. In C#, I have used the SOAP formatter class[^] and it works well. You should look for something that exists for both your endpoints.