Re: [NTG-context] XMP metadata schema yields invalid PDF/A

2022-02-04 Thread luigi scarso via ntg-context
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
___
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
___


Re: [NTG-context] XMP metadata schema yields invalid PDF/A

2022-02-04 Thread Karl Pettersson via ntg-context
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  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
___


Re: [NTG-context] XMP metadata schema yields invalid PDF/A

2022-02-04 Thread luigi scarso via ntg-context
On Fri, Feb 4, 2022 at 10:26 PM Hans Hagen via ntg-context <
ntg-context@ntg.nl> 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
>
>

and also in XMPSpecificationPart1.pdf

https://github.com/adobe/XMP-Toolkit-SDK/tree/main/docs

 dc:description

Language
Alternative

DCMI definition: An account of the resource.
XMP addition: XMP usage is a list of textual descriptions of the content of
the
resource, given in various languages.


--
luigi
___
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
___


Re: [NTG-context] XMP metadata schema yields invalid PDF/A

2022-02-04 Thread Hans Hagen via ntg-context

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)

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
___


[NTG-context] XMP metadata schema yields invalid PDF/A

2022-02-04 Thread Karl Pettersson via ntg-context
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

Regards

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