>I don't think that the average user should be using XNI directly.
I'd agree in principle. But this may require that some of the things now available only via XNI be made available in a consumer-friendly form. (For example, reintroducing top-level controls for incremental parsing...) >Let's make a convenient grammar caching implementation for >people to use with the parser configuration implementations >that we provide and design the internal APIs appropriately. Works for me. And/or put an API on the grammar-cache so folks can plug in their own, just as we did for Entity Resolvers (partly with the intent of allowing folks to cache instance documents). Sounds like folks are headed the right direction... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
