- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Tue, 28 Nov 2017 21:23:26 -0800
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Received on Wednesday, 29 November 2017 05:24:20 UTC
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. -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_Expressi > ons_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 05:24:20 UTC