XML for Beginners, Part 1: Structured Documents, Plain Text, and Rendering
PrefaceWho in the world is Dick Baldwin?
Hello! My real name is Richard Baldwin, although most people call me Dick.
Although I have authored numerous articles on XML in the past, this is the first XML article that I have authored under my new XML relationship with EarthWeb.
I maintain a consolidated index of hyperlinks to all of my XML articles at my personal website so that you can access earlier articles from there.
Not a new relationship
My relationship with EarthWeb is not a new one. I have been publishing Java and Python articles on an EarthWeb site for quite some time. If you have any interest in Java or Python programming, please look me up there as well.
I am a college professor, private consultant, and technical author. Like many in my field, I spend twelve to fourteen hours each day at the keyboard of my trusty Dell laptop.
I am very pleased to be here, and I promise to do my best to provide an XML resource that you will find both useful and productive. -- So, read on!
IntroductionThe title of this article is XML for Beginners, Part I, and it really is meant for beginners in XML.
Experts skip this article
Those of you who already know a lot about XML can skip ahead to something more challenging, such as some of my articles on XSL, for example. You will find links to all of my articles at my personal website.
Beginners, keep reading
Those of you who are just getting your feet wet in this area (and may have found the XML water to be a little deep), keep reading.
I will throw you an XML lifeline in this and the next few articles.
No jargon allowed
Computer people are the world's worst at inventing new jargon. XML people seem to be the worst of the worst in this regard.
Go to an XML convention and everything that you hear will be X-this, X-that, X-everything. Sometimes I get dizzy just trying to keep the various X's separated from one another.
In this explanation of XML for beginners, I will try to avoid the use of jargon, or will at least explain the jargon the first time that I use it.