Fwd: [widgets] Re: i18n comments:

Hi All,

Marcos has completed all of the changes to the Widget Packaging and  
Configuration (P&C) spec related to the new <span> element and dir  
attribute and the removal of the ITS references. The latest Editor's  
Draft that includes these changes is:

[ED]  http://dev.w3.org/2006/waf/widgets/

Would the I18N WG please review the changes and submit comments to  
public-webapps?

Given the last formal publication of this spec was a CR and we  
consider the <span> and dir changes as a replacement for ITS, our  
plan (once we have sufficient implementation data) is to move  
directly to PR and not publish another LC or CR. As such, we want to  
know if the I18N WG sees any issues with [ED].

-Thanks, Art Barstow

Begin forwarded message:

> From: Arthur Barstow <Art.Barstow@nokia.com>
> Date: April 6, 2010 10:05:33 AM EDT
> To: Addison Phillips <addison@amazon.com>, Marcos Caceres  
> <marcosc@opera.com>, Felix Sasaki <felix.sasaki@fh-potsdam.de>,  
> "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Richard Ishida  
> <ishida@w3.org>
> Cc: public-i18n-core@w3.org, public-webapps <public-webapps@w3.org>
> Subject: [widgets] Re: i18n comments:
>
> Hi Marcos, All,
>
> Has the I18N Core WG reviewed Marcos' latest proposal? If yes,  
> where can we find their comments; if no, when can we expect a reply?
>
> -Art Barstow
>
> On Mar 30, 2010, at 11:07 AM, ext Marcos Caceres wrote:
>
>>
>>
>> On 29/03/10 5:16 PM, Phillips, Addison wrote:
>>> This doesn't make any sense to me. I think you are over-thinking  
>>> this.
>>>
>>> The author element contains the author's *NAME*. It can also  
>>> include an href and an email attribute. UTR#36 refers explicitly  
>>> to IRIs and IDNA addresses, which would be the values of these  
>>> attributes. However, it does NOT refer to plain text (the body of  
>>> the element 'author') which is what the 'dir' attribute really  
>>> applies to. To not provide bidirectional overrides for the  
>>> author's name strikes me as incredibly short sighted, given that  
>>> you can override any higher-level element. To have one place in  
>>> your configuration document that requires controls is not to  
>>> improve security, it is to reduce usability.
>>
>> I've updated the spec and the RelaxNG to include "rlo" and "lro".
>>
>>> It would make far more sense for you to cite UTR#36 with regard  
>>> to an implementations presentation of the href or email  
>>> attributes, suggesting (or forbidding) the application of the dir  
>>> attribute to these values. But the body of the<author>  element  
>>> needs the bidi markup and should not depend on Unicode bidi  
>>> controls.
>>
>> I trashed the old note, made this new note.
>>
>> [[
>> Note: Implementations intending to display IRIs and IDNA addresses  
>> found
>> in the configuration document are strongly encouraged to follow the
>> security advice given in [UTR36]. This could include, for example,
>> behaving as if the dir attribute had no effect on any IRI attributes,
>> path attributes, and the author element's email attribute.
>> ]]
>>
>> IRI attributes, path attributes are defined in the specification.
>>
>> Any better?
>>
>> Kind regards,
>> Marcos
>>
>>
>> -- 
>> Marcos Caceres
>> Opera Software
>