Update: Other useful quotes from Tim Bray...
I’m deeply suspicious of “standards” built by committees in advance of industry experience, and I’m deeply suspicious of... multiple layers of abstraction that try to get between me and the messages full of angle-bracketed text that I push around to get work done.And Sean McGrath writes...
The whole WS standards thing has more moving parts than a 747. Much of it recently invented, untested and unproven in the real world... there are no exceptions to Gall's Law:Originally I quoted jeff schneider writing..."A complex system that works is invariably found to have evolved from a simple system that worked."
I am of the opinion that the WS-* spec teams are doing a severe disservice to the community by releasing these specifications without also identifying the best practices. In my opinion, it is no longer acceptable to release paradigm changing specifications without also releasing an implementation or best practice guide to go with it.I could not agree more. The argument could be made there is a good bit of experience with these particular verbs. I think that argument is implicit (read below). But such an argument would be invalid. By far the majority of experiences with these verbs is unrelated to the kinds of systems this spec is intended for. Clearly this kind of a shift should be accompanied by references, examples, and best practices.
Standardizing verbs is good. I was a bit curious why the group didn't create a 'verb extension' or 'verb introduction' mechanism, but rather just 'hardcoded' a handful of verbs.I am thankful they did not. Better to get experience with a fixed set and expand on that later if warranted.
No comments:
Post a Comment