Hi Chris,
Sorry for moving so slow on this. I am a bit over-committed lately and
clearly this is not a subject I am that knowledgeable about, so it takes
some time to digest.
On Tue, 2006-02-07 at 12:11 +, Chris Burdess wrote:
So, does anybody else have any comments? Otherwise I think
Hi,
On Fri, 2006-02-03 at 12:46 +, Chris Burdess wrote:
Mark Wielaard wrote:
Arguably, if we change the name we lose any benefit of being able to
plug in a 3rd party datatype library implementation. It would be
trivial to duplicate just the part of the API we need in a private
Hi Chris,
On Thu, 2006-02-02 at 16:02 +, Chris Burdess wrote:
Arguably, if we change the name we lose any benefit of being able to
plug in a 3rd party datatype library implementation. It would be
trivial to duplicate just the part of the API we need in a private
namespace and use
Mark Wielaard wrote:
Arguably, if we change the name we lose any benefit of being able to
plug in a 3rd party datatype library implementation. It would be
trivial to duplicate just the part of the API we need in a private
namespace and use that for our own providers, but we would only be
able to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Burdess wrote:
This patch adds the RELAX NG pluggable datatypes library to Classpath.
This API, and an implementation of it, will be used by the W3C XML
Schema and RELAX NG JAXP validators currently in development.
[...]
Please let me know
Hi Chris,
On Tue, 2006-01-31 at 20:07 +, Chris Burdess wrote:
This patch adds the RELAX NG pluggable datatypes library to
Classpath. This API, and an implementation of it, will be used by the
W3C XML Schema and RELAX NG JAXP validators currently in development.
Please let me know
Mark Wielaard wrote:
This patch adds the RELAX NG pluggable datatypes library to
Classpath. This API, and an implementation of it, will be used by the
W3C XML Schema and RELAX NG JAXP validators currently in development.
Please let me know how you feel about this.
Could you explain a bit more
