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

Classification: Honeywell Internal
Section 5.1 of the Pointer Event spec defines pointerType as follows:

pointerType of type DOMString, readonly
Indicates the device type that caused the event (mouse, pen, touch, etc.). If a user agent is to fire a pointer event for a mouse, pen stylus, or touch input device, then the value of pointerType must be according to the following table:
Pointer Device Type

pointerType Value

Mouse

mouse

Pen Stylus

pen

Touch Contact

touch



Section 4.2.11 of the EMMA 1.1 spec defines emma:device-type as follows:

Definition

The type of device, or list of types of device through which the input is captured. An attribute of type xsd:nmtokens which contains a space delimited set of values from an open set of values including: {microphone, touchscreen, mouse, keypad, keyboard, pen, joystick, touchpad, scanner, camera_2d, camera_3d,thumbwheel...}.



These definitions overlap but do not appear to be consistent between each other.   In particular, the EMMA definition isn't an extension of the Pointer Event spec definition. Nor do they have the same type name. Nor do they reference each other.

Can this be corrected? If not, can it be explained?

I'm trying to implement a system that handles all of the W3C event specifications in a consistent manner.


Steve Hickman
System Architect, Flight Deck of the Future
480-236-8367


============================================================================================================================================================================================================
This message classified as Honeywell Internal by Hickman, Steve (AdvTech) on Monday, September 30, 2013 at 11:02:34 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.
============================================================================================================================================================================================================