Coming straight to the point, XML stands for EXtensible Markup Language. As the name suggests, it is a language that can be molded according to the need of the hour. Personally, I don't think calling it a language is justified, but I fanatically follow the ordinance of the techie Gurus, and if they say it is a language, then it is a language.

This tutorial describes: Simple XML Elements with Pre-defined Data Types Simple XML Elements with Extended Data Types Complex XML Elements Simple Content XML Elements Empty XML Elements Anomymous Data Types Sample XSD File - dictionary.xsd

Learn how to create an XML document from scratch and find out why XML is becoming so important. Topics covered include: popular XML editors, basic XML syntax, how to properly nest your XML tags, and much more.

XPointer, the XML Pointer Language, defines an addressing scheme for individual parts of an XML document. These addresses can be used by any application that needs to identify parts of or locations in an XML document. For instance, an XML editor could use an XPointer to identify the current position of the insertion point or the range of the selection. An XInclude processor can use an XPointer to determine what part of a document to include. And the URI in an XLink can include an XPointer fragment identifier that locates one particular element in the targeted document. XPointers use the same XPath syntax that you're familiar with from XSL transformations to identify the parts of the document they point to, along with a few additional pieces.

XSL Formatting Objects (XSL-FO) are the second half of the Extensible Stylesheet Language (XSL). XSL-FO is an XML application that describes how pages will look when presented to a reader. A style sheet uses the XSL transformation language to transform an XML document in a semantic vocabulary into a new XML document that uses the XSL-FO presentational vocabulary. While one can hope that Web browsers will one day know how to directly display data marked up with XSL formatting objects, for now an additional step is necessary in which the output document is further transformed into some other format, such as Adobe's PDF.

The recent rush to adopt XML can be attributed in part to the hope that the static typing provided by DTDs (or more sophisticated mechanisms such as XML-Schema) will improve the robustness of data exchange and processing. However, although XML documents can be checked for conformance with DTDs, current XML processing languages offer no way of verifying that programs operating on XML structures will always produce conforming outputs.

This paper will cover the following topics: HTML vs. XHTML; XHTML modularization and XHTML Basic; well-formed XML documents; names and namespaces; global attributes and XLink; namespace URI and RDDL (XHTML Basic + XLink).

Provides a central location for everything that a developer needs to know about XML technologies (XML, XSLT, XLL, SVG and about 40 other categories). You will find examples with Source Code, Tutorials, Tools, Resources, Books, etc.

When designing XML and Web services schemata you will often (and ideally) reuse data elements defined in pre-existing standards. If so, it is extremely useful to include links to such standards, providing precise data dictionary references. In so doing, you make processing and maintenance easier to automate. This tip illustrates this practice.

The IBM developerWorks Live! Technical Briefings, which were a great success worldwide in 2003, have been expanded for 2004. The following five types of technical briefings, which include presentations and extensive demonstrations, will be held in cities around the world in 2004 (at no cost to you): e-business on demand, IBM Software Development Platform, Speed-start Linux applications, Speed-start Web services, Globalizing your applications.