I'm running XXE Standard Edition V2.8.

The behaviour that I described is *not* related to those xi:include elements 
that XXE manages, eg. when the value of the xpointer attribute use the element 
scheme. Those are, as you state, transparently resolved.

But I happen to use other editors, mostly emacs+psgml or emacs+nxml, and I also 
like to take advantage of the XPointer scheme in XInclude.

I've been unable to reproduce the behaviour that I described; when I insert an 
xi:include element now, all attributes appear as expected in the attribute edit 
tab. The best explanation that I can think of is that I had been editing a 
document using an older costumization (with the old content model for 
xi:include) and then updated the costumization driver file. XXE is caching 
document type information, and won't, of course, discover that I changed the 
content of the costumization driver file.

BTW, is there an easy way to trace XXE's resolution of doctype declarations and 
schema references?

kind regards

Peter Ring



> -----Original Message-----
> From: Hussein Shafie [mailto:hussein at pixware.fr]
> Sent: 21. januar 2005 14:05
> To: Peter Ring
> Cc: xmleditor-support at xmlmind.com
> Subject: Re: [XXE] XPath-Expressions with XInclude and XPointer
>
> Peter Ring wrote:
> > While XXE carps on and does not resolve XIncludes using the 
> XPointer scheme, they are preserved and round-tripped, as far 
> as I can see. That is, while you can't see and edit the 
> resulting infoset in XXE, you can at least edit the XPointer 
> expression.
> > 
<snip /> 
> 
> This is no longer true. Yes, XMLmind XML Editor used to use fragment 
> identifiers in XInclude hrefs because this was what was 
> mandated in an 
> early version of the XInclude.
> 
> But, as of V2.7 (August 20, 2004), we have changed our 
> implementation to
> conform to the recommendation.
> 
> See http://www.xmlmind.com/xmleditor/changes.html.
> 
> Excerpts of this file:
> ~~~~~~~~~~~~~~~~~~~~~~~
> 
> The XInclude elements generated by XXE to represent modular 
> document now
> conform to the latest W3C candidate recommendation (13 April 2004).
<snip />

Reply via email to