Quick TMQL question re namespaces

Hi Folks,

After thinking about TMQL and path navigation in general quite a bit this week, how would you resolve conflicts with pre-defined axis names vs. user-defined role names?  In TMQL as it stands, since it's really based on a particular TMRM->TMDM mapping, can this happen?

I know I currently have only two places where this is an issue in my TMRM-based system, but, if I were to implement TMQL on top of it, I would ideally like to be able to do so without the TMDM baggage and operate more directly on the proxy roles themselves.

Namespace qualification is one way to do this, so I guess I could leverage the same type of thing Lars H already mentioned in the t1 / tmdm:types vs t1 / types example where tmdm would be the default prefix unless it was explicitly  requested.  However, in the scenario in my head, you'd still have the same need to redefine the default namespace you occasionally do in XML so you could say the default namespace was nil and then you would be required to fully-qualify the built-in axes so you could be sure to avoid conflicts.

I had an admittedly brief skim through the latest slides, the CTM spec and the previous TMQL drafts, but I couldn't really see any support for doing something like this.

Any thoughts, or is this an impossible scenario?

Cheers,

ast
--
Andrew S. Townley <[email protected]>
http://atownley.org