- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Tue, 10 Apr 2018 15:53:06 +0200
- To: public-xformsusers@w3.org, "Steven Pemberton" <steven.pemberton@cwi.nl>
(One omission in the table of attributes: label also carries @mediatype) One more issue about unification: label, hint, help and alert all allow text content: <label>Date</label> but output doesn't: not <output>Date</output> but <output value="'Date'"/> (funnily enough I only used this today, in order to put a class on it; see my earlier post on viewing data in XForms). Do we want to do this? Steven On Wed, 04 Apr 2018 13:49:33 +0200, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > Summary of the attributes on the 5 elements > > All 5 carry > Common (=id, model, context, foreign attributes including event > attributes) > appearance > Binding (=ref, bind) > > The other elements carry these extra attributes: > > output > UI Common (=label/hint/help/alert) > value > mediatype > > label > value > > help > Linking (optional host-language attributes, e.g. HTML @src) > > hint/alert > [none] > > So my idea for unification is: > > On all > Common (=id, model, context, Foreign) > appearance > Binding (=ref, bind) > value > mediatype > > On output only: > UI Common (=label/hint/help/alert) > > > And that leaves us with Linking, which I am not sure what to do with, > and maybe is worth dropping. > > Comments? > > Steven > > > > On Wed, 28 Mar 2018 12:18:13 +0200, Steven Pemberton > <steven.pemberton@cwi.nl> wrote: > >> These 5 elements are very similar, but not exactly the same. >> >> For instance, output and label both have @mediatype, but the others not >> (for instance text/html as a mediatype if allowed would also be handy >> for <help>). >> >> My feeling is that all 5 elements are essentially the same, just used >> in different ways/contexts. >> >> So, should we just unify them? >> >> Steven
Received on Tuesday, 10 April 2018 13:53:35 UTC