Edit comment LC-1575 for Device Independence Working Group

Quick access to

Next: LC-1566

Comment LC-1575
Commenter: Al Gilman <Alfred.S.Gilman@IEEE.org>

Resolution status:

I don't understand the rationale offered.

Arbitrarily forcing the result of an 'expr' evaluation to 'true'
can't result in ill-formed XML if
the source was well-formed XML and conforms to the specification for
the module.

Getting garbage when a program runs amok is always possible, and
should be handled
as error control outside the scope of the DISelect module or its host
language. This
is in the OS, if I understand things right.

[reaction to the disposition of this comment: puzzlement.]


At 11:15 AM +0000 1/4/06, Roland Merrick wrote:
>Greetings Al, thanks for your comments on the content selection last
>call [1]. As part of this you include
>show/hide policy".
>The DIWG assigned this comment the identifier Gilman-9
>This mail documents DIWG's response to your comments.
>DIWG Response
>This issue is similar to Gilman-1. The problem we face is that an
>unrecoverable error in expression processing yields completely
>unpredicatble results, including XML that is invalid or badly
>formed. Allowing processing to continue could lead to effects
>similar to those we outlined in Gilman-1, including crashing or
>damaging the user's device, or showing completely inappropriate
>material to a minor.
>In contrast, the default value of the expr attribute is specified so
>the behaviour obtained by omitting it is at least predictable.
>In addition, by providing a default value, we ensure backwards
>compatibility when DISelect is added to a processor which processes
>existing markup written before the DISelect module was added.
>Regards, Roland
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 1575.html,v 1.1 2017/08/11 06:39:27 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org