Conference April 2008 📍 Berlin, Germany

PDF Days Europe 2008 — Berlin: PDF 1.7 Becomes ISO 32000-1

PDF Days Europe 2008 was held in Berlin in April 2008 — the same year PDF 1.7 was standardised as ISO 32000-1. This landmark event marked the formal transition of PDF from an Adobe-controlled proprietary specification to an open international standard, shaping government and enterprise PDF adoption for years to come.

Official event page →

Key takeaways

ISO 32000-1:2008 published — PDF 1.7 became an international standard, changing its regulatory and procurement status globally.
PDF/A-2 development was underway, incorporating transparency, layers, JPEG 2000, and three conformance levels rather than two.
The PDF Association was building the ecosystem of interoperability testing and compliance tools around the new ISO family.
Open-source PDF tools were improving but still lagged commercial tools in creation quality and standards compliance.
Web-based PDF delivery was transitioning from plugin-dependent to plugin-independent models, though the transition was incomplete.

PDF Days Europe 2008 was held in Berlin in April 2008, organised by the PDF Association. The 2008 edition arrived at a historic moment: in that same year, ISO 32000-1 was published, making PDF 1.7 an international standard and ending the era in which PDF was solely a proprietary Adobe format. For PDF Days 2008 attendees, the standardisation question was live — the publication was imminent or recent depending on the event timing — and the dominant discussion was what ISO standardisation would mean in practice for developers, adopters, and regulators. The 2008 conference brought together the PDF developer community at a moment of transition. The PDF Association had been founded in 2006 and the PDF/A Competence Center established in 2007. By 2008 both were actively developing the ecosystem of PDF interoperability specifications, and the 2008 conference was a forum for that community-building work alongside the technical programme.

ISO 32000-1 and what PDF standardisation meant

The publication of ISO 32000-1:2008 was the defining development of the 2008 cycle. PDF 1.7 had been submitted to ISO by Adobe in 2007, and after a relatively fast-track approval process for a document of that scope and complexity, it was published in 2008. Key discussion points at PDF Days Europe 2008 around this development included: What standardisation changed — Before ISO 32000-1, PDF was a de facto standard maintained by Adobe. Regulators and procurement officers in many jurisdictions were reluctant to mandate a proprietary format regardless of how widely used it was. ISO 32000-1 resolved this: government procurement rules that required ISO or national standards for mandated file formats could now reference PDF. This was immediately consequential for European government e-procurement and document management directives. What ISO 32000-1 did not change — The specification was still the same document; PDF 1.7 and ISO 32000-1 describe the same format. The technical content did not change from Adobe's PDF Reference 1.7. Existing PDF implementations did not need to change to be conformant with ISO 32000-1. The significance was governance and legitimacy, not technical change. Subsets and the ISO family — ISO 32000-1 was the base specification. The PDF subset standards — PDF/A (ISO 19005), PDF/X (ISO 15930), PDF/E (ISO 24517) — were separate ISO standards normatively referencing ISO 32000-1. The standardisation of the base format completed the ISO family. PDF/UA was still in development (it would not be published until 2012 as ISO 14289-1). Future revision — The PDF 2.0 revision process (what would become ISO 32000-2) was discussed as a future project. ISO standardisation meant that future revisions would go through the ISO TC 171 SC 2 WG process rather than being unilateral Adobe decisions.

PDF/A-2 and long-term archiving standards development

PDF/A-1 (ISO 19005-1) had been published in 2005 based on PDF 1.4. By 2008, the working group was actively developing PDF/A-2, which would be based on PDF 1.7/ISO 32000-1. Sessions at PDF Days Europe 2008 discussed the key additions PDF/A-2 was incorporating: Transparency support — PDF/A-1 prohibited transparency due to implementation variability. PDF/A-2 would allow ISO 32000-1's transparency model, which by 2008 was sufficiently well implemented in RIPs and viewers to be considered reliable for archiving. Optional content — PDF Layers (optional content groups) were not permitted in PDF/A-1. PDF/A-2 would allow them under specific constraints, addressing the needs of engineering drawing workflows that relied on layer-separated content. JPEG 2000 compression — PDF/A-2 would permit JPEG 2000 (compression) for image streams, offering significantly better image quality at equivalent file sizes for photographic content. PDF/A-2 conformance levels — Unlike PDF/A-1 which had Level A and Level B, PDF/A-2 was introducing three levels: /b (basic), /u (Unicode), and /a (accessible). The accessibility level would incorporate tagging requirements that had been developed through the PDF/UA working group.

Developer ecosystem and tooling in 2008

In 2008, the PDF developer ecosystem was beginning to segment in ways that are now familiar. Discussions at PDF Days Europe 2008 reflected this: Commercial PDF libraries — iText (then still open source under MPL/LGPL), PDFlib, Adobe's own libraries, and various platform-native solutions (Apple's Quartz PDF, Microsoft's XPS-to-PDF converters) were the main options for server-side PDF generation and processing. The Java and .NET ecosystems each had multiple options. Open source landscape — Ghostscript remained the primary open-source PDF rendering and conversion tool. Poppler (a Xpdf-based library) was being actively developed for Linux desktop use. PDF.js had not yet been created (it would emerge from Mozilla in 2011). The open-source options for high-quality PDF creation (as opposed to rendering) were limited. PDF in web applications — Most web applications served PDFs by generating them server-side and delivering them to the browser, which would hand off to a plugin (Adobe Reader plugin or the platform's native PDF support on macOS). Inline browser rendering without a plugin was not yet standard. The limitations of this model — plugin security issues, version fragmentation, poor mobile experience — were becoming apparent. ISO 32000-1 and independent implementations — The publication of ISO 32000-1 was expected to lower the barrier for independent, clean-room PDF implementations by providing a stable, publicly available specification. This expectation would be realised over the following years as open-source implementations improved.

Frequently asked questions

What is ISO 32000-1 and how does it differ from PDF 1.7?

ISO 32000-1:2008 is the ISO standardisation of the PDF 1.7 specification, submitted by Adobe to the ISO TC 171 SC 2 WG 8 committee. The technical content of ISO 32000-1 is identical to Adobe's PDF Reference 1.7 (sixth edition). The difference is governance: ISO 32000-1 is an international standard maintained by the ISO committee process, while PDF 1.7 was a proprietary specification maintained by Adobe. The practical effect was that organisations and governments subject to requirements for ISO-standardised formats could now mandate PDF. Future PDF development would go through the ISO process — PDF 2.0 was published in 2017 as ISO 32000-2.

What are the differences between PDF/A-1 and PDF/A-2?

PDF/A-1 (ISO 19005-1, 2005) is based on PDF 1.4 and prohibits transparency, optional content groups (layers), and JPEG 2000 compression. PDF/A-2 (ISO 19005-2, 2011) is based on ISO 32000-1 (PDF 1.7) and permits transparency, optional content groups under specific constraints, and JPEG 2000 compression. PDF/A-2 also introduces three conformance levels: /b (basic — PDF/A-1/B equivalent), /u (Unicode — all text must be Unicode-mappable), and /a (accessible — /u plus tagging requirements). PDF/A-2 additionally allows embedding of PDF/A-compliant documents within a PDF/A-2 document, enabling composite document archiving.

What was the PDF Association's role in 2008 and how has it evolved?

In 2008, the PDF Association (founded 2006) was a newly established industry body focused on promoting PDF interoperability and the ISO standards family. Its primary activities were organising PDF Days conferences, running the PDF/A Competence Center (a testing and certification body for PDF/A conformance tools), and participating in ISO standardisation working groups. By the 2020s, the PDF Association had grown to coordinate multiple working groups (PDF/UA, PDF 2.0 errata, PDF/A, PDF/X), operate the PDF Association Developer Portal with developer resources, and publish the Matterhorn Protocol (a machine-testable interpretation of PDF/UA requirements). It remains the primary industry body for the PDF standards ecosystem.

Try it in your browser

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

Compress PDF Edit PDF Sign PDF Open editor