[jira] [Commented] (FOP-3304) Custom XMP Extension Schema dropped when generating PDF/A-2a and PDF/UA-1 compatible PDF

    [ https://issues.apache.org/jira/browse/FOP-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083719#comment-18083719 ] 

Michael Schubert commented on FOP-3304:
---------------------------------------

Hello [~jgoncalves] , thank you for fixing this issue. Do you know when a new version of FOP (2.12?) will be released?

> Custom XMP Extension Schema dropped when generating PDF/A-2a and PDF/UA-1 compatible PDF
> ----------------------------------------------------------------------------------------
>
>                 Key: FOP-3304
>                 URL: https://issues.apache.org/jira/browse/FOP-3304
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 2.10, 2.11
>            Reporter: Michael Schubert
>            Priority: Minor
>             Fix For: main
>
>         Attachments: FOP_Test.zip, report_test.fo, report_test_2.fo, veraPDFValidationReport.xml
>
>
> I am using fop 2.10 to generate a PDF-File which needs to be compatible with both PDF/A-2a and PDF/UA-1.
> The resulting file passes the PDF/UA-1 check, but fails the PDF/A-2a verification because of rule 6.6.2.3.1:
>  * Test number1: "XMP property is either not predefined, or is not defined in any XMP extension schema";
>  * Test number 2: "XMP property does not correspond to type null".
> The offending property is {{{}myschema:CustomProp{}}}, which is correctly defined in the fo-file, but somehow seems to be dropped when the document is created with both PDF/A-2a and PDF/UA-1 profiles activated. Actually, my custom XMP extension schema definition for schema "{{{}myschema{}}}" seems to be replaced by the definition of the schema "{{{}pdfuaid{}}}", which is automatically generated into the PDF.
> I reproduced the problem using the files in the attached zip-archive.
> Using the same {{report_test.fo}} as input, I started {{fop}} three times:
>  # with {{-c cfg_a_2a.xml}} (configuration file which only activates the PDF/A-2a mode)
> *Result:* {{test_1_a_2a.pdf}} - {color:#00875a}passes the PDF/A-2a validation{color}
>  # with {{-c cfg_ua_1.xml}} (configuration file which only activates the PDF/UA-1 mode)
> *Result:* {{test_1_ua_1.pdf}} - {color:#00875a}passes the PDF/UA-1 validation{color}
>  # with {{-c cfg.xml}} (configuration file which activates both the PDF/A-2a and the PDF/UA-1 modes)
> *Result:* {{test_1.pdf}} - {color:#FF0000}passes the PDF/UA-1 validation, but not the PDF/A-2a validation{color}
> see the attached veraPDFValidationReport.xml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)