And that would be great if it didn't inadvertently break certain browsers, proxies, web servers and parameter parsers. Back in the day the advice was you could

And that would be great if it didn't inadvertently break certain browsers, proxies, web servers and parameter parsers. Back in the day the advice was you could use & or ;. TBL had subtly different semantics in mind for them though: apparently ; was meant to represent some coordinates in some spacial system while & was the normal query parameter separator. Somewhere along the line, for some reason, everyone settled on & and the web ossified around the assumption that was the only character that ever gets used.