On Sat, Feb 21, 2009 at 3:07 PM, Michael Glavassevich <mrgla...@ca.ibm.com> wrote: > Hi Paul, <snip/>
> I'm not sure what qualifies as an XPath compliant regex but the regex > support in Xerces exists for the XML Schema validator which is only > concerned with the grammar defined in the XML Schema specification [3]. I believe they are defined the same way, though neither references the other. I'll confess that I came to Xerces because a friend who has also implemented SPARQL told me that Xerces had a compliant Regex. After looking into it more, I realize should have been considering Xalan. But then I discovered they haven't actually implemented that function yet. > There are other processing modes supported by this code but Xerces never > uses them and we haven't made an effort to maintain them. It's also very old > code (at least April, 2000 [4] and probably even older than that) so would > be surprised if it conformed to another spec that didn't exist yet at the > time it was originally written. I have no idea why it's in a sub-package of > org.apache.xerces.impl.xpath (a question to ask one of the original > developers) but has nothing to do with Xerces' XPath support (also for the > XML Schema validator and only supports the subset required for identity > constraints). This was certainly enough to have me consider my options. I spent the afternoon out there checking out the implementations of XPath. The only one that appears to have fn:matches implemented is Saxon. But after running a series of tests over the Xerces internal RegularExpression and the Saxon one, I've found that Xerces is significantly more compliant. So I guess I'll have to stick with Xerces and put in some strict regression testing in case anything ever changes. >> I've never done more than basic stuff with xerces, so I don't even >> really know what constitutes the "public" API. (any tips there?) > > A starting point is here [5]. The docs for the classes which aren't part of > the public APIs explicitly say that they're internal. Ah, OK. I've gone through here before, and am familiar with these interfaces. I realize now that these are the ONLY ones I should know, and it was a silly question to ask. Thanks though. Regards, Paul Gearon --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org