2014-09-01 Preserving PDF - identify, validate, repair

Version 43 by Ed Fay
on Sep 02, 2014 08:03.

compared with
Version 44 by Ed Fay
on Sep 02, 2014 08:12.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (17)

View Page History
| 09.30 - 10.30 | {color:#222222}{*}Talk: What does it take to build a comprehensive PDF/A validator?*{color} {color:#222222}{*}Will any two validators ever agree? *{color}\\ {color:#222222}{*}And why is there no readily available reference implementation?*{color}{color:#222222} {color}\\
\\ {color:#222222}{*}Discussion{*}{color}{color:#222222}: How to validate and who validates the validators.{color} | Hacking | {color:#222222}Olaf Drümmer, Chairman of the PDF Association{color}\\ |
| 10:30 - 10:45 | {color:#222222}{_}Break{_}{color}\\ {color:#222222}_(sign up for optional sessions)_{color} | | |
{color:#222222}_(sign up for optional sessions)_{color} | | |
| 10.45 - 11.15 | Write-up group work on wiki - prepare development tasks | Plenary | |
| 11:15 - 13:00 | {color:#222222}{*}Hacking and Optional sessions{*}{color}{color:#222222}:{color}\\
(1) Policy workflow talk from our hosts GoPortis (Michelle/Yvonne)\\
(1) Policy workflow talk from our hosts GoPortis (Michelle/Yvonne) \\ {color:#222222}Our hosts, will explain their organisation background and motivation behind their policy decision-making.{color} {color:#222222}They will also give practical examples of their current workflows with PDF files.{color}\\
\\
(2) Validation demonstrations using virtual environments (Carl) \\
* {color:#222222}Automating characterisation, PDF/A validation and policy conformance checking.{color}
* {color:#222222}An evidence based demonstration of JHOVE, Apache Tika, and Apache PDFBox/PreFlight. {color} | Hacking | Carl Wilson, OPF \\
Sabine Krug, SLUB Dresden \\
\\
\\
\\
\\
\\
\\
Michelle Lindlar / Yvonne Freise, Go Portis \\
\\
\\ |
| 13:00 - 14:00 | {color:#222222}{_}Lunch{_}{color}\\ | | |
| 14:00 \- 16:00 | *Hacking and Optional Sessions* \\
Continue to work on tools, or the optional sessions will run again if there is demand.\\
{color:#222222}Finish requirement write ups and progress on the wiki in teams.{color}\\ {color:#222222}Prepare presentations/demos to report back to the group.{color}\\ {color:#222222}Try out the tools discussed on day 1 with prepared exercises on a virtual machine.{color}\\
\\ | {color:#222222}Final hacking, check in code{color} {color:#222222}and prepare to report back to the group.{color} | OPF |
Continue to work on tools, or the optional sessions will run again if there is demand. \\ {color:#222222}Finish requirement write ups and progress on the wiki in teams.{color}\\ {color:#222222}Prepare presentations/demos to report back to the group.{color} | {color:#222222}Final hacking, check in code{color} {color:#222222}and prepare to report back to the group.{color} | All |
| 16:00 - 17:00 | {color:#222222}{*}Presentations & Coffee{*}{color}\\ {color:#222222}Each team will report back to the group on their progress and show demonstrations as appropriate.{color}\\
{color:#222222}Each team will report back to the group on their progress and show demonstrations as appropriate.{color}\\
\\
{color:#222222}{*}Road-mapping{*}{color}\\
\\ {color:#222222}{*}Road-mapping{*}{color}\\
\\ {color:#222222}As a group we'll discuss what has worked well, and what hasn't worked and why.{color}\\ {color:#222222}We'll discuss how both requirements, and development actions arising from the event can be taken{color} \\ {color:#222222}forward by OPF and its members.{color}\\
\\ {color:#222222}Wrap up and next steps{color} | \\
Plenary session | OPF \\ {color:#222222}Olaf Drümmer{color} |
Plenary session | All  \\
\\ |
| 17:00 | _Close_ | | |