Re: Standardize Buttons For TV-Web Remotes?

Thanks, this looks good. My only remaining concern is in regards to
implementation defined key values. The definition:

[[
If there is no appropriate key value in the key values set, then a key value
must be devised. The key value should be as human friendly as possible and
must not contain whitespace characters. The value must be composed only of
characters in the ranges \u0030..\u0039, \u0041..\u005A, or \u0061..\u007A,
and must begin with a character in the range \u0041..\u005A.
]]

is not adequate to prevent name collisions between custom definitions. Some
normative convention is needed to prevent collisions.

G.

On Tue, May 24, 2011 at 8:29 PM, Doug Schepers <schepers@w3.org> wrote:

> Hi, Giuseppe, Glenn-
>
> Giuseppe Pascale wrote (on 5/24/11 6:23 AM):
>
>
>> thanks for keeping us posted.
>>
>> Please notify this group once that section of the spec is "complete".
>> I think there are participants from different TV industry organizations
>> on this list that could provide feedbacks on that section.
>>
>
> I've made a few more edits to the spec, but for now, I think the key values
> are fairly stable.  We plan to go to Last Call, so we welcome any comments
> from the TV-Web folks during that period.
>
> Glenn and Mark suggested that we might trim down the list of key values,
> perhaps to the set of "required" values, but we also saw value in having a
> wider set; at the same time, though, the list is rather long, so I wouldn't
> want to overburden implementers.  We'll see what LC comments say, and I'll
> continue to keep y'all in the loop.
>
> Please let me know if this approach is satisfactory.
>
>
>
> [1] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
>
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG, WebApps, and Web Events WGs
>