W3C home > Mailing lists > Public > public-xformsusers@w3.org > October 2016

Re: output@value

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Sat, 22 Oct 2016 09:48:07 -0700
Message-ID: <CAAc0PEWC_FT5RpNJX1pTD7P9Ox-Fy3kh+OmtRwgi2940_orbwA@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
I agree with removing that exclusivity restriction.

This should pose much of a compatibility issue as it wouldn't make sense,
in an implementation which follows XForms 1.1 strictly, to have both a
binding and @value, unless the @value was placed there by accident.

-Erik

On Thu, Oct 20, 2016 at 2:58 AM, Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The
> _output_Element
>
> "The output control renders the value of an instance node by using a
> Single Item Binding, or evaluating the expression in the value attribute.
> If both are present, value is ignored."
>
> This is the oposite of what we decided yesterday as the general case,
> where if you have both, the @ref is used as context, but @value is used for
> the actual value.
>
> Should we change this for output, to make it match the general case?
>
> Steven
>
>
Received on Saturday, 22 October 2016 16:48:56 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 22 October 2016 16:48:57 UTC