[
Lists Home |
Date Index |
Thread Index
]
doesn't at least some of this come from the dual use of a uri in the
html 'a' tag.
<a href="..."> and <a name="...">
one is reference (function if you like) while the other is a ... name.
takes a while to get your head around this when playing with rdf. in xul
the uri tells something (usually a tree) where to go to get a resource
and which parts of it are relevant.
in the resource the uri's are used to tag resources for retrieval.
in C we use pointers in a similar way: x is the pointer and it's name,
&something is where the value is, and *x is it's value.
pointers are the strength of C (and it's comprehension weakness) - uri's
seem to have a similar role.
rick
Bullard, Claude L (Len) wrote:
>It is the natural sense of it to me as well, although,
>given the names of arguments, I can conceive of a URI
>as a document itself (particularly if it names a name).
>
>If I think of the hyperlink as a function a) I win
>an old discussion with Goldfarb from a long time ago
>b) the framework of objects makes more sense to me
>as I can conceive of it as a control.
>
>Then the range is computed, not declared per se,
>and that fits the quantum logic model (the act
>of addressing a continuous resource is just
>a vector address).
>
>Now, does that fit what Fielding says. One
>thing that leaps out at me is that if the
>URI is not itself a resource or a representation,
>its space parallels the information space, that
>is, it is not itself part of the web by definition.
>If it is, then it should be addressable when in
>a document state (which of course, it is given
>an element container where it is just the value
>of the href attribute).
>
>The quantum logic approach fits.
>
>len
>
>
>From: Alan Gutierrez [mailto:alan-xml-dev@engrm.com]
>
>* Bullard, Claude L (Len) <len.bullard@intergraph.com> [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.
>
>-----------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>
>To subscribe or unsubscribe from this list use the subscription
>manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
>!DSPAM:425bd3ab311971829815068!
>
>
>
begin:vcard
fn:Rick Marshall
n:Marshall;Rick
email;internet:rjm@zenucom.com
tel;cell:+61 411 287 530
x-mozilla-html:TRUE
version:2.1
end:vcard
|
