Re: [xep-support] Validation fails on non-FO, Non-RX Namespace Attributes

From: David Tolpin (
Date: Thu Oct 10 2002 - 22:05:49 PDT

> I do not think that XEP should be complaining about
> any non-FO or non RX attributes. At a minimum, it


good point, but the purpose of the validation pass is make
sure that only things explicitely allowed are passed to the kernel.

The only element for which non-fo attributes are explicitly allowed
by the recommendation is instream-foreign-object. Everything else
is non-compliant; rx extensions are passed through just because
we know what they are for; it is better to stop everything else
than to let stylesheet bugs through.

If you have non-compliant stylesheets with extensions exernal to XEP
and want to see the results, just turn validation off.

java com.renderx.xep.Driver -DVALIDATE=false


  <option name="VALIDATE" value="false"/>

in the configuration file.

> should be reporting the full-qualified attribute name
> in the validation report.

A good point. Thank you.


By using the Service, you expressly agree to these Terms of Service

This archive was generated by hypermail 2.1.5 : Wed Dec 18 2002 - 08:41:28 PST