Routing definitions could support an encoding decoding function or declaration

[bryanrasmussen]

Why -

parts of routes might best be represented by a human readable text for example
ServiceStatus.html#!Driftsinfo/Address/Tv, Broadband & Mobile/

TV, Broadband & Mobile in the current situation breaks things, client side will definitely want to access the human readable path fragment, and it might be useful for SEO / other reasons to have the route be structured like this in the actual url.

'Encoding / Decoding of the url path fragment can be done on the project level, but then we miss out on having human readable urls in the address bar. For this reason it should probably handle encodable values somewhere in the router,

On edit: clarified issues.