XHTML is basically HTML, which requires a validated XML structure. The fact is that you are less likely to implement minor errors that can be interpreted differently on different platforms. And you can test your work in accordance with established browser standards with greater ease (you immediately warn about a problem, while HTML often makes mistakes to fall through cracks).
Here is more information about XHTML:
http://www.w3schools.com/xhtml/xhtml_intro.asp
http://www.w3schools.com/xhtml/xhtml_html.asp
Many well-known websites use XHTML, however many other websites use plain old HTML. I tend to use plain old HTML because it works, and I throw caution down the drain. If you are studying for the first time, and you donโt mind for a few extra hours to do it in the โrightโ way, get XHTML.
However, I will add to this discussion the issue of data storage, you must distinguish between your terminology โ data storage โ and presentation . A well-designed website usually stores data in some kind of data warehouse (usually in a database) and presents the data in some form (be it XML, or more often a set of objects), and uses viewing technology to present this information in that could be one of many different forms. One may be XHTML, but you can create a different view of the same data for mobile users and a different view of the same data for the BB backend application or web service or XML for the iPhone application ... the list goes on.
The fact is that if you developed the application well at the beginning (here you will use a new term), using the Model-View-Controller approach, it will be easy to create different "views" from the same source data, regardless of how this data is stored . This means that you separate the code that creates the final HTML / XHTML presentation, webservice, etc., from the data that is used to create this view. In the Java world, an example is Spring-MVC.
I hope this helps you move in the right direction.
source share