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

Re: Uncle! New alternate draft [comments on some of section 5]

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Fri, 21 Mar 2008 16:51:45 +0000
To: Norman Walsh <ndw@nwalsh.com>
Cc: public-xml-processing-model-wg@w3.org
Message-ID: <f5biqzghvfi.fsf@hildegard.inf.ed.ac.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Norman Walsh writes:

> | 5.1.3    "It is a static error (err:XS0023) for a p:pipe to appear in
> |           a default binding."  Why is this necessary?  The tableau for
> |           input declarations doesn't include p:pipe, so XS0044 does
> |           the necessary, doesn't it?
>
> 5.1.3 is in the wrong place; it should be at the end of 5.1.1.

It still doesn't need to be said at all.  The tableau for input port
declaration does not have a p:pipe child.
> Ok. But I also left in these two paragraphs because I think they make
> an important point:

I agree.

> | 5.7.3    Similarly, the second para after the tableau in this section
> |          needs to change to something like the following:
> |
> |          Also, retrospectively, we need to add bindings back in to the
> |          Environment and defining *in-scope options* and *in-scope
> |          variables* with reference thereto -- see separate message.
>
> I don't think you've sent that message yet.

No, I haven't.  Looks like being Monday now, sorry.

> |     If a select expression is given, it is evaluated as an XPath
> |     expression using the context defined in Section 2.6.1, Processor
> |     XPath Context, for the surrounding step, with the addition of
> |     variable bindings for all options whose declarations precede its
> |     declaration in the surrounding step's _signature_.
> |     If a select expression is given, it is evaluated as an XPath
> |     expression using the context defined in Section 2.6.1, Processor
> |     XPath Context, for the surrounding step, with the addition of
> |     variable bindings for all options whose declarations precede its
> |     declaration in the surrounding step's _signature_.
> |
> |     When XPath 1.0 is being used, the string value of the expression
> |     becomes the value of the option; when XPath 2.0 is being used, the
> |     value is an untypedAtomic.
>
> I think I did the right thing. I could be wrong. :-/

Well, you didn't include anything like

> |     If a select expression is given, it is evaluated as an XPath
> |     expression using the context defined in Section 2.6.1, Processor
> |     XPath Context, for the surrounding step, with the addition of
> |     variable bindings for all options whose declarations precede its
> |     declaration in the surrounding step's _signature_.

I'll include this in what I send on Monday, if I still think it's needed.

ht
- -- 
 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]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD4DBQFH4+ehkjnJixAXWBoRAm80AJj5gHr1PgY516Fo57dL6n+UjDilAJ4+gvk0
IEn7NLtt/5Fb0NVezgPASg==
=dszT
-----END PGP SIGNATURE-----
Received on Friday, 21 March 2008 16:52:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 March 2008 16:52:21 GMT