Conference May 2007 📍 Berlin, Germany

PDF Days Europe 2007 — Berlin: The First PDF Days and the PDF/A Launch

PDF Days Europe 2007 was the inaugural PDF Days event, held in Berlin in May 2007 — two years after the publication of PDF/A-1 (ISO 19005-1:2005). The event marked the founding of the PDF/A Competence Center (later the PDF Association) and established the annual rhythm of European PDF standards conferences.

Official event page →

Key takeaways

PDF Days Europe 2007 was the inaugural PDF Days conference, founding a community forum that would continue annually for nearly two decades.
PDF/A-1 (ISO 19005-1) was 18 months old; early adopters were government archiving, legal preservation, and financial services.
Font embedding, colour management, and XMP metadata were the most common PDF/A-1 conformance failure causes in 2007.
The PDF/A Competence Center was established to provide rigorous, auditable certification for PDF/A tools rather than self-certification.
ISO standardisation of PDF 1.7 (which became ISO 32000-1 in 2008) was imminent and actively discussed as a governance improvement.

PDF Days Europe 2007 was the inaugural PDF Days event, held in Berlin in May 2007, organised by the PDF Association — which had itself only been founded in 2006. The 2007 conference launched what would become the longest-running annual gathering for the PDF developer and enterprise community. It coincided with the very early period of PDF/A adoption: ISO 19005-1 (PDF/A-1) had been published in 2005 and the PDF/A Competence Center had been established to support implementation. The first PDF Days was primarily a community-building event. The PDF specification was still an Adobe proprietary format (ISO 32000-1 would not be published until 2008). The conference brought together the developers of PDF creation tools, RIP vendors, archiving system builders, and early adopters of PDF/A in government and finance. The sessions reflected the concerns of a community adapting to a newly published archiving standard and trying to make PDF interoperability work in real deployments.

The founding of the PDF Days series and the PDF/A Competence Center

The PDF Days conference series was founded by the PDF Association with a specific mission: to provide a neutral, vendor-collaborative forum for the PDF developer and enterprise community that was distinct from Adobe-controlled events. The PDF/A Competence Center (PDFA-CC), established as part of the PDF Association's structure, was the other founding institution of this period. The PDFA-CC had a specific role: to develop and administer a testing and certification programme for PDF/A-creating and PDF/A-validating tools. The concern in 2007 was that "PDF/A compliant" was being claimed by vendors with varying degrees of rigour. A tool might pass the test files available at the time but fail on edge cases involving specific font types, colour profiles, or metadata structures. The PDFA-CC was building a systematic test suite and certification process to give "PDF/A certified" a concrete, auditable meaning. The inaugural PDF Days addressed both the technical implementation questions and the ecosystem-development questions: who was adopting PDF/A, for what use cases, which tools worked, and what the most common implementation failures were.

PDF/A-1 adoption: early use cases and implementation challenges

PDF/A-1 had been published in September 2005. By May 2007, the format had been in existence for about eighteen months. Real-world adoption was concentrated in several areas: Government document archiving — European government agencies, particularly in Germany, Switzerland, and the Netherlands, were among the earliest PDF/A-1 adopters. German federal and state archiving requirements and the Dutch "NEN 2082" information management standard were driving mandated use in public sector document management. Legal document preservation — Law firms and courts dealing with electronic discovery and long-term case file preservation were examining PDF/A as a format for assured readability of case documents years into the future. The legal sector requirement for exact replication of document appearance (critical for disputed documents) aligned well with PDF/A's fixed-appearance guarantee. Financial document archiving — Banks and insurance companies subject to regulatory retention requirements (MiFID in the EU, various national regulations) were evaluating PDF/A for customer statement and contract archiving. Implementation challenges being reported in 2007: Font embedding failures — The most common PDF/A-1 conformance failure was font-related: fonts not embedded, fonts with incomplete Unicode mappings, and proprietary fonts with licensing that prohibited embedding. Many legacy document workflows used system fonts that were not embedded in the output PDF. Colour management — PDF/A-1 requires an output intent (ICC colour profile) for PDFs with colour content. Many document workflows did not include colour management and produced PDFs without the required output intent. Metadata requirements — PDF/A-1 requires XMP metadata conforming to specific schemas. Existing document management systems often produced DocInfo dictionaries but not XMP, or XMP that did not include the required PDF/A-specific conformance schema.

The PDF format before ISO: governance and the case for standardisation

In May 2007, PDF was still an Adobe proprietary format governed by Adobe's PDF Reference. The most recent version was PDF 1.7, documented in Adobe's "PDF Reference, sixth edition" published in November 2006. Adobe had announced its intention to submit PDF 1.7 to ISO, but the submission had not yet formally occurred (that happened in 2007, with publication of ISO 32000-1 in 2008). The governance question was a significant theme at the inaugural PDF Days. The arguments for ISO standardisation that were made in 2007: Government procurement neutrality — Public procurement rules in many jurisdictions required mandated file formats to be open international standards. PDF's proprietary status was a barrier to formal mandating in EU government contexts. Maintenance transparency — Under Adobe ownership, decisions about what went into or out of the PDF specification were Adobe's alone. ISO governance would give the broader community voice in future specification development through the ISO TC 171 SC 2 committee process. Independent implementation confidence — Open-source and third-party PDF implementors were working from a published specification that Adobe could technically revise at any time. ISO 32000-1 would create a stable published standard that independent implementations could target without risk of the reference changing. The counter-concern was that ISO governance might slow down innovation or produce committee-designed extensions. This tension between stability and innovation would remain a recurring theme in PDF specification discussions through the PDF 2.0 development cycle.

Frequently asked questions

When was the first PDF Days conference and what was its purpose?

The first PDF Days conference was held in Berlin in May 2007, organised by the PDF Association. Its founding purpose was to create a vendor-neutral, community-owned forum for PDF developers, enterprise adopters, and standards participants — distinct from Adobe-controlled events. PDF Days conferences are specifically focused on PDF technical implementation, interoperability, and the ISO standards family (PDF/A, PDF/X, PDF/UA, ISO 32000). The Berlin location reflects the PDF Association's German origins and has remained the primary venue for the European editions of the conference.

What are the most common causes of PDF/A-1 conformance failure?

The most common PDF/A-1 conformance failures identified in early adoption are: (1) Fonts not embedded — PDF/A requires all fonts to be embedded in the file; system fonts and fonts not embedded by the creating application fail. (2) Missing or incomplete /ToUnicode mappings — required for text extraction reliability. (3) Missing output intent — PDF/A requires an ICC colour profile (output intent) for documents containing colour. (4) Missing or non-conformant XMP metadata — PDF/A requires XMP metadata with the PDF/A conformance schema; older tools produced only DocInfo dictionaries. (5) Prohibited features — encryption, transparent objects (in PDF/A-1), external content references, JavaScript, and embedded executables are prohibited. Validators such as veraPDF or PAC can identify which specific requirements a PDF fails.

What is the PDF/A Competence Center and what does it do?

The PDF/A Competence Center (PDFA-CC) is an industry body founded as part of the PDF Association in 2007 to develop and administer certification for PDF/A-creating and PDF/A-validating tools. It maintains a test suite of PDF/A conformant and non-conformant test files, publishes implementation guidance, and awards certification to tools that demonstrate correct PDF/A creation and validation against the test suite. Certification by the PDFA-CC provides assurance beyond a vendor's self-declaration of PDF/A support. The PDFA-CC also contributed to the development of PDF/A-2 and PDF/A-3 through technical feedback from implementation experience.

Try it in your browser

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

Edit PDF Compress PDF Sign PDF Open editor