So what is it exactly that we can do with xml, that we cannot do with URL encoded form data? Why get hung up on the type of the resource representation?
So you build your service and it accepts two kinds of representations: xml or UEFD. Either can represent the same resource with equal fidelity. Quibble with me about the hierarchical relationships you can represent in xml. You can represent hiereachies in UEFD using your own patterns (and interoperability really isn't the use case here).
Hugh Winkler holding forth on computing and the Web
- ► 2008 (21)
- ► 2007 (38)
- ► 2006 (39)
- ► 2005 (28)