Re: Please allow "yes" and "no"

Krzysztof Maczyński <1981km@gmail.com> writes:
>> Probably it is safer to wait until XML Schema 1.1 *do* this change.
>> Then XProc could be updated to take this new feature into account
>
> I'll email them as well. But from what kind of danger do you mean to
> be safer? Seeking full alignment with XML Schema boolean values in
> this attribute apparently wasn't a goal for XSLT or XQuery.

XSLT's decision to use yes/no precedes XML Schema and really couldn't
be changed without massive hassles due to backwards compatibility.

XQuery doesn't give the user control over serialization in the
standard, so they never crossed this bridge.

XProc doesn't have any legacy, and we've tried elsewhere to stick to
values that are XSD types. It didn't seem unreasonable to extend that
design to cover the serialization options.

> If this small change is
> omitted now, introducing it in a later version of XProc (if any) may
> take very long and have diminished benefit then. I'm asking you
> therefore to reconsider.

Making this change would almost certainly require us to go back to
Last Call. I don't (speaking personally) see this change as valuable
enough to warranty such a delay.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Idealism is what precedes experience;
http://nwalsh.com/            | cynicism is what follows.--David T. Wolf