When I interview somebody for a web-related technical position, I use to ask what the differences between GET and POST are. I have heard almost all creative (but wrong) answers about that, but very few guys have answered it quiet well.
Besides the HTTP specification where it is stated that the capital difference between those methods (GET is semantically idempotent, POST isn’t) and a lot of consequences, fortunately today I found an article (a finding they call) from the Technical Architecture Group (TAG) that will help to understand those consequences about the intrinsic difference by exposing well documented examples as to reinforce the specification points regards this topic. The whole TAG findings list is also available.
Architecture of the World Wide Web as a W3C Proposed Recommendation
These guys stated that the Architecture of the World Wide Web was a Proposed Recommendation. This is a very well documented reference for those who want to get the benefits of a number of recommendations from the W3C on their web sites or applications. This is also a TAG work.
XML Binary Characterization Use Cases
A lot have been said about the overhead XML impose to the communication layer in a number of architectures. Well, W3C is working on an initiative that goals in provide an alternative serialization method in order to alleviate this issue. Currently they are grouping all the different XML use cases, and ask the community to provide some cases they are missing. Personally, I found that they miss EDI/XML and ASN.1 XML use cases. I already emailed this observation.