Mark Baker: This is such a perfectly RESTful
system
I'm pleased to see such a ringing endorsement by Mark Baker of
XML Web Services. Unfortunately, we still have a semantic gap
where Mark uses the terms "browser" and "web services" in such a
limited way, but we can overlook that for now.
It's not XForms
The path to InfoPath trails over Sam and Mark. This is not XForms, but based on all other XML standards according to the techy FAQ.Anyone knows about an (open source?) XForms implementation that shares any of the drule-effect? Rembering the...
I use those terms in limited ways, because in practice they are quite limited. Of course I understand what they could be; I've implemented both.
That's twice recently that you've suggested that "Web services" is somehow this amorphous umbrella term under which all (or far too many) forms of solution can happily co-habitate. Just remember that the bigger the umbrella, the closer you are to the null style.
And, IMHO, Mark, you are looking at the problem domain from one dimension.
Limiting oneself to GET+POST is goodness. Perhaps a few more modes of interaction might make sense (I'd argue that it is asynch that rounds out a trio, but I recognize that this is open to debate).
There is another dimension. That's the dimension that WebServices has focused on. It is on representations. You have made it clear that you believe that RDF solves this problem. I spent a decade of my life on fine grained information models. (anybody remember AD/Cycle?) I'm unconvinced.