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

Re: select in for-each and iteration-source

From: Norman Walsh <ndw@nwalsh.com>
Date: Wed, 06 Jun 2007 19:32:51 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87y7iwirq4.fsf@nwalsh.com>
/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| On 6/6/07, Norman Walsh <ndw@nwalsh.com> wrote:
[...]
|> No, I don't believe that's the case. If it was, then 'select' wouldn't
|> have the semantics of an XSLT 'select' and I'd want to change the
|> attribute's name.
|>
|> We decided to use 'match' on p:viewport where it's really important
|> not to process elements more than once. Everywhere else where we've
|> used select=, I assume we're using the standard XPath/XSLT select
|> semantics.
|
| I agree with your analysis but I'm sorry : THAT'S NOT WHAT IS WAS
| WRITTEN IN THE SPEC !

Bah! Fire the editor!

| [[
| The select expression, if specified, applies the specified [XPath 1.0]
| select expression to the document(s) that are read. Each node that
| matches is wrapped in a document and provided to the input port. After
| a node has been matched, its descendants are not considered for
| further matching; a node is passed at most once as input. In other
| words,

I can implement this if I must, but I'd rather not.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | We cannot put off living until we are
http://nwalsh.com/            | ready. The most salient characteristic
                              | of life is its coerciveness: it is
                              | always urgent, 'here and now' without
                              | any possible postponement. Life is
                              | fired at us point blank.--José Ortega Y
                              | Gasset

Received on Wednesday, 6 June 2007 23:33:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:53 GMT