2006-120 Meeting Minutes

PDF-UA 2006-120
June 21, 2006

PDF/UA Working Group Meeting Minutes

Teleconference

PDF/UA (Universal Accessibility) Working Group Draft Meeting Agenda
Wednesday, June 21, 2006,  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:  All attending members should load the PDF/UA page.
We'll be working "live" throughout the meeting!

Duff Johnson called the meeting to order at 3:11 pm Eastern

Roll Call

Duff Johnson - DJ Chair Document Solutions
Joe Clark - JC Independent Accessibility Consultant
Mark Gavin - MG Appligent
Loretta Guarino-Reid - LGR Adobe Systems
Richard Herring - RH Independent Accessibility Consultant
Karen McCall KM - Karlen Communications
Greg Pisocky - GP Adobe Systems

Action Items indicated by AI:

Approval of PDF/UA 2006-119, June 21, 2006 [pdfua-2006-06-21agenda]

Pisocky / Gavin

Approval of PDF/UA 2006-116, May 17-18, 2006 MINUTES, AND Approval of PDF/UA 2006-118, May 31 MINUTES

Johnson / Gavin

Report on / update and discuss PDF/UA - Action Items

Editing moved to the action items page.

Discussion of JavaScript

A discussion of JavaScript issues occured at this point.

Continue review of Draft Specification outline.  Select 1-2 individual elements and discuss in detail.

MG: Richard and I went through some items this morning that can be dealt with fairly quickly. The document catalog title should be changed to Document information dictionary.

RH: Mark and I simplified the document and identified redundancies.

Page tree can be deleted. PDF-UA named dictionary can also be deleted.

Changing the title works. The remaining requirement is to specify what goes into the file. PDF/X and PDF/A come up with explicit tags as an example. Version, subversion, and conformance level. There appears to be no harm in adopting the PDF/A convention for this. Currently conformance levels have not been determined, but it is a concept we will adopt. Must should be shall and should is stronger than may. Should is acceptable. Can or may are options and required items are shall. The word "must" is being replaced by "shall."

MG: Has the PDF/A namespace equivalent. Making this construct work for our purposes will take a little bit of revision. The schema can be adopted.

AI: modify the PDF/A definition to reflect PDF/UA naming conventions.

MG: Item 2 (not item 3) is wholly redundant. There is a personal preference within Adobe to deprecate the document information dictionary, but since that has not been done in the PDF Reference it is not. This information needs to get replicated in the XML meta data as well.

MG: Flags for the document information dictionary are not explicitily defined in PDF/A. They are defined in PDF/X.

RH: Question: If there are two places where the data can be, are they both equially subject to being lost.

MG: Most 3rd party apps today do not recognize the XML meta data. Most Adobe apps keep them in synch. THe way to go is to say they have to be in both.

RH: That's what I favor at this point.

DJ: It's fine therefore to make it multiply redundant.

MG: We need to come up with some text for the field names and some values. We could just follow exactly what PDF A has done.

Part Amd=Amendment and conformance is all lower case for the document information dictionary. For the somekind of designator. PDFUAid:part, next line would be PDFUAID:Conformance, etc. See [[ ]].

DJ: Do we need to explain ourselves, what do we mean by this?

RH: We should.

MG: I can copy and paste the text. There's a big description.

AI: DJ to cleanup Document Information Dictionary entry.

DJ: Should we take a look at another page?  Looks like there remains some work for Angy to move some of this content around.

DJ: Let's take a look at [Preferences].

• document specific (not appl)
• display bookmarks? - worthy of a should. If bookmarks are present, the bookmarks should be displayed as a default.
• magnification levels
• user agents
• etc.

JC: Maybe we would be better off coming up with examples. If the viewing agent shows bookmarks by default.... that sort of thing.

LGR: Philosophical issue. As a user I would like to be controlling these things rather than the author.

Table 8.1 from PDF Reference 1.6 Manual for example. I don't think we can say things which conflict with the specification. It is within our bounds to say you must provide the following attributes...

JC: Terms like should allow  us to nudge people in a certain direction. Send this to John Gunderson who is chair of UAAG.

LGR: That would be nice.

JC: It's possible they discussed this under the heading navigation mechnism That's John Gunderson at UIUC the University of Chicago.

KM: I usually urge people to add bookmarks everything over two pages.

MG: Bookmarks are a much more powerful mechanism than people actually use. In addition to hyperlinks they can zoom in on specific portions of a page.

JC: In our informative portion of the spec we should spend some time informing people of the utility of bookmarks. This implementation that was just described is much better. We're writing the spec, so we can but this sort of detail in there. All it takes is a short paragraph.

LGR: Rather than use the Acrobat UI for all this, use the spec to refer to them.

DJ: What we have now, if bookmarks are present, the

LGR: There has to be some key in here that as some value. Non full screen page mode key should have the value "use outlines". That's the name of the key in this dictionary.

GP: So we have checkpoints and techniques.

DJ: How about page layout. Single page mode, continous, continuous facing mode...

LGR: Is there an instance where we would allow the author to specify that as opposed to allowing the user to make the choice.

RH: I don't think we're in the position to judge why a person would set a particular preference in order to get value out of a PDF in a nonstandard way.

LGR: One key called display doctitle that controls whether the title or the name of the file is displayed in the title bar.

DJ: For page layout should be set to default.

KM: In terms of layout, I have a layout that I prefer. Full Size. I would err on the part of let the user decide how they want to use the document.

DJ: We're on the viewer preferences page of the wiki. I have added the text Loretta sent me under bookmarks. I have added Karen's idea under page layout.

MG: There is no default under page layout per se. It has to be removed from the dictionary, (there's an implementation note here, isn't there?). So the page layout key does not exist is goes to whatever the user has set it to be.

DJ: In the User Preferences Dictionary the viewer preferences key should

MG: Looking at page 115

LGR: Looking at page 548 (PDF Reference Manual)

DJ: Magnification

LGR: We will have to guess how to track these separately if we are going to get our spec to refer back to the PDF spec. For instance we are talking about entries in the catalog dictionary.

MG: We changed it to Docuemnt Information Dictionary. Changes was correct. Looks like we need to add an item under docuemnt structure called Document Catalog.

LGR: Viewer preferences dictionary I was looking at is an element of the catalog. These are a subset

MG: THe catalog itself is a dictionary.

DJ: Is the location of the Viewer PReferences catalogn.

LGR: Out outline put together Viewer PReferences section is discussed under Interactive Features in the PDF spec.

RH: Unless advisable should display with viewer preferences set in the user agent.

LGR: In  order to make this a spec we will have to take it to the next step and say what should be inside this PDF file?

DJ: The discussion under the viewer preferences page, I take it these are all part of the same sub dictionary of the document catalogn

LGR: THe problem is we are talking about some keys that are in the catalog... We need to be careful in specifying which sections of the specification refer to the corresponding section of the PDF Reference.

MG: This won' t be much mmore than a 20 to 30 page document to begin with.

DJ: Must we maintaoin the organization strictly according to the PDF reference?

LGR: If we should, then we should have two different entries on that point.

DJ: I need to readd another heading.

MG: I would put document catalog under document structure and I would put Document Information Dictionary in there too. If you want to follow the PDF Reference then it should go: Document Structure > DOcument Catalog > Document Information Dictionay.

 RH: Neil Soiffer gave a presentatioh on MathML through the

MG: There it is, we already have a section called Document Information Dictionary under Document Interchange which is where it should be. Item 7.

DJ: Please refresh the draft table of contents.

MG: 6.3.2 goes down to 7.1.1

DJ: That's easy enough to do....

MG: The document catalog can now have the information about page mode and page layout.

DJ: I made the appropriate changes and in the viewer preferences page some of this content, perhaps all of it moves up

LGR: THe page layout section.

MG: Page layout and Page Mode are both keys within the page catalog.

DJ: Okay refresh the document catalog page and those items should appear there.

LGR: What we want to say is in the Document Catalog the page layout key should not be present

DJ: Instead of in the Viewer Prefernces Dictionary

LGR: It's actually catalog dictionary (lower case)

MG: Refer to page 114 of the PDF Reference.

MG: Page Layout, Page Mode, Outline Threads, these are all part of the catalog, it even goes on to a fourth page.

DJ: SOunds as if we have to go through each of the items i n the table.

MG: Viewer Preferences Items should be placed onthe viewer prefences page. Page 548 3 pages of items that refrer to the Viewer Preferences page.

DJ: Our draft spec will follow the dictionaries the PDF Reference specifies. The reference is in one location but the dictionay or item is in another location.

2 items in the document catalog.

MG: When you come out of full screen mode it defines what is meaningful....

LGR: In document catalog we want to talk about the page mode key. Is the outlines dictionary only present if you have bookmarks?

MG: An empty outlines dictionary is allowed. It does occur. It can have a single root item and the root item is never displayed.

DJ: Should the structure of this page be a list of the keys?  Read me the ones that are in the table.

LGR and MG: Pages no, dest or named, no Viewer Prefernces Dictionary exists (requirement). Page Layout you need, Page Mode you need. Open Action you might want to say something about that.  

LGR: We might need additional actions.

DJ: I'll leave them in there.

Wrap up

Meeting adjourned 5:01

Pisocky / Guarino-Reid

Next meeting:

Wednesday July 26, 2006 3:00 pm - 5:00 pm EST