Conference November 2006 📍 Berlin, Germany

PDF Days Europe 2006 — Berlin: PDF/A-1 in Its First Year and the Road to ISO

PDF Days Europe 2006 was held in Berlin in 2006, the year the PDF Association was founded. The conference addressed the very early real-world adoption of PDF/A-1 (published September 2005), the establishment of the PDF/A Competence Center, and the beginning of the ISO 32000 submission process for PDF 1.7.

Official event page →

Key takeaways

PDF Days Europe 2006 was among the first events under the newly founded PDF Association, establishing the community forum that would become PDF Days.
PDF/A-1 was 14 months old; font embedding at scale, RGB colour management, and XMP metadata were the three dominant implementation challenges.
The PDF/A Competence Center was establishing its certification programme — giving "PDF/A certified" a rigorous, auditable meaning.
Adobe's forthcoming ISO submission of PDF 1.7 (which would become ISO 32000-1 in 2008) was actively discussed as a governance improvement for the ecosystem.
First-generation PDF/A validators had significant disagreement rates, which was identified as a major obstacle to enterprise adoption confidence.

PDF Days Europe 2006 was held in Berlin in November 2006, the same year the PDF Association was formally founded. The conference was held in the immediate wake of PDF/A-1 (ISO 19005-1) being published in September 2005 — just over a year earlier. The 2006 event was among the earliest structured gatherings of the PDF developer and enterprise community under the PDF Association's umbrella, distinct from Adobe-organised events. For participants in 2006, the fundamental question was: now that PDF/A is a published ISO standard, what does it actually take to implement it correctly? The first year of PDF/A production had already revealed a long list of implementation problems — fonts, colour, metadata, transparency — and the 2006 conference was a forum to share early experience and begin building the ecosystem of tools and guidance that would make PDF/A production reliable.

Founding of the PDF Association and PDF/A Competence Center

The PDF Association was founded in 2006 as an industry membership body to promote interoperability among PDF implementations and to steward the development of the ISO PDF standards family. Its establishment reflected the community's recognition that PDF interoperability could not be sustained by individual vendor effort alone — it required a neutral body to: - Coordinate interoperability testing between implementations - Provide technically authoritative guidance on the standards - Represent industry interests in ISO standardisation committees - Organise community events (PDF Days) for knowledge sharing The PDF/A Competence Center (PDFA-CC) was set up as the certification arm. The PDFA-CC developed a suite of reference test files — a set of PDF/A-1 conformant documents covering all requirements, and a set of intentionally non-conformant documents testing each specific violation — to which PDF/A tools could be certified. Certification required a tool to correctly identify conformant documents as valid and correctly identify each non-conformant document as failing the specific requirement it violated. In 2006, this certification programme was in its formation stage. By 2007 it would become the primary mechanism for giving meaning to the phrase "PDF/A certified tool."

First-year PDF/A-1 production experience

By the time of PDF Days Europe 2006, PDF/A-1 had been a published standard for approximately 14 months. Early adopters — primarily German government agencies, Swiss financial institutions, and Dutch document management system vendors — were sharing their first-year experiences. The font embedding problem at scale — Enterprise document management systems were producing PDFs at scale from legacy applications: mainframe print streams, Windows GDI printing, PostScript processing. In many of these pipelines, font embedding was not standard practice. The PDF/A-1 requirement for complete font embedding with proper /ToUnicode mappings was catching vast categories of documents that passed visual inspection but failed programmatic validation. Remediation at scale was the primary practical challenge. RGB colour in business documents — Most business document workflows were RGB-based. Screens, Office applications, and web content all used sRGB. PDF/A-1 required an output intent ICC profile for documents with colour content. Many organisations had never engaged with colour management; the concept of an output intent was foreign to their IT workflows. Guidance on which ICC profile to use for a "standard office document viewed on screen" was actively needed. The metadata alignment problem — PDF/A-1 required both DocInfo dictionary entries and XMP metadata, with the two in alignment. Applications generating PDFs were inconsistent: some populated only DocInfo, some only XMP, some both but with different values (e.g., different date formats or creator tool strings). The XMP requirement was widely seen as disproportionate overhead for straightforward document archiving. First validator tools — The first generation of PDF/A-1 validators were appearing in 2006: early versions of what would become Acrobat's built-in preflight, specialist prepress tools with PDF/A profiles, and early command-line validators. Their false-positive and false-negative rates were significant — validators disagreed with each other, which undermined confidence in the standard.

The path to ISO 32000-1

Adobe's PDF 1.7 specification had been published in November 2006 as the "PDF Reference, sixth edition." Adobe had announced its intention to submit PDF 1.7 to ISO for standardisation. The 2006 conference included discussion of what this submission would mean: The governance argument — PDF was the world's most widely used document format, but it was a proprietary specification maintained by a single company. Government agencies in multiple EU member states had legal requirements to use formats governed by open standards. ISO standardisation would resolve this and allow PDF to be formally mandated in public procurement. The technical freeze concern — ISO standardisation would subject future PDF revisions to the ISO committee process, which was significantly slower than Adobe's revision cycle. Some in the developer community were concerned that this would slow innovation. Others viewed the slower, consensus-driven pace as appropriate for a format used in long-term archiving. Subset standards alignment — PDF/A (ISO 19005), PDF/X (ISO 15930), and PDF/E (ISO 24517) were all normatively referencing specific PDF specification versions. Standardising the base specification as ISO 32000-1 would complete the formal ISO family structure, with all subset standards referencing the base ISO document.

Frequently asked questions

What is the PDF/A Competence Center and how does it certify tools?

The PDF/A Competence Center (PDFA-CC) is an industry body within the PDF Association that develops and administers a certification programme for PDF/A-creating and PDF/A-validating tools. Certification involves testing a tool against a standardised test corpus of PDF/A-conformant and intentionally non-conformant documents. A creating tool must produce valid PDF/A output for a defined set of document types. A validating tool must correctly accept valid documents and correctly reject non-conformant documents, identifying the specific requirement violated. Tools that pass receive PDFA-CC certification, which is the primary third-party quality signal in the PDF/A tool ecosystem. The certification is periodically updated for new PDF/A versions (PDF/A-2, PDF/A-3).

What was the main PDF standard before ISO 32000-1?

Before ISO 32000-1:2008, PDF was governed by Adobe's PDF Reference — a series of specification documents published by Adobe corresponding to each PDF version. The sixth edition, "PDF Reference, Adobe Portable Document Format version 1.7," was published in November 2006 and documented PDF 1.7. This was a de facto standard: widely implemented, publicly available, but ultimately under Adobe's control with no formal ISO or ANSI governance. Adobe submitted PDF 1.7 to the ISO TC 171 SC 2 WG 8 standardisation committee in 2007; ISO 32000-1 was published in 2008, with identical technical content to the PDF Reference 1.7 but with ISO governance for future maintenance.

Which ICC output intent profile should I use for a PDF/A document intended for screen viewing?

For PDF/A documents that will primarily be viewed on screen (not print), embed an sRGB ICC profile as the output intent. The standard sRGB profile (IEC 61966-2-1) is available from the International Color Consortium at icc.color.org and from the colour profiles included with most operating systems. In Adobe Acrobat Pro: Edit > Preferences > Color Management > Working Spaces shows the available colour profiles. When setting the output intent in Acrobat's PDF/A conversion, select sRGB IEC61966-2.1 (or the equivalent name in your tool). If your document contains greyscale content only, the output intent requirement may be relaxed in some PDF/A-2 conformance interpretations, but including an sRGB output intent is always safe practice.

Try it in your browser

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

Edit PDF Compress PDF Protect PDF Open editor