W3C

- DRAFT -

Protocols and Formats Working Group Teleconference

07 Oct 2015

See also: IRC log

Attendees

Present
JF, Joanmarie_Diggs, janina, ShaneM, JamesNurthen, Rich_Schwerdtfeger
Regrets
Chair
SV_MEETING_CHAIR
Scribe
JF

Contents


<trackbot> Date: 07 October 2015

preview agenda with items from two minutes

<scribe> scribenick: ShaneM

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

<MichaelC> action-1669 due weeks

<trackbot> Set action-1669 Look at data on the web best practices http://www.w3.org/tr/dwbp/ due date to 2015-09-16.

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

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

<MichaelC> Web Platform Incubator Community Group

<MichaelC> The Hardware Pixel Community Group

putting in the dead groups list

JF: Do we have any way of noticing of something we think is dead is alive again?

MichaelC: not really
... maybe we should have a process of checking dead groups periodically.

janina: once a year seems often enough.

JF: every six months seems better

janina: sure but we can't track our usual list for updates every six months.

JamesN: It isn't something we need to do in the group. Some individual could check it.

MichaelC: Yeah, and that's what staff contacts are for. It would only take me like an hour.
... janina and michael will make sure this happens each six months.

<MichaelC> Schema Architypes Community Group

MichaelC: note that there is no reason for the chair and staff contact to do this. anyone can volunteer.

ShaneM: it might be related to the open group ArchiMate activity. I don't think it is related to us.

JF: it looks like metadata

MichaelC: a11y of archives is important. not clear if this would get high enough up. does the schema have that information.

janina: there is a difference between extending current tagging in schema.org and finding other ways of doing things.

MichaelC: I don't know enough about what schema.org is doing

JF: libraries and dublin core are in this group. some us based libraries and universities.

janina: maybe we could ask Jon Gunderson about this. Also, is there anything that should be related to the congnitive task force.

MichaelC: I don't know - if you are tagging medieval documents for cognitive, that could get interesting.
... I think we should take this as might need examination later.

general agreement.

MAUR

janina: there are a couple of comments.

ShaneM: checklist is done

janina: there were errors in the checklist.

ShaneM: there were? I didn't see them

janina: I will forward to list.

ShaneM: will review and comment on list

Rechartering Progress

<JF> scribe: JF

MC: Progress is ongoing.

<ShaneM> rssagent, make minutes

TPAC Update

JS: hope to have draft calendar ready this week to get posted on wiki
... wanted to spend time defining our CSS concerns - detailed

requested CSS WG to meet on the Friday

JS: will meet with dPub group as well - looking to take som e time Thursday afternoon

have also been requested to meet with Web Payments - time TBD

will discuss issues with Web Payments folks however

KHS: trying to arrange a time that works better (more convenient) to us

SM: they have a complicated agenda, everyone wants to talk to them
... want to talk to them about PAUR

however, they want to talk about the APIS - what to expose to make things better for AT

also, what do we need in the spec - i.e. human readable language, not just the API

JS: i.e. "what this does", "what is this for"

KHS: the push-back is that these are APIs, there is no interface to interact with

we need to find a new way to talk about the requirements we need/want them to add, so that the APIs can deliver on XYZ

what do we need/want to have added to the API specs

JS: what we need/want isn't that hard to name, but the other WGs are struggling what that is
... we need sentencase, in plain english, what a piece of code is doing - the purpose

often all we get is code examples, but we have no idea what the code is intended to do

KHS: agree, but this may not be what Web Payments is doing

JS: yes, but they are talking about an API

KHS: what they are attempting to do... there is no code in any of their documents at this time

SM: we're not talking about implementation yet

KHS: right, and we want the documentation to explain what is going on - more guidance on that

perhaps a smaller, off-line conversation, perhaps with the chairs. Happy to facilitate that

JS: what Shane suggested is what Ian has also proposed. Focus on PAUR will be important
... I hope this effort will also spur the ARIA WG to look at some of what came over from IndieUI

<Zakim> ShaneM, you wanted to talk about Web Payments and the PAUR

HTML 5.1 Alt Edits -- https://w3c.github.io/alt-techniques/

JS: we have never been fully happy with HTML 5.0 spec guidance on @alt
... for example, avoids @longdesc, etc.

there is a new draft, something a lot shorter, and many of the examples have been moved to a landing page which is named (referenced?) in the HTML spec

we need wider reviews

Shane and Liam have worked on the re-drafted text

will ask WCAG and EO WGs to also review the text

not sure how we move forward, and when. Next week? at TPAC? Other?

JN: is there a diff on the previous version

SM: there is not - could likely produce one, but the differences are fairly different

JN: are there major sections that are different?

SM: lots removed, and lots of editorial (language) changes

<scribe> ACTION: Shane_m to produce a diff of the two @alt text items [recorded in http://www.w3.org/2015/10/07-pf-minutes.html#action01]

<trackbot> Error finding 'Shane_m'. You can review and register nicknames at <https://www.w3.org/WAI/PF/Group/track/users>.

<scribe> ACTION: ShaneM to produce a diff of the two @alt text items [recorded in http://www.w3.org/2015/10/07-pf-minutes.html#action02]

<trackbot> Created ACTION-1729 - Produce a diff of the two @alt text items [on Shane McCarron - due 2015-10-14].

ARIA.Next Items

JS: Rich is not here. Not aware of anything major, looking to move some heartbeats soon
... review of balance of agenda, seems nothing more to review today
... waiting on multiple charter renewals so taht we can continue the conversations going
... will discuss the role of the APA at TPAC on how we move forward. More TF's, or a return to simple reviews only

discussion is on-go9ing. Pros and Cons for both approaches

JS: any other business?
... convene early

Summary of Action Items

[NEW] ACTION: Shane_m to produce a diff of the two @alt text items [recorded in http://www.w3.org/2015/10/07-pf-minutes.html#action01]
[NEW] ACTION: ShaneM to produce a diff of the two @alt text items [recorded in http://www.w3.org/2015/10/07-pf-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/10/07 16:53:38 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Extension to PFWG so that we can continue - provides overlap//
Succeeded: s/bee/been/
Found ScribeNick: ShaneM
Found Scribe: JF
Inferring ScribeNick: JF
ScribeNicks: ShaneM, JF
Present: JF Joanmarie_Diggs janina ShaneM JamesNurthen Rich_Schwerdtfeger

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 07 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/07-pf-minutes.html
People with action items: shane_m shanem

[End of scribe.perl diagnostic output]