Ask Ms. GeekSpeak
By: Laurie Weaver
Member Columnist
Have you been trying to work with Information Technology, but your initiatives and patience grind to a screeching halt? Do the terms they use sound like so much gobbledygook? Do you ever get the sneaking feeling that IT professionals just may, in fact, have come from Mars? If so, you’ve probably run headlong into some common “GeekSpeak” roadblocks. The aim of this ongoing column is to help forms professionals and technology professionals overcome roadblocks by gaining mutual understanding, vocabulary, and context. So, if you need help with specifics, or if you’d just like to know more about a techie topic, email or post any and all questions to Ask Ms. GeekSpeak. On to this month’s topic: XML.
Dear Ms. GeekSpeak, Could you shed some light on what exactly is XML?
Sure! XML stands for EXtensible Markup Language. It is plain, vanilla text with a few conventions. It can be written with any word processor if you understand its syntax. XML is a way to put category labels around electronic data so it can be “parsed” by any system that is XML-aware. Parsed is just a fancy way of saying the system knows what to do with the data because it understands the XML tags (labels) around the data and its relationships. Why go with XML? Most systems that need data are XML-aware. Systems are usually part of, or attached to the “middleware” that moves data from one place to next. Here’s an example. An order is placed via e-form. The order data are parsed by a system that hooks into and checks the inventory database to ascertain sufficient stock. If sufficient stock exists, the system sends the parsed data on to the fulfillment center for shipping via its system. Hmm, still a little too Geeky?
Think of XML like setting up a file system. If you have files to place into folders, and folders to place into cabinets, you need to figure out what is related to what, and which method is best suited to sorting your files. Alphabetically? Historically? By business line? After you have decided on your filing scheme, you would then put labels on your folders and on your drawers so that you could place your files in the correct place in each cabinet according to the relationships in your filing scheme. In XML, we call this its schema.
Here’s an example of data, labels, and relationships: Let’s say BFMA wants to have a record of members’ names and email addresses.
<member>
<name>
<first> Laurie</first>
<last> Weaver</last>
</name>
<email>LAWW@capgroup.com</email>
</member>
In the example above we have a schema in which the main category of data is the “member”. It is known as the root element. It is also the parent element of two child elements – one element for “name” and one for “email.” This schema further splits the “name” element into two more child elements: one element for “first” and one for “last.” Family relationships are used to describe data relationships in XML. The elements “first” and “last” are siblings (same level of hierarchy). The elements “name” and “email” are also siblings. The elements “first” and “last” are also children of “name.” The elements “first” and “last” are also grandchildren of “member.”
To further clarify, in the above example, the name data of this entry is Laurie Weaver. The data are not nested between arrow brackets<>, but are contained between <name></name> elements in brackets. That is how the parsing system knows the difference between what is data and what is the category of the data. What makes XML really powerful is that while the conventions used to mark up our data and indicate its categories are standard, what we name our element categories and the relationships we create are strictly up to us.
If this topic has sparked your interest, and you’d like to learn more, here’s a link to the W3 School’s free online XML tutorial and overview.
http://www.w3schools.com/xml/default.asp
Remember, post here, or email Ask Ms. GeekSpeak if you’d like more information about XML, or any other “geeky” word or topic.


Recent Comments