UML, XMI, and code generation, Part 1
In this first article in a new series on UML and XML schema development, Benoit discusses the motivations for modeling XML schema through the use of UML.

..., Part 2
In the second part of this series on UML and XML, Benoit introduces the UML metamodel. He proceeds to XMI, the XML-based specification for the exchange of ...

..., Part 3
In his third article on UML modeling and XML, Benoit further refines the conversion stylesheet with the introduction of stereotypes and tags.

..., Part 4
In this final article in his series on UML and XML, Benoit wraps up the technique. He discusses the need to simplify the model by burying some of the logic ...

Using XSLT for content management
This is the first installment of Working XML, a column with companion project code that demonstrates the evolution of full-fledged XML applications.

Link management and preparing the future
This article shows how to use XML filters to add new functionality to XM, an open-source Web publishing application.

Fundamentals of Web publishing with XML
As more developers learn and experiment with XML, many have become interested in using stylesheets to publish and manage Web sites.

Define and load extension points
In this article, Benoit takes integration between XM, the simple content-management solution, and Eclipse one step further. Publishing a Web site requires ...

Creating a project
Work continues to integrate Eclipse -- IBM's open-source project to build an extensible IDE for Java developers -- and Benoit Marchal's simple ...

A lightweight XML client
While excellent solutions are available for large corporations that want to implement XML, few solutions exist for smaller organizations.

Processing instructions and parameters
This month our hardworking columnist adds support for multiple style sheets to the XM content-management project. In so doing, he taps into TrAX URIResolver ...

Compiling the proxy
In this column, Benoit provides the front end for the Handler Compiler, HC, and encounters unexpected problems with the DFA. A stable but less than optimal ...

A first version of the lightweight client
Benoit continues to develop a lightweight XML client. In this article, he shows you how to create SOAP transactions through XSLT.

Importing text as XML with XI
This column marks the launch of the third 'Working XML' project. This new project deals with importing text documents in an XML publishing solution (or any ...

Wrestling with Java NIO
This column takes the XI project to the next step. Here, Benoît reports his findings with the new Java technology APIs -- in particular, ...

Wrapping up XM version 1
In this month's column, developer and author Benoît Marchal adds final features to the first release of XM, a low-cost open-source content management ...

Compiling the paths and automating tests
This month, our columnist discusses the compilation algorithm. He also invests a bit of time automating tests with JUnit.

Building a compiler for the SAX ContentHandler
This installment of the column describes the requirements for the Java project
and analyzes its overall design. The new project, called HC (short for ...

Compiling XPaths
This month our columnist describes how he implements the DFA construction algorithm, giving the first concrete example of using the compiler to recognize ...

Map files into SOAP requests, Part 1
Many applications are being upgraded to accommodate e-commerce transactions. In the first of two articles on the subject, Benoit Marchal shows one simple ...

Mapping files into SOAP requests, Part 2
Many applications are being upgraded to accommodate e-commerce transactions. In his previous column, Benoit Marchal analyzed legacy data and showed how to ...

Wrapping up XI
Columnist Benoît Marchal continues to shape XI, an open-source project that converts legacy text to XML. For increased efficiency, XI now implements the SAX ...

Putting XI to good use
When it comes to user interfaces, simplification is the key. Fewer options and fewer controls mean less confusion and less chance for error.

XML : Technical library view
... Take advantage of lessons learned by refactoring XM ... Working XML:A first version of the lightweight client ...

Link management and preparing the future
In this installment of Working XML, Benoit Marchal uses XML filters to add new functionality to XM, his open-source Web publishing application.

Importing text as XML with XI
Importing text as XML with XI, e-mail it! Related content:.Subscribe to the developerWorks newsletter. Also in the XML zone:. Tutorials ...

Wrapping up XM version 1
Wrapping up XM version 1, e-mail it! Managing a list of links and the table of contents.

Compiling the proxy
... br>"); writer.println(" * A project developed for the 'Working XML' column at developerWorks."); writer.println(" * @see <a ...

Compiling the proxy
Compiling the proxy, e-mail it! Related content:. Subscribe to the developerWorks newsletter. Also in the XML zone:. Tutorials ...

Compiling XPaths
The Java-based Handler Compiler (HC) project for SAX parsing nears its alpha release. This month our columnist describes how he implements the DFA ...

The XML Cover Pages

Also Standards and Interoperability

Standards Tracks and XML Standards Reference

SOAP (Simple Object Access Protocol) and Java SAX (Simple API for XML)

NT Explorer: Simple Object Access Protocol (SOAP): Brett Burridge investigates the use of the Simple Object Access Protocol (SOAP), the XML-based protocol that is taking a leading role in the emerging area of Web Services.

OASIS

OASIS, the Organization for the Advancement of Structured Information Standards, is a non-profit, international consortium that creates interoperable industry specifications based on public standards such as XML and SGML, as well as others that are related to structured information processing.

DELOS Standardization Forum

A number of emerging Web standards will provide much of the basic architecture for digital libraries (RDF, Dublin Core, INDECS, DIENST protocol, UNICODE, XML, Z39.50, etc.). Many of these standards have just begun to move from research to deployment. Implementers will need to follow the progress of research, while researchers will need to monitor the experience of early adopters. The refinement of a stable architecture for digital libraries will require several iterations as these standards are adapted for various applications. The Standardisation Forum focuses on issues related to the deployment of standard metadata schemas and of related infrastructures for publishing, registering, and cross-linking application schemas based on standards.

Several DELOS Standardization working groups will examine the relation between standards for high-level resource description, such as Dublin Core, and standards for fine-grained description within specialised applications, and how multiple standards can be used in combination to address the unique needs of applications. This issue was the focus of a metadata workshop held in Vienna on 30 June 2000 organised by the Standardisation Forum at an EC concertation event presenting projects sponsored by the Digital Heritage and Cultural Content programme, as well as of a workshop session on "Building Digital Library Portals with Harvested Metadata" held on 8 February 2001 at the First EU-DL All Projects Concertation meeting in Luxembourg.

· Agent’s Requirements in Digital Libraries

· Formal Metadata

Information Society Technologies (IST) Electronic Publishing

XML/EDI

Notes about secure data exchange

Standard Naming (XML at Builder.com, 30^th Oct 02)

How many times have you received an XML document from an external source and the data was all there, but you knew you would need to tweak it to make it work with your system? It's a common problem that is often the result of a lack of precision. Being more precise can alleviate problems with many common data types. Let's look at some examples of how you can create precision standards for your XML elements.

THE NAME GAME

One of the most common problematic elements is one that includes name information. Here are a few of the many name formats:

* SCHAFFNER, BRIAN

* Brian T. Schaffner

* Mr. Brian Schaffner

* Rev. Dr. Brian Schaffner, III

There are several different formats for someone's name, and communicating it in XML can be confusing if there's not enough precision in your elements to hold each component. Let's try to create an all-encompassing name element that you can use for nearly any name.

We'll start with the first part of the name--the prefix. Of course, there may be more than one prefix (as in the Reverend Doctor), so you'll need space for multiple prefixes, and probably something that indicates their proper order. Next is the first or proper name followed by one or more middle names (or perhaps an initial, or perhaps no middle name). Nearly last is the last name or surname followed by the suffix (as in Jr.). When put together, it might end up like this:

<Name>

<LongForm>Reverend</LongForm>

</Prefix>

<LongForm>Doctor</LongForm>

</Prefix>

<Proper>Brian</Proper>

<Surname>Schaffner</Surname>

<LongForm>the third</LongForm>

</Suffix>

</Name>

XML PHONE HOME

Another element in XML documents that frequently suffers from format abuse is telephone numbers. Here are a few of the many ways to format telephone numbers:

* (502) 555-1212

* 502.555.1212

* 5025551212

* 502-555-1212

* +1(502)-555-1212 x334

There certainly are others that aren't listed here. You can run into the same problem with phone numbers as you do with names. The solution is to determine what are all the possible components that a telephone number may include and create a model that supports them. That way you won't lose any information in your XML documents.

We've identified five important components of a telephone number above. They start with the country code and end with the extension number. Creating a comprehensive telephone number element shouldn't be too difficult with this information:

</TelephoneNumber>

XML Dictionary

My new book "Dictionary of XML Technologies and the Semantic Web" (Springer-Verlag, 2004) is now available for sale world-wide.

This 250-page hardcover includes over 1,800 terms/acronyms and 264 illustrations. An accompanying CD-ROM contains a searchable version of the dictionary.

For more information, visit Amazon http://www.amazon.com/exec/obidos/tg/detail/-/1852337680/ or see sample pages at Springer http://www.springeronline.com/sgw/cda/frontpage/0,10735,3-40109-22-17629028-0,00.html

Digital Object Models (DOM, CSS, HTML, Web, XML, SVG, …)

tutorial at w3schools <http://www.w3schools.com/dom/default.asp> will get you into the XML DOM quickly. Perl shouldn't be any different from any other language; that's the point of the DOM.

NameSpaces and URIs

The list had some 1840 postings through July 03, 2000. See in particular the post of C. M. Sperberg-McQueen on 2000-07-03: "Moving toward a decision", [Proposed by the Plenary:] "Proposed: to deprecate the use of relative URI references in namespace declarations; that is: to say that while t