W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2003

RE: Resource definition

From: Burdett, David <david.burdett@commerceone.com>
Date: Tue, 18 Feb 2003 17:32:47 -0800
Message-ID: <C1E0143CD365A445A4417083BF6F42CC053D1755@C1plenaexm07.commerceone.com>
To: "'Mark Baker'" <distobj@acm.org>, "Burdett, David" <david.burdett@commerceone.com>
Cc: www-ws-arch@w3.org
I agree that the act of turning on/off the switch is not a resource. I also
don't think that the HTTP PUT message that changes the state either is a
resource. Do you agree?


-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org]
Sent: Tuesday, February 18, 2003 5:33 PM
To: Burdett, David
Cc: www-ws-arch@w3.org
Subject: Re: Resource definition

On Tue, Feb 18, 2003 at 04:38:54PM -0800, Burdett, David wrote:
> In an earlier email, Francis McCabe said ...
> >>>... to use one of Mark's earlier examples, turning on a light switch.
> state of the light is a representable resource; no question. The action of
> flipping the switch is not so representable. The arm which is used to flip
> the switch is, however, a resource; although any representation of it in
> terms of bits is merely a symbol and not the real thing.<<<
> So is the act of moving the arm to turn on/off the switch a resource?

Well, I suppose you could make it one, but I'm not sure what that
would accomplish.

One doesn't need to talk about a switch, or the movement of a switch, or
even a toggleSwitch() method, in order to effect a state change with the
bulb, because the interaction style is one of *state transfer*; if I
want to turn the bulb on, I just do a HTTP PUT containing a
representation of the "on state" to the URI identifying the lightbulb.

Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis
Received on Tuesday, 18 February 2003 20:33:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:03 UTC