Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

7.11.4.1 (Embedded file streams): Rewording how embedded file streams can be included in a PDF file #481

Open
stechio opened this issue Oct 13, 2024 · 2 comments
Assignees
Labels
bug Something isn't correct proposed solution Proposed solution is ready for review

Comments

@stechio
Copy link

stechio commented Oct 13, 2024

In subclause 7.11.4.1 (Embedded file streams - General), the bulleted list beginning with

An embedded file stream shall be included in a PDF file in one of the following ways:
[...]

is unnecessarily convoluted, redundant and confusing.

PROPOSAL

I propose to replace the old list with this one:

To be included in a PDF file, an embedded file stream shall be referenced by a file specification 
through its EF entry; such file specification then shall be used in one of the following ways:
  • at page level: the file specification may be associated with a location on a page in the
    document through a file attachment annotation (see 12.5.6.15, "File attachment annotations").
  • at document level: the file specification may be associated with the document as a whole
    through the EmbeddedFiles entry in the PDF file’s name dictionary (see 7.7.4, "Name dictionary"),
    mapping a name string to the file specification.
@stechio stechio added the bug Something isn't correct label Oct 13, 2024
@petervwyatt
Copy link
Member

It's much worse than that - this text hasn't been maintained for other PDF features such as embedded files at the object level (Associated Files) and various specific features such as 3D or RichMedia assets, Movie and Sound annot resources, SlideShow resources, Related Files array, the ability of any stream to use FFilter, Output Intent URLs, etc.

If the intention is to maintain a list of all places in PDF where embedded file streams might be used in a PDF then I don't think it should use "shall"-style normative language since the relevant requirements will be in other subclasses and they may (some definitely do!) have particular nuances. But this still creates an informative maintenance issue so I don't like that.

I think all this text can be deleted as it adds nothing useful besides a few informative "you may also want to see ..." clause references.

@pdf-association pdf-association deleted a comment Oct 23, 2024
@petervwyatt petervwyatt self-assigned this Oct 29, 2024
@petervwyatt petervwyatt added the proposed solution Proposed solution is ready for review label Oct 29, 2024
@petervwyatt
Copy link
Member

Proposed solution 1: delete text
Proposed solution 2: reword to be informative and clearly indicating that there are also other ways files can end up embedded inside PDF

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't correct proposed solution Proposed solution is ready for review
Projects
None yet
Development

No branches or pull requests

2 participants