From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114348 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 09:59: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="===============7794488092960182375==" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33505"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luigi scarso , mailing list for ConTeXt users To: Karl Pettersson Original-X-From: ntg-context-bounces@ntg.nl Sat Feb 05 10:00:26 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 1nGGvh-0008Qj-5S for gctc-ntg-context-518@m.gmane-mx.org; Sat, 05 Feb 2022 10:00:25 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id D2C812A2820; Sat, 5 Feb 2022 10:00:04 +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 AvZbJIASUaT4; Sat, 5 Feb 2022 10:00:03 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 77A7E2A280C; Sat, 5 Feb 2022 10:00:03 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id E8F422A280C for ; Sat, 5 Feb 2022 10:00:00 +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 41NncBlPzYR3 for ; Sat, 5 Feb 2022 09:59:59 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.161.42; helo=mail-oo1-f42.google.com; envelope-from=luigi.scarso@gmail.com; receiver= Original-Received: from mail-oo1-f42.google.com (mail-oo1-f42.google.com [209.85.161.42]) (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 960E52A17DC for ; Sat, 5 Feb 2022 09:59:59 +0100 (CET) Original-Received: by mail-oo1-f42.google.com with SMTP id p4-20020a4a8e84000000b002e598a51d60so7547396ook.2 for ; Sat, 05 Feb 2022 00:59:59 -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 :cc; bh=uJspAO1T8v3O11t7XDCaEFDUClNGgjt1wcjFBaU/0d8=; b=DncR/45EYdfLXdYBuMEjkTGANUBXnm2Arz/KCCm7Fgyl+f9yjBiRKMk3T1qjVGhUZl Isw1fz10fNXDky7r6GyuxMprWl2Z0TQEbwquW6cumzTUGcCkkug2NEEX2P7DSNdWXlI9 HM05PqrHx8kpZo7lOqn9C00DgCcQifyz7cz15OiJq1ZDdB4CUMUQc524QvZdHsQyaUOx ivj02SXDxLkMob4sQPAnFHpuEQPfK7enqkLFc++quly+1nGwE5YvogQG4ERYz6gae2GX yp2TTKfaItf6x/86dnzg2BntxyWvhxAfg8JMseZKq/f5RULW5NB3vsj4KCtUTg0zRfUn 4gig== 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:cc; bh=uJspAO1T8v3O11t7XDCaEFDUClNGgjt1wcjFBaU/0d8=; b=6g8ur+6KAemhwynnh/U770u/VLEPNVTFN8juqmNBZ17NV+MiPFLERExmpr4WziDlui WTdKHDWcyXAzFtmI5g1cU7Ln+g/Y7d4070W9xmHEzbbdvDoYu53SJmCM0gDkRFaavN3M TlPKUv/isZdO2lnE6S3WJ+3CMjqtU9dkpJI3KqRD72SAfuPdCLaVC8aCvTbsNxWawnlc pHX0zwdSAeDUIQRq7AYW4hGCNs3qYTseWQz9j1nc0s2WRFX1sQgFA7FKZksvmG0PgBYx 5Ew0+UG/ou54PJiu39IOikEKpy0A0ORw35r1nToFDODXbDaWqOOqqKwkIYEdmzYgjcc2 LEbw== X-Gm-Message-State: AOAM530051krNCO1rTIDqIubYCQInigRzyJfaVxnKcATBaUzI16+UhKl kdNfSBIqynsJXKqg5DnzfD10k/sbBNvJCavGuk8= X-Google-Smtp-Source: ABdhPJwIAsfh0WMHfjpPIG8Gh3tyE9LDtww4emFB7U6XWtNU7K4+WmZALPHVVFZVypHINrl7ZTFYsz4hmVm2wkjVRls= X-Received: by 2002:a4a:e742:: with SMTP id n2mr793506oov.1.1644051595934; Sat, 05 Feb 2022 00:59: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:114348 Archived-At: --===============7794488092960182375== Content-Type: multipart/alternative; boundary="0000000000005e41b505d74197da" --0000000000005e41b505d74197da Content-Type: text/plain; charset="UTF-8" On Sat, Feb 5, 2022 at 9:48 AM Karl Pettersson wrote: > > Attach metadata xml for the non-validating and validating example > (extraced with `pdfinfo -meta | xmllint format -`) in the > Github issue. > > Here is a reference to the description element. Note that only > description seems to be redefined, not title. > it's not redefined -- it's dropped. And this is ok. You can also check with FOO TITLE and again it's valid. But https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:1:v1:en and https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:2:v1:en:tab:1 suggest that dc:description and dc:title are of the same type, which is coherent with XMPSpecificationPart1.pdf as in https://github.com/adobe/XMP-Toolkit-SDK/tree/main/docs I.e. these are correct -- but Subject must agree with dc:description TITLE At least, this is what I understand. -- luigi --0000000000005e41b505d74197da Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Feb 5, 2022 at 9:48 AM Karl P= ettersson <karl.pettersson@kl= pn.se> wrote:

Attach metadata xml for the non-validating and validating example
(extraced with `pdfinfo -meta | xmllint format -`) in the
Github issue.

Here is a reference to the description element. Note that only
description seems to be redefined, not title.


it's not redefined -- it's dropped. And this = is ok.
You can also check with=C2=A0
=C2=A0 <dc:desc= ription>FOO</dc:description>
=C2=A0 =C2=A0 =C2= =A0 <dc:title>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <rdf:Alt>
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <rdf:li xml:lang=3D"x-default"= >TITLE</rdf:li>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 </rdf:Alt>=C2=A0 =C2=A0 =C2=A0 </dc:title>
and again it's valid.<= /div>
But=C2=A0
and=C2=A0
suggest that dc:description and dc:title are of the same= type,
which is coherent with=C2=A0

I.e. these are correct=C2=A0 =C2=A0--=C2=A0 but = Subject must agree with dc:description
=C2=A0 <dc:description&= gt;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <rdf:Alt>
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 <rdf:li xml:lang=3D"x-default"/>
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 </rdf:Alt>
=C2=A0 =C2=A0 =C2=A0 </dc:descr= iption>
=C2=A0 =C2=A0 =C2=A0 <dc:title>
=C2=A0 =C2=A0 =C2=A0= =C2=A0 <rdf:Alt>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <rdf:li xm= l:lang=3D"x-default">TITLE</rdf:li>
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 </rdf:Alt>
=C2=A0 =C2=A0 =C2=A0 </dc:title>
=C2=A0
At least, this is what I understand.
<= div>
--
luigi
--0000000000005e41b505d74197da-- --===============7794488092960182375== 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== --===============7794488092960182375==--