From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114346 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: luigi scarso via ntg-context Newsgroups: gmane.comp.tex.context Subject: Re: XMP metadata schema yields invalid PDF/A Date: Sat, 5 Feb 2022 00:37:44 +0100 Message-ID: References: <1f7be313-e921-1fdf-f87c-33d3899e397a@xs4all.nl> Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3142165151389305244==" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26478"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luigi scarso To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Sat Feb 05 00:38:42 2022 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane-mx.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nG8A5-0006kG-Fo for gctc-ntg-context-518@m.gmane-mx.org; Sat, 05 Feb 2022 00:38:41 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 2FCD32A17E4; Sat, 5 Feb 2022 00:38:03 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayNdk3vYjeSb; Sat, 5 Feb 2022 00:38:01 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id A63D02A22C8; Sat, 5 Feb 2022 00:38:01 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 8EBB42A22C8 for ; Sat, 5 Feb 2022 00:37:59 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSGYSTrW7zBT for ; Sat, 5 Feb 2022 00:37:58 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.167.181; helo=mail-oi1-f181.google.com; envelope-from=luigi.scarso@gmail.com; receiver= Original-Received: from mail-oi1-f181.google.com (mail-oi1-f181.google.com [209.85.167.181]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 289202A17E4 for ; Sat, 5 Feb 2022 00:37:58 +0100 (CET) Original-Received: by mail-oi1-f181.google.com with SMTP id y23so10277527oia.13 for ; Fri, 04 Feb 2022 15:37:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=QpJ0sRC4Fubg2t4voduZfctaPk29W6gk9b6vSP7E6vY=; b=XIS8THktHjCHLsG1WXcuWL70PXPKTOqKCmCJuJ6avShnlPzVFQ9SWyEz9g9nuuh7dq /PMTXGORRbb+hQER3nXVdSbGTbstEB4G6R+FCws9dT+uha54Pux7GHSKV2bzInwdaXQ6 txabRbCmJperS0nhOgpdv3oMjjF6G2/hq3xAiorgfZfuBovYm6Z/kY4hThz9xBfqWLt/ as7P5sGGwaTffCuSYXI6wtapvgoLb0M0dq9uZm/3SLrNCM+bw60TaSPj+EOMax7bh3c1 kwozf/RdukDf5zWBxe7NyEj3EK6Kp8YHrgOH50HNnlB8mHWNg0q2KnRQevl9xbj+5Nxq VaYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=QpJ0sRC4Fubg2t4voduZfctaPk29W6gk9b6vSP7E6vY=; b=oSoIedAp5KWlACz4P8cUyezYXIsXonJqQBo/17Xl4gkITMTUd8Ww5DwQa4iBvpsTrL r6EWEdp4b/uPp4bBfPILzd1ayyk4x2HQlx9OlpD9R5hBDPuCQ3ZjUafnGQiDDtJqcRJN EO6pfKsbdrlGNKkx2ZVjlZO2t5b3f+DNShiny0tk8utD+IXGpJ3ANoqpcGb1CggYO35f 1pRWN3uO+g47plSwbXgKB4T5yvsdST4rrH64xuKr+S2nC9D+EHFHtDvEJfFYlo1FTsFT g7EnOAVab/3WrxDcm68PVKx4DCOTZU0l3GrGl/5wDT4mCCZVoRr78qXRmClkhZVxI80b wXlw== X-Gm-Message-State: AOAM531wIuKiecABwnngIXlInwQyLrt973tFzoYjo9J39vVZQDrEIPy0 4RCUHTDGl98uV5goXvZAKn6Vk8S3Jd+XUXQE+Tn6BkoZ X-Google-Smtp-Source: ABdhPJyJ9+Lc3BPVHAbkUJOXfSB6V66wGj++mgnwzfmOUme0i55JkiFRN4Mb7Nf89U1KvU3AoLt8vYydEjAcAI3/BdQ= X-Received: by 2002:a05:6808:1645:: with SMTP id az5mr2801072oib.313.1644017875045; Fri, 04 Feb 2022 15:37:55 -0800 (PST) In-Reply-To: X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.io gmane.comp.tex.context:114346 Archived-At: --===============3142165151389305244== Content-Type: multipart/alternative; boundary="00000000000072508a05d739bd55" --00000000000072508a05d739bd55 Content-Type: text/plain; charset="UTF-8" On Fri, Feb 4, 2022 at 11:11 PM Karl Pettersson via ntg-context < ntg-context@ntg.nl> wrote: > 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 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 I am missing something here... true FOO makes a valid pdf 3a with verapdf 1.20.1. But dc:description is like dc:title, so where we are redefining dc:description as Text ? -- luigi --00000000000072508a05d739bd55 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Feb 4, 2022 at 11:11 PM Karl = Pettersson via ntg-context <ntg-co= ntext@ntg.nl> wrote:
On Fri, Feb 04, 2022 at 10:25:27PM +0100, Hans Hagen via ntg-co= ntext 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 define= d with
> > the wrong type in the embedded XMP extension schema.
> >
> > https://tex.stac= kexchange.com/questions/632380/generate-pdf-a-with-context
> >
> > https://github.com/veraPDF/veraPDF-l= ibrary/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=3Drdf#= l81
> so "dc:description" is not permitted? it is mentioned in
>
> https://www.dublincore.org/specifications/dublin-core/dcmi-te= rms/#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=3D"x-default"> structure.

https://github.com/ver= aPDF/veraPDF-library/issues/1224#issuecomment-1029932963

(I suppose the reference to "title" in the issue comment should b= e "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

=
<dc:description>FOO</dc:description>
makes a val= id pdf 3a with verapdf 1.20.1.
But dc:description is like dc:titl= e, so where we are redefining dc:description as Text ?
=C2=A0
--
luigi
--00000000000072508a05d739bd55-- --===============3142165151389305244== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============3142165151389305244==--