[
https://issues.apache.org/jira/browse/PDFBOX-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Leleu reopened PDFBOX-1368:
--------------------------------
I updated my XMPBox module and I still have two types of error :
The first one :
<rdf:Seq>
<rdf:li rdf:parseType="Resource">
<stEvt:action>converted</stEvt:action>
<stEvt:instanceID>uuid:95890424-4550-4d2f-9830-431aa7f9dcd4</stEvt:instanceID>
<stEvt:parameters>converted to PDF/A-1b</stEvt:parameters>
<stEvt:softwareAgent>Preflight</stEvt:softwareAgent>
<stEvt:when>2011-08-18T13:13:33-04:00</stEvt:when>
</rdf:li>
</rdf:Seq>
In this example, the "li" contains a Description but the syntax is quite
specific because the rdf:Description element isn't used. Instead the "li"
element must be parsed as a Resource (parseType:Resource is for me the same as
rdf:Description)
- The second one (see attached file override_ns.rdf):
The namespace "http://ns.adobe.com/pdf/1.3/"; is override in this XMP stream. My
PDF/A validation failed because the Copyright entry is unknown. But this entry
is declared in the last PDFAExtension.
It should be possible to override an existing schema with the PDFAextension
description (or at least append the custom description). Your opinion ?
BR,
Eric
> Xmp validation KO if there are complex type in a seq element
> -------------------------------------------------------------
>
> Key: PDFBOX-1368
> URL: https://issues.apache.org/jira/browse/PDFBOX-1368
> Project: PDFBox
> Issue Type: Bug
> Components: XmpBox
> Affects Versions: 1.8.0
> Reporter: Eric Leleu
> Assignee: Guillaume Bailleul
> Fix For: 1.8.0
>
> Attachments: metadata.rdf, override_ns.rdf
>
>
> Hi,
> I updated my local repository with the last revision of the XMPBox.
> I encounter a validation issue on five PDF/A that were valid before.
> In attachment, there are the XMP stream.
> The XMPBox parser expects a text content in a <rdf:seq><rdf:li> element, but
> in this XMP there are a rdf:Description as content.
> BR,
> Eric
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
