Conference October 2007 📍 Washington D.C., USA

PDF Days North America 2007 — Washington D.C.: PDF Association Founding Year

PDF Days North America 2007 in Washington D.C. coincided with the founding year of the PDF Association and the inaugural PDF Days Europe conference. North American attendees engaged with early PDF/A-1 enterprise pilots, government archiving requirements, and the AIIM/ARMA records management community interest in PDF standards.

Official event page →

Key takeaways

PDF Association founded in 2006/2007 — first neutral steward for PDF standards implementation
NARA developing PDF/A guidance for federal agencies; practical adoption questions dominated discussion
FRCP 2006 ESI amendments created new legal PDF workflow obligations
Adobe Acrobat 8 added PDF/A-1b export; Microsoft Office 2007 added PDF export capability
Section 508 and PDF/A-1a overlapping requirements created a useful convergence for accessible archival PDFs
Open-source PDF tooling growing but validation tooling gap remained

PDF Days North America 2007 in Washington D.C. was held in the founding year of the PDF Association — the organisation that would become the primary steward of PDF standards development for the following two decades. 2007 was also the year of the inaugural PDF Days Europe in Berlin, which established the annual conference format that continues today. Washington D.C. brought a strong government and legal community representation. Two years after PDF/A-1's publication, the practical reality of federal adoption was becoming clear: some agencies were moving forward with PDF/A mandates; many were still evaluating; and the records management community was wrestling with the gap between policy intent and operational capability.

The PDF Association founding and mission

The PDF Association was formally established in 2006 (as the PDF/A Competence Center, later renamed), with the 2007 conference marking the first full year of the organisation's operations. The founding rationale addressed a structural gap: PDF standards were being developed by various ISO committees, national standards bodies, and Adobe, with no neutral organisation coordinating the implementation community. The PDF Association's founding mission included: - Coordinating between PDF standards committees (ISO TC 171/SC 2, AIIM, AIIM Europe) - Publishing implementation guidance, test suites, and technical notes - Providing a neutral forum for PDF implementors (software vendors, service providers, end users) - Running educational events (PDF Days) to build implementation capability The Washington D.C. location for the 2007 North America event was deliberate: government agencies were the primary audience for the PDF Association's early work, given NARA's PDF/A interest, the US e-government initiative, and the courts' e-filing requirements.

Federal records and e-government in 2007

The US e-government landscape in 2007 provided the backdrop for Washington D.C. discussions: NARA guidance — NARA had been tracking PDF/A since before its publication. By 2007, NARA was developing guidance for federal agencies on PDF records management. The 2007 conference addressed the practical questions NARA was grappling with: Which PDF/A conformance level should be required? How should agencies handle legacy PDFs created before PDF/A tools were available? What validation tools were adequate for large-scale compliance checking? Courts and CM/ECF — The federal court e-filing system (CM/ECF/PACER) had been expanding its PDF requirements. The FRCP amendments of 2006 addressing electronically stored information (ESI) created new obligations for legal PDF workflows. The 2007 conference addressed alignment between court filing PDF requirements and emerging archival standards. Section 508 and PDF accessibility — The Rehabilitation Act Section 508 required federal agency electronic documents to be accessible. The 2007 conference addressed the gap between Section 508 compliance (which required tagged PDFs accessible to screen readers) and PDF/A-1a requirements (which also required tagging). The overlap between accessibility and archival requirements made PDF/A-1a theoretically attractive but practically difficult to achieve. AIIM and records management — AIIM (formerly the Association for Information and Image Management) was a primary organiser of the North America PDF events. The AIIM community bridged the archivists, records managers, and IT systems integrators who collectively represented the primary enterprise PDF workflow community.

Software vendor landscape in 2007

The 2007 conference surveyed a PDF software market in rapid change: Adobe's dominant position — Adobe Acrobat 8 (released November 2006) had added PDF/A-1b export support, making the standard accessible to mainstream users. Acrobat Professional remained the dominant PDF authoring and editing tool. Adobe's simultaneous role as the format creator, primary software vendor, and standards contributor was a source of tension that the PDF Association's formation was partly designed to address. Microsoft and OpenXML — Microsoft had recently added "Save as PDF" functionality to Office 2007 via the free Save as PDF add-in. The Office 2007 PDF export used PDF 1.5 with some tagged PDF support — not full PDF/A-1, but a significant step toward mainstream PDF production quality. The competition between PDF (Adobe-backed) and XPS (Microsoft's own fixed-layout format, also emerging in 2007) was actively discussed. Open source momentum — Ghostscript, Poppler, and the emerging iText/PDFBox Java ecosystem were making server-side PDF generation increasingly viable without Adobe licensing costs. Government IT departments were particularly interested in open-source options for high-volume document processing. PDF/A validation tools — By 2007, pdfaPilot (callas software), Enfocus PitStop, and early versions of what would become veraPDF's predecessors provided PDF/A validation. The lack of a single authoritative open-source validator was noted as a gap — one that would remain until the veraPDF project was launched under EU funding in 2014.

Frequently asked questions

What is the PDF Association and what does it do?

The PDF Association is a non-profit membership organisation founded in 2006 that promotes adoption and development of PDF technology. Its work includes: publishing technical specifications, implementation guides, and best practice documents; coordinating participation in ISO TC 171/SC 2 standardisation committee work; running the annual PDF Days Europe and North America conferences; maintaining the PDF/UA Competence Center resources; publishing the Matterhorn Protocol (PDF/UA test framework); and operating working groups that produced veraPDF (the reference PDF/A validator). Members include PDF software vendors, document service providers, and end-user organisations. The PDF Association is the primary non-Adobe body that has shaped PDF standards since 2007.

What were the FRCP 2006 ESI amendments?

The 2006 amendments to the Federal Rules of Civil Procedure (FRCP) in the United States formally addressed electronically stored information (ESI) in civil litigation discovery. Before 2006, the discovery rules primarily addressed paper documents; the amendments created explicit obligations for preserving, collecting, and producing electronic documents (including PDFs, emails, databases, and metadata). The amendments required parties to discuss ESI preservation and production at early case management conferences and established "safe harbor" protections for routine ESI destruction pursuant to a good-faith records management policy. For PDF practice: the amendments required that PDFs produced in discovery include relevant metadata; that they be in agreed formats (typically with Bates numbering and load files); and that redactions be applied correctly (not visually-only). These requirements drove the legal community's interest in PDF/A and proper PDF redaction practices.

Did Microsoft Office 2007's PDF export comply with PDF/A?

The Office 2007 PDF export add-in (and the built-in PDF export in Office 2007 SP2) produced PDF 1.5 documents with some accessibility tagging. It did not produce PDF/A-1 compliant output by default; a specific "ISO 19005-1 compliant" option was added in later Office versions. The Office 2007 PDF output had variable quality: documents with embedded fonts, standard colour spaces, and basic structure tags were close to PDF/A-1b compliance, but many documents failed on output intent, non-embedded fonts, or transparency handling. Microsoft's successive Office versions improved PDF/A compliance, with Office 2010 and later offering a more robust PDF/A-1b export option.

Try it in your browser

The PDF tools and standards discussed at this event are available free — no account needed.

Edit PDF Sign PDF Annotate PDF Open editor