Should the TokenizerText parser be extended to parse paths? so it could parse something like "<x:one>/<x:two>"
This would involve adding Path to Token as well some other changes, but does it make sense? Claude -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
