- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Sat, 13 Dec 2014 14:47:04 +0000
- To: Ben Peters <Ben.Peters@microsoft.com>, Katie Haritos-Shea GMAIL <ryladog@gmail.com>, "chaals@yandex-team.ru" <chaals@yandex-team.ru>, 'Simon Pieters' <simonp@opera.com>, 'Arthur Barstow' <art.barstow@gmail.com>, 'Tobie Langel' <tobie.langel@gmail.com>, Frederico Knabben <f.knabben@cksource.com>
- CC: 'public-editing-tf' <public-editing-tf@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>, "public-indie-ui@w3.org" <public-indie-ui@w3.org>, "public-html@w3.org" <public-html@w3.org>
On 13/12/2014 05:58, Ben Peters wrote: > You all have excellent points, thank you! Device Independent Events > gets straight to the point, and I like that. Are there any objections > to calling this concept Device Independent Events? [...] > The reason I want to have this broad conversation about naming is > simply for consistency in terminology across relevant specs. For what it's worth, I remember first coming around to this idea of device-independent input stuff (at that time, mainly meaning "don't just design for mouse, but also for keyboard") from WCAG 1.0 (1999) http://www.w3.org/TR/WCAG10/#gl-device-independence So I think this phrase/naming - which continues the same thinking and expands it to include further input modalities - is more than appropriate, as it builds on already established concepts. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Saturday, 13 December 2014 14:47:33 UTC