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: Sat, 5 Feb 2022 13:28:30 +0100 [thread overview]
Message-ID: <Yf5tbpi0gpNGmjex@karl-ThinkPad-P50> (raw)
In-Reply-To: <Yf5qGgXL5YKaI7qK@karl-ThinkPad-P50>
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
>
> From what I understand, ConTeXt applies a custom Dublin Core schema
> containing just a redefinition of dc:description, which is not coherent
> with how dc:description is written by the application.
>
> This patch to lpdf-pda.xml removes the validation error.
>
Sorry, diff the other way round according to diff original new.
--
Karl Pettersson
Uppsala, Sweden
https://static-dust.klpn.se/
[-- Attachment #2: lpdf-pda.diff --]
[-- Type: text/plain, Size: 1188 bytes --]
80,97d79
< <pdfaSchema:namespaceURI>http://purl.org/dc/elements/1.1/</pdfaSchema:namespaceURI>
< <pdfaSchema:prefix>pdf</pdfaSchema:prefix>
< <pdfaSchema:schema>Dubline Core Schema</pdfaSchema:schema>
< <pdfaSchema:property>
< <rdf:Seq>
< <rdf:li rdf:parseType="Resource">
< <pdfaProperty:category>internal</pdfaProperty:category>
< <pdfaProperty:description>Subject in Document Properties</pdfaProperty:description>
< <pdfaProperty:name>description</pdfaProperty:name>
< <pdfaProperty:valueType>Text</pdfaProperty:valueType>
< </rdf:li>
< </rdf:Seq>
< </pdfaSchema:property>
< <pdfaSchema:valueType>
< <rdf:Seq/>
< </pdfaSchema:valueType>
< </rdf:li>
< <rdf:li rdf:parseType="Resource">
[-- Attachment #3: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-02-05 12:28 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
2022-02-05 12:14 ` Karl Pettersson via ntg-context
2022-02-05 12:28 ` Karl Pettersson via ntg-context [this message]
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=Yf5tbpi0gpNGmjex@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).