W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2005

DOM Interfaces & XInclude

From: Frans Englich <frans.englich@telia.com>
Date: Sat, 16 Apr 2005 14:53:24 +0000
To: www-dom@w3.org
Message-Id: <200504161453.24247.frans.englich@telia.com>


Hello,

What in my opinion reduces XInclude's usefulness is that it's not transparent 
to users and hidden at the parsing level, but is its own XML application 
which requires explicit invocation and attention. Hence, I think it can be 
argued that this usage/tool problem can hinder XInclude's usefulness and 
sub-sequently what it is here for.

However, in my opinion it is perhaps possible for the DOM interfaces to help 
in this area. For example, perhaps could DOM 3 Load and Save's LSParser have 
the option "process-xinclude" on its DOMConfiguration object which by default 
is disabled but when enabled, makes it process XIncludes. This could be 
combined with additional exception codes.

The XInclude specification extends the infoset, and it can be wondered if a 
DOM interface should cover that. To my experience no implementation have made 
use of that, and hence wonders what value coverage from a DOM interface would 
give, and if, if it's enough to overwin the increased burden for 
implementors.

I don't know if a DOM interface for XInclude is a good idea, but it would be 
interesting to hear people's thoughts on the matter.


Cheers,

		Frans
Received on Saturday, 16 April 2005 14:44:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:58 GMT