Difference between revisions of "PDF"
Jon Phillips (talk | contribs) |
(+ description of current state of PDF tagging) |
||
Line 1: | Line 1: | ||
+ | '''Current status''' | ||
+ | |||
+ | You can already [http://creativecommons.org/technology/xmp embed a Creative Commons license in a PDF document] using [http://partners.adobe.com/public/developer/xmp/topic.html Adobe's XMP] through, for example, Adobe Photoshop CS. | ||
+ | |||
+ | However, there is still no free means of embedding license data in PDFs. | ||
+ | |||
+ | The most recent PDF standard (as of May 7, 2006), [http://partners.adobe.com/public/developer/en/pdf/PDFReference16.pdf version 1.6], provides two mechanisms for the storing of metadata, such as license information, in the file. In section 10.2 of the standard, the two methods described are the document information dictionary and the metadata stream. | ||
+ | |||
+ | '''Document information dictionary''' | ||
+ | |||
+ | An example of the first, the document information dictionary, is given in section 10.2.1: | ||
+ | <pre> | ||
+ | 1 0 obj | ||
+ | << /Title (PostScript Language Reference, Third Edition) | ||
+ | /Author (Adobe Systems Incorporated) | ||
+ | /Creator (Adobe® FrameMaker® 5.5.3 for Power Macintosh®) | ||
+ | /Producer (Acrobat® DistillerTM 3.01 for Power Macintosh) | ||
+ | /CreationDate (D:19970915110347-08'00') | ||
+ | /ModDate (D:19990209153925-08'00') | ||
+ | >> | ||
+ | endobj | ||
+ | </pre> | ||
+ | |||
+ | Table 10.2 in section 10.2.1 lists 9 standard keys in the dictionary. "License" is not among them, but the specification makes reference to the creation of new keys in two sentences in section 10.2.1: "New keys should be chosen with care so that they make sense to users. The value associated with any key not specifically mentioned in Table 10.2 must be a text string." | ||
+ | |||
+ | This suggests that writing a tool that added a license key to the dictionary might be a reasonable way to proceed. | ||
+ | |||
+ | '''Metadata stream''' | ||
+ | |||
+ | This is the second method by which metadata can be embedded in a PDF. XMP is an example of the metadata stream, in which a chunk of XML is embedded in the PDF file for parsing by agents that don't necessarily understand how to read a PDF, but can read XML. | ||
+ | |||
[[Category:Developer]] | [[Category:Developer]] | ||
[[Category:Developer Challenges]] | [[Category:Developer Challenges]] | ||
[[Category:Technology]] | [[Category:Technology]] | ||
[[Category:filetype]] | [[Category:filetype]] | ||
− |
Revision as of 18:58, 7 May 2006
Current status
You can already embed a Creative Commons license in a PDF document using Adobe's XMP through, for example, Adobe Photoshop CS.
However, there is still no free means of embedding license data in PDFs.
The most recent PDF standard (as of May 7, 2006), version 1.6, provides two mechanisms for the storing of metadata, such as license information, in the file. In section 10.2 of the standard, the two methods described are the document information dictionary and the metadata stream.
Document information dictionary
An example of the first, the document information dictionary, is given in section 10.2.1:
1 0 obj << /Title (PostScript Language Reference, Third Edition) /Author (Adobe Systems Incorporated) /Creator (Adobe® FrameMaker® 5.5.3 for Power Macintosh®) /Producer (Acrobat® DistillerTM 3.01 for Power Macintosh) /CreationDate (D:19970915110347-08'00') /ModDate (D:19990209153925-08'00') >> endobj
Table 10.2 in section 10.2.1 lists 9 standard keys in the dictionary. "License" is not among them, but the specification makes reference to the creation of new keys in two sentences in section 10.2.1: "New keys should be chosen with care so that they make sense to users. The value associated with any key not specifically mentioned in Table 10.2 must be a text string."
This suggests that writing a tool that added a license key to the dictionary might be a reasonable way to proceed.
Metadata stream
This is the second method by which metadata can be embedded in a PDF. XMP is an example of the metadata stream, in which a chunk of XML is embedded in the PDF file for parsing by agents that don't necessarily understand how to read a PDF, but can read XML.