W3C

Digital Publishing Interest Group Teleconference

06 Mar 2017

Agenda

See also: IRC log

Attendees

Present
George Kerscher, Ivan Herman, Avneesh Singh, Dave Cramer (dauwhe), Luc Audrain (laudrain), Rick Johnson, Deborah Kaplan, Karen Myers, Leonard, Garth Conboy, Vladimir Levantovsky, Bill Kasdorf, Matt Garrish (mattg), Nick Ruffilo, Romain Deltour (rdeltour), Charles LaPierre (clapierre), Brady Duga (duga), Laurent Le Meurs
Regrets
Peter, Bill McCoy
Chair
Garth
Scribe
nickruffilo

Contents


Garth: "The minutes are approved."

A11y in the charter


Garth "Carley from Pierson put regrets in, but that might change. We'll carry welcoming pearson until then week." ... "Anything to say about accessibility in the charter?"

Avneesh: "We worked on the text and posted it to the list - and we have agreement on it, so we'd like to post it on the chat and get opinions."
... "One chunk is for the scope, and the other is for co-ordination section."

<ivan> The Working Group will incorporate accessibility considerations into the Working Group's deliverables. Recommendation-track deliverables will contain mechanisms to make Web Publications accessible to a broad range of readers with different needs and capabilities. This includes general WCAG and WAI requirements of the W3C; additional extended requirements will be identified as conformance requirements in the Working Group’s normative specifications. Profiles of

<ivan> Web Publications may be defined with more stringent accessibility requirements.

Ivan: "This is the statement for the scope"

Avneesh: "We can start the discussion from scope, but if you wish to paste both, that works."

<ivan> For liaison section: The Digital Publishing Working Group will coordinate with WCAG/ARIA Working Group to integrate accessibility requirements created as part of its recommendation-track deliverables into generalized technology. One or more pipeline of the requirements will be maintained to manage diverse turnaround times of the W3C groups.

Leonard: "I'm a little confused/concerned about the 2nd sentence where we're specifically calling out WCAG, WAI and identifying. I think we don't need it. The profiles piece is more than sufficient."

Garth: "So the recommendation is dropping the middle of the 3 sentences?"

Deborah: "We wanted that there for specific reasons. We want to make it clear that there will be a pipeline from our recommendations. Our recommendations cannot change WCAG unless there is a specific pipeline. A lot of what we will be requiring will require modifications and we want it on their timeline. So we want to make sure there is pipeline."

Ivan: "To add to Deborah, the problem is that we expect during the work on the publication, features will arrive on accessibility that current WCAG documents do not cover. we know this because the accessibility people have already put together a note on this. To make it clear that we may go beyond what WCAG gives, we just want to make sure that people understand that we add things that are important. In this sense, I'm pretty much in favor of keeping this sentence."

Garth: "We have the next agenda item coming up to talk about where the next generation of the ARIA work will happen. It's only semi-related. Does it make it more accurate by changing the Will to a May? Leonard?"

Dave: "I think the sentence clarifies the larger goal - that we are going to use existing web accessibility groups but may go further."

Leonard: "I get what has been said, but why are we specifically calling out - in that section - when we've later called on in the liaisons' area. We're going to work with lots of other groups - so that is why I am concerned. It isn't part of scope - it's a different part of the document - it doesn't belong."

Garth: "I get where you're going, but it seems as though the portion after the semicolon is clearly scope. So we could keep the extended scope."

Leonard: "Why is that specific to accessibility? Why are we calling this out more than CSS or any other area? We are going to liase with other groups."

Dave: "Because it's more important."

<leonardr> @dauwhe - while accessibility is very important, I would argue that security is more important...so why not call that out?

Deborah: "The reason it is important here: we know with the work done and what we've published. Some of the things we do are impossible if existing specs are not modified. Some things are extremely difficult to get existing specs modified - it is exceedingly complex. It is political and time consuming to get requirements debated and accepted. It is important - in order for us to succeed to achieve the goals that are set - there needs to be an explicit callout. And there will be stringent requirements that will be pipelined. Does that mean it shouldn't exist in security? It could. We're not saying the other things aren't as important, but that what we must do will not be possible unless we make it explicitly clear."

<dauwhe> +1

Avneesh: "Again, the main concept is regarding the timelines. It looks easy to say: 'put it all in WCAG'. WCAG can be a long struggle. The timelines are long. It could be 5-8 years is something to expect. WP becomes a recommendation first. Will our spec exist in the universe without any specification? This is important due to the slow process of the WCAG. In the working group of digital publishing, we should be working with the pipeline and feeding the WCAG pipeline. We cannot expect the timelines to meet."

Ivan: "In a way Avneesh covered all the items in my mind. I have a small disagreement with what Deborah has said. Some of the issues that are identified may end up standardized by this group and not necessarily by the other groups. We need to make it clear in the text/scope that we leave open to make it possible. This text is blissfully silent to say whether that is here or there. The timing issue will be a definite factor. I agree with Leonard that we will have issues. We may have issues with any other item. I personally prefer - if those issues come up - I prefer if specific issues come up, that we should make it explicit additionally and not remove what's there."

...: "compared to what was noted. I don't expect us to standardize anything with security. It's probably the same for all the others. In this sense, it's a slight bit different. "

Leonard: "I've been looking over the charter, and I think I have a solution, but it may require a little bit of info from ivan. We have, down in 3.1 - 4 specific deliverables. Those are clearly defined individual deliverables that the group is going to do. We talk later about use-cases. If you go up to the scope, we are only focused on that first bullet - packaged web publications. I wonder if the way to address this, is to take the 2nd half of the sentence, can we take the 2nd part of the sentence and put that in a separate paragraph? Instead of tying it to web publications - make it a separate deliverable. Other work/deliverables. If we can pull it out of the scope, it will get called out so that the other folks can see that we are very serious about doing that."

Ivan: "To be very clear about charter organization, the Packaged/Web publications. That doesn't mean we have to produce 4 and only 4 documents. If we need to have two or three specifications, that is our decision and we are allowed to do that. To put it another way, if I call it out separately, as another bullet item on the same level, we are suddenly obliged to do that. Do we want to make that decision - I'm not sure. The current text leaves us a certain level of freedom, what you say gives more granularity."

Deborah: "To a certain extent - much of this was constrainted that we had to keep it short, clear, and leave out politics - so this wording was the most logical. We should note that the concerns have been heard and will be considered."

Garth: "You did not like the 'Will to a may' transition. I still remain that we might want to switch?"

<Garth> The Working Group will incorporate accessibility considerations into the Working Group's deliverables. Recommendation-track deliverables will contain mechanisms to make Web Publications accessible to a broad range of readers with different needs and capabilities. This includes general WCAG and WAI requirements of the W3C; additional extended requirements will be identified as conformance requirements in the Working Group’s normative specifications.

<Garth> Profiles of Web Publications may be defined with more stringent accessibility requirements.

Deborah: "For simple things such as legal constraints, we will be moving much faster than WCAG. But it's not a matter of slowness, they don't know about them. it will be our job to notify them. It's a question - if one person is folding, and one is putting away, the putting away cannot happen until the folder is done folding."

<clapierre> I am happy with the text as is.

Garth: "I'm not too unhappy. Ivan is not to happy. Leonard - is this a hold your breath and turn blue?"

Leonard: "Can you tell me exactly where this is going to go?"

Ivan: "In section 2 - 3rd bullet item."

Leonard: "If you put it after the bullets, as a separate bullets, I'd be OK, but it doesn't flow with the bullet. I would leave in the first sentence in the 3rd bullet, and put the rest after all the bullets."

Ivan: "I'm fine with that."

Deborah: "I'd like to see it first, can we move this to email?"

<leonardr> +1 on the branch!

Garth: "Can we make a branch with the new text."

<Garth> The Digital Publishing Working Group will coordinate with WCAG/ARIA Working Group to integrate accessibility requirements created as part of its recommendation-track deliverables into generalized technology. One or more pipeline of the requirements will be maintained to manage diverse turnaround times of the W3C groups.

Garth: "That leaves us with the Liason section. I just posted that above."

Leonard: "It's great text - i just want to confirm exactly where it's going - 4.1 W3C groups?"

Ivan: "In 4.1 the last item is 'accessibility guidelines working group.'"

Leonard: "Sounds great - thanks for clarification."

Garth: "Ivan, there was an email thread you started with the ARIA folks ..."

Publication of the drafts

Ivan: "Can i get one thing out of the way first? Can we have a vote on the publication of the draft?"
... "I just want agreement that the PWP and UCR should be published as draft. If we agree it will be published this Thursday."

<dkaplan3> +1

+1

<laudrain> +1

<HeatherF> +1

ARIA WG work

Ivan: "The way DPUB-ARIA 1 was done, was that there was a common task force between the two groups. Since it's only an interest group, the document will be published as a recommendation by the other group. Since we have two working groups, we have 3 different choices. We can say we follow the same model as before - where it gets published by ARIA. We can publish it and ask for help from ARIA

if we need it. Or we take a joint deliverable group, which means both groups have to agree with the document - and both groups have say in it. But we have to say how we are going to do that in the charter. I have asked some people - the chairs - for the time being, I have not gotten any more replay except the staff conact. They seem to be OK with a joint release."

Ivan: "Avneesh/Deborah - was there an accessiblity conference? Maybe that is why they didn't answer. We may have a preference on how we want to proceed. Maybe Matt can comment."

Matt: "I did see a response from rich, saying if we weren't planning on doing new mappings, so he didn't see a need on doing a joint release. I think that is a good guiding principle. It all depends on if we want to do the mappings or not. If we're not planning on doing the mapping... If we're planning on doing some of the mappings, we should consider doing a joint. If we're doing semantics

without the mappings, then doing it alone probably makes more sense."

<clapierre> CSUN was the a11y conference last week.

Ivan: "I don't have an answer to that..."

Matt: "It's hard to gauge what comes next. At this point we probably hammered out the painful details of doing a vocabulary like this. Alot of the time was spent explaining why we needed this to exist. Those issues have now been resolved. I don't think it is going to be as much work. We were really establishing the groundwork. I'd be good either way. If we want to do joint, I'd be OK with

that."

Ivan: "I must admit that I am always a bit of weary of administrative things - so anything that reduces admin is helpful. If we have to req-track and vote by two different groups it might lead to delays of several weeks. It's a good reason why we should keep it in group. But there is no reason to have them vote on things that are more related to us. I'm in favor of keeping it just to us, but

that's just one voice."

<Bill_Kasdorf> +1 to Ivan

Garth: "Perhaps we should do what you say - note it as separate."
... "We have 15 minutes less - Ivan do you want to - with completing the charter - we want it published. We have a little changes with the accessibility language, then we should republish..."

Ivan: "The charter now is simply a living document..."

Garth: "My point is that I'd like to say to the business group ' here we are in the draft, do you have comments?'"

Ivan: "there is one more thing we have to work on, but we can do later - something about the timeline. Content wise if we have the changes done on the accessibility one, I think we are done - but there are two issues that I put there way back because we did have a discussion if we should have references to the BFF work on the one hand and documents coming from the Readium consortium - saying

that I'm waiting for some references there. It would be good to have those by next week."

Garth: "I think we discussed that and they were going to provide us with some links - there were some discussion - as long as we 'may or may not' do something with these documents. I think we're OK going to the business group - and late binding that. We should pull Rick's chain one more time and if we don't get anything, then drop it."

Ivan: "The less yellow blobs in the charter, the better."

Garth: "I'm not unhappy to just drop it...."

<leonardr> +1 to removing them until someone submits the URL

Ivan: "Actually - Keeping it there is better - as the question on 'what do we do with the inheritance of IDPF will come up. when it comes to the AC votes, the yellow blobs need to go away."

Garth: "Our last agenda items - should I run through the Face 2 face?"

F2F meeting

<Rick_Johnson> +1 to moving the date back

Garth: "Tentatively scheduled 5th or 6th. we have an 8 week notice. But - to in order to hit that, we must send it by april 10th, which is a month and a few days. Part of me likes that as it's a deadline, which might help motivate the process. part of me thinks we should stay the course. The other suggestion is to move our F2F back 3ish weeks to a different venue. That's where we are. Ivan

- did I get that?"

Ivan: "If I want to have proper prices for my flight tickets, then I should make the reservation within 1-2 weeks. After that, prices go up - especially for those coming from Europe. If I make a reservation now, for early June, and we have to move the meeting, I lose lots of meetings."
... "We should have a deadline as to when we'll have a deadline."
... "Is the 10th of April doable or not - if we have doubts, I would prefer to go for a safe bet and do it towards the end of June. That is more realistic in my books."

Garth: "Deadline for a deadline is 2 weeks from today. Is that enough?"

Heather: "I have to side with ivan - I book 4-6 months in advanced. Having 2 months notice I'm usually booked. The longer lead time, the more that someone like me - who is an avid planner, can fit it."

Leonard: "In terms of location, I'm more than happy if the group decides to move date/location, that should be reasonable. If we decide to do Europe, I can make some recommendations."

Garth: "I heard some grumbling of the 20th. No later than the 20th we will have this nailed down. Sounds like some freedom to move it back. Lets revisit. My take is that given the business group meeting on the 13th, we don't meed next week but two weeks from today. The real decision will be made then."

<Karen> https://www.w3.org/2002/09/wbs/97159/pbg201703f2f/

Karen: "So far there are only 9 people set up for the pub business group in London. I know there are more people attending who have completed the registration form. I need to know the food requirements - vegetarian, allergies, etc. Complete it or email me if you're having issues."

Dave: "there may be confusion, it seemed like an "either or" but it was a "both"

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/03/07 09:43:46 $