#25642
Discusses the need for custom DTDs: why making a custom DTD for the sole purpose of validation is a mistake, and in which cases it does make sense to create and use one. For these cases, this article will also present techniques for creating clean custom DTDs and avoiding hacks.
W3C Quality Assurance Team. List Apart, A (2005). Design>Web Design>Standards>XML
#22199
Some Thoughts about SOAP versus REST on Security
REST is the underlying architecture of the World Wide Web and its two core specifications, URIs and HTTP. It has been proposed that instead of using new-from-scratch Web Services technologies we can get much more bang for our buck by understanding the full generality of what we've got. A community has arisen around this idea and we spend our time proving that what the Web already has is better than what is being developed. This page addresses the security weaknesses of the SOAP approach.
#20009
XML is the acronym for the extensible markup language. According to the W3C, it is 'the universal format for structured documents and data on the Web'. The following list explains what XML is and what it is not.
Helo, Julia and Betsy Kent. Carolina Communique (1999). Design>Web Design>Standards>XML
#22074
Extensible Markup Language, or XML, is currently the most promising language for storing and exchanging information on the World Wide Web. Although Hypertext Markup Language (HTML) is presently the most common language used to create Web pages, HTML has a limited capacity for storing information. In contrast, because XML allows you to create your own elements, attributes, and document structure, you can use it to describe virtually any kind of information—from a simple recipe to a complex database. And an XML document—in conjunction with a style sheet or a conventional HTML page—can be easily displayed in a Web browser.
Young, Michael J. mjy Online. Design>Web Design>Standards>XML
#30455
In Mozilla-based applications, the yellow screen of death is the screen displayed when they encounter an XML parsing error. This typically happens when the XML document that the browser is trying to access is not well-formed, for example when it does not nest tags properly.
#33787
DOM, SAX and Standards - Where Now?
It's been 7 years and three "levels" since the first W3C DOM activity. XML and the way it is used has changed vastly over that time. DOM itself has moved from an API to access and manipulate an in-memory tree with no concept of namespaces, to an end to end XML technology, where parsing, modification of the tree (with the ability to check for validity with a schema as you go) and serialization are all specified.
Reakes, Gareth, Alberto Massari, Lucian Holland and Neil Graham. IDEAlliance. Articles>Web Design>Standards>XML
#34005
Browser Problems with the XML Prolog
Some browsers have difficulty upon encountering the XML Prolog. In some cases, the browser will render all the markup as text. In other cases, when a browser has some XML support, it might attempt to render the document as an XML tree. To avoid these problems, many practicing web professionals prefer to leave the prolog off. This table will help you make that decision by showing you which browsers have known problems with the XML prolog.
Web Standards Project (2007). Articles>Web Design>Standards>XML
#35175
RDFa (“Resource Description Framework in attributes”) is having its five minutes of fame: Google is beginning to process RDFa and Microformats as it indexes websites, using the parsed data to enhance the display of search results with “rich snippets.”
Birbeck, Mark. List Apart, A (2009). Articles>Web Design>Standards>XML
