Lists Home |
Date Index |
* Bullard, Claude L (Len) <firstname.lastname@example.org> [2005-04-11 17:30]:
> So a URI is a function?
> No, a resource is a function per definition.
> A resource maps a URI to another URI in the case of a redirect.
> A URI is an argument to a resource?
> It makes better sense that way. A hyperlink is not a URI. A hyperlink is
> a function. A hyperlink can be a resource (and so can anything else except
> a URI).
Coming in late. Probably covered.
I'm using URIs a lot in Java programming. Pretty much where ever
I need a key. I'm building frameworks, and to keep things
extesnible, I'll use a URI keyed Map for data, for those things
whose type cannot be anticipated. (Perlish, Perlish, me.)
Thus, I tend to see URIs as arguments. This breakdown of
hyperlink as function, URI as argument is how I see it.
The distinction between the resource and the identifier was a
leap, but it's natural now. The distinction between a URI and
the code that resolves it was a leap, but it's natural now.
Unless it's unnatural. I'm coming in late.
Alan Gutierrez - email@example.com