>
> I can't speak for others, but your points accurately reflected my general
> thinking. I espcially liked the www.my-home.org examples as an
application
> where action verbs are a much more natural way of modeling the system.
For me, those example are not 'natural', they are merely 'procedural'. A
noun/object/resource based approach isn't any more natural either - it is
just a different way to doing things and it has different characteristics.
Let's follow this example through.

1 Verb-oriented URLs
> For example, a program to control devices in my house might look like
this:
>
> http://www.my-home.org/connect-to-central-computer
> http://www.my-home.org/air-conditioning/on
> http://www.my-home.org/air-conditioning/adjust-temp?value=68
> http://www.my-home.org/stereo/on
> http://www.my-home.org/stereo/play-cd?cd=Timeless-Serenity

Question: by 'adjust-temp' do you mean 'add 68 degrees' or do you mean 'set
equal to 68 degrees'?
Question: how do you get the current temperature or the current album?

Additional URLs might look like:
http://www.my-home.org/disconnect-from-the-central-computer
http://www.my-home.org/stereo/powerDown
http://www.my-home.org/stereo/play-cd?cd=none
http://www.my-home.org/air-conditioning/turnOffNow
http://www.my-home.org/air-conditioning/reportTemp


2 Noun-oriented URLs
> For me it is more program friendly to have something like:
> home.server = "http://www.my-home.org/";
> home.put("air-conditioning/power,"on");
> home.put("air-conditioning/temp","68");
> home.put("stereo/power","on");
> home.put("stereo/current-album","Timeless-Serenity");

> If you wanted api based access, it wouldn't be hard to define objects with
> named properties where each property maps to a URI. You could then have
the
> client do something like:
> home.airConditioner.power = "on";
> home.airConditioner.temp = "68";
> home.stereo.power = "on";
> home.stereo.album = "Timeless-Serenity";