Protocols and Formats Working Group Teleconference -- 09 Sep 2015

<trackbot> Date: 09 September 2015

Other Business

<janina> zakim close this item

preview agenda with items from two minutes

<scribe> Scribe: Katie Haritos-Shea

<scribe> ScribeNick: Ryladog

<scribe> Meeting: PF Teleconference

GZ: I was at JTC 1 WG 8 we decided we will go for 2 parts of URC standards. Both would be restful. One for target. According to user preference

GZ; WG 6 which is for Accessibility. I should send a list of standards that they have here.

GZ: Janina is also on the WG. If want you can be on the National Dellegatoion

KHS: Glad to see it is not dead

JS: It was a very lively meeting

GZ: We got the time we needed'

Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open

MC: #1689 on Janina

JS: I did not figure that out. Close it.

<MichaelC> close action-1689

<trackbot> Closed action-1689.

MC: #1685 on Janina

JS: Close it, it was realted to the new charter

MC: We had a review request on this as per chnarter dependencies. We need to reply and say we have no comments if we dont

JS: Give me another week

<MichaelC> action-1685 due 1 week

<trackbot> Set action-1685 Manage review of http://www.w3.org/tr/2015/wd-tracking-compliance-20150714/ tracking compliance and scope (note explicit review request needs response) due date to 2015-09-16.

MC: We have probablypassed
... #1654 on GZ

GZ: Give me 1 more week please

<MichaelC> action-1654 due 1 week

<trackbot> Set action-1654 Take preliminary look at discovery & registration of multimodal modality components: state handling http://www.w3.org/tr/mmi-mc-discovery/ due date to 2015-09-16.

MC: #1631 on Shane
... #1615 on Janina

<MichaelC> action-1615 due 1 week

<trackbot> Set action-1615 Review media capture and streams http://www.w3.org/tr/mediacapture-streams/ due date to 2015-09-16.

JS: Give me 1 week

new on TR http://www.w3.org/TR/tr-status-drafts.html

MC: No new publication

<MichaelC> EMMA: Extensible MultiModal Annotation markup language Version 2.0

MC: We should look at EMMA
... We had a geat deal of interest in the 1.0 version. We worked with them on it
... we thought we were looking at this to solve some prroblems with ARIA, but I dont know how that went. This is a Debbie D thing. I am not worried, but I thinkwe should at least look at this

JS: Lets ask her to introduce it to us

<MichaelC> ACTION: janina to look at EMMA 2.0 http://www.w3.org/TR/2015/WD-emma20-20150908/ - due 2 weeks [recorded in http://www.w3.org/2015/09/09-pf-minutes.html#action01]

<trackbot> Created ACTION-1722 - Look at emma 2.0 http://www.w3.org/tr/2015/wd-emma20-20150908/ [on Janina Sajka - due 2015-09-23].

JS: Give me two weeks to look through it

<MichaelC> ARIA in HTML

MC: ARIA in HTML was published a week ago. Are we going to look at it or should the Task Force do it?

JS: We should review but we will bring it up on the Thursday call. It will get published almost everyy two weeks I think. It is in the new automated cue

MC: It is intended to become a W3C Recommendation

JS: It is going to be a W3C Recommendation

MC: It is ridiculous that people cant understand the spec. It looks like it is not our call - but there is a real problem here

JS: The short name is even more confusing

MC: I think we may have reeal probllems down the road because of this

JS: I think the doc that we can have the most impact on is the Using ARIA in doc

MC: This is getting old

JS: I will take on mentioning this

MC: It looks like HTML 5.1 has been published now. Actually every 3 days
... The redesign of the TR is - nothing else for TR

RS: what do you mean published

JS: Working Draft
... Rich I think we need to do a run through on this doc. I will bring it up on the Thurs call

RS: I got it

Fred: Remind folks to talk about CSS Grid Layout

JS: Yes wwe should add a topic for later on this

Community Groups http://www.w3.org/community/groups/

<MichaelC> Stroke Fonts Community Group

MC: 2 CG for is Stroke Fonts - wants to design a whole new kind of font - to style the pen movement. But does not hae a chair. Think it is dea

<MichaelC> Exposing and Linking Cultural Heritage data Community Group

MC: Next is Exposingg and Linking Cultural Hertage group - which looks completely dead

css grid

<MichaelC> CSS Grid Layout Module Level 1

Fred: I notice that there was a WD from CSS it was the Grid alyout. I emailed Beau Campbell - I think they are NOT thinking about it. The doc desnt mention focus. S

<MichaelC> Grid Style Sheets

Fred: It a[appears to be completely independent of the DOM order
... there fore their are concerns

<joanie> https://lists.w3.org/Archives/Public/www-style/2015Aug/0285.html

<joanie> https://lists.w3.org/Archives/Public/www-style/2015Jun/0180.html

MC: Non of us seem to know of any idea of what to do about it. this might be a good TPAC for Reading Order and Navigation Order are something we neeed to help them get a handle on

Joannie: She is a chair of CSS - put a conformance requirement on authoring tools...(see link fro full text)...
... First URL if you click the stored link...

<MichaelC> Previous PF discussion on Grid Style Sheets

Joannie: This BTW is why I suggested you connect with Bo - that needs to be renewed

Fred: My concern is they dont seem to do anything about it

JS; It seems like a brraod statement without technical support - that doesnt seem reliable'

Joannie: Read email...
... they talk about Authoring Tools - she suggests seems to ask the tools to fix the problems - if it just works, I think that is an awesome solutions

<Zakim> JF, you wanted to suggest that Notepad is an authoring tool...

Joannie: That is a win if it is technically best

KHS: we always want the tools to do it

JF: I am 100% on board with the spirit. But Notepd is also an authoring tool
... I agree with anything a tooling can do...I would support that...

JF; I they are correct it is only half the solution. Authoringguidance is an important peice of that. I think we need to follow through on more than just let the tool fix it.

JS: What are our next steps here then?
... Send to ATAG or WCAG - or do we wnat to see if we want to directly do here

JF: We should do all of the above WCAG and ATAG if exists and follow up with CSS WG at TPAC. So maybe their documentation can identify concerns

MC: On the WCAG content guidance if there are content patters then WCA techniques might be the ppllace for it. If we dicver that their is a need for WCAG SC then we should put it on their radar. They may want an additional TF
... Addititonal Extension to solve some of this poblem. It i at lest something wwe can be discussing thos things

CS: That solve Focus order problems

JS: the potential to solve Focus Order is certaininly somethings. Do we have something for REadingg Order

MC: We can follow 12 year old ideas

FRed: I think in CSS4 fornaviagtiona nd directions

CS: that is still navigationa nd not reading. Some AT use hueristics for that and other dont

<janina> http://lists.w3.org/Archives/Public/public-pfwg/2015Sep/0022.html

JS: I am not sure what out next stps are. There was talkk on the list
... We need to bring this back and possible at TPAC

Rechartering Progress

TPAC 2013 Update

JS: They are closin the hotel you can no longer book the entire week there
... It looks like they dont have one you may want to look sooner rather
... There is a skiing destination
... Who do we want to have time with CSS is one
... Lets start naming groups and topics we want to dicsuss with them

<MichaelC> TPAC Schedule

JS: APA is THurs Fri, ARIA is Mon Tues

MC: Web Application Security about CAPTHA and Authentication
... HTML WG. Topics, Extension specifications and what happens when they wine down to the HTML A11Y Task force next steps

JS: Timed Text for transcripts

JF: also watching the Second Screen WG timpacts it might have on Accessibility models

JS: Yes we want to see some of their Use Cases
... Yes we could have a number of things we want to see in their specs

JF: the germ is still Cas =- they like to work with us - keeping that active and freindly

MC: I am bot sure that Cas is the Core - I think it os FRancios
... FRancios is less familair with A11Y

JS: Then our next step is we want to talk about use cases

<MichaelC> staff contact: Francois Daoust

LS: I cannot make it to Japan but several COGA folks will on WEb Security and Web Payments - we want folks to knwo that their is a paper being written

<MichaelC> chair: Janina_Sajka

<MichaelC> chair is Anssi Kostiainen

JS: They web payments are asking for close involvment - we talked about a PAUR to do this for them
... We want to ensure COGArequirements are written into the PAUR

MC: Second Screen - Use Cases

JS: Timed Text WG - topic
... WoT - Use Cases or REequirents

JF: Ther was an interesting discussions at M-Enablinhg

JS: They know can you bring me some specifics

KHS: They are planning on having a Demo - we should look at that

JS: We must remember that it is not a UI - so we need specific things for infrastrucre

MC: We b Real time communicatopns

JS: IOur interest are going to be inn th UI

- DRAFT -

Protocols and Formats Working Group Teleconference

09 Sep 2015

Attendees

Contents