[NTG-context] Validation of pdf/A-2a

[NTG-context] Validation of pdf/A-2a

[Thomas Meyer]

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

Hello,

I would like to use pdf/A-2a for my documents and was wondering whether 
the documents will stand up to validation.
I used veraPDF for the validation check.

Unfortunately the a-variants (pdf/A1-a and pdf/A-2a) fail.
Here the Validation Information:


    Validation information

*Rule* 	*Status*
Specification: ISO 19005-2:2011, Clause: 6.7.3.3, Test number: 1 
<https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-6733-1> 
	
The logical structure of the conforming file shall be described by a 
structure hierarchy rooted in the StructTreeRoot entry of the document's 
Catalog dictionary, as described in ISO 32000-1:2008, 14.7 	**Failed**
1 occurrences 	Hide
PDDocument 	
StructTreeRoot_size == 1 	
root/document[0]
StructTreeRoot entry is not present in the document catalog

	
Specification: ISO 19005-2:2011, Clause: 6.7.2.2, Test number: 1 
<https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-6722-1> 
	
The document catalog dictionary shall include a MarkInfo dictionary 
containing an entry, Marked, whose value shall be true 	**Failed**
1 occurrences 	Hide
CosDocument 	
Marked == true 	
root
MarkInfo dictionary is not present in the document catalog, or Marked 
entry is set to false or is not present in the MarkInfo dictionary 
(MarkInfo = null, Marked = null)

	


See the (shortened) minimal example taken from the wiki below.

Does anyone have any experience or advice on how to make pdf/A-2a valid?

Greetings Thomas

\setupinteraction
   [title=TITLE,
    subtitle=SUBTITLE,
    author=AUTHOR,
    keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]

%% For PDF/A
\setupbackend[
format={pdf/a-2a},            %%%%validation fails
%format={pdf/a-2b},            %%%%validation passed
%format={pdf/a-2u},            %%%%validation passed
%format={pdf/a-1b:2005},        %%%%validation passed
%format={pdf/a-1a:2005),        %%%%validation fails
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\space (ECI)]


\starttext

\chapter[chap:testing]{Testing}

\input knuth

\input tufte

\stoptext

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

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Jacob Kauffmann via ntg-context]

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

Hi Thomas,

> Am 10.09.2024 um 19:21 schrieb Thomas Meyer <thomasgmeyer@t-online.de>:
> Does anyone have any experience or advice on how to make pdf/A-2a valid?

I don’t know about the ConTeXt way, but I have done it in the past with Adobe Acrobat Preflight and pdfaPilot (https://www.callassoftware.com/en/products/pdfapilot), both granted through my institution.

In complex documents, there are often things that ConTeXt cannot solve for you, such as missing color palettes in external figures etc.

Best,
Jacob


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

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Thomas Meyer]

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

Thank you, Jakob, for your answer,

I didn't think that my example was too complex.
pdf/A-2a works with ConTeXt, it is recognized as pdf/A by FoxitReader. 
However, I would like the result to be valid, as with pdf/A-2u.

Does anyone else have any tips or ideas? Is it not that important?

Greetings
Thomas


Am 12.09.24 um 15:52 schrieb Jacob Kauffmann via ntg-context:
> I don’t know about the ConTeXt way, but I have done it in the past 
> with Adobe Acrobat Preflight and pdfaPilot 
> (https://www.callassoftware.com/en/products/pdfapilot), both granted 
> through my institution.
>
> In complex documents, there are often things that ConTeXt cannot solve 
> for you, such as missing color palettes in external figures etc.

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

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Hans Hagen]

On 9/12/2024 5:50 PM, Thomas Meyer wrote:
> Thank you, Jakob, for your answer,
> 
> I didn't think that my example was too complex.
> pdf/A-2a works with ConTeXt, it is recognized as pdf/A by FoxitReader. 
> However, I would like the result to be valid, as with pdf/A-2u.
> 
> Does anyone else have any tips or ideas? Is it not that important?

i have no time for validation / tagging now but you can try

% \setupbackend[format=pdf/ua-2]
% \setuptagging[state=start]

we will pick up on tagging etc in a couplke of months ... the pdf 
standard is not as stable as one thinks nor are these validators so it's 
a waste of time to continously look at it (and no fun either) so that 
goes in batches

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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Thomas Meyer]

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

Hello Hans,

thank you for your answer for now.
\setupbackend[format=pdf/ua-2] should work but validation test via 
verapdf failed.
I hope for the future.

Greetings
Thomas



Am 12.09.24 um 18:05 schrieb Hans Hagen:
> On 9/12/2024 5:50 PM, Thomas Meyer wrote:
>> Thank you, Jakob, for your answer,
>>
>> I didn't think that my example was too complex.
>> pdf/A-2a works with ConTeXt, it is recognized as pdf/A by 
>> FoxitReader. However, I would like the result to be valid, as with 
>> pdf/A-2u.
>>
>> Does anyone else have any tips or ideas? Is it not that important?
>
> i have no time for validation / tagging now but you can try
>
> % \setupbackend[format=pdf/ua-2]
> % \setuptagging[state=start]
>
> we will pick up on tagging etc in a couplke of months ... the pdf 
> standard is not as stable as one thinks nor are these validators so 
> it's a waste of time to continously look at it (and no fun either) so 
> that goes in batches
>
> 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 / 
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net 
> (mirror)
> archive  : https://github.com/contextgarden/context
> wiki     : https://wiki.contextgarden.net
> ___________________________________________________________________________________ 
>

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

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Hans Hagen]

On 9/12/2024 7:01 PM, Thomas Meyer wrote:
> Hello Hans,
> 
> thank you for your answer for now.
> \setupbackend[format=pdf/ua-2] should work but validation test via 
> verapdf failed.
> I hope for the future.

Because we don't want a bloated pdf by default, if you want tagging then 
you also need to set:

   \setuptagging[state=start]

and you can try with

   \setupbackend[format={pdf/ua-2}]

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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Ulrike Fischer]

Am Thu, 12 Sep 2024 18:05:05 +0200 schrieb Hans Hagen:

>> I didn't think that my example was too complex.
>> pdf/A-2a works with ConTeXt, it is recognized as pdf/A by FoxitReader. 
>> However, I would like the result to be valid, as with pdf/A-2u.
>> 
>> Does anyone else have any tips or ideas? Is it not that important?
> 
> i have no time for validation / tagging now but you can try
> 
> % \setupbackend[format=pdf/ua-2]
> % \setuptagging[state=start]

pdf/A-2a is not pdf/ua-2. pdf/A-2a is for pdf 1.7 or less, so you
would need pdf/ua-1 as accompanying accessibility standard and not
ua-2 which is for pdf 2.0.

But if context still maps everything to NonStruct it can't claim
that the document is pdf/ua-1. The UA-standards clearly require that
structures elements should be semantically appropriate. 

I don't own the pdf/A-2 standard so I don't know how it exactly
defines the accessibility for the "a" in 2a, so it could be enough
to simply enable tagging. 

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Thomas Meyer]

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

Oh, I'm afraid that my “I hope for the future.” has now led to a 
misunderstanding.

I would like to archive my documents as pdf/A-2a. As a reference to the 
German Bundesarchiv, which recommends pdf/A-2a in the first instance - 
and pdf/A-2u in the second.

I simply noticed that, as described in my initial email, the pdf/A-1a 
and pdf/A-2a variants do not pass the validation test with verapdf.

Since there seems to be no way around this, I will probably have to fall 
back on the second recommendation.

Greetings


Am 12.09.24 um 21:00 schrieb Ulrike Fischer:
> Am Thu, 12 Sep 2024 18:05:05 +0200 schrieb Hans Hagen:
>
>>> I didn't think that my example was too complex.
>>> pdf/A-2a works with ConTeXt, it is recognized as pdf/A by FoxitReader.
>>> However, I would like the result to be valid, as with pdf/A-2u.
>>>
>>> Does anyone else have any tips or ideas? Is it not that important?
>> i have no time for validation / tagging now but you can try
>>
>> % \setupbackend[format=pdf/ua-2]
>> % \setuptagging[state=start]
> pdf/A-2a is not pdf/ua-2. pdf/A-2a is for pdf 1.7 or less, so you
> would need pdf/ua-1 as accompanying accessibility standard and not
> ua-2 which is for pdf 2.0.
>
> But if context still maps everything to NonStruct it can't claim
> that the document is pdf/ua-1. The UA-standards clearly require that
> structures elements should be semantically appropriate.
>
> I don't own the pdf/A-2 standard so I don't know how it exactly
> defines the accessibility for the "a" in 2a, so it could be enough
> to simply enable tagging.
>

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

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Hans Hagen via ntg-context]

On 9/13/2024 9:51 AM, Thomas Meyer wrote:
> Oh, I'm afraid that my “I hope for the future.” has now led to a 
> misunderstanding.
> 
> I would like to archive my documents as pdf/A-2a. As a reference to the 
> German Bundesarchiv, which recommends pdf/A-2a in the first instance - 
> and pdf/A-2u in the second.
> 
> I simply noticed that, as described in my initial email, the pdf/A-1a 
> and pdf/A-2a variants do not pass the validation test with verapdf.
> 
> Since there seems to be no way around this, I will probably have to fall 
> back on the second recommendation.

You cna try this:

\setupinteraction
   [title=TITLE,
    subtitle=SUBTITLE,
    author=AUTHOR,
    keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]

\setupbackend
   [format={pdf/a-2a},
    profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]

\setuptagging
   [state=start]

\enabledirectives
   [backend.usetags=mkiv]

\starttext

     \chapter[chap:testing]{Testing}

     \input knuth

     \input tufte

\stoptext

This validates in the verapdf that i have installed (1.25.271).

So, you choose some standard (which we try to accomodate as good as 
possible but who knows ... this one is a bloated one due to the icc 
profiles). As you want tags we enable that (no need for it as long as 
one is not finished with the document unless one wants to trace). We 
also load the the old school mkiv mapping.

You can define your own mappings if needed. After looking into the 
latest greatest volatile specifications Mikael and I decided that we 
don't want to be waste too much time on it (at least not now as we hav 
emore interestign thinsg to work on) and settled for what validates and 
let users themselves decide. We mostly aim(ed) at making the university 
enforced tools happy.

Structure in pdf is (to put it mildly) a mess, insufficient and never 
will be (conceptually) okay, which is probably why it keeps being 
adapted to what some applications can support or not. We don't want to 
cripple what structure in ConTeXt we have. For the long time 
accessibility tagging (there are other kinds of tagging being in use) 
has been around for a quite vwhile now it has been the domain of acrobat 
professional toolkit so in a broader context it is kind of useless anyeay.

(One can wonder what organizations demanding it really have in mind, 
given that older stuff doesn't validate and probably no one ever checked 
how useful it is. But that's often the case with standrads like this: 
some checkbox ticks so we're okay.)

So, the best we can do is to provide some flexibility, as usual in tex 
tools,

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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Thomas Meyer]

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

Hello Hans,

thanks for the detailed answer.  Now it works!

I didn't realise until now that pdf is also messy. In my job I have 
enough to do with the fact that some products never work as they should 
("Mr Gates has won and now we have to use his products.’ - said our 
former head of IT). I have nothing to do with IT, I am a scientist.

I am grateful for LaTeX, and of course I thank you, Hans, for ConTeXt!

I can only emphasise that I am just a user who keeps turning to lists 
for support.

Thank you for your time and patience.

Have a nice weekend
Thomas


Am 13.09.24 um 11:59 schrieb Hans Hagen via ntg-context:
> On 9/13/2024 9:51 AM, Thomas Meyer wrote:
>> Oh, I'm afraid that my “I hope for the future.” has now led to a 
>> misunderstanding.
>>
>> I would like to archive my documents as pdf/A-2a. As a reference to 
>> the German Bundesarchiv, which recommends pdf/A-2a in the first 
>> instance - and pdf/A-2u in the second.
>>
>> I simply noticed that, as described in my initial email, the pdf/A-1a 
>> and pdf/A-2a variants do not pass the validation test with verapdf.
>>
>> Since there seems to be no way around this, I will probably have to 
>> fall back on the second recommendation.
>
> You cna try this:
>
> \setupinteraction
>   [title=TITLE,
>    subtitle=SUBTITLE,
>    author=AUTHOR,
>    keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
>
> \setupbackend
>   [format={pdf/a-2a},
>    profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
>
> \setuptagging
>   [state=start]
>
> \enabledirectives
>   [backend.usetags=mkiv]
>
> \starttext
>
>     \chapter[chap:testing]{Testing}
>
>     \input knuth
>
>     \input tufte
>
> \stoptext
>
> This validates in the verapdf that i have installed (1.25.271).
>
> So, you choose some standard (which we try to accomodate as good as 
> possible but who knows ... this one is a bloated one due to the icc 
> profiles). As you want tags we enable that (no need for it as long as 
> one is not finished with the document unless one wants to trace). We 
> also load the the old school mkiv mapping.
>
> You can define your own mappings if needed. After looking into the 
> latest greatest volatile specifications Mikael and I decided that we 
> don't want to be waste too much time on it (at least not now as we hav 
> emore interestign thinsg to work on) and settled for what validates 
> and let users themselves decide. We mostly aim(ed) at making the 
> university enforced tools happy.
>
> Structure in pdf is (to put it mildly) a mess, insufficient and never 
> will be (conceptually) okay, which is probably why it keeps being 
> adapted to what some applications can support or not. We don't want to 
> cripple what structure in ConTeXt we have. For the long time 
> accessibility tagging (there are other kinds of tagging being in use) 
> has been around for a quite vwhile now it has been the domain of 
> acrobat professional toolkit so in a broader context it is kind of 
> useless anyeay.
>
> (One can wonder what organizations demanding it really have in mind, 
> given that older stuff doesn't validate and probably no one ever 
> checked how useful it is. But that's often the case with standrads 
> like this: some checkbox ticks so we're okay.)
>
> So, the best we can do is to provide some flexibility, as usual in tex 
> tools,
>
> 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 / 
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net 
> (mirror)
> archive  : https://github.com/contextgarden/context
> wiki     : https://wiki.contextgarden.net
> ___________________________________________________________________________________ 
>

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

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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: Validation of pdf/A-2a

[Hans Hagen]

On 9/14/2024 10:14 AM, Thomas Meyer wrote:

> I can only emphasise that I am just a user who keeps turning to lists 
> for support.

Which is what the list is for, so okay,

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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________