Hi Aspose team,
we would like to create ZUGFerd-compliant PDF files with Aspose. In principle, this works quite well.
However, when checking the generated PDF file, we noticed that the XMP data in the PDF file
are not quite correct.
The following information is not correct:
- Zugferd version:
Always seems to be 1.0. However, this should depend on the embedded XML file and could therefore also be 2.0 - Zugferd ConformanceLevel:
Always appears to be EXTENDED. However, this should depend on the XML file included and could therefore also be BASIC, for example
Is there a way to configure this data in the course of generating the Zugferd or to do this by directly modifying the XMP data?
Content of XMP-data created by Aspose
…
pdfaExtension:schemas
rdf:Bag
<rdf:li rdf:parseType=“Resource”>
pdfaSchema:schemaZUGFeRD PDFA Extension Schema</pdfaSchema:schema>
pdfaSchema:namespaceURIurn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0#</pdfaSchema:namespaceURI>
…
</rdf:li>
</rdf:Seq>
</pdfaSchema:property>…
<rdf:Description rdf:about=“” xmlns:zf=“urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0#”>
zf:DocumentFileNamezugferd-invoice.xml</zf:DocumentFileName>
zf:DocumentTypeINVOICE</zf:DocumentType>
zf:Version1.0</zf:Version>
zf:ConformanceLevelEXTENDED</zf:ConformanceLevel>
</rdf:Description>
Wanted content of XMP-data
…
pdfaExtension:schemas
rdf:Bag
<rdf:li rdf:parseType=“Resource”>
pdfaSchema:schemaZUGFeRD PDFA Extension Schema</pdfaSchema:schema>
pdfaSchema:namespaceURIurn:zugferd:pdfa:CrossIndustryDocument:invoice:2p0#</pdfaSchema:namespaceURI>
…
</rdf:li>
</rdf:Seq>
</pdfaSchema:property>
…<rdf:Description xmlns:zf="urn:zugferd:pdfa:CrossIndustryDocument:invoice:2p0#" rdf:about=""> <zf:DocumentFileName>zugferd-invoice.xml</zf:DocumentFileName> <zf:DocumentType>INVOICE</zf:DocumentType> <zf:Version>2p0</zf:Version> <zf:ConformanceLevel>BASIC</zf:ConformanceLevel> </rdf:Description>
Kind regards
Matthias