On March 29th, iText organized a summit in Ghent to inform customers and users about the road ahead. Today, we're proud to present the videos that were made of all the different presentations:
Overview of the iText Summit videos
Intro by Frank Gielen
Leonard Rosenthol explains the importance of standardization and the need for diversification. He will give a brief overview of the umbrella of standards: ISO-32000-1 and its various subsets PDF/X, PDF/A, PDF/UA,...) and a preview of things to come.
In this talk, we'll discuss why and when it makes sense to create a PDF document on an Android device. We'll show some examples of Android apps involving iText, and we'll explain the differences between the regular iText and the Android port. Speaking of the Android port: you can also use it in the context of a cloud solution running on Google App Engine.
In PDF, there are interactive forms and there are interactive forms. There are many tools that support the AcroForm technology to create templates with form fields that can be filled in manually or programmatically. The coordinates of these fields are fixed: all the data needs to fit into predefined rectangles on predefined pages. With the XML Forms Architecture (XFA), you can define fields in a more dynamic way. You can create repeatable subforms that allow the document to adapt to the amount of data that is entered. In this talk, we'll focus on using XFA forms as a template.
The PDF file format is organised very differently from most other filetypes. This is a source of its strength and weakness and the cause of a huge number of misunderstandings. In this talk I will take you inside the PDF file to give you an understanding of how it works, the strengths of its elegant design and also possible areas of weakness. At the end I want you to know exactly how to make the PDF file format work for you.
HTML5 is the first decent version of HTML to tempt me away from PDF for some tasks. It also turns out to have a lot of similarities to PDF and Java. So let me spend 30 minutes getting you up to speed on the similarities so that you can extend your existing coding skills to this new platform.
PAdES (acronym of PDF Advanced Electronic Signatures) is a set of standards published by ETSI to support European requirements for electronic signatures. These standards are based on existing PDF Signatures as specified in ISO-32000-1, but also include support for the validation of signatures which are stored for years or even decades (LTV). Paulo will explain how PAdES is integrated in iText, and show the different options that are available to sign PDF documents.
We'll take a deep dive into the world of Digital Certificates and future proof algorithms and remove some of the jargon and hyperbole around signatures. We'll highlight the simple and effective steps that iText delivers in order to create a PDF document that preserves its integrity, its authenticity and its longevity towards a diverse set of multilingual relying parties. We'll focus on key areas such as the choice of certificate hierarchy and the provision of additional trust services. As a Certification Authority, GlobalSign provides ongoing support throughout the lifetime of the Digital Certificate with key PAdES best practice services such as Timestamping, Certificate Revocation Lists and OCSP responder services. We'll touch on some code samples and highlight the alternative vertical markets that are already operational.
Together with Thieme-Meulenhoff, Q42 is developing a large scale Educational iPad app for use in schools. PDF Encryption, rendering and renderfarms are used within Google App Engine to maintain, deliver and process PDF documents and deliver them to the iPad clients. Already a few thousand students are using the current App in a Beta Program for a year now. ThiemeMeulenhoff is a large Educational publisher in The Netherlands. In this lecture we'll dive into the Google App Engine architectural setup and the pro's and cons we've learned in the development process.
iText is free to use under the AGPLv3 license. But free doesn't mean free of obligations. This session gives a quick guide to (A)GPLv3 compliance (see annex).