So, reading up on URIs today to see if there is some way in the .NET framework to get access to a "default path separator" character so I wouldn't have to hardcode / when constructing URLs. It doesn't look like anything that specific is available, however, while reading up on URI Fragments on wickerpedia I came across this, which is cool - if not particularly useful:

In URIs for MIME application/pdf documents Adobe PDF viewers recognize a number of fragment identifiers.[9] For instance, a URL ending in .pdf#page=35 will cause Adobe Reader to open the PDF and scroll to page 35. Several other parameters are possible, including #nameddest= (similar to HTML anchors), #search="word1 word2", #zoom=, etc. Multiple parameters can be combined with ampersands: http://example.org/doc.pdf#view=fitb&nameddest=Chapter3.