text, code, data

It's the season for confession. First Tim Bray reveals a dirty secret: "a lot of input data these days is XML...in most cases, I use the perl regexp engine to read and process it." Then Sean McGrath fesses up to his Python habit: "I know I should be invoking a WF [well-formed] parser on the content.xml string but gee Ma, I've got work to do." ... [Jon's Radio]

In our last extension of the XMLMap we closed with a discussion of ontologies and topic maps, both concepts for expressing semantics of resources. I received many questions on the rather abstract nature of these concepts, as well as their practical applications and implications. This installment tries to explain topic maps. [eXploringXML]

Extensible Markup Language (XML) is a double-edged sword for application designers. XML has become the ultimate data bridge for joining disparate applications. But like actual makeshift bridges that are flexible enough to work in jungle terrain, XML can be somewhat precarious.

There are times to let your creativity flow and push XML’s flexibility to the limit. There are other times when it’s better to pull back and stay with what you know works. [Source: Builder.com]