Extensible Markup Language (Xm L) is a system for defining specialized markup languages that are used to transmit formatted data.
XML is a simplified version or dialect of SGm L. It allows you to define your own tags in a structured way. It adds order to a world that was getting fragmented with non-standard browser tags. XML has the potential to be the universal data format for communication.
You might want to check some XML Lin Ks for further reading. See also Dt D.
From the Biz Talk website: Many companies report a strong interest in XML. XML however, is so flexible that this is similar to expressing a strong interest in ASCII characters. Despite the advances that XML affords, they are hard to achieve without a consistent Frame Work for XML implementations.
One of the weaknesses of a browser-based interface is the necessity of making a round-trip to the server to validate user input, or use of client-side scripting. However, if a DTD is transmitted to the browser along with XML data, and there is some way of running XML through a parser for validation *before* it is sent back to the server, then it might be much easier to do vailidation at the client, but still under control of the server.
Now, this can be taken a little step further, by transmitting multiple "packages" of XML, each with its own DTD, so that (in effect) each field, or a set of interdependent fields can be validated independently at the client.
What is the difference between " ... or use of client-side scripting" versus XML with respect to validating data? I haven't gotten much beyond creating my own tags with XML (I don't understand much yet) but both techniques are initialized by the client-browser. (It does look like XML is easier to understand/write then Java Script.)
Contributors: Steve Sawyer jMM
Category XML Category Web Development
( Topic last updated: 2000.03.03 02:25:39 PM )