RE: Namespaces are dropped in XMP stream. XML invalid
Jörn Willhöft <[email protected]> Thu, 7 Nov 2024 11:28:48 +0100 (CET)
| Newsgroups | gmane.text.xml.fop.user |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_403639_911658455.1730975328272
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi Joao,
=20
thank you for taking the time to look into that issue. Meanwhile, I set up =
a test case with plain Apache FOP and could not reproduce the issue either.
=20
It still happens with the same static input via the Apache Camel FOP compon=
ent though. In both scenarios it's FOP 2.10 and the Camel component is actu=
ally just a thin wrapper. So I am currently trying to set up a better test =
case and analysis on the Camel side.
=20
Just for the records, I see that I quoted the wrong FO which added the XMP =
to a page (there is a test case for that already in FOP). Instead, the XMP =
should be added to the document. Since FOP FOP merges some metadata into th=
is stream there is a potential for error, but my tests showed that plain FO=
P works as it should. So this is the one I am using:
<fo:root
xmlns:fo=3D"http://www.w3.org/1999/XSL/Format"
font-family=3D"Arial">
<fo:layout-master-set>
<fo:simple-page-master master-name=3D"simple">
<fo:region-body region-name=3D"xsl-region-body" />
</fo:simple-page-master>
</fo:layout-master-set>
<fo:declarations>
<x:xmpmeta xmlns:x=3D"adobe:ns:meta/">
<rdf:RDF xmlns:abc=3D"http://www.abc.de/abc/"
xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=3D"" abc:def=3D"val" />
<rdf:Description xmlns:pdfaExtension=3D"http://www.aiim.org/pdfa/ns/extensi=
on/"
xmlns:pdfaProperty=3D"http://www.aiim.org/pdfa/ns/property#"
xmlns:pdfaSchema=3D"http://www.aiim.org/pdfa/ns/schema#" rdf:about=3D"">
<pdfaExtension:schemas>
<rdf:Bag>
<rdf:li rdf:parseType=3D"Resource">
<pdfaSchema:property>
<rdf:Seq>
<rdf:li rdf:parseType=3D"Resource">
<pdfaProperty:name>split</pdfaProperty:name>
</rdf:li>
</rdf:Seq>
</pdfaSchema:property>
</rdf:li>
</rdf:Bag>
</pdfaExtension:schemas>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
</fo:declarations>
<fo:page-sequence master-reference=3D"simple">
<fo:flow flow-name=3D"xsl-region-body">
<fo:block>SLIDE 1</fo:block>
</fo:flow>
</fo:page-sequence>
</fo:root>
=20
I'll report back after I eliminated all potential stupid mistakes on my sid=
e. It could also be a different XML stack or the different JVM in the Camel=
environment? I'll try to find out...
=20
Cheers
J=C3=B6rn Willh=C3=B6ft
> Joao Andre Goncalves <[email protected]> hat am =
06.11.2024 22:26 CET geschrieben:
> =20
> =20
>=20
> Hi,
>=20
> can you share the full FO? I tried to replicate your issue but my file is=
compatible with PDFA 3b. I used https://avepdf.com/en/pdfa-validation to v=
erify the pdf.
>=20
> Regards
>=20
> =20
>=20
> From: J=C3=B6rn Willh=C3=B6ft <[email protected]>
> Sent: Tuesday, November 5, 2024 5:26 AM
> To: [email protected]
> Subject: Namespaces are dropped in XMP stream. XML invalid
>=20
> =20
>=20
> =20
>=20
> You don't often get email from [email protected] mailto:jwi@willhoeft-=
it.com. Learn why this is important https://aka.ms/LearnAboutSenderIdentifi=
cation
>=20
> =20
>=20
> Dear list members,
>=20
> =20
>=20
> I need to create PDF/A-3B compliant documents with special references to =
an embedded document (ZUGFeRD compliant invoices). Currently, this fails in=
VeraPDF with some very vague and rather misleading validation errors:
>=20
> * "Specification: ISO 19005-3:2012, Clause: 6.6.2.1, Test number: 5
> All metadata streams present in the PDF shall conform to the XMP Specific=
ation. The XMP package must be encoded as UTF-8"
>=20
> * "Specification: ISO 19005-3:2012, Clause: 6.6.4, Test number: 1
> The PDF/A version and conformance level of a file shall be specified usin=
g the PDF/A Identification extension schema"
>=20
> * "Specification: ISO 19005-3:2012, Clause: 6.6.2.1, Test number: 4
> All metadata streams present in the PDF shall conform to the XMP Specific=
ation. All content of all XMP packets shall be well-formed, as defined by E=
xtensible Markup Language (XML) 1.0 (Third Edition), 2.1, and the RDF/XML S=
yntax Specification (Revised)"
>=20
> =20
>=20
> I finally tracked this down to FOP, which dropped some necessary namespac=
es in the created XMP stream. This can be reproduced with the corresponding=
example from the FOP homepage (https://xmlgraphics.apache.org/fop/2.10/met=
adata.html). E.g. here is the fo:
>=20
> <fo:simple-page-master master-name=3D"simple">
>=20
> <fo:region-body/>
>=20
> <pdf:page page-numbers=3D"*">
>=20
> <x:xmpmeta xmlns:x=3D"adobe:ns:meta/">
>=20
> <rdf:RDF xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns# h=
ttp://www.w3.org/1999/02/22-rdf-syntax-ns" xmlns:abc=3D"http://www.abc.de/a=
bc/ http://www.abc.de/abc/">
>=20
> <rdf:Description rdf:about=3D"" abc:def=3D"val"/>
>=20
> <rdf:Description rdf:about=3D"" xmlns:pdfaExtension=3D"http://www=
.aiim.org/pdfa/ns/extension/ http://www.aiim.org/pdfa/ns/extension/"
>=20
> xmlns:pdfaSchema=3D"http://www.aiim.org/pdfa/ns/=
schema# http://www.aiim.org/pdfa/ns/schema"
>=20
> xmlns:pdfaProperty=3D"http://www.aiim.org/pdfa/n=
s/property# http://www.aiim.org/pdfa/ns/property">
>=20
> <pdfaExtension:schemas>
>=20
> <rdf:Bag>
>=20
> <rdf:li rdf:parseType=3D"Resource">
>=20
> <pdfaSchema:property>
>=20
> <rdf:Seq>
>=20
> <rdf:li rdf:parseType=3D"Resource">
>=20
> <pdfaProperty:name>split</pdfaProperty:name>
>=20
> </rdf:li>
>=20
> </rdf:Seq>
>=20
> </pdfaSchema:property>
>=20
> </rdf:li>
>=20
> </rdf:Bag>
>=20
> </pdfaExtension:schemas>
>=20
> </rdf:Description>
>=20
> </rdf:RDF>
>=20
> </x:xmpmeta>
>=20
> </pdf:page>
>=20
> </fo:simple-page-master>
>=20
> And this is returned when I run pdfinfo -meta example.pdf:
>=20
> <?xpacket begin=3D"" id=3D"W5M0MpCehiHzreSzNTczkc9d"?><x:xmpmeta xmlns:x=
=3D"adobe:ns:meta/">
> <rdf:RDF xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns# http:=
//www.w3.org/1999/02/22-rdf-syntax-ns">
> <rdf:RDF xmlns:abc=3D"http://www.abc.de/abc/" abc:def=3D"val" rdf:ab=
out=3D""/>
> <rdf:RDF xmlns:dc=3D"http://purl.org/dc/elements/1.1/" rdf:about=3D"=
">
> <dc:format>application/pdf</dc:format>
> <dc:language>
> <rdf:Bag>
> <rdf:li>x-unknown</rdf:li>
> </rdf:Bag>
> </dc:language>
> <dc:date>
> <rdf:Seq>
> <rdf:li>2024-11-05T11:46:27+01:00</rdf:li>
> </rdf:Seq>
> </dc:date>
> </rdf:RDF>
> <rdf:RDF xmlns:pdf=3D"http://ns.adobe.com/pdf/1.3/" rdf:about=3D"">
> <pdf:Producer>Apache FOP Version 2.10</pdf:Producer>
> <pdf:PDFVersion>1.4</pdf:PDFVersion>
> </rdf:RDF>
> <rdf:RDF xmlns:pdfaExtension=3D"http://www.aiim.org/pdfa/ns/extensio=
n/" rdf:about=3D"">
> <pdfaExtension:schemas>
> <rdf:Bag>
> <rdf:li rdf:parseType=3D"Resource">
> <pdfaSchema:property>
> <rdf:Seq>
> <rdf:li rdf:parseType=3D"Resource">
> <pdfaProperty:name>split</pdfaProperty:name>
> </rdf:li>
> </rdf:Seq>
> </pdfaSchema:property>
> </rdf:li>
> </rdf:Bag>
> </pdfaExtension:schemas>
> </rdf:RDF>
> <rdf:RDF xmlns:pdfaid=3D"http://www.aiim.org/pdfa/ns/id/" rdf:about=
=3D"">
> <pdfaid:conformance>B</pdfaid:conformance>
> <pdfaid:part>3</pdfaid:part>
> </rdf:RDF>
> <rdf:RDF xmlns:xmp=3D"http://ns.adobe.com/xap/1.0/" rdf:about=3D"">
> <xmp:MetadataDate>2024-11-05T11:46:27+01:00</xmp:MetadataDate>
> <xmp:CreateDate>2024-11-05T11:46:27+01:00</xmp:CreateDate>
> </rdf:RDF>
> </rdf:RDF>
> </x:xmpmeta>
> <?xpacket end=3D"r"?>
>=20
> As you can see, the two namespaces xmlns:pdfaSchema=3D"http://www.aiim.or=
g/pdfa/ns/schema# http://www.aiim.org/pdfa/ns/schema" and xmlns:pdfaPrope=
rty=3D"http://www.aiim.org/pdfa/ns/property# http://www.aiim.org/pdfa/ns/pr=
operty"
>=20
> are dropped from the metadata, while the prefixes are still used. Thus, t=
he XML is invalid and so is the PDF/A.
>=20
> This is pretty unfortunate, as I don't have any workaround for this. I am=
using Apache FOP 2.10 in the context of Apache Camel 4.8.1. Any help would=
be greatly appreciated.
>=20
> =20
>=20
> With kind regards,
>=20
> J=C3=B6rn Willh=C3=B6ft
>=20
>=20
> ---------------------------------------------
> Joao Andre Goncalves
> Customer Developer
>=20
> t | m 07733161880
> [email protected]
> smartcommunications.com https://www.smartcommunications.com/
>=20
> https://www.smartcommunications.com/resources/benchmark-report/?utm_sourc=
e=3Doutlook&utm_medium=3Demail&utm_campaign=3Dbenchmark_report_2024_webpage
>=20
>=20
> The largest study of its kind! Unlock unparalleled insights into customer=
preferences and stay ahead in today=E2=80=99s market. Download now! https:=
//www.smartcommunications.com/resources/benchmark-report/?utm_source=3Doutl=
ook&utm_medium=3Demail&utm_campaign=3Dbenchmark_report_2024_webpage =09Smar=
t Communications is a trading name of SmartComms SC Limited which is regist=
ered in England under No. 4303041 whose registered office is at Suite 23, L=
CLB, 95 Mortimer Street, London, W1W 7GB. Please consider the environment b=
efore printing. The contents of this e-mail are intended for the named addr=
essee only. It contains confidential information. Unless you are the named =
addressee or an authorized designee, you may not copy or use it, or disclos=
e it to anyone else. If you received it in error please notify us immediate=
ly and then destroy it. Smart Communications will process your data as desc=
ribed in the Smart Communications' External Privacy Policy. https://www.sma=
rtcommunications.com/external-privacy-policy/
>=20
> Follow us on LinkedIn https://www.linkedin.com/company/15166060/admin/ an=
d Twitter https://twitter.com/ccminnovators?lang=3Den
>=20
------=_Part_403639_911658455.1730975328272
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<!doctype html>
<html>
<head>=20
<meta charset=3D"UTF-8">=20
</head>
<body>
<div>
Hi Joao,
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"default-style">
thank you for taking the time to look into that issue. Meanwhile, I set =
up a test case with plain Apache FOP and could not reproduce the issue eith=
er.
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"default-style">
It still happens with the same static input via the Apache Camel FOP com=
ponent though. In both scenarios it's FOP 2.10 and the Camel component is a=
ctually just a thin wrapper. So I am currently trying to set up a better te=
st case and analysis on the Camel side.
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"default-style">
Just for the records, I see that I quoted the wrong FO which added the X=
MP to a page (there is a test case for that already in FOP). Instead, the X=
MP should be added to the document. Since FOP FOP merges some metadata into=
this stream there is a potential for error, but my tests showed that plain=
FOP works as it should. So this is the one I am using:
</div>=20
<div class=3D"default-style">
<fo:root=20
<br>xmlns:fo=3D"http://www.w3.org/1999/XSL/Format"
<br>font-family=3D"Arial">
<br><fo:layout-master-set>
<br><fo:simple-page-master master-name=3D"simple">
<br><fo:region-body region-name=3D"xsl-region-body" />
<br></fo:simple-page-master>
<br></fo:layout-master-set>
<br><fo:declarations>
<br><x:xmpmeta xmlns:x=3D"adobe:ns:meta/">
<br><rdf:RDF xmlns:abc=3D"http://www.abc.de/abc/"
<br>xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<br><rdf:Description rdf:about=3D"" abc:def=3D"val" />
<br><rdf:Description xmlns:pdfaExtension=3D"http://www.aiim.org/pdfa/=
ns/extension/"
<br>xmlns:pdfaProperty=3D"http://www.aiim.org/pdfa/ns/property#"
<br>xmlns:pdfaSchema=3D"http://www.aiim.org/pdfa/ns/schema#" rdf:about=
=3D"">
<br><pdfaExtension:schemas>
<br><rdf:Bag>
<br><rdf:li rdf:parseType=3D"Resource">
<br><pdfaSchema:property>
<br><rdf:Seq>
<br><rdf:li rdf:parseType=3D"Resource">
<br><pdfaProperty:name>split</pdfaProperty:name>
<br></rdf:li>
<br></rdf:Seq>
<br></pdfaSchema:property>
<br></rdf:li>
<br></rdf:Bag>
<br></pdfaExtension:schemas>
<br></rdf:Description>
<br></rdf:RDF>
<br></x:xmpmeta>
<br></fo:declarations>
<br><fo:page-sequence master-reference=3D"simple">
<br><fo:flow flow-name=3D"xsl-region-body">
<br><fo:block>SLIDE 1</fo:block>
<br></fo:flow>
<br></fo:page-sequence>
<br></fo:root>
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"default-style">
I'll report back after I eliminated all potential stupid mistakes on my =
side. It could also be a different XML stack or the different JVM in the Ca=
mel environment? I'll try to find out...
</div>=20
<div class=3D"default-style">
</div>=20
<div class=3D"io-ox-signature">=20
<p>Cheers<br> J=C3=B6rn Willh=C3=B6ft</p>=20
</div>=20
<blockquote type=3D"cite">=20
<div>
Joao Andre Goncalves <[email protected]>=
hat am 06.11.2024 22:26 CET geschrieben:
</div>=20
<div>
</div>=20
<div>
</div>=20
<div class=3D"WordSection1">=20
<p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt; mso-fareast-la=
nguage: EN-US;">Hi, <br><br>can you share the full FO? I tried to replicate=
your issue but my file is compatible with PDFA 3b. I used <a href=3D"https=
://avepdf.com/en/pdfa-validation">https://avepdf.com/en/pdfa-validation</a>=
to verify the pdf.<br><br>Regards</span></p>=20
<p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt; mso-fareast-la=
nguage: EN-US;"> </span></p>=20
<div>=20
<div style=3D"border: none; border-top: solid #E1E1E1 1.0pt; padding: =
3.0pt 0cm 0cm 0cm;" data-darkreader-inline-border-right=3D"" data-darkreade=
r-inline-border-bottom=3D"" data-darkreader-inline-border-left=3D"" data-da=
rkreader-inline-border-top=3D"">=20
<p class=3D"MsoNormal"><strong><span style=3D"font-size: 11.0pt; font=
-family: 'Calibri',sans-serif;">From:</span></strong><span style=3D"font-si=
ze: 11.0pt; font-family: 'Calibri',sans-serif;"> J=C3=B6rn Willh=C3=B6ft &l=
t;[email protected]> <br><strong>Sent:</strong> Tuesday, November 5, =
2024 5:26 AM<br><strong>To:</strong> [email protected]<br><s=
trong>Subject:</strong> Namespaces are dropped in XMP stream. XML invalid</=
span></p>=20
</div>=20
</div>=20
<p class=3D"MsoNormal"> </p>=20
<table class=3D"MsoNormalTable" style=3D"width: 100.0%;" border=3D"0" w=
idth=3D"100%" cellspacing=3D"0" cellpadding=3D"0" align=3D"left">=20
<tbody>=20
<tr>=20
<td style=3D"width: .3pt; background: #A6A6A6; padding: 5.25pt 1.5pt=
5.25pt 1.5pt;" width=3D"0" data-darkreader-inline-bgcolor=3D"" data-darkre=
ader-inline-bgimage=3D""> </td>=20
<td style=3D"width: revert !important; background: revert !important=
; padding: revert !important; aspect-ratio: revert !important; block-size: =
revert !important; border: revert !important; bottom: revert !important; co=
lor: revert !important; color-scheme: revert !important; content-visibility=
: revert !important; cursor: revert !important; direction: revert !importan=
t; display: revert !important; font-size: revert !important; height: revert=
!important; hyphens: revert !important; letter-spacing: revert !important;=
line-height: revert !important; margin: revert !important; opacity: revert=
!important; order: revert !important; outline: revert !important; overflow=
: revert !important; position: revert !important; resize: revert !important=
; rotate: revert !important; scale: revert !important; tab-size: revert !im=
portant; table-layout: revert !important; text-align: revert !important; te=
xt-indent: revert !important; text-orientation: revert !important; text-ove=
rflow: revert !important; text-shadow: revert !important; text-transform: r=
evert !important; text-wrap: revert !important; top: revert !important; tra=
nsition: revert !important; user-select: revert !important; vertical-align:=
revert !important; visibility: revert !important; white-space: revert !imp=
ortant; word-break: revert !important; word-spacing: revert !important; wri=
ting-mode: revert !important; zoom: revert !important;" width=3D"100%" data=
-darkreader-inline-bgimage=3D"">=20
<div>=20
<p class=3D"MsoNormal" style=3D"mso-element: frame; mso-element-fr=
ame-hspace: 2.25pt; mso-element-wrap: around; mso-element-anchor-vertical: =
paragraph; mso-element-anchor-horizontal: column; mso-height-rule: exactly;=
"><span style=3D"font-size: 9.0pt; font-family: 'Segoe UI',sans-serif; colo=
r: #212121;" data-darkreader-inline-color=3D"">You don't often get email fr=
om <a href=3D"mailto:[email protected]">[email protected]</a>. <a hre=
f=3D"https://aka.ms/LearnAboutSenderIdentification"> Learn why this is impo=
rtant</a> </span></p>=20
</div> </td>=20
<td style=3D"width: revert !important; background: revert !important=
; padding: revert !important; aspect-ratio: revert !important; block-size: =
revert !important; border: revert !important; bottom: revert !important; co=
lor: revert !important; color-scheme: revert !important; content-visibility=
: revert !important; cursor: revert !important; direction: revert !importan=
t; display: revert !important; font-size: revert !important; height: revert=
!important; hyphens: revert !important; letter-spacing: revert !important;=
line-height: revert !important; margin: revert !important; opacity: revert=
!important; order: revert !important; outline: revert !important; overflow=
: revert !important; position: revert !important; resize: revert !important=
; rotate: revert !important; scale: revert !important; tab-size: revert !im=
portant; table-layout: revert !important; text-align: revert !important; te=
xt-indent: revert !important; text-orientation: revert !important; text-ove=
rflow: revert !important; text-shadow: revert !important; text-transform: r=
evert !important; text-wrap: revert !important; top: revert !important; tra=
nsition: revert !important; user-select: revert !important; vertical-align:=
revert !important; visibility: revert !important; white-space: revert !imp=
ortant; word-break: revert !important; word-spacing: revert !important; wri=
ting-mode: revert !important; zoom: revert !important; align: left !importa=
nt;" width=3D"75" data-darkreader-inline-bgimage=3D""> </td>=20
</tr>=20
</tbody>=20
</table>=20
<div>=20
<div>=20
<p class=3D"MsoNormal">Dear list members,</p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal"> </p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">I need to create PDF/A-3B compliant documents =
with special references to an embedded document (ZUGFeRD compliant invoices=
). Currently, this fails in VeraPDF with some very vague and rather mislead=
ing validation errors:</p>=20
</div>=20
<div>=20
<div>=20
<p class=3D"MsoNormal">* "Specification: ISO 19005-3:2012, Clause: 6=
.6.2.1, Test number: 5 <br>All metadata streams present in the PDF shall co=
nform to the XMP Specification. The XMP package must be encoded as UTF-8"</=
p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">* "Specification: ISO 19005-3:2012, Clause: 6=
.6.4, Test number: 1 <br>The PDF/A version and conformance level of a file =
shall be specified using the PDF/A Identification extension schema"</p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">* "Specification: ISO 19005-3:2012, Clause: 6=
.6.2.1, Test number: 4 <br>All metadata streams present in the PDF shall co=
nform to the XMP Specification. All content of all XMP packets shall be wel=
l-formed, as defined by Extensible Markup Language (XML) 1.0 (Third Edition=
), 2.1, and the RDF/XML Syntax Specification (Revised)"</p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal"> </p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">I finally tracked this down to FOP, which dro=
pped some necessary namespaces in the created XMP stream. This can be repro=
duced with the corresponding example from the FOP homepage (<a href=3D"http=
s://xmlgraphics.apache.org/fop/2.10/metadata.html">https://xmlgraphics.apac=
he.org/fop/2.10/metadata.html</a>). E.g. here is the fo:</p>=20
</div>=20
<div>=20
<pre><em><span style=3D"font-family: 'Courier New';"><fo:simple-p=
age-master master-name=3D"simple"></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> <fo:r=
egion-body/></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> <pdf:=
page page-numbers=3D"*"></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <x:xmpmeta xmlns:x=3D"adobe:ns:meta/"></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <rdf:RDF xmlns:rdf=3D"<a href=3D"http://www.w3.org/1999/=
02/22-rdf-syntax-ns"><span style=3D"font-style: normal;">http://www.w3.org/=
1999/02/22-rdf-syntax-ns#</span></a>" xmlns:abc=3D"<a href=3D"http://www.ab=
c.de/abc/"><span style=3D"font-style: normal;">http://www.abc.de/abc/</span=
></a>"></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <rdf:Description rdf:about=3D"" abc:def=3D"v=
al"/></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <rdf:Description rdf:about=3D"" xmlns:pdfaEx=
tension=3D"<a href=3D"http://www.aiim.org/pdfa/ns/extension/"><span style=
=3D"font-style: normal;">http://www.aiim.org/pdfa/ns/extension/</span></a>"=
</span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
xmlns:pdfaSchema=3D"=
<a href=3D"http://www.aiim.org/pdfa/ns/schema"><span style=3D"font-style: n=
ormal;">http://www.aiim.org/pdfa/ns/schema#</span></a>"</span></em></pre>=
=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
xmlns:pdfaProperty=
=3D"<a href=3D"http://www.aiim.org/pdfa/ns/property"><span style=3D"font-st=
yle: normal;">http://www.aiim.org/pdfa/ns/property#</span></a>"></span><=
/em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <pdfaExtension:schemas></span=
></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <rdf:Bag></span><=
/em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; <rdf:li =
rdf:parseType=3D"Resource"></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
<pdfaSchema:property></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
<rdf:Seq></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
<rdf:li rdf:parseType=3D"Resource"></span></=
em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
<pdfaProperty:name>split</pdf=
aProperty:name></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
</rdf:li></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp;  =
; </rdf:Seq></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; =
</pdfaSchema:property></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; </rdf:li=
></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; </rdf:Bag></span>=
</em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; </pdfaExtension:schemas></spa=
n></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; </rdf:Description></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; </rdf:RDF></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> &nb=
sp; </x:xmpmeta></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"> </pdf=
:page></span></em></pre>=20
<pre><em><span style=3D"font-family: 'Courier New';"></fo:simple-=
page-master></span></em></pre>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">And this is returned when I run pdfinfo -meta=
example.pdf:</p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal" style=3D"margin-bottom: 12.0pt;"><span style=
=3D"font-family: 'Courier New'; color: black; background: white;" data-dark=
reader-inline-color=3D"" data-darkreader-inline-bgcolor=3D"" data-darkreade=
r-inline-bgimage=3D""><?xpacket begin=3D"" id=3D"W5M0MpCehiHzreSzNTczkc9=
d"?><x:xmpmeta xmlns:x=3D"adobe:ns:meta/"> </span><span style=3D"f=
ont-family: 'Courier New';"><br> <rdf:RDF xmlns:rdf=3D"<a hre=
f=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns">http://www.w3.org/1999/02/=
22-rdf-syntax-ns#</a>"> <br> <rdf:RDF xm=
lns:abc=3D"<a href=3D"http://www.abc.de/abc/">http://www.abc.de/abc/</a>" a=
bc:def=3D"val" rdf:about=3D""/> <br> <rd=
f:RDF xmlns:dc=3D"<a href=3D"http://purl.org/dc/elements/1.1/">http://purl.=
org/dc/elements/1.1/</a>" rdf:about=3D""> <br> &n=
bsp; <dc:format>application/pdf</dc:format> <b=
r> <dc:language> <br>&=
nbsp; <rdf:Ba=
g> <br>  =
; <rdf:li>x-unknown</rdf:li> <br> &=
nbsp; </rdf:Bag> <br>&=
nbsp; </dc:language> <br>&nb=
sp; <dc:date> <br> &nbs=
p; <rdf:Seq> <br=
> &n=
bsp; <rdf:li>2024-11-05T11:46:27+01:00</rdf:li> <br> =
</rdf:Seq>=
; <br> </dc:date> <br>=
</rdf:RDF> <br> =
<rdf:RDF xmlns:pdf=3D"<a href=3D"http://ns.adobe.com/pdf/1.3/">htt=
p://ns.adobe.com/pdf/1.3/</a>" rdf:about=3D""> <br> &nb=
sp; <pdf:Producer>Apache FOP Version 2.10</=
pdf:Producer> <br> <pd=
f:PDFVersion>1.4</pdf:PDFVersion> <br> &nbs=
p;</rdf:RDF> <br> <rdf:RDF xmlns:pdfa=
Extension=3D"<a href=3D"http://www.aiim.org/pdfa/ns/extension/">http://www.=
aiim.org/pdfa/ns/extension/</a>" rdf:about=3D""> <br> &=
nbsp; <pdfaExtension:schemas> <br> =
<rdf:Bag> <br>&=
nbsp; &nbs=
p; <rdf:li rdf:parseType=3D"Resource"> <br> &nb=
sp; =
<pdfaSchema:property> <br> &=
nbsp; &nbs=
p; <rdf:Seq> <br>  =
; &n=
bsp; <rdf:li rdf:parseType=3D"Resource"> <br> &=
nbsp; &nbs=
p; <pdf=
aProperty:name>split</pdfaProperty:name> <br> &nb=
sp; =
</rdf:li> <br> &=
nbsp; &nbs=
p; </rdf:Seq> <br> &nbs=
p; &=
nbsp;</pdfaSchema:property> <br> &=
nbsp; </rdf:li> <br> &n=
bsp; </rdf:Bag> =
<br> </pdfaExtension:sche=
mas> <br> </rdf:RDF> <br> =
<rdf:RDF xmlns:pdfaid=3D"<a href=3D"http://www.aiim.or=
g/pdfa/ns/id/">http://www.aiim.org/pdfa/ns/id/</a>" rdf:about=3D""> <br>=
<pdfaid:conformance>B=
</pdfaid:conformance> <br> &=
nbsp;<pdfaid:part>3</pdfaid:part> <br> &=
nbsp;</rdf:RDF> <br> <rdf:RDF xmlns:x=
mp=3D"<a href=3D"http://ns.adobe.com/xap/1.0/">http://ns.adobe.com/xap/1.0/=
</a>" rdf:about=3D""> <br> &nbs=
p;<xmp:MetadataDate>2024-11-05T11:46:27+01:00</xmp:MetadataDate>=
; <br> <xmp:CreateDate>=
;2024-11-05T11:46:27+01:00</xmp:CreateDate> <br> &nb=
sp; </rdf:RDF> <br> </rdf:RDF> <br></x:xmpme=
ta> <br><?xpacket end=3D"r"?></span></p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">As you can see, the two namespaces <em><span =
style=3D"font-family: 'Aptos',sans-serif;">xmlns:pdfaSchema=3D"<a href=3D"h=
ttp://www.aiim.org/pdfa/ns/schema"><span style=3D"font-style: normal;">http=
://www.aiim.org/pdfa/ns/schema#</span></a>" and xmlns:pdfaPrope=
rty=3D"<a href=3D"http://www.aiim.org/pdfa/ns/property"><span style=3D"font=
-style: normal;">http://www.aiim.org/pdfa/ns/property#</span></a>"</span></=
em></p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">are dropped from the metadata, while the pref=
ixes are still used. Thus, the XML is invalid and so is the PDF/A.</p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal">This is pretty unfortunate, as I don't have a=
ny workaround for this. I am using Apache FOP 2.10 in the context of Apache=
Camel 4.8.1. Any help would be greatly appreciated.</p>=20
</div>=20
<div>=20
<p class=3D"MsoNormal"> </p>=20
</div>=20
</div>=20
<div>=20
<p>With kind regards,</p>=20
<p> J=C3=B6rn Willh=C3=B6ft</p>=20
</div>=20
</div>=20
</div>=20
<table style=3D"width: 400px;">=20
<tbody>=20
<tr>=20
<td colspan=3D"2">
<hr align=3D"left" size=3D"4" width=3D"30%"></td>=20
</tr>=20
<tr>=20
<td style=3D"font-family: Arial Black; color: #20407f; font-size: 11p=
x;" width=3D"65%" data-darkreader-inline-color=3D"">Joao Andre Goncalves<br=
>Customer Developer<br><br></td>=20
</tr>=20
<tr>=20
<td style=3D"font-family: Arial; color: #20407f; font-size: 9px;" dat=
a-darkreader-inline-color=3D"">t | m 07733161880<br>JGoncalves@SmartCommuni=
cations.com<br><a href=3D"https://www.smartcommunications.com/">smartcommun=
ications.com</a><br><br></td>=20
</tr>=20
</tbody>=20
</table>=20
<table style=3D"width: 400px;">=20
<tbody>=20
<tr>=20
<td colspan=3D"2" width=3D"100%"><a href=3D"https://www.smartcommunic=
ations.com/resources/benchmark-report/?utm_source=3Doutlook&utm_medium=
=3Demail&utm_campaign=3Dbenchmark_report_2024_webpage"><img width=3D"" =
height=3D"160"></a><br><br></td>=20
</tr>=20
<tr>=20
<td style=3D"font-family: Arial Black; color: #20407f; font-size: 10p=
x;" width=3D"28%" data-darkreader-inline-color=3D""><a href=3D"https://www.=
smartcommunications.com/resources/benchmark-report/?utm_source=3Doutlook&am=
p;utm_medium=3Demail&utm_campaign=3Dbenchmark_report_2024_webpage">The =
largest study of its kind! Unlock unparalleled insights into customer prefe=
rences and stay ahead in today=E2=80=99s market. Download now!</a></td>=20
<td style=3D"font-family: Arial; color: #939597; line-height: 13px; f=
ont-size: 9px;" width=3D"72%" data-darkreader-inline-color=3D"">Smart Commu=
nications is a trading name of SmartComms SC Limited which is registered in=
England under No. 4303041 whose registered office is at Suite 23, LCLB, 95=
Mortimer Street, London, W1W 7GB. Please consider the environment before p=
rinting. The contents of this e-mail are intended for the named addressee o=
nly. It contains confidential information. Unless you are the named address=
ee or an authorized designee, you may not copy or use it, or disclose it to=
anyone else. If you received it in error please notify us immediately and =
then destroy it. Smart Communications will process your data as described i=
n the Smart Communications' <a href=3D"https://www.smartcommunications.com/=
external-privacy-policy/">External Privacy Policy.</a></td>=20
</tr>=20
<tr>=20
<td style=3D"font-family: Arial Black; color: #20407f; font-size: 10p=
x;" colspan=3D"2" width=3D"100%" data-darkreader-inline-color=3D""><br>Foll=
ow us on <a href=3D"https://www.linkedin.com/company/15166060/admin/">Linke=
dIn</a> and <a href=3D"https://twitter.com/ccminnovators?lang=3Den">Twitter=
</a></td>=20
</tr>=20
</tbody>=20
</table>=20
</blockquote>
</body>
</html>
------=_Part_403639_911658455.1730975328272--