ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso via ntg-context <ntg-context@ntg.nl>
To: Karl Pettersson <karl.pettersson@klpn.se>
Cc: luigi scarso <luigi.scarso@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XMP metadata schema yields invalid PDF/A
Date: Sat, 5 Feb 2022 09:59:44 +0100	[thread overview]
Message-ID: <CAG5iGsAFGGX+xXqEUr50G-2oHZj9zg5xk+b1PYFuDKHxKH3UkQ@mail.gmail.com> (raw)
In-Reply-To: <Yf450DSUa2WAqScs@karl-ThinkPad-P50>


[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]

On Sat, Feb 5, 2022 at 9:48 AM Karl Pettersson <karl.pettersson@klpn.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
  <dc:description>FOO</dc:description>
      <dc:title>
        <rdf:Alt>
          <rdf:li xml:lang="x-default">TITLE</rdf:li>
        </rdf:Alt>
      </dc: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
  <dc:description>
        <rdf:Alt>
          <rdf:li xml:lang="x-default"/>
        </rdf:Alt>
      </dc:description>
      <dc:title>
        <rdf:Alt>
          <rdf:li xml:lang="x-default">TITLE</rdf:li>
        </rdf:Alt>
      </dc:title>

At least, this is what I understand.

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2433 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2022-02-05  8:59 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
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 [this message]
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=CAG5iGsAFGGX+xXqEUr50G-2oHZj9zg5xk+b1PYFuDKHxKH3UkQ@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=karl.pettersson@klpn.se \
    --cc=luigi.scarso@gmail.com \
    /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).