Cart
[Home] [By Thread] [By Date] [Recent Entries]
"N E S T L E S, Nestles make the very best BARTOK!" Rather than pursue straightforward questions, we are derailed back to syntax vs data model, a debate in which a shift of a term is funny but not meaningful, so little progress is made. So I ask again: 1. Why does SOAP need a subset sanctioned at a higher level than its own specification? 2. Would the XML-SW serve that requirement whatever that requirement is? Otherwise, what is Liam's task and what would satisfy it? len From: Joshua Allen [mailto:joshuaa@m...] This is the most important point. Common syntax (unicodeWithAngleBrackets) is beautiful for data interop, "information exchange" or whatever you want to call it. The infoset people are concerned with interop at the data model layer rather than the syntax layer, though. Data model interop is important in its own scenarios; mainly programming model (e.g. DOM). True, the two goals are somewhat orthogonal and even contradictory, but XML is appealing in part because it does a good job of bridging these two worlds. To some people, that bridge is a problem which allows the two domains to pollute one another, but I'm more of a "glass half full" person.
|
