- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Tue, 18 Dec 2018 22:53:57 +0100
- To: public-xformsusers@w3.org, "Steven Pemberton" <steven.pemberton@cwi.nl>
FYI, the overview I made is at https://homepages.cwi.nl/~steven/forms/examples/xforms-spec/elements.xhtml Steven On Mon, 17 Dec 2018 17:01:24 +0100, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > As part of action 2208, I'm creating an overview of all attributes, and > I have a couple of questions to raise before I make any changes to fix > them: > > 1. The bind element has > https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_bind_Element > > Common Attributes: Common > > Special Attributes: > ref > Optional model binding expression that selects the items on which to > operate. > If the attribute is omitted, the default is the in-scope evaluation > context. > nodeset [deprecated] > A synonym for ref. Ignored if attribute ref is present. > > While the repeat element has > https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_repeat_Element > > Common Attributes: Common, Appearance, Sequence Binding > > Presumably bind doesn't use "Sequence Binding", so that you don't use > > <bind bind="..." .../> > > But I can't really see a reason why @bind should be disallowed on <bind/> > > Can't we just use "Sequence Binding" for <bind/>? > > 2. Similarly with <submission/> > https://www.w3.org/community/xformsusers/wiki/XForms_2.0#submit-submission-element > > which lists ref and bind, rather than using "Single Node Binding". This > is surely an oversight. > > (There were a couple of errors in the overview tables that I have > silently corrected). > > Steven
Received on Tuesday, 18 December 2018 21:54:26 UTC