Re: XProc comment

"Alex Brown" <alexb@griffinbrown.co.uk> writes:

> For the "validate-with-relax-ng" step, an option controls whether
> "dtd-compatibility" is selected.
>
> This specification (http://relaxng.org/compatibility-20011203.html)
> defines three features, which each have two conformance levels. So I do
> not think it is sufficient to select this with a simple boolean value.

I've given this some more thought and done a little bit of
investigation and I think you're probably right.

> Maybe have instead something like:
>
> dtd-compatible-id-conformance "0" | "1" | "2"
> dtd-compatible-attribute-defaulting-conformance "0" | "1" | "2"
> dtd-compatible-documentation "yes" | "no"

I don't think that the documentation support in the DTD Compatibility
specification has any bearing on validation, so I think we can ignore
that.

But it is probably worth offering independent support for the ID
conformance and attribute value defaulting clauses.

Perhaps

  dtd-attribute-values = true|false
  dtd-id-idref-errors = true|false

If dtd-attribute-values is true, the resulting infoset should be
augmented with default attribute values.

If dtd-id-idref-errors is true, then the step fails unless all of the
ID/IDREF/IDREFS constraints are satisfied.

I propose that the default should be "false" in both cases.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | I have seen the truth and it makes no
http://nwalsh.com/            | sense.