Draft agenda: 12 March 2013 call

Below is the draft agenda for PEWG's 12 March call. Discussion on the 
agenda topics in advance of the meeting is encouraged, especially if you 
will not be able to attend the call.

Reminder: March 19 is the deadline for comments for the Pointer Events 
Last Call <http://www.w3.org/TR/2013/WD-pointerevents-20130219/>

-Thanks, ArtB

1. Getting started

a. Tweak Agenda
b. Determine scribe

2. Last Call comments - here is a list of comments from Jacob including 
status and in some cases a proposed resolution. If we have consensus on 
a comment, we should record the resolution and ask the commenter if they 
agree (or not) with the group's decision.

a. pointerType Extensibility - closed for V1 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0172.html>. 
Feb 26 discussion 
<http://www.w3.org/2013/02/26-pointerevents-minutes.html#item04>.

b. Missing rotation attribute on PointerEvent - is there a compelling 
reason to add? 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0171.html>

c. Should pointerId be an integer? No. Add a non-normative note e.g. the 
following? 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0170.html>. 
(Feb 26 discussion 
<http://www.w3.org/2013/02/26-pointerevents-minutes.html#item05>.)

[[
The pointerId selection algorithm is implementation specific. Therefore 
authors cannot assume values convey any particular meaning other than an 
identifier for the pointer that is unique from all other active 
pointers. As an example, values are not guaranteed to be monotonically 
increasing.
]]

d. Editorial suggestion from Alex Russell - "The spec should lead with 
examples, i.e., move Section 9 to where Section 2 is now." No 
objections. 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0169.html>

e. Change buttons field representation? No. But add this to V.Next list. 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0169.html>

f. The new touch-action CSS property seems to have conceptual overlap 
with the pointer-events property. Close this one without any action. 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0169.html>

g. navigator.maxTouchPoints seems deeply touch-specific? Yes it is touch 
specific. 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0169.html>

h. Clarify the positioning of the spec? "The pointer event spec does not 
require other device events be supported (e.g. mouse events, touch 
events, etc.)" 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0169.html>

i. Click and contextmenu events coming to a closure. Clarify that 
contextmenu is not a compatibility mouse event. 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0163.html>. 
February 26 discussion 
<http://www.w3.org/2013/02/26-pointerevents-minutes.html#item06>.

3. Test Assertion: status, plans

4. Any other Business: implementation status

= Logistics

* Time: UTC: 16:00; Helsinki: 18:00; Paris: 17:00; Boston: 11:00; San 
Francisco: 08:00; Tokyo: 01:00 (Wed); Duration = 60 minutes maximum

* Phone Numbers: W3C's Zakim Bridge +1.617.761.6200; PIN = 7394# 
(PEWG#); SIP information <http://www.w3.org/2006/tools/wiki/Zakim-SIP>

* IRC: irc://irc.w3.org/ ; channel #pointerevents

* Meetings page: <http://www.w3.org/wiki/PointerEvents/Meetings> 
(includes "tips" on IRC, scribing, etc.)

* Minutes wiki: <http://www.w3.org/2010/webevents/wiki/Minutes>

Received on Monday, 11 March 2013 11:59:28 UTC