| The WWW kinda shows that, empirically, having a small set of verbs is a pretty darn good idea. CORBA and most call/return programming has shown that having to invent new verbs all the time ( getX(), getY(), getTopLeftCorner() ...) gets old really fast. The other thing a common set of verbs gets you is generic endpoints and, even more interesting, generic intermediaries. My approach is to let resource-y things be resource-y, and let verb-y things be verb-y. After all, language has nouns and adjectives and verbs, maybe there is a good reason for this diversity? So var:myhome/doorbell ring.
(Although I am highly skeptical of IoT, so somewhat wary of such an example).If you wanted to model this in a more resource-y way, you could doL var:/myhome/doorbell/ringing := true.
// delay
var:/myhome/doorbell/ringing := false.
That would also get you the ability to read the status of the doorbell.> I'm also convinced nobody actually knows what "REST" means Considering REST is the basis of the WWW, the largest and arguably most successful information system of all time, I would say (a) most people understand it "well enough" to work with it and (b) if we don't understand it, it behooves us to make an effort to do so. Because it's not like there haven't been other attempts to build something like the WWW, they just failed miserably. |