Here is a quick outliine of the functionality of my exporter.
Get the input from the interface for location to save the file, the name of the file, and a prefix for all the objects.
For each object in my selection list:
I get the objects history. I then step through the history and get the nodeType of each member of the history. If the nodeType is a skinCluster I write out the object in a certain format, if the nodeType is "locatator" I write the info out in a different format, and if I get to the end of the history without encountering either of the above nodeTypes, I write it out in a third format.
When I'm writting the data, I get different things for each type of object. There are some common things between all objects, like position in world space, and rotation in world space.
All of the special case data is written based on whether the object in question has custom attributes assigned to them i.e. if I want to tell the game that a certain object uses morph targets I apply a custom attribute called "morph" to the object, when my exporter encounters the "morph" attribute, it checks the value of the attribute and if it is 1, it writes the object out as a , if the value is 0 or it doesn't find the attribute, it moves on.
Using the above method, I am about to start writting an exporter that will be used to define our cameras, trigger sounds and particle effects, allow tagging of animations, all based on data inside of Maya. I will be using custom attributes assigned to special objects (probably locators) to write out animation script files, camera data files, and probably a couple other files as well.
Hope that gives you a little insight as to what is possible, and maybe a little pointer in the right direction to start.