From: Sean W. <se...@ya...> - 2003-09-15 12:30:06
|
--- Artur Hefczyc <ko...@pl...> wrote: > Hi, > > > The bad new is that XXE doesn't recognise the > xpath. :( > In what sense it doesn't recognise xpath? Does it > try to > resolve it in some way? Should it just leave > <xinclude> element > as is? > > > The other problem is that the <xinclude> tag > requires 2 lines of text for one > > variable, compared to an ENTITY which only takes > one word. > Yes, you are right. While it is acceptable that > inclusion of external file > takes two lines of code, it does not well look if > simple variable takes > that amount of space. Readability is decreasing: > The purpose of &projectname; project.... (looks > fine) > The purpose of <xi:include > href="resources/generconfig.xml#xpointer(/generconfig/varset/var[@name='projectname']/text())"/> > project.... (looks ugly) > > > I'd like to look around and see what other > alternatives we have. ENTITIES are > > starting to look more attractive to me again. > Cameron, I think we should look for another editor > in place of xxe not because > of <xicnlude> and <xpath> support but rather because > of good support for entities. I think that a basic XML Editor, that does not use CSS to try give WYSIWYM is a sound platform. My thinking is first to get the foundation working. If it works according to standard, then any XML Editor worth its salt will work. The problem with trying to use a WYSIWYM editor is that it adds a level of complexity that keeps detracting development from solving foundation problems, like when to use entity and when to use xinclude. My 2 cents. Sean __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |