Conference October 2009 📍 San Jose, California, USA

PDF Days North America 2009 — San Jose: PDF as Open Standard and Enterprise Adoption

PDF Days North America 2009 took place in San Jose in October 2009. As the first North American PDF Days following ISO 32000-1 standardisation, the event focused on open standards in enterprise document management, PDF/A deployment experiences, and the growing use of PDF in regulated industries.

Official event page →

Key takeaways

Enterprise DMS adoption of PDF was near-universal — but generation quality was poor; sessions advocated PDF/A requirements at generation rather than conversion.
Web-based PDF delivery was emerging — linearisation and browser rendering were identified as the future direction.
PDF digital signatures were still a niche technology in 2009; adoption barriers (PKI cost, UX complexity, legal uncertainty) were explicitly discussed.
PDF was positioned as complementary to ODF/OOXML — output format vs. editable source format — defusing the format war positioning.
Approximately 130 delegates from enterprise document management, government contracting, software development, and legal technology.

PDF Days North America 2009 was held in San Jose, California, in October 2009 — a few months after the Berlin event, and during a period when ISO 32000-1 was beginning to reshape how enterprise software vendors and government agencies thought about PDF. Silicon Valley's proximity to Adobe's headquarters (also in San Jose) gave the event a distinctive technology-company flavour alongside the usual government and regulated-industry attendance. Approximately 130 delegates attended — the first North American PDF Days of note, establishing what would become a consistent bi-coastal PDF event calendar (alternating between Washington D.C. for the government focus and the West Coast for the technology industry focus). Sessions covered enterprise document management, open-source PDF infrastructure, digital signature adoption, and the emerging use of PDF in web applications.

Enterprise document management: PDF as the universal output format

By late 2009, PDF had become the default output format for virtually every enterprise document management system (DMS) — from SAP and Oracle ERP outputs to SharePoint document libraries and Documentum repositories. Sessions examined how organisations were managing PDF in large enterprise DMS deployments and what standards conformance meant for DMS vendor selection. Key themes from enterprise sessions: - **Generation vs storage**: Many enterprise systems generated PDFs from business applications (purchase orders, invoices, reports) as an afterthought — optimising for visual output but not for searchability, accessibility, or long-term archiving. Sessions advocated moving PDF/A requirements upstream to the generation step rather than applying post-hoc conversion. - **Metadata consistency**: Enterprise PDFs often had inconsistent metadata — document type, creation date, department — which made full-text search and records classification difficult. Sessions on the PDF metadata system (DocInfo vs XMP) and the value of standardised metadata templates were well-attended. - **Migration projects**: Several large enterprises were undertaking legacy PDF migration to PDF/A — driven by risk assessments that identified non-self-contained PDFs (referencing external fonts or colour profiles) as long-term accessibility risks.

PDF in web applications: the emerging challenge

2009 saw the early growth of web-based document management and the first generation of browser-based PDF viewing. Google Docs had launched PDF upload and viewing. Scribd was growing as a document publishing platform. The first experiments with browser-based PDF rendering were underway — Mozilla's PDF.js project would launch in 2011, but in 2009 the primary browser PDF experience was via the Acrobat/Reader plugin. Sessions explored what PDF in web applications required differently from desktop PDF: performance (large PDFs loaded slowly over HTTP), security (malicious PDFs delivered via web were the primary PDF exploit vector in 2009), and the emerging need for PDF linearisation to enable page-by-page web delivery. The PDF linearisation concept — structuring files for progressive download — was discussed in the context of web delivery. Several sessions predicted that the future of PDF viewing would increasingly be browser-based, reducing dependence on installed PDF reader applications — a prediction that proved accurate with PDF.js's adoption in Firefox (2012) and Chrome's native PDF viewer.

Digital signatures: from niche to mainstream

In 2009, PDF digital signatures were still primarily used in specialist contexts — federal government (PIV card signing), pharmaceutical regulatory submissions (FDA eCTD), and financial services. For most enterprises, "digital signature" still meant a scanned image of a handwritten signature pasted into a PDF — not a cryptographically verifiable signature. Sessions presented the business case for genuine cryptographic PDF digital signatures in enterprise contexts: contract execution, policy acknowledgements, and internal approval workflows. The barriers to adoption were examined honestly: certificate infrastructure cost, user experience complexity (smart cards, PIN management), and legal uncertainty about electronic signature acceptance in different jurisdictions. The PDF forms and signature field design guidance that emerged from these discussions helped organisations reduce the friction of signature deployment — particularly the guidance on Reader Extensions that allowed Adobe Reader users to sign PDFs without Acrobat Pro.

Open standards advocacy: PDF vs ODF vs proprietary formats

2009 was the height of the ODF vs OOXML format war — ISO's standardisation of OOXML (ISO/IEC 29500) in 2008 had been controversial, and the debate about which document format governments should mandate was active in multiple countries. Sessions at PDF Days North America 2009 positioned PDF as complementary to both ODF and OOXML — not competing with editable document formats but serving as the final-form, presentation-layer format that both document formats produced. PDF's role was as the universal output — the "printed document" equivalent in digital workflows — while ODF or OOXML served as the editable source. This framing proved influential in subsequent government policy discussions. Rather than arguing "PDF vs ODF," the PDF community successfully argued that they addressed different stages of the document lifecycle: ODF/OOXML for creation and collaboration, PDF for publication, sharing, archiving, and legal records.

Frequently asked questions

What is PDF.js and when was it introduced?

PDF.js is an open-source, JavaScript-based PDF renderer built by Mozilla. It parses PDF files and renders them using the HTML5 Canvas API, without requiring a native PDF plugin. PDF.js was publicly released in 2011 and integrated into Firefox as the default PDF viewer in version 19 (2013). It is also used by Google Drive, many web-based document management systems, and countless web applications. PDF.js does not execute PDF JavaScript — it renders page content and supports form filling and annotation, but not Acrobat-API scripting.

What were the main barriers to PDF digital signature adoption in enterprises in 2009?

In 2009, the main barriers were: (1) PKI infrastructure cost — issuing certificates to all employees required either a commercial CA (per-user cost) or an internal CA (infrastructure investment); (2) hardware token complexity — smart cards and USB tokens required card readers and driver management; (3) user experience — the signing workflow in Acrobat was complex for non-technical users; (4) legal uncertainty — the legal status of electronic signatures under ESIGN and state UETA varied, and many organisations were not confident about enforceability; (5) Reader Extensions requirement — only Acrobat Pro users could sign without special Reader Extensions licensing, limiting scalability.

How does PDF relate to ODF and OOXML in a document workflow?

ODF (Open Document Format, ISO/IEC 26300) and OOXML (Office Open XML, ISO/IEC 29500) are editable document formats — they store document content in a way that can be modified, tracked, and collaborated on. PDF is a final-form presentation format — it preserves visual layout precisely but is not designed for authoring or collaboration (though it supports annotations and comments). In a typical document workflow: create and edit in ODF or OOXML → review with comments using PDF annotations → publish and archive as PDF/A. The three formats are complementary, serving different stages of the document lifecycle.

Try it in your browser

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

Sign PDF Protect PDF Edit PDF Open editor