Specification of routing syntax and semantics

We should create a *precise* specification of dotvvm routing behavior. It should consist of (informal) grammar of the syntax, how will that behave and some examples explaining it. Documenting extensibility points (custom constraints, custom routes...) may be a good idea.