>At best, we can load the included tree with >readonly nodes, and excluded them at save time. Note that this is precisely isomorphic to the question of how to handle Parsed Entity References. Those too are generally rendered as readonly nodes, optionaly with an Entity Reference node to make re-serializing the document practical. Enumerate the usecases -- including ones that aren't immediately relevant to your particular application. Use those to drive requirements. Use those to drive the solution. That's the only way to get something general-purpose enough that it's worth standardizing. ______________________________________ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filkReceived on Friday, 22 April 2005 13:30:29 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 May 2007 00:17:17 GMT