- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Wed, 29 Nov 2017 12:07:23 +0100
- To: "Erik Bruchez" <ebruchez@orbeon.com>
- Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Received on Wednesday, 29 November 2017 11:07:57 UTC
On Wed, 29 Nov 2017 06:23:26 +0100, Erik Bruchez <ebruchez@orbeon.com> wrote: > Reading that part of the spec, it seems that whoever updated it (maybe > Nick?) intended to fix that, since the text at the beginning says: > >> If the property name is not recognized, the empty sequence is returned. > > I would say that we should update the table and make it return the empty > sequence in all cases where the property name is not recognized, whether > it is an NCName or a >QNameButNotNCName. I agree fully. Steven > > -Erik > > > On Wed, Nov 15, 2017 at 6:58 AM, Steven Pemberton > <steven.pemberton@cwi.nl> wrote: >> https://www.w3.org/community/xformsusers/wiki/XPath_Expressions_Module#The_property.28.29_Function >> >> property('foo') gives a fatal(!) exception. This seems to me a bit >> extreme, especially if you consider that event('foo') doesn't. >> >> Is there a reason why we care so much about non-existent properties? >> Isn't an empty string enough? >> >> Steven
Received on Wednesday, 29 November 2017 11:07:57 UTC