Welcome to the 35th issue of Pineapplesoft Link! Last month, I was a speaker at the XML One conference in London. I met many readers after my presentations, during book signings and in the exhibition hall. It's good to see so many developers enjoying XML by Example and Applied XML Solutions.

In this month's Pineapplesoft Link, I want to share some thoughts on XML, how it's being used and how it will evolve. By the way, you can find more information on the books at http://www.marchal.com.

An Update on XML

The XML One conference is my excuse to look back and summarize my thoughts on XML. I know many organizations are deploying XML and they raise many questions on where and how they should apply it. I hope this issue will help answer some of the questions.

Versatile Technology

If I judge from reader's emails and other discussions, XML is confusing because it is so versatile. XML means different things to different people. Business-to-business eCommerce, browsers, smartphones, workflow, databases are some of the applications of XML.

For the newcomer, this diversity is confusing. What's the relationship between the browser and the database? The confusion arises from the fact that XML is a low-level technology. Like TCP/IP, Java or SQL, it can used in many different solutions.

Let's build on the SQL analogy. Beside database engineers and book authors, few developers are interested in SQL as a generic technology. What most developers are interested into is writing accounting software, stock management, catalogues or dynamic web sites. Although they all depend on SQL, we don't think of them as "SQL applications."

I am sure that in a few years, XML will follow suit. Developers will be writing, say, business-to-business eCommerce applications. They will regard XML as a component of the solution but it will not be more important than Java, SQL or TCP/IP.

Incidentally, I am not suggesting that XML will become less important in the future, just that it will be better assimilated and perceived as one of the tools in a programmer's toolbox.

I look forward to the day when people don't call me for help on "integrating XML in their application" but for help developing a product which, in turn, will use XML and Java.

Ease-of-Use

As far as I am concerned, one of the most interesting aspects of XML is the ease with which one can learn and deploy it. I got further insight into this aspect during a discussion on XHTML.

XHTML, as you might recall from the March 2000 issue, is an XML rewriting of HTML. Until recently, I considered XHTML as a solution in the making. It will be useful in the future but we're not there yet.

It turns out some developers have found an application for XHTML today. At XML One, I met developers who have deployed XHTML. Their reasons? XHTML is viewable with current HTML browsers and it can be parsed with XML parsers.

As one developer, Fergus McMenemie, explained: "the document can be opened in a regular browser but also used for importing."

Programmer's Tool

If I had any doubts that XML was first and foremost a developer's tool, the last 6 months have removed them. When XML appeared, it was originally touted as a replacement for HTML. Yet I believe XML is closer to a database than to HTML.

Indeed most XML applications center not on the browser but on information storage. What better proof than all the buzz surrounding XSDL (XML Schema Definition Language)?

XSDL is a replacement for the DTD that offers more control over the data structure (some object-oriented concepts are supported) and more built-in data types (integer, float, date and more). Who needs increased control over data structures and data types if not programmers?

If XML is a programmer's tool, it means that when learning XML, you should concentrate on programmer's tools for XML and more specifically XSLT. See the September 2000 issue for a complete discussion of XSLT.

Incidentally, after the September issue on XSLT, I received a few emails from readers who wanted to know if they had to use XSLT to manipulate XML documents. I take the opportunity to answer "no." Use whatever is most convenient but you will find XSLT is convenient in many cases.

Self-Promotion Department

The Pineapplesoft team has grown! We welcome Pascale Dechamps who brings her expertise in project management to our customers. If you are interested by this new service, visit Pineapplesoft homepage at http://www.psol.be/

XML by Example is still doing surprisingly well and I have received positive comments from readers of Applied XML Solutions. Both books are available in your usual technical bookstore.

I'll be at the XML Forum in Paris on the 20, 21 and 22 of November. Hope to see you there!

Finally I am considering a licensing option for Pineapplesoft Link. The idea being that you could distribute a "Your company" Link with the same feature article but your ads and your promotion. If you have a technical web site than a "Your company" Link is the perfect complement to retain and acquire visitors.

I would host and manage the list for you, use the same feature article as in Pineapplesoft Link but let you change the title, the ads, etc. I have not decided on the fee yet although I would expect something between $500 and $1000 per month. If you think you might be interested (no obligations), please let me know. !

About Pineapplesoft Link

Pineapplesoft Link is a free email magazine. Each month, it discusses technologies, trends and facts of interest to web developers.

The information and design of this issue of Pineapplesoft Link are owned by Benoit Marchal and Pineapplesoft. Permission to copy or forward it is hereby granted provided it is prefaced with the words: "As appeared in Pineapplesoft Link - http://www.pineapplesoft.com."

Editor: Benoit Marchal
Publisher: Pineapplesoft www.psol.be

Acknowledgments: thanks to Sean McLoughlin MBA for helping me with this issue.

Back issues are available at http://www.psol.be/old/1/newsletter/.

Although the editor and the publisher have used reasonable endeavors to ensure accuracy of the contents, they assume no responsibility for any error or omission that may appear in the document.

Last update: November 2000.
© 2000, Benoît Marchal. All rights reserved.
Design, XSL coding & photo: PineappleSoft OnLine.