Lenguajes de marcas para la gestión de contenidos y la publicación Web (debate)
Enero 7, 2009
First and foremost, we would like to explain the terms involved. Being both markup languages, on the one hand, HTML stands for “Hyper Text Markup Language”, and on the other, XML stands for “Extensible Markup Language”.
Focusing on the differences, XML points at the structure of the information, saving time and simplifying the software, not requiring, consequently, DTD or Document Type Definition. Besides, it supports Unicode, allowing almost any information in any written human language
to be communicated, and in addition, it doesn’t have any data. HTML however, requires from the authors to avoid the use of presentational markup as well as to use available markup to differentiate the meanings of phrases and structure in the document. Moreover, HTML documents are more difficult to be delivered, as they are normally delivered either over HTTP servers or through e-mail.
In short, XML is more useful than HTML not only because it is easier to try for the computer programs, but also because HTML does not indicate what it is representing. In fact, HTML is known for describing the content of what it labels.
References:
1. HTML. (2008, December 13). In Wikipedia, The Free Encyclopedia. Retrieved 19:35, December 14, 2008, from
http://en.wikipedia.org/w/index.php?title=HTML&oldid=257683789
2. Markup language. (2008, December 14). In Wikipedia, The Free Encyclopedia. Retrieved 19:36, December 14, 2008, from
http://en.wikipedia.org/w/index.php?title=Markup_language&oldid=257834827
3. Hipertexto, el nuevo concepto de documento en la cultura de la imagen (2008, November 23) by María Jesús Lamarca Lapuente in Hipertexto. Retrieved 20:39, December 14 from: http://www.hipertexto.info/documentos/lenguajes_h.htm
4. Extensible Markup language (1999) by Joaquin Bravo Montero in Programacion. Retrieved 20:41, November 23 from:
http://www.programacion.net/html/xml/htmdsssl/capitulo1/capitulo1.htm
Entry Filed under: Uncategorized. .
Trackback this post | Subscribe to the comments via RSS Feed