2007-112 Minutes

PDF-UA 2007-112
April 11, 2007

PDF/UA Working Group Teleconference

PDF/UA (Universal Accessibility) Working Group Draft Meeting Agenda
Wednesday, April 11, 2007,  3:00 P.M. - 5:00 P.M. EST

Conference Call Information
International Dial-in: +1-303-928-2600
U.S. Dial-in: 1-888-742-8686
Conference ID: 7083945

NOTE:  The meeting will be conducted "live" on the Wiki.Attendess

Duff Johnson, DJ - Chair
Joe Clark, JC - Independent Accessibilty Consultant
Ebony Dowtin, ED - AIIM
Ferass Elreyes, FE - Netcentric Technologies
Betsy Fanning, BF - AIIM
Mark Gavin, MG - Appligent
Dick Herring, DH - Independent Accessibilty Consultant
Greg Pisocky, GP - Adobe Systems
Leonard Rosenthol, LR - Adobe Systems
Neil Soiffer, NS - Design Sciences

Approval of PDF/UA 2007-111 Agenda

Rosenthol / Soiffer

Approval of 2007-110 Minutes

Gavin / Soiffer

Review Action Items, agenda for F2F meeting

Action Items page:

To be updated by Duff. Action Items have now become work on the actual components themselves.

Agenda for F2F meeting:

LR will not be present for the second day. FE will not be present the first day. Programmatic validation discussion moved to today.

There were no objections to a  request by FE to change the discussion of tables from day 1 to day 2. As a result the general discussion on annotations will be moved to the first day. JC also recommended inviting Alan Cantor to participate in the table discussion.

Review of the role of programmatic validation in PDF/UA

LR: Do we favor an approach that documents that are conformant of compliant are marked as such? If we endorse such an approach, how can a conformance writer know that a document is truly conformant if there is no possibilty of programmatic validation.

JC: Accessibility problem, not all criteria can be programmatically validated.

FE: A couple of examples. Redundant links.

GP: 2 part issue. One divide it into those components that can be validated programatically and then provide a means for human reviewers to indicate that those items which require human intervention were attended to.

 MG: PDF/UA should provide an indicator. Remember that those other specifications are exclusionary specifications it is easier to do this. Also there is no ISO requirement that a specification be programmatically verifiable.

DJ: The factor is whether or not we are adequately meeting the mission.

JC: Unfortunately the web guidelines while confronting similar issues have the same problems.

DJ: Distinguishing artifacts from pictures is part of the issue.

LR: No one is taking the position that 100% of the standard has to be validatable.

DJ: I proposed a scheme 3 years ago that marked a PDF as accessible and as progressively accessible.

FE: If we want to have a rule for programmatic validation, we should have some form of a basis within the standard itself.

LR: In addition to talking about conformant readers and conformant writers, we could define what constitutes a conformant validator as well.

DJ: We may need a new module or component in the spec (or module level) called the validator discussion.

FE: As we are doing for the Reader we could do for the validator.

Action Item for DJ: Ensure that there is a validator subsection for each module. Each module could get a validator component.

GP: How do we indicate that a file that has gone through such a process be marked so that users removed from the original authoring need not perform the same checks again.

DJ: Per image, per page, per table, per document constructs that have to be accounted for. The marks would indicate which workflow processes have occured from no compliance to fully assured compliance.

FE: We probably need a separate module as well for Programmatic Validation as well

LR: Yes, that should be a separate module. Look under Preferences, document. PDF/A

LR: PDF/A, X, E are all XMP based. Moving away from docinfo in favor of XMP. PDF/A v 2 is proposing deprecating doc info.

LR: Proposed we adjourn early and move on to the face to face

Rosenthol / Elreyes

Continue review of Framework and Modules

Deferred to Face to Face

Update Action Items, review ASSIGNMENTS

Deferred to Face to Face.

Wrapup

Next meeting the Face to Face Wednesday and Thursday, April 18 - 19 in Boston, MA

Adjourn

Meeting adjourned 4:30 pm EDT