Metadata in signature dictionary
"Petras Petkus" <[email protected]> Fri, 12 Aug 2016 14:41:18 +0300
| Newsgroups | gmane.comp.java.lib.itext.general |
|---|---|
| Organization | UAB "Mit-Soft" |
| Message-ID | <[email protected]> |
This is a multipart message in MIME format.
--===============1215332242115692577==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0048_01D1F4A7.964EFDD0"
Content-Language: lt
This is a multipart message in MIME format.
------=_NextPart_000_0048_01D1F4A7.964EFDD0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I have a question to PDF experts regarding placing metadata in signature
dictionary.
Our national PDF-based electronic document specification defines metadata
which may be included into signature dictionary. ISO 32000-1 section "14.3.2
Metadata Streams" states, that "Metadata, both for an entire document and
for components within a document, may be stored in PDF streams called
metadata streams". Therefore as a component, signature dictionary may
contain metadata entry. Section "7.3.8 Stream Objects" states, that "All
streams shall be indirect objects", but this requirement clashes with the
requirement for signature dictionary entries in "12.8 Digital Signatures",
which states: "When a byte range digest is present, all values in the
signature dictionary shall be direct objects."
I looked at the earlier (2014) draft of ISO 32000-2 and those requirements
were not changed, probably this contradiction will remain unchanged in the
final version.
Does that mean that metadata stream may not be included in signature
dictionary?
Thank you in advance for any input.
------=_NextPart_000_0048_01D1F4A7.964EFDD0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 1.0cm 2.0cm 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DLT link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>I have a question to PDF experts regarding placing metadata =
in signature dictionary. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p> </o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Our national PDF-based electronic =
document specification defines metadata which may be included into =
signature dictionary. ISO 32000-1 section “14.3.2 Metadata =
Streams” states, that “Metadata, both for an entire document =
and for components within a document, may be stored in PDF streams =
called metadata streams”. Therefore as a component, signature =
dictionary may contain metadata entry. Section “7.3.8 Stream =
Objects” states, that “All streams shall be indirect =
objects”, but this requirement clashes with the requirement for =
signature dictionary entries in “12.8 Digital Signatures”, =
which states: "When a byte range digest is present, all values in =
the signature dictionary shall be direct =
objects."<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p> </o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I looked at the earlier (2014) draft of ISO 32000-2 and =
those requirements were not changed, probably this contradiction will =
remain unchanged in the final version.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p> </o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Does that mean that metadata stream =
may not be included in signature dictionary?</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-fareast-language:LT'><o:p></o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US><o:p> </o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thank you in advance for any =
input.<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0048_01D1F4A7.964EFDD0--
--===============1215332242115692577==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
--===============1215332242115692577==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
--===============1215332242115692577==--