Before I start, let me say that I fully approve the Collada idea, and I hope it actually survive the initial hype to become a useful standard. Additionally, I found the Maya collada import/export implementation a good starting point for my personal needs, so I'd like to thank Alias for sharing the source code with us.
That said, as I implement import support for Collada in our engine, I bumped into a number of issues with the latest version (September 4th) of the Maya exporter. Note that some of these issues probably apply the collada spec itself.
In particular, consider a scene with a sphere (sphere1) which is assigned to a default material (lambert1) which has two color textures (file1 and file2) assigned respectively to its color and incandescence attributes.
I saw a number of problems with this simple scenario:
1. Abusive name-mangling: the resulting textures get names like "#file1-DIFFUSE" or "#file2-GLOW": it appears that the actual attribute where the texture is assigned has been appended to the original file texture node name. As far as I can tell this is unnecessarily ugly, considering that additional XML attributes could have been added to indicate the material channel in use. This also causes the next problem:
2. No longer invariant: try to export the above scenario, then import it back. You'll see that the resulting file texture nodes will be called "file1_DIFFUSE". Export it back: the resulting texture will have a name like "file1_DIFFUSE-DIFFUSE".
3. The Lambert material node in Collada has the following type of param:
"<param name="DIFFUSE" type="ColorRGB" flow="IN">0.000000 0.000000 0.000000</param>". There's no obvious relationship with the assigned texture, instead, a (wrong) black color has been assigned.
By now I hope you realize that this is a ugly hack. This could easily be avoided by keeping the texture name from the Maya texture placement node (that's what the collada texture element means anyway), and avoiding the name mangling ugliness. Instead, indicate the channel assignment through the material param, eg:
"<param name="DIFFUSE" type="ColorRGB" flow="IN">#place2dTexture1</param>", or add a new optional attribute to each Collada element (e.g. "dccName="file1"). If you absolutely need to ensure unicity of collada textures by name mangling, at least choose some special separating character that is not typically in use by DCC apps (e.g. "#file1#name_mangled") instead of '-'.
Finally, where does the name GLOW come from? I checked in the 1.0 collada spec and saw no mention of it. (BTW is there a more up-to-date, alpha spec circulating?) Why is the Maya exporter using GLOW instead of the regular Maya term (Incandescence)? Glow is a completely different property of a material in the Maya software renderers, so please avoid switching names for no good reasons. IMHO you should stick to the actual name used in the DCC package unless the Collada spec clearly dictates otherwise... doing otherwise will just cause unnecessary confusion.
One last thing: I'd be interested in beta-testing the next exporter release if this is a possibility.