W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > June 2007

Re: Proposed dynamic error: a select that doesn't select nodes

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 01 Jun 2007 16:31:42 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87tztr4dsh.fsf@nwalsh.com>
/ "Innovimax SARL" <innovimax@gmail.com> was heard to say:
| hum....
| for me a
|   <p:input select="/div">
|     <p:empty/>
|   </p:input>
| should give an empty sequence and not a dynamic error

Yes, fair point. That's going to cause a dynamic error later if the
input isn't allowed to be empty, but it's not an error on the face
of it.

| I also agree that
|   <p:input select="3 + 2">
|     <p:empty/>
|   </p:input>
| should raise a dynamic error and even a static one because *IT WOULD
| NEVER SELECT A NODE SET* whatever the input

I agree that it's an error that can be detected statically, but do we
want to insist that implementations MUST detect it statically?

I don't feel strongly about it.

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | Endurance is frequently a form of
http://nwalsh.com/            | indecision.--Elizabeth Bibesco

Received on Friday, 1 June 2007 20:31:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:43 UTC