[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Are URIs Resources? (WAS RE: Re: Non-info set)


RE:  Are URIs Resources? (WAS RE:  Re: Non-info set)
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@e...]

* Bullard, Claude L (Len) <len.bullard@i...> [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.

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.