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

Re: empty document node or undefined

From: Alessandro Vernet <avernet@orbeon.com>
Date: Tue, 8 Apr 2008 11:39:31 -0700
Message-ID: <4828ceec0804081139i3c80e6fdxda85cdb06954614@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On Tue, Apr 8, 2008 at 8:13 AM, Norman Walsh <ndw@nwalsh.com> wrote:
>  If we leave it as is, as an empty document node, then child:: returns
>  an empty sequence. If we make it undefined then, like xsl:functions,
>  it'll be an error to refer to the context.
>  I think it's better/safer to make it an error. Especially since it
>  makes it possible for us to do something else in the future. If we
>  make it an empty document today, it'll be backwards incompatible to
>  change it. If we make it an error, it won't be.

Agreed. Since we are looking at cases where we don't have a context,
it indeed makes a lot of sense to set this up so expressions that
refer to the context raise an error.

Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Received on Tuesday, 8 April 2008 18:40:11 UTC

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