And just to be clear on this: the `::` might not be a big deal if it happens after the `/` delimiter specifying the host part. So: http://localhost:8000::data

And just to be clear on this: the `::` might not be a big deal if it happens after the `/` delimiter specifying the host part. So: http://localhost:8000::dataset http://localhost:8000::dataset may break code that tries to discern the host name. However: http://localhost:8000/::dataset http://localhost:8000/::dataset Might not. Further, you could also reserve `_` in your scheme to refer to the default database: http://localhost:8000/_::dataset http://localhost:8000/_::dataset But as I mentioned in my previous reply, there may be unintended consequences. If this is something you guys want to do (and have HTTP/HTTPS URL compatibility) to check it out on different language/platform and see if your scheme breaks things. (And definitely see if Windows library assumes this; Windows file paths uses `:` as a reserved character)