Did you really think I posted blind? Man, I hate it when people glom onto a concept without actually examining its implications....
Again, URIs are not a usability matter -- users should never interact directly with a URI value (no matter what anyone says in a paper). There is a mechanism in place for "permanent resources" (see the namespace spec). REST is a solution looking for a problem -- and the problem isn't there. As I pointed out, the simple matter of getting, say, a usage sheet (loads, torques, etc.) on a milspec 1 3/4 by 3/8-20 UNC bolt with a one-inch unthreaded shank, cross-drilled for safety wiring (trust me, this is a common-enough occurence in the real world) is going to result in an unfriendly URL, no matter what the ideals of something like REST are. It is an incredibly limited and short-sighted concept. Oh, but it does look good in an address bar, eh? That's not usability or accessibility -- that's contrived nonsense.
Did you really think I posted blind? Man, I hate it when people glom onto a concept without actually examining its implications....
Again, URIs are not a usability matter -- users should never interact directly with a URI value (no matter what anyone says in a paper). There is a mechanism in place for "permanent resources" (see the namespace spec). REST is a solution looking for a problem -- and the problem isn't there. As I pointed out, the simple matter of getting, say, a usage sheet (loads, torques, etc.) on a milspec 1 3/4 by 3/8-20 UNC bolt with a one-inch unthreaded shank, cross-drilled for safety wiring (trust me, this is a common-enough occurence in the real world) is going to result in an unfriendly URL, no matter what the ideals of something like REST are. It is an incredibly limited and short-sighted concept. Oh, but it does look good in an address bar, eh? That's not usability or accessibility -- that's contrived nonsense.