Clearing up some API ambiguity (@-syntax)

[reposting this as a new thread]

Looking at svn_opt_parse_path(), it's not clear to me how to interpret
the following input paths to that function:

   http://server/repos/path@{2006-03-05}
   http://server/repos/path@%7B2006%2d03%2D05%7D ({2006-03-05}, encoded)
   http://server/repos/path@%48%45%41%44 (HEAD, encoded)

In fact, it occurs to me that, in general, I don't understand if we
consider the @-and-stuff-that-follows-it to be part of the path, or just
some unencoded bits we slap onto the end of properly-formatted paths as
a way to flatten otherwise tabular input data at the command-line UI.

What about when the @ symbol itself is URI-encoded. Does that mean
something different from when it is not?

(Sorry. I feel like I should know the answer here already, but if I do,
it's crouching in some dark corner in the back of my mind.)

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand