W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > April 2013

Re: [ACTION-487][ISSUE-97][ISSUE--118] HTML5 Defaults

From: Felix Sasaki <fsasaki@w3.org>
Date: Wed, 17 Apr 2013 19:04:33 +0200
Message-ID: <516ED621.4070107@w3.org>
To: Jirka Kosek <jirka@kosek.cz>
CC: Yves Savourel <ysavourel@enlaso.com>, public-multilingualweb-lt@w3.org
Hi Jirka, Yves, all,

co-chair hat on: what worries me here is timing. We have in this mail a 
new proposal to create an HTML special purpose precedence mechanism, and 
in the "Translate" defaults different types of defaults
http://www.w3.org/International/multilingualweb/lt/wiki/HTML5_Defaults

Given the timeline we have: will we be able to get consensus on these 
proposals? Will we have answers to questions at
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Apr/0115.html
that might influence implementations & testing?

HTML defaults have been on our plate for a long time - the issue
https://www.w3.org/International/multilingualweb/lt/track/issues/118
was opened 22 February, nearly 2 months - and didn't really move 
forward. Some implementers are now for good reasons asking for a 
timeline, see
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Apr/0079.html
is 24 April reasonable?

I'm not saying we should stop this discussion - I'm just worried about 
ad hoc decisions.

Best,

Felix

Am 17.04.13 11:46, schrieb Jirka Kosek:
> On 17.4.2013 11:10, Felix Sasaki wrote:
>
>> It has three drawbacks:
>>
>> 1) Global rules are different than "real" defaults in terms of precedence.
> We have special section for HTML precedence (6.4 -
> http://www.w3.org/TR/2013/WD-its20-20130411/#html5-selection-precedence), so
> we can modify it if necessary.
>
> Also we can create two rule files one providing defaults, second
> providing extraction of local ITS values. Then we can say something like:
>
> 1. Implicit local selection in documents (ITS local attributes on a
> specific element). *Local selection is defined by the following rules...*
>
>
> 2. Global selections in documents (using mechanism of external global
> rules or inline global rules), to be processed in a document order, see
> Section 5.2.1: Global, Rule-based Selection for details.
>
> 3. Selection via inherited values. *Inheritance rules are by provided by
> the following rules...*
>
> 4. Selections via defaults for data categories. *Defaults are provided
> by the following rules...*
>
> Then implementation is very easy -- it will just put global user-defined
> rules in between rules for 1. and 3. and will not interpret local ITS
> datacategories inside HTML.
>
>> 2) If we go this way we won't be able to speficy "how to work with
>> translate in HTML5" for "local only" implementations.
> We can say that "local only" implementations MUST behave as if the
> following rules will be used. Implementation doesn't have to support
> global approach, it just have to behave in the same way as is described
> in default rules.
>
>> 3) we will have a disalignment with the behaviour of HTML5 "translate"
>> implementations in browsers.
> Why, we can model rules in a way it matches this.
>
> 				Jirka
>
Received on Wednesday, 17 April 2013 17:05:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:07 UTC