[dev-context] attachments in PDF/A-3

Pablo Rodriguez oinos at gmx.es
Sun Mar 17 16:41:31 CET 2019


Dear list,

my sample to add attachments to a PDF/A-3 valid document is the following:

    \setuptagging[state=start]

    \setupbodyfont[30pt]

    \setupbackend
      [format=PDF/A-3a,
       intent=sRGB IEC61966-2.1,
       profile={sRGB.icc,default_gray.icc},
       level=0]

    \setupcolors[pagecolormodel=auto]

    \setupinteraction[state=start]
    \starttext
    \startTEXpage[offset=1em]
    an attachment\attachment[file=xml-mkiv.pdf]
    \stopTEXpage
    \stoptext

There are five reported errors when tested with the latest development
version of veraPDF (http://downloads.verapdf.org/dev/verapdf-installer.zip):

- Annotation should have /F value
(https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-632-1);
unless their Rect key value 1 equal to value 3 and value 2 equal to
value 4, or the annotation subtype is /Popup or /Link.

- Although not reported, the /F value should conform these considerations:

    If present, the F key's Print flag bit shall be set to 1 and its
    Hidden, Invisible, ToggleNoView, and NoView flag bits shall be set
    to 0.
https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-632-2

- Annotations need an appearance dictionary
(https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-633-1);
unless the same exception for the /F value apply.

- The /EmbeddedFile dictionary should specify the MIME type in its
/Subtype entry
(https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-1).

- The /AFRelationship key is missing from the /Filespec dictionary
(https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-3).
Possible values are: Source, Data, Alternative, Supplement,
EncryptedPayload, FormData, Schema or Unspecified (from
https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf).

- The /Filespec lacks association with the PDF document or any of its
parts, such as pages
(https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-4).

    From
    https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf,
    it seems that either the /Catalog or a /Page dictionary (there are
    other ones, but I would limit attachments in ConTeXt to those two
    [if not to the /Catalog itself only]) should contain an /AF entry
    with the reference to the /Filespec object(s). I assume that
    the value type for the /AF entry is an array of one or multiple
    object references.

These are all the issues veraPDF finds when validating the PDF document
generated from the source above.

I hope it helps. Many thanks for your help,

Pablo
-- 
http://www.ousia.tk


More information about the dev-context mailing list