Thanks for the suggestions regarding the exceptions. However, because MicroID places no restrictions on the semantics of a given EntityURI, I believe it doesn't make sense to validate these URIs and throw exceptions. Thus, I am leaning towards only having a Auth_MircoID_AlgorithmNotFoundException exception.
Thoughts?
Kurt,
I think what they mean is that you should validate that it is, in fact, a valid URI structure. URI's have their own RFC and a *very* structured setup. Examples of MicroID URI's that are invalid:
* joestump
* /foo.com/users/joestump
*
http://()*&^)(*&/users/joestump
*
ftp://ftp.example.com/users/joestump (A valid URI, but I don't think MicroID's should be verified over FTP servers)
Validate::uri() *just* looks at the structure of the URI to make sure it conforms to the RFC for URI's (along with, optionally, checking DNS and a few other things).
--Joe