W3C home > Mailing lists > Public > public-xformsusers@w3.org > April 2018

Re: output/label/help/hint/alert unification

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Tue, 10 Apr 2018 15:29:01 +0200
To: "Erik Bruchez" <ebruchez@orbeon.com>, "Steven Pemberton" <steven.pemberton@cwi.nl>
Cc: XForms <public-xformsusers@w3.org>
Message-ID: <op.zg9bqny2smjzpq@steven-xps>
I made these changes:

   * moved @class and @xml:lang to Common
     https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Common_Attributes

   * added a normative reference to xml:lang
     https://www.w3.org/community/xformsusers/wiki/XForms_2.0#ref-xml-lang

   * Created a Navigation attribute set containing @navindex and  
@accesskey, and added it to Control Common
     https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Common_attribute_and_content_sets

Please check.

Steven

On Mon, 09 Apr 2018 10:17:13 +0200, Steven Pemberton  
<steven.pemberton@cwi.nl> wrote:

> Following on from this, I see that "8.1 Common attribute and content  
> sets" lists Control Common, appearance, inputmode, incremental, UI  
> Common, xml:lang, class, navindex and >accesskey.
>
> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Common_attribute_and_content_sets
>
> Of these, all are mentioned on the elements where they are used, with  
> the exception of
>    class, xml:lang, navindex, and accesskey.
>
> I propose to move class and xml:lang into Common, and navindex and  
> accesskey into Control Common, so that it becomes obvious where they are  
> permitted.
>
> Steven
>
>
> On Sat, 07 Apr 2018 01:27:04 +0200, Erik Bruchez <ebruchez@orbeon.com>  
> wrote:
>
>> LGTM.
>>
>> I don't remember ever needing or even desiring the `src` attribute on  
>> any of those. I would favor dropping that.
>>
>> -Erik
>>
>> On Wed, Apr 4, 2018 at 4:49 AM, 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:29:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 April 2018 13:29:33 UTC