The site offers articles, tutorials, tools, and examples to help you keep up with the latest developments in XML and Web services from developerWorks and alphaWorks.

Voici trois techniques différentes d'affichage d'un document XML au sein d'une page Web :

• le Data Binding HTML,
• le DOM ,
• par XSLT.

Chacune de ces techniques présente des caractéristiques bien spécifiques. Le choix de l'une ou l'autre technique dépend des affinités du développeur. On utilisera plus aisément le Data Binding pour des développeurs qui veulent juste afficher des données de manière globale avec un minimum de code.
Les développeurs habitués à manipuler par programmation des modèles objets préfèreront sans doute utiliser le DOM.
La feuille de style XSLT, en dépit de la complexité du langage, reste une technologie très puissante et offre une grande flexibilité dans le traitement de données XML.

XML has gained popularity as a platform- and language-independent format for transferring data across systems. In situations where you need to transfer binary data within an XML document, you must encode that binary data into an acceptable character format. This tip describes three different encoding approaches ranging from the simple to the most sophisticated techniques. (2,100 words)

• The brute force approach : converts each binary data byte into its two character, hexadecimal representation. Use StringBuffer and hexadecimal number lookup table for optimization.
• Base-64 encoding approach : Use A-Z a-z 0-9 + / (64 characters) to encode bytes. Generate 1.33 characters per byte instead of 2 characters per byte
• Huffman coding approach : This approach uses the binary data sets' statistical properties to compress the resulting encoded character stream.

In summary, for cases where the transferable data sets are very large and where the byte value distribution within the data set is skewed, the Huffman coding approach is the best candidate. For cases where the data sets are not large and you need a quick implementation, the Base-64 encoding scheme is the best choice.

The author creates a user interface that enables users to view the same section of data in a dual form using XML and XSL...

In this article, XML tool watcher Dennis Sosnoski compares the usability of several Java document models. It's not always clear what the tradeoffs are when you choose a model, and it can require extensive recoding to switch if you later change your mind. Combining sample code with analysis of the model APIs, the author gives recommendations for which models may really make your job easier. Includes code samples that show the methods for the five different document models.
(contains sample code)

The major advantages of XML for interoperability of data are its extensibility and its ability to represent all forms of data in text format. XML proves its worth even when dealing with binary data. This article focuses on three ways to represent binary data in XML. The first method uses XML and DTD to represent a binary file or data source in the most appropriate way. The second way uses a simple format where everyone can define their own format to represent the binary data. With the third method, all of the binary data is contained within the XML file.
(contains sample code)

developerWorks is moving toward a custom XML dialect as the source format for the articles that appear on the site. However, writing XML is always going to be difficult for people (but easy for machines). One approach to the "human interface" problem is the public domain txt2dw utility that author David Mertz uses for his own articles.
(contains sample code)

In this column, Kevin Williams takes a look at some options for modeling many-to-many relationships in XML. Several different techniques, and the advantages and disadvantages of each, are discussed. Examples are provided in XML.
(contains sample code)

The parsing of ResultSets forms one of the most significant tasks involved in retrieving data from a database. But, as a repetitious and uninteresting assignment, it is not a favorite among developers. In this article, Abhilash Koneri demonstrates how to supplant ResultSet parsing in the data access objects. Attention lazy programmers or managers who supervise a lackadaisical bunch: this article is for you! (To truly appreciate code reuse, you must be lazy!) (2,000 words)

Joe Slovinski creates a Progress Indicator object that uses XML and XSLT. This object has several uses, including updating the client browser of the progress of a data binding routine or the preloading of images.

Joe Slovinski creates a drag-and-drop object for folder trees. This control has the capability to drag and drop entities from one point within a tree to another or between multiple trees.

Joe Slovinski explains how to dynamically insert, update, rename, and delete entities within a folder tree. Providing features such as unlimited metadata support via XML and XSLT this version of the folder tree can be re-used to represent any array of data.

Welcome to Advanced UI Design Using XML and XSL. Each article in my series will demonstrate the creation of a specific user interface (UI) component using eXtensible Markup Language (XML) and eXtensible Stylesheet Language (XSL).
This article explains how to create a custom, object-specific context menu of unlimited depth by using XML and XSLT. The context menu discussed here functions by taking an XML feed of a specific format and applying an XSLT style sheet to it. The resulting transformation is then printed to the client. The client handles all user requests to navigate the menu. The client used in this article is Internet Explorer 5.5+.

Joe Slovinski explains how to use XML and XSL to create a Web-based folder tree. Using XML and XSL makes this tree low maintenance and when transformed on the client can reduce load on your server.

With recent interest in XML standards and availability of tools supporting these standards, it has become possible to generate multiple types of documents by applying XML document transformation technology. Using XML document transformation technology, it has become easier to develop custom code/document generators in application development projects. Complexities in the current approach to code/document generation have impeded widespread acceptability of the generative approach in application software development projects. This article will show how current XML based standards and freely available tools supporting these standards provide an easier way to develop custom code/document generators.