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

Re: Match Pattern Proposal

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Thu, 02 Nov 2006 13:58:59 +0000
To: Norman Walsh <Norman.Walsh@Sun.COM>
Cc: public-xml-processing-model-wg@w3.org
Message-ID: <f5b64dyhrvg.fsf@erasmus.inf.ed.ac.uk>

Hash: SHA1

Norman Walsh writes:

> / Alex Milowski <alex@milowski.org> was heard to say:
> | For a number of reasons--including support of streaming processors and
> | consistency between viewports and other constructs--I believe we should
> | restrict XPaths to match patterns for everything but parameters.  As
> | such, here is what I think is a cohesive proposal:
> I'm not convinced.
> When I write a select expression on input, for-each, or viewport, I'm
> thinking "Ok, I've got this document in my hand, what nodes do I want
> to select out of it." I think it is more natural to write a select
> expression than a match pattern.

I've been using viewport for some years now, in the MT Pipeline
language, and

 a) It's hugely useful;
 b) It uses match semantics.

I find it _much_ more natural to write

 <xx:viewport attrNameAtIssue="div">
  . . .

than to write

 <xx:viewport attrNameAtIssue=".//div">
  . . .
which I believe is what I'd have to write if we go with 'select'

- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)

Received on Thursday, 2 November 2006 14:00:09 UTC

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