[
https://issues.apache.org/jira/browse/PDFBOX-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636729#comment-14636729
]
Maruan Sahyoun commented on PDFBOX-2896:
----------------------------------------
The generated XMP is
{code}
<x:xmpmeta xmlns:x="adobe:ns:meta/">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
<rdf:Description xmlns:dc="http://purl.org/dc/elements/1.1/"; rdf:about="">
<dc:title>
<rdf:Alt>
<rdf:li
xml:lang="x-default">/Users/msahyoun/Desktop/PDFATest.pdf</rdf:li>
</rdf:Alt>
</dc:title>
</rdf:Description>
<rdf:Description xmlns:pdfaid="http://www.aiim.org/pdfa/ns/id/";
rdf:about="PDFBox PDF/A sample">
<pdfaid:part>1</pdfaid:part>
<pdfaid:conformance>B</pdfaid:conformance>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
<?xpacket end="w"?>
{code}
where there are two different {{rdf:about}} attributes - my thanks go to
PDF-Tools for spotting this.
According to the XMP spec
{quote}
If the XMP data model has an AboutURI (6.1, “XMP packets”), that same URI shall
be the value of an rdf:about attribute in each top-level rdf:Description
element. Otherwise, the rdf:about attributes for all top- level rdf:Description
elements shall be present with an empty value. The rdf:about attribute shall
not be used in more deeply nested rdf:Description elements.
{quote}
I've changed the CreatePDF sample to not set the attribute for the second
{{ref:Description}} element. After that it's also validated with PDF-Tools
online checker.
[~tilman] at this point in time I don't think that it's worth the effort to put
that rule into XMPBox - WDYT?
> XMPBox not creating valid "title" entry in DublinCoreSchema in trunk
> --------------------------------------------------------------------
>
> Key: PDFBOX-2896
> URL: https://issues.apache.org/jira/browse/PDFBOX-2896
> Project: PDFBox
> Issue Type: Bug
> Components: XmpBox
> Affects Versions: 2.0.0
> Reporter: Tim Allison
> Priority: Minor
>
> On TIKA-1678, I was trying to generate a test PDF that had a dc:title in the
> XMP with XMPBox from PDFBox's trunk. I modified the code from CreatePDFA by
> adding this:
> {code}
> DublinCoreSchema dc = xmp.createAndAddDublinCoreSchema();
> dc.setTitle("this is the title");
> {code}
> The generated PDF doesn't appear to have a compliant dc:title entry in the
> XMP.
> [~tilman] noted the divergence from the standard
> [here|https://issues.apache.org/jira/browse/TIKA-1678?focusedCommentId=14634045&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14634045].
> What PDFBox does:
> {code}
> <dc:title>
> <rdf:Alt>
> <dc:li>this is the title</dc:li>
> </rdf:Alt>
> </dc:title>
> {code}
> It should be:
> {code}
> <dc:title>
> <rdf:Alt>
> <rdf:li xml:lang="x-default">this is the title</rdf:li>
> </rdf:Alt>
> </dc:title>
> {code}
> Error message from the PDF-Tools validator:
> {quote}
> 'dc:li' is not allowed in arrays. The elements must be rdf:li or rdf:_N,
> where N is a positive number.
> There is only one RDF resource allowed in XMP.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
