In an earlier Python and XML column I discussed ways to achieve proper XML output from Python programs. That discussion included basic considerations and techniques in generating XML output in Python code. I also introduced a couple of useful functions for helping with correct output: xml.sax.saxutils.escape from core Python 2.x and Ft.Xml.Lib.String.TranslateCdata from 4Suite.

The Boeing Co. deployed XyEnterprise’s XML tools for publishing technical manuals and service documents for the C-17 aircraft. XML Professional Publisher enables Boeing to take documents formatted in XML and publish them in print format or as Adobe PDF files, commonly found on the web. Boeing makes the C-17 Globemaster III for the Air Force. The aircraft is used to carry large combat equipment, troops or humanitarian aid across countries.

As the adoption of extensible markup language (XML) spreads to corporate networks, helping computers speak to each other more efficiently over the Web, what about XML for humans? After all, the financial world has its own dialect of XML, called XBRL (Extensible Business Reporting Language). Tech services vendors have all their flavors of XML as part of the language frameworks for a coming era of Web Services among corporate networks.

XyEnterprise, a developer of XML content management and enterprise publishing software, has announced a new Web Services Development Kit for its XML Professional Publisher (XPP) software line. This new Web Services interface makes available the XML publishing capabilities of XPP to Web interfaces, portals, and application integrations, providing rapid deployment of automated XML publishing solutions.

I was sitting at my desk a few days ago, whiling away the time and I suddenly wondered why HTML includes a < code > tag, and a < var > tag, and yet it takes marking up code no further than that. It’d be understandable to have just the < code > tag, but if they’re going to have a < var > tag, shouldn’t they have more programming tags?

In recent years, the extensible markup language (XML) has been adopted by more and more businesses as an industry standard for data exchange and data sharing. XML provides a system-independent standard format for specifying the information exchanged over networks and between applications.

In the following two articles, I’m going to wrap up my pondering on XML. We’ll explore the basic schema of a DTD, and the future of XML.

Que’s book, “Special Edition: Using XML”, talks about why schemas are an important evolvement in the XML world:

One of the most frustrating things to me is seeing developers doing new things, but in “old” ways. A classic example is one you may have seen yourself: Here we have a sophisticated client – side application that runs in Internet Explorer, we use XML Data Islands and XSLT transforms and parameters, templates, and we even use XMLHTTP from the client. And along with this we may have page upon page that needs to get a recordset from SQL Server – sometimes many recordsets, and bring them into the page as XML so we can do all our “new kind of cool stuff” with it. Well, that’s great.

This tutorial is divided into two parts. We will explain how to create an XML document and how to assign data types to the values in the XML document. All of the examples in this tutorial are designed to be viewed with either Internet Explorer 5.0 or 5.5.

In the first article in this series I presented a brief introduction to the use of XSL as a means to display XML in HTML browsers. Before continuing, I’d like to clear up a few points which I believe may have been confusing, largely due to a lack of rigorous clarity on my part.

Those of you who have been reading DevNewz for a few months already know that XML is one of the greatest things to come along. It is, therefore, ironic that the very features of XML which give it its strength and versatility also make it impractical for use as a Web authoring language: most mainstream browsers don’t know what to do with it. This will change. Before you know it, every Web browser on the planet will be able to handle XML just fine, but for now we must live with those that are equipped to deal with HTML.

When you have to work with HTML controls in a web-based application, 100% of which are populated and whose properties are set via dynamically-generated XSL transformations at runtime, you get to be pretty inventive. And one of the first things you learn is how NOT to “reinvent the wheel”. That is to say, if there is an example somewhere or some existing code that you can borrow from or re-use, there is “no shame and no blame”.

At EggheadCafe.com, we have resources that are added on a daily basis – both by member visitors and by the staff. These resources are searchable and are broken down by categories such as Hotlinks, Articles, Tips & Tricks, etc. Each evening , we have a script that’s kicked off by the NT Scheduler service at a time when traffic is normally low, that scours our resource database for the most recent items in each category.

I regard myself as a particularly fortunate “XML Dude”: About a year ago, I determined that, regardless of the amount of time I had in the day, and regardless of the fact that the company I worked for at the time had virtually no vision as to what XML could do to help solve their problems, I was going to spend some time — for ME — each evening, studying this new technology and learning how to use it.

SVG is built on top of XML in order to describe 2D vector capable graphics. XML stands for “Extensible Markup Language”. A full description of XML is best suited for a future article since it can be quite technical. To simplify XML, it is similar to HTML but provides greater customization of the tags. HTML is a set of pre-defined tags that are used to describe a web page. XML however, does not pre-define the tags.