From: Artur H. <ko...@pl...> - 2003-09-15 12:14:13
|
> > I'd like to look around and see what other > > alternatives we have. ENTITIES are > > starting to look more attractive to me again. > Yep. This also bothers me. But it's a trade. To me > entities are the way if you are prepared to give up > the notion that every document needs to be > independently validated and hence transformable. Sean, example code Cameron sent was not for modular documentation and file inclusion but for project customization and variables set. For this we can use one, external file defining all required entities we want to use in project. I think that for customization with variables inside documents entities are better solution than <xinclude>. As I see from Cameron's example <xicnlude> is just to complicated for this task. However for modular documentation and file inclusion <xinclude> is much better and give us flexibility we need. It seems to me very important that all documents are valid XML files, so all files can be edited in structural editors exactly the same way. I suggest to try implement environment for these to tasks as follows: 1. Customization with entities 2. Modularity with <xinclude> I would like to discuss this during our meeting. Artur -- Artur Hefczyc Open Source Developer http://generguide.sourceforge.net/ http://www.geotools.org/ http://wttools.sourceforge.net/ http://maven-plugins.sourceforge.net/ |