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

Re: standard components edits

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Mon, 16 Apr 2007 17:40:10 +0100
To: "Alex Milowski" <alex@milowski.org>
Cc: public-xml-processing-model-wg@w3.org
Message-ID: <f5br6qki87p.fsf@hildegard.inf.ed.ac.uk>

Hash: SHA1

Alex Milowski writes:

> The specification right now says that:
> <query>
>   declare namespace atom="http://www.w3.org/2005/Atom";
>   /atom:feed/atom:entry
> </query>
> will be treated as:
>   declare namespace atom="http://www.w3.org/2005/Atom";
>   /atom:feed/atom:entry
> I have it on my list to move that into a namespace.  Now, for XQuery,
> the following is also legal:
> <query>
>   declare namespace atom="http://www.w3.org/2005/Atom";
>   <atom:feed>{/atom:feed/atom:entry}</atom:feed>
> </query>

That's true of our component as documented, is what you mean, right?
Not XQuery itself.

> and so the query element must be able to contain elements.  This isn't
> the case for RelaxNG's compact syntax.  If we provided an input element
> for that step, it would have xs:string content.

I think that's the wrong way to go.  I'd much prefer to handle all
this consistently, and say it has to be

   declare namespace atom="http://www.w3.org/2005/Atom";

Then the xinclude trick will work for it as well.

- -- 
 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 Monday, 16 April 2007 16:40:33 UTC

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