See also: IRC log
JS: any edits to minutes?
FE: did Gregg get a chance to approve?
JS: no we will send to gregg to get approval
ACTION-1610?
<trackbot> ACTION-1610 -- Janina Sajka to Skim css scroll snap points module level 1 to see if there are issues with content bigger than viewport http://www.w3.org/tr/css-snappoints-1/ -- due 2015-04-15 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1610
JS: have done it but should discuss
<MichaelC> close action-1610
<trackbot> Closed action-1610.
MC: close the action
JS: we were worried about whether there was a mechanism to handle the magnification case where there was less on screen than was expected due to coom
... there seems to be a setting for how strongly the snap points are enforced
... we might want to ask for that to be global
... I don't see them discussing the fact that someone may have enlarged their content. I think they should consider that scenario
... I will write that up and maybe send as comments
... on the PF list initially
ACTION-1609?
<trackbot> ACTION-1609 -- Janina Sajka to Make sure html a11y tf reviews media source extensions http://www.w3.org/tr/media-source/ -- due 2015-04-15 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1609
<MichaelC> close action-1609
<trackbot> Closed action-1609.
JS: we have gone around and around in the task force
... there is no deeper engineering knowledge in the TF than here on that. Has been looked at. Had a concern which was just a misundersatnding
ACTION-1604?
<trackbot> ACTION-1604 -- Fred Esch to Review manifest for web application http://www.w3.org/tr/appmanifest/ -- due 2015-04-15 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1604
FE: did review and wrote a note where they are talking about icons... they have a name which would be accessible. didn't find any issues
<MichaelC> close action-1604
<trackbot> Closed action-1604.
<MichaelC> close action-1580
<trackbot> Closed action-1580.
<fesch> scribe: fesch
<jnurthen> scribe:jnurthen
FE: I had one i thought was taken care of
ACTION-1588?
<trackbot> ACTION-1588 -- Richard Schwerdtfeger to Send email regarding pf group charter status and how it affects publication of api mappings -- due 2015-02-27 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1588
ACTION-1558?
<trackbot> ACTION-1558 -- Fred Esch to Review compositing and blending level 1 http://www.w3.org/tr/2015/cr-compositing-1-20150113/ -- due 2015-01-28 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1558
FE: do we need to keep this open
... I was happy with his description of things used in the formula. and that you need to calculate the colours yourself
... the formula is still valid
JS: and his point that trying to handle edge cases is a losing battle
... got a better understanding of how they thought about things
... what does it mean to us when see something like that from CSS
... what do we say to a WG
... how do we evaluate - it is not clear to me
... end of the story is that we don't need to say anything to CSS about that spec
<MichaelC> close action-1558
<trackbot> Closed action-1558.
MC: can close the action?
<MichaelC> Media Capture and Streams
MC: here is the one with an explicit review request
his document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform.
MC: no last call date
<MichaelC> ACTION: janina to review Media Capture and Streams http://www.w3.org/TR/mediacapture-streams/ - due 2 weeks [recorded in http://www.w3.org/2015/04/15-pf-minutes.html#action01]
<trackbot> Created ACTION-1615 - Review media capture and streams http://www.w3.org/tr/mediacapture-streams/ [on Janina Sajka - due 2015-04-29].
MC: want comments by Mat 15
<MichaelC> ACTION: Fred to review Gamepad http://www.w3.org/TR/gamepad/ [recorded in http://www.w3.org/2015/04/15-pf-minutes.html#action02]
<trackbot> Created ACTION-1616 - Review gamepad http://www.w3.org/tr/gamepad/ [on Fred Esch - due 2015-04-22].
The Gamepad specification defines a low-level interface that represents gamepad devices.
<MichaelC> Internet Protocol Identity Community Group
consensus: don't care and no activity
<MichaelC> Organisation Profile Documents Community Group
<MichaelC> Multi-device Timing Community Group
no messages
https://www.w3.org/community/webtiming/
Timing mechanisms allow operations to be executed at the correct time. The Web already has several mechanisms supporting timed operations, including setTimeout and setInterval, as well as controllers for media frameworks and animations. However, the Web lacks support for multi-device timing. A multi-device timing mechanism would allow timed operations across Web pages hosted by different devices. Multi-device timing is particularly important for the
broadcasting industry, as it is the key enabler for web-based secondary device offerings.
MC: mailing list slow but there is activity
... are we moving in the direction of tracking this group
... examine later
JS: in the next few weeks need to decide if we plan to do any business at TPAC this year
... hopefully the idea is to meet with other WGs
... need more in-depth conversations in the next few weeks
JS: conversations continue with various groups
... there is no objection to APA
... continuing conversation as to whether we will split or not
... tending to the notion of "aint broke don't fix it"
... question coming is IndieUI
... their charter not up for erview. Their charter expires end of april
... IndieUI would prefer that APA be involved in their work
... Does not want this group exclusively involved
... APA+CSS on context, APA+WebApps for rest
... If CSS doesn't pick up enough of context then could pick up the rest in APA.
... I'm hearing the same concerns as whenever any new deliverable comes on the agenda
Joanie: seems to me that if there is a deliveable that we agree with then that deliverable would be taken up or if we split then it would go into the deliverable branch of APA
... like the events part
+1 to that
Joanie: taking up some of their work may be good. My concern is if we don't it will die
JN: really like the events part but don't like the contexts part
Joanie: could we give a tentative answer to IndieUI.
... definately like events but a portion of people aren't sure about contexts
... gather from MC that we need to get back to them ASAP
... Could we tell them we would love to take events but not sure about contexts yet
MC: we do have a draft charter. Don't have a draft with those deliverables
... don't think we have quorum to do that