• From: Mike Sokolov <sokolov@i...>
• To: George Cristian Bina <george@o...>
• Date: Fri, 18 Sep 2009 09:26:10 -0400

Well that is interesting.  As in so many other cases, I can see I'm not 
the first one with this problem.

I am reluctant to introduce a patched Xerces only for this case, 
although being tied to a DTD is really painful in various other ways, so 
maybe it would be worth it to take on the support of that.

George, yours seems like a very pragmatic patch, and if Xerces were 
being developed according to a democratic process, I'd certainly vote to 
include it in the main branch at this point! Consider that more than 
three years later, the original intent to support xml:id more broadly in 
Xerces seems to have been dropped.

-Mike

George Cristian Bina wrote:
> For enabling xml:id support in Xerces for XInclude you can use the 
> patch I posted in the following issue report:
>
> http://issues.apache.org/jira/browse/XERCESJ-1113
>
> We use this in oXygen for some years.
> I agree that a separate xml:id processor in Xerces will be better but 
> until that will be available the patch solves very well the XInclude 
> issue.
>
> Best Regards,
> George

• References:
  • Re: is an xml:id attribute a "DTD-determined ID"?
    • From: Mike Sokolov <sokolov@i...>
  • Re: is an xml:id attribute a "DTD-determined ID"?
    • From: Michael Glavassevich <mrglavas@c...>
  • Re: is an xml:id attribute a "DTD-determined ID"?
    • From: Michael Ludwig <milu71@g...>
  • Re: is an xml:id attribute a "DTD-determined ID"?
    • From: George Cristian Bina <george@o...>