New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Documentation about GreenField- and/vs. PDFBox-implementation #956

Open
r-pf opened this Issue Apr 16, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@r-pf
Copy link

r-pf commented Apr 16, 2018

Dev Effort

1D

Description

Based on e.g. #955, #938 and #939 the following question:

Is there are documentation (present in the web) which describes the reason for a new/second implementation named GreenField and the advantages/disadvantages of it vs. the PDFBox-implementation?

@bdoubrov

This comment has been minimized.

Copy link
Contributor

bdoubrov commented Apr 18, 2018

I don't think we put this explicitly to the web site. But the reasons are fairly simple:

  • PDFBox is a proven PDF parser, but unfortunately it didn't fit into the PREFORMA project, which required that all the code should be licensed under MPLv2+ and GPLv3+. This excluded Apache license, as used by PDFBox

  • the initial version of veraPDF validation was developed based on PDFBox library mainly because it allowed to test the validation model at a much earlier stage. Later on a a completely new (Grenfield) PDF parser was developed

  • the goal is always to have both versions of veraPDF to be fully compatible. So, any difference in validation results are to be fixed.

  • most of the optimization efforts are spent now on the Greenfield parser. So, we normally recommend this version in long run. But PDFBox version is supported as well.

@beckymcg beckymcg added bug P1 labels Jan 3, 2019

@beckymcg beckymcg added this to the v1.14-m4 milestone Jan 3, 2019

@bdoubrov

This comment has been minimized.

Copy link
Contributor

bdoubrov commented Jan 10, 2019

See also the discussion in #923

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment