[xep-support] Validation fails on non-FO, Non-RX Namespace Attributes
David Tolpin
dvd at renderx.com
Thu Oct 10 22:05:49 PDT 2002
> I do not think that XEP should be complaining about
> any non-FO or non RX attributes. At a minimum, it
Eliot,
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
or
<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.
David
-------------------
By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
More information about the Xep-support
mailing list