RE: Apparent inconsistency between W3C Pointer Event spec and EMMA 1.1 spec [Honeywell Internal]

Classification: Honeywell Internal

Having 2 different terms for the same concept seems like a bad idea. The problem here is that the same concept shouldn't be implemented in 2 different ways. Doing so means that software attempting to process events that could be either Pointer events or EMMA events has to check for both values, no matter what they are. This will inevitably result in bugs when some code fails to do this dual check somewhere.

Is there a compelling reason why one spec can't just refer to the other one for this concept?

---
Steve H.


-----Original Message-----
From: Arthur Barstow [mailto:art.barstow@nokia.com]
Sent: Tuesday, October 01, 2013 7:55 AM
To: Hickman, Steve (AdvTech)
Cc: public-pointer-events@w3.org; www-multimodal@w3.org
Subject: Re: Apparent inconsistency between W3C Pointer Event spec and EMMA 1.1 spec [Honeywell Internal]

On 9/30/13 2:02 PM, ext Hickman, Steve (AdvTech) wrote:
>
> Can this be corrected? If not, can it be explained?
>

If EMMA used "touch" instead of "touchscreen", would that `worky`?

-AB

============================================================================================================================================================================================================
This message classified as Honeywell Internal by Hickman, Steve (AdvTech) on Tuesday, October 01, 2013 at 8:11:32 AM.
The above classification labels are in accordance with the Honeywell Corporate Classification Policy.  The information contained in this electronic message is confidential and intended only for the use of the individual/entity named above, and the information may be privileged. If you, the reader of this message, are not the intended recipient or an employee or agent responsible to deliver this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error, please immediately notify the sender and delete the original message.
============================================================================================================================================================================================================

Received on Tuesday, 1 October 2013 15:12:06 UTC