From: Jeremias Maerki Date: Fri, 22 Jun 2007 14:23:30 +0000 (+0000) Subject: A note on the PDF/A namespace confusion. X-Git-Tag: fop-0_94~74 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=6437c1d00cd12a8b1cfd33e2c16e6aa9560c867f;p=xmlgraphics-fop.git A note on the PDF/A namespace confusion. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@549827 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/src/documentation/content/xdocs/trunk/pdfa.xml b/src/documentation/content/xdocs/trunk/pdfa.xml index 505a10805..49ffbeb71 100644 --- a/src/documentation/content/xdocs/trunk/pdfa.xml +++ b/src/documentation/content/xdocs/trunk/pdfa.xml @@ -129,5 +129,31 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); activated at the same time.

+
+ Interoperability +

+ There has been some confusion about the namespace for the PDF/A indicator in the XMP + metadata. At least three variants have been seen in the wild: +

+ + + + + + + + + + + + + +
http://www.aiim.org/pdfa/ns/id.htmlobsolete, from an early draft of ISO-19005-1, used by Adobe Acrobat 7.x
http://www.aiim.org/pdfa/ns/idobsolete, found in the original ISO 19005-1:2005 document
http://www.aiim.org/pdfa/ns/id/correct, found in the technical corrigendum 1 of ISO 19005-1:2005
+

+ If you get an error validating a PDF/A file in Adobe Acrobat 7.x it doesn't mean that + FOP did something wrong. It's Acrobat that is at fault. This is fixed in Adobe Acrobat 8.x + which uses the correct namespace as described in the technical corrigendum 1. +

+