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

RE: Re: [rest-discuss] Objects at REST...

• From: Len Bullard <len.bullard@u...>
• To: Peter Hunsberger <peter.hunsberger@g...>, Michael Kay <mike@s...>
• Date: Thu, 13 Mar 2008 13:15:40 -0600

Unfortunately for all of us who participated in the "what is a resource"
thread, it came down to "any *thing* addressable by a URI", so that didn't
shrink the space much in specifications where it is claimed the whole
universe is addressable.  We could have said "thing" or "whatever is between
the outermost parens" and been just as clear.

I do agree that in a programming context, object is overloaded.  Because a
resource is any identifiable thing, that is probably a better term if just
as noisy when implemented.

My sense of what Rick is talking about is naming but I haven't read the PDF
so I can be way off here.  I'm just looking at his examples.

len


From: Peter Hunsberger [mailto:peter.hunsberger@g...] 
 
On Thu, Mar 13, 2008 at 6:53 AM, Michael Kay <mike@s...> wrote:
> > However, I was more pointing to the fact that the word
>  > "resource" is really whatever you make of it, including
>  > objects (whatever you make "object" out to be). :)
>
>  It's pretty clear to me that the people who chose the words "object" and
>  "resource" were both trying to make the concepts as general as they could
>  possibly make them, and therefore by intent they are equivalent. If there
is
>  a difference, then I don't think it's one that the originators of the
terms
>  intended.

Sure, that's fair. However, these days, at least around here, everyone
and their brother ends up taking at least one programming course just
to graduate from high school.  As a result, for the casual observer
"object" carries with it semantic baggage that "resource" manages to
escape. That may not have been the "original intent", but that's the
modern reality.

-- 
Peter Hunsberger


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.