Re: XInclude and DOM
| From: | Adam Trachtenberg | Date: | Tue, 06 Jan 2004 19:17:18 +0000 |
| Subject: | Re: XInclude and DOM | ||
| References: | 1 | Groups: | php.xml.dev |
| Request: | Send a blank email to php-xml-dev+get-278@lists.php.net to get a copy of this message | ||
On Jan 6, 2004, at 1:36 PM, Rob Richards wrote:
After a document has been processed via xinclude, how should xinclude nodes be handled in dom? the origional xinclude elements remain in the document as XML_XINCLUDE_START and XML_XINCLUDE_END nodes, but are ignored when serializing. Should these be treated as standard ELEMENT nodes in regards to the object, methods and properties while navigating the processed tree?My natural inclination is to ignore them under the theory that the point of XIncluding content is to make the resulting document identical to how it would have looked if it was actually one physical XML file. But I can't say I've spend much time mucking around with XInclude, most of my XML include use is Schema includes.
Have not found any references to these node types and they arent part of the dom specs so really not sure how these should be handled.What does the major Java, Perl, Python extensions do here? Maybe the best behavior is to mimic general usage even if it's not an official standard? -adam -- adam trachtenberg adam@trachtenberg.com