From: Karl Pettersson via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Karl Pettersson <karl.pettersson@klpn.se>
Subject: Re: XMP metadata schema yields invalid PDF/A
Date: Fri, 4 Feb 2022 23:11:33 +0100 [thread overview]
Message-ID: <Yf2klQY+WSfK62y2@karl-ThinkPad-P50> (raw)
In-Reply-To: <1f7be313-e921-1fdf-f87c-33d3899e397a@xs4all.nl>
On Fri, Feb 04, 2022 at 10:25:27PM +0100, Hans Hagen via ntg-context wrote:
> On 2/4/2022 7:29 PM, Karl Pettersson via ntg-context wrote:
> > Hi
> >
> > PDF/A files generated using ConTeXt fail validation with veraPDF, and
> > the reason seems to be that the dc:description metadata is defined with
> > the wrong type in the embedded XMP extension schema.
> >
> > https://tex.stackexchange.com/questions/632380/generate-pdf-a-with-context
> >
> > https://github.com/veraPDF/veraPDF-library/issues/1224
> >
> > I can reproduce the problem using TeX Live 2021 (MkIV 2021.03.05). The
> > definition seems to be controlled by this code.
> >
> > https://source.contextgarden.net/tex/context/base/mkiv/lpdf-pua.xml?search=rdf#l81
> so "dc:description" is not permitted? it is mentioned in
>
> https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/description
>
> (btw it never failed before)
The description element is permitted, but the problem seems to be that
its valueType is defined as Text in the embedded schema, while the
metadata element in the PDF has an embedded <rdf:Alt><rdf:li
xml:lang="x-default"> structure.
https://github.com/veraPDF/veraPDF-library/issues/1224#issuecomment-1029932963
(I suppose the reference to "title" in the issue comment should be "description".)
Validating with veraPDF <1.20 does not raise the error. The validation
seems to have changed for redefined types in that version.
https://github.com/veraPDF/veraPDF-library/blob/integration/RELEASENOTES.md#validation
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
--
Karl Pettersson
Uppsala, Sweden
https://static-dust.klpn.se/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-02-04 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 18:29 Karl Pettersson via ntg-context
2022-02-04 21:25 ` Hans Hagen via ntg-context
2022-02-04 21:36 ` luigi scarso via ntg-context
2022-02-04 22:11 ` Karl Pettersson via ntg-context [this message]
2022-02-04 23:37 ` luigi scarso via ntg-context
2022-02-05 8:48 ` Karl Pettersson via ntg-context
2022-02-05 8:59 ` luigi scarso via ntg-context
2022-02-05 12:14 ` Karl Pettersson via ntg-context
2022-02-05 12:28 ` Karl Pettersson via ntg-context
2022-02-05 12:33 ` luigi scarso via ntg-context
2022-02-05 14:18 ` luigi scarso via ntg-context
2022-02-05 14:29 ` Karl Pettersson via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yf2klQY+WSfK62y2@karl-ThinkPad-P50 \
--to=ntg-context@ntg.nl \
--cc=karl.pettersson@klpn.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).