Conference October 2008 📍 San Jose, California, USA

PDF Days North America 2008 — San Jose: ISO 32000-1 Published, PDF is an Open Standard

PDF Days North America 2008 in San Jose occurred months after the landmark publication of ISO 32000-1, formally making PDF 1.7 an international open standard. Sessions addressed what this meant for procurement, interoperability, and the emergence of open-source PDF tooling freed from proprietary constraints.

Official event page →

Key takeaways

ISO 32000-1 published in July 2008 — PDF became a formal international standard for the first time
Open-source PDF tooling (Ghostscript, Poppler, iText) was mature enough for production use
Government procurement policies could now formally mandate PDF via ISO standard reference
PDF/A-1 had three years of real production experience; conversion services market had emerged
PDF/A-2 development was underway to address known PDF/A-1 limitations
The iText AGPL relicensing (coming in 2009) would significantly disrupt the open-source PDF ecosystem

PDF Days North America 2008 in San Jose, California occurred months after a landmark event in PDF history: the publication of ISO 32000-1 in July 2008. For the first time, PDF had a formal international standard. The format that Adobe had controlled for 15 years as a proprietary specification was now an ISO standard, owned by no company, freely implementable by any organisation. The implications were immediate and far-reaching: government procurement officers who had previously been cautious about mandating a proprietary format could now reference an ISO standard. Open-source developers who had been working from incomplete reverse-engineered specifications could now access the full normative text. Competitors and interoperability partners could implement PDF readers and writers with formal specification backing.

ISO 32000-1: what it changed for PDF implementors

ISO 32000-1:2008 standardised PDF 1.7 — the version that had been published by Adobe in 2006. The process of ISO standardisation required Adobe to clarify numerous ambiguities in the specification that had been papered over in earlier versions. The formal specification ran to over 750 pages. For open-source developers — Prior to ISO 32000-1, open-source PDF libraries (Ghostscript, Poppler, pdf-lib, Xpdf) had been implemented using Adobe's published but proprietary PDF Reference documents and significant reverse engineering. ISO 32000-1 provided a normative specification text that was publicly available (ISO documents are paid, but PDF 1.7 Reference from Adobe was freely available and closely aligned). The formal specification made it clearer which behaviours were required by the standard versus which were Adobe extensions. For procurement — Government and enterprise procurement policies that required ISO standards could now formally mandate PDF. NARA and US federal agencies referencing PDF in records management policies could cite ISO 32000-1 rather than a proprietary Adobe document. European government procurement frameworks similarly gained a formal standard reference. What ISO 32000-1 did not include — XFA (XML Forms Architecture) was documented in ISO 32000-1 as part of the PDF specification but as a normative reference to an Adobe specification. This created a tension that would persist until PDF 2.0 deprecated XFA entirely. JavaScript in PDF was similarly referenced but not fully specified in ISO 32000-1 — it relied on the ECMAScript standard but the PDF-specific JavaScript API remained an Adobe specification.

Open-source PDF tooling comes of age

The 2008 conference marked a visible inflection point for open-source PDF tooling: Ghostscript — The long-standing open-source PostScript and PDF interpreter had been the dominant free PDF tool for a decade, but its dual GPL/commercial licensing and complex architecture made it difficult to use as a library. The 2008 period saw Ghostscript 8.x maturity and increased use in server-side PDF processing pipelines. Poppler — The Poppler PDF rendering library (a fork of the original Xpdf codebase) was gaining adoption in Linux distributions as the default PDF backend. Poppler's LGPL licence made it easier to embed in applications than Ghostscript. iText (then iTextSharp for .NET) — The iText Java library had become the de facto standard for PDF generation in Java applications, with the .NET port gaining enterprise adoption. The 2008 conference coincided with the period before iText switched to the AGPL licence (which happened in 2009, a significant disruption for commercial users). The iText AGPL transition — The 2009 AGPL relicensing of iText (just after the 2008 conference) was a watershed moment in open-source PDF tooling: commercial users who had relied on iText's LGPL licence were forced to either adopt the AGPL (requiring open-sourcing their own applications) or pay for a commercial iText licence. This created a significant market for alternatives including Apache PDFBox and, later, pdf-lib. The 2008 conference discussions about open-source viability anticipated these tensions.

PDF/A-1 adoption: one year of real production

By October 2008, PDF/A-1 had been a published standard for three years. The 2008 North America conference had real production data to discuss: Government adoption progress — Several US federal agencies had adopted PDF/A-1 as a preferred format for permanent records. NARA had published guidance referencing PDF/A as an acceptable format for electronic records. Courts were evaluating PDF/A-1 requirements for e-filing systems. State archives were independently adopting PDF/A-1 policies, often looking to European government experiences for implementation guidance. Exception rates improving — With PDF/A-aware creation tools (Acrobat Professional 8.0 had PDF/A export mode), new documents from compliant workflows were achieving high PDF/A-1b conformance rates. The challenge was the existing legacy archive — documents created before PDF/A tools were available. Conversion service market — A market for bulk PDF/A conversion services had emerged: organisations with large legacy archives of non-PDF/A PDFs were contracting with services to bulk-convert and validate them. The conversion quality and economics of this service market were discussed at the 2008 conference. PDF/A-2 development begins — By 2008, the known limitations of PDF/A-1 were well-understood: no JPEG 2000, no layers, restricted transparency, limited font format support. PDF/A-2 development was formally underway, addressing the most significant gaps. Attendees discussed the timeline and scope of the forthcoming standard.

Frequently asked questions

What is the relationship between ISO 32000-1 and PDF 1.7?

ISO 32000-1:2008 is the ISO standardisation of PDF 1.7. Adobe published the PDF 1.7 specification (the PDF Reference, Sixth Edition) in November 2006. In 2007, Adobe submitted this specification to ISO/TC 171/SC 2 for standardisation. After a standards development process, ISO 32000-1 was published in July 2008. The technical content is essentially identical to PDF 1.7; the standardisation process added formal normative/informative distinctions, resolved some ambiguities, and aligned with ISO document conventions. All valid PDF 1.7 documents are valid ISO 32000-1 documents and vice versa. The "PDF 1.7" version identifier in PDF file headers refers to the same specification.

Why was XFA included in ISO 32000-1 if it was later deprecated?

XFA was included in ISO 32000-1 as a normative reference because it was part of the Adobe PDF 1.7 specification at the time of standardisation. Excluding it would have required a deviation from the specification Adobe submitted. XFA was referenced normatively but its definition depended on an Adobe-controlled specification (the XFA specification) — creating a dependency on a proprietary document within the ISO standard. This tension was noted by committee members at the time. PDF 2.0 (ISO 32000-2:2017) deprecated XFA, removing this dependency. PDF/A has never allowed XFA at any conformance level, correctly anticipating XFA's incompatibility with long-term archival requirements.

Is ISO 32000-1 freely available to read?

ISO 32000-1 itself is a paid ISO document. However, Adobe separately published the PDF 1.7 Reference (PDF Reference, Sixth Edition) as a free download. Since ISO 32000-1 and PDF 1.7 are technically identical, the Adobe PDF Reference serves as the free reference equivalent. Adobe also donated the PDF specification to ISO as part of the standardisation commitment, with the intent that the specification would be accessible. The ISO 32000-2 (PDF 2.0) specification is similarly available via ISO at a cost, with Adobe publishing corresponding documentation. The technical content of the specification is also embedded in the PDF Association's various technical resources at pdfa.org.

Try it in your browser

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

Edit PDF Protect PDF Sign PDF Open editor