oxf:validation processor does not support substitutionGroup attribute

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

oxf:validation processor does not support substitutionGroup attribute

Stephen Bayliss

I get an error if I try and validate using oxf:validation with a W3C XML schema that uses the substitutionGroup attribute on an element.

 

Some questions…

1)       What parser does oxf:validation use?

2)       Is it possible to plug in alternative parsers?

3)       Is it the same parser that would be used by adding schema-href to inputs of other processors?

 

Steve



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: oxf:validation processor does not support substitutionGroup attribute

Erik Bruchez
Administrator
Stephen Bayliss wrote:
> I get an error if I try and validate using oxf:validation with a W3C XML
> schema that uses the substitutionGroup attribute on an element.
>
> Some questions…
>
> 1)       What parser does oxf:validation use?

 From what I can tell, MSV is used in both cases, through
MSVValidationProcessor.

Before there was MSVValidationProcessor, we used ValidationProcessor,
which was delegating to either RNGValidationProcessor or
W3CValidationProcessor. The RNG validator used Jing, and the W3C one
used MSV. For some reason, we then switched to using MSV in all cases.

> 2)       Is it possible to plug in alternative parsers?

You could add a processor declaration for RNGValidationProcessor in
custom-processors.xml, and this way use Jing. If you are looking for yet
another validator, you will need to write some Java code. There is no
unified API for validators AFAIK.

> 3)       Is it the same parser that would be used by adding schema-href
> to inputs of other processors?

Yes, the Pipeline processor appears to be using MSV in both cases,
through the MSVValidationProcessor class. However it does not use the
indirection in processors.xml and directly uses MSVValidationProcessor.

I think the architecture for those validation processors could be
improved somewhat. A couple of things come to mind:

o Pipeline processor should use an indirection in processors.xml
o Validation processor should be pluggable

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws