NDSA:March 29, 2013 Call: Difference between revisions

From DLF Wiki
Wlaz (talk | contribs)
Wlaz (talk | contribs)
Line 35: Line 35:


Steve: conforming reader would recognize it as A-3 and set up an additional dialog.
Steve: conforming reader would recognize it as A-3 and set up an additional dialog.
Caroline: we're in the posotion of having to preserve files that somebody else created. We need tools to characterize files. Some PDF/A-3 files may not have any  embedded content so would actually behave like a PDF/A-2. But would the
Steve: We'd have to talk to the developers about that. There is a vendor that is looking to create an independent service to validate the writers to ensure that they are actually complying with the standards. The software would have to get certified that it works. Then we'd actually have validators at ingestion. We have to get somebody interested in creating this software as a business and we think we finally have somebody who will do this.

Revision as of 12:28, 29 March 2013

Back to Standards Working Group Main Page

Back to PDF Exploration Page

Agenda

Discussion with Stephen Levenson, an IT Specialist for Policy and Planning at the Office of the US Courts and the chair of the PDF/A working group.

Participants

Don Chalfant, Kate Murray, Sheila Morrissey, Kevin DeVorsey, Chris Dietrich, Carl Fleischhauer, Stephen Levenson, Butch Lazorchak

Meeting Notes

Stephen on how standards are implemented in the ISO community.

PDF/A-3 doesn't necessarily replace A-1 or A-2. Should be able to use a PDF/A-1 file 30 years from now. The methodology used should not change for rendering these files in the future.

PDF/A movement highly influenced by manufacturers, now PDF/A center, dominated by the Germans. Had many use cases for instances where creators wanted to include the original files wihtin a PDF/A document.

Brazilian government wanted to preserve their material as XML but XML wasn't trusted by users because of complexity. Wanted to make a more presentation-ready format but didn't want to throw away the XML.

U.S. Courts, bankruptcy court, claims, when an individual goes into court, and the claims are laid out, in order for someone to assert the claim, we print a document for them. That's what they bring back to court to assert their claim. Ginny Mae started this and Mastercard is also movin gon this. We get the PDF but then have to reenter the data from this doucment in their case management systems.

We're putting an XML output of what the claim represents inside the PDF document. Ginny Mae's automated processes work on this XML.

Down with PDF/A-3 we have downstream functions that leverage the inner materials. Adobe's server product does not currently output A-3 files.

When you look at a A-3 document in Adobe Reader it will render the

Chris D. How will hidden content be protected from certain readers of the document.

Steve: For A-3 you can still include the information as "private data" that would make it hidden.

Caroline:

Steve: conforming reader would recognize it as A-3 and set up an additional dialog.

Caroline: we're in the posotion of having to preserve files that somebody else created. We need tools to characterize files. Some PDF/A-3 files may not have any embedded content so would actually behave like a PDF/A-2. But would the

Steve: We'd have to talk to the developers about that. There is a vendor that is looking to create an independent service to validate the writers to ensure that they are actually complying with the standards. The software would have to get certified that it works. Then we'd actually have validators at ingestion. We have to get somebody interested in creating this software as a business and we think we finally have somebody who will do this.