[
https://issues.apache.org/jira/browse/FOP-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077127#comment-18077127
]
Joao Goncalves commented on FOP-3304:
-------------------------------------
[~mschubert] I got the second solution to work without problems, but could you
add the fo you mentioned for the first solution? I tried to add the pdfuaid
myself, but for some reason, the PDF still doesn't validate with VeraPDF. I'm
trying to figure out which of the two options is better. I don't want to remove
the Extension work from commons, but perhaps we can merge it all together
instead of just simply having both of the extensions in the PDF.
Currently, the second solution will result in the following:
{code:java}
<rdf:Description xmlns:pdfaExtension="http://www.aiim.org/pdfa/ns/extension/";
xmlns:pdfaProperty="http://www.aiim.org/pdfa/ns/property#";
xmlns:pdfaSchema="http://www.aiim.org/pdfa/ns/schema#"; rdf:about="">
<pdfaExtension:schemas>
<rdf:Bag>
<rdf:li rdf:parseType="Resource">
<pdfaSchema:namespaceURI>https://myschema.de/pdfa/2a/</pdfaSchema:namespaceURI>
<pdfaSchema:prefix>myschema</pdfaSchema:prefix>
<pdfaSchema:property>
<rdf:Seq>
<rdf:li rdf:parseType="Resource">
<pdfaProperty:category>external</pdfaProperty:category>
<pdfaProperty:name>CustomProp</pdfaProperty:name>
<pdfaProperty:description>My custom
property</pdfaProperty:description>
<pdfaProperty:valueType>Text</pdfaProperty:valueType>
</rdf:li>
</rdf:Seq>
</pdfaSchema:property>
<pdfaSchema:schema>My schema</pdfaSchema:schema>
</rdf:li>
<rdf:li rdf:parseType="Resource">
<pdfaSchema:schema>PDF/UA identification
schema</pdfaSchema:schema>
<pdfaSchema:namespaceURI>http://www.aiim.org/pdfua/ns/id/</pdfaSchema:namespaceURI>
<pdfaSchema:prefix>pdfuaid</pdfaSchema:prefix>
<pdfaSchema:property>
<rdf:Seq>
<rdf:li rdf:parseType="Resource">
<pdfaProperty:name>part</pdfaProperty:name>
<pdfaProperty:valueType>Integer</pdfaProperty:valueType>
<pdfaProperty:category>internal</pdfaProperty:category>
<pdfaProperty:description>Indicates, which
part of ISO 14289 standard is followed</pdfaProperty:description>
</rdf:li>
</rdf:Seq>
</pdfaSchema:property>
</rdf:li>
</rdf:Bag>
</pdfaExtension:schemas>
</rdf:Description> {code}
> 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
> Assignee: Joao Goncalves
> Priority: Minor
> Attachments: FOP_Test.zip, report_test.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)
