- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Thu, 01 Dec 2016 18:55:30 +0100
- To: "Erik Bruchez" <ebruchez@orbeon.com>
- Cc: XForms <public-xformsusers@w3.org>
Received on Thursday, 1 December 2016 17:56:15 UTC
On Thu, 01 Dec 2016 18:54:27 +0100, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > On Thu, 01 Dec 2016 18:39:55 +0100, Erik Bruchez <ebruchez@orbeon.com> > wrote: > >> - @context changes the current XPath evaluation context >> - @model to change the current model, which also can change the current >> XPath evaluation context >> >> So these two attributes are not very different and it probably makes >> sense to group them together. > > I tend to agree, but why in Core and not in Binding? Sorry, I meant: why in Common and not in Binding? > > Steven > >> >> I also found the old wiki about this feature, "context everywhere": >> >> https://www.w3.org/MarkUp/Forms/wiki/@context_everywhere >> >> -Erik >> >> On Thu, Dec 1, 2016 at 8:52 AM, Steven Pemberton >> <steven.pemberton@cwi.nl> wrote: >>> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Core_Attribute_Collections >>> >>> I can maybe understand why @model is part of the Core attribute >>> collection rather than the Binding collection, but @context I find >>> harder to >>>understand. >>> >>> Anybody able to enlighten me? >>> >>> Steven
Received on Thursday, 1 December 2016 17:56:15 UTC