Open zakkinsey opened 5 years ago
Peter Spraul <p.spraul@axes4.com>
assigned issue to self
Comment created by Peter Spraul <p.spraul@axes4.com>
:
Attached PDF changed: is now an atomic example
@MarkusErle changed assignee from Peter Spraul <p.spraul@axes4.com>
to @pkopicar
Comment created by @MarkusErle:
Accepted
Has to be cleaned up
Comment created by @pkopicar:
Cleaned up
@pkopicar changed assignee from self to @PaulRayius
@calanca2 changed assignee from @PaulRayius to @BPeboeck
Comment created by @BPeboeck:
We have another example with more than one document Tag (#53). So I think we can delete Test #2.
@willkil added a link to #198: This issue relates to #198
@willkil added a link to #53: This issue relates to #53
Comment created by @willkil:
I believe the statement, "A Document structure element is required at the root of a PDF's tags tree.", in the current description is incorrect for UA-1. 32k-1 says, "If the PDF file contains a complete document, the structure type Document should be used for this top- level element in the logical structure hierarchy. If the file contains a well-formed document fragment, one of the structure types Part, Art, Sect, or Div may be used instead." I can't find anything in the UA-1, Matterhorn 1.1, or the 2019 syntax guide further restrict the top-level tag.
@zakkinsey unassigned issue from @BPeboeck as part of jira->github migration
Jira issue originally created by user Peter Spraul p.spraul@axes4.com:
The objective of this technique is to show that, no matter how simple a document's content is, the Document tag is used as the root level [structure element](https://www.pdfa.org/glossary-of-accessibility-terminology-in-pdf/#structure element). All other structure elements are children of (nested inside) the Document tag.
A Document [structure element](https://www.pdfa.org/glossary-of-accessibility-terminology-in-pdf/#structure element) is required at the root of a PDF's tag tree.