The SRB URI scheme is similar to the http scheme. Only the domain home needs to be added to the userinfo section. The format "userName.domainHome:password" fits within URI standards. Note that authentication information in clear text is a security risk. The Jargon API has methods to allow a URI and password to be used separately, see FileFactory.newFile( URI, password ). Certain parts of a http URI are generally left optional. The SRB [will allow] anonymous userinfo/login, and also have a default port number.
SRB URI protocol:
srb:// [ userName . domainHome [ : password ] @ ] host [ : port ][ / path ][ ? query ]
where square brackets [...] delineate optional components, the characters :, /, @, ?, and . stand for themselves, and spaces should be ignored.
This example would point to and give access to the testfile.txt in testuser's home directory on srb.sdsc.edu at port 5555.
The second example would point to the root SRB directory on srb.sdsc.edu using an anonymous login and the default SRB port 5544.
The third example would, through the Zone Authority, give "testuser" access to the srbtest directory on the sdscdemo zone, which is currently at srb.sdsc.edu at port 8544. (At least at the time of writing it was there. With the Zone Authority, even if the host and port name the zone name will stay the same. This will make URI strings more permanent. Repositories can change hands but the users will remain blissfully unaware. Especially useful for the long term storage of digital libraries and paper citations, which are expected to remain valid and accessible for many years.)
This example uses anonymous login, the Zone Authority, and refers to the file by GUID. In this case the query portion is: if GUID equals "myVeryUniqueFileID" then return the filepath. GUIDs are by definition globally unique, so they can only refer to one file.