[http://www.adobe.com/products/xmp XMP] ([http://en.wikipedia.org/wiki/Extensible_Metadata_Platform Extensible Metadata Platform]) facilitates embedding metadata in files using a subset of RDF. Most notably, XMP supports embedding metadata in PDF and many image formats, though it is designed to support nearly any file type.

−

</div>

−

[http://www.adobe.com/products/xmp XMP] (Extensible Metadata Platform) facilitates embedding metadata in files using a subset of RDF. Most notably XMP supports embedding metadata in PDF and many image formats, though it is designed to support nearly any file type.

+

Creative Commons is recommending XMP as the preferred format for embedded metadata, given its [http://web.archive.org/web/20070426051136/http://labs.adobe.com/technologies/xmptoolkit/#FAQ support for numerous file formats] and the balkanized state of embedded metadata standards. Others are coming to a similar conclusion; Microsoft has announced support for [http://blogs.msdn.com/pix/archive/2006/08/23/715340.aspx XMP in Vista applications] and Jon Udell [http://blog.jonudell.net/2007/02/14/truth-files-microformats-and-xmp/ notes] "There’s also good support in .NET Framework 3.0 for reading and writing XMP metadata." Note that even when embedded with XMP metadata, Creative Commons recommends a licensed document include a visible copyright notice; [[Marking|format-specific recommendations]] for visible notices are available.

−

Creative Commons is considering recommending XMP as the preferred format for embedded metadata, given its [http://labs.adobe.com/technologies/xmptoolkit/#FAQ support for numerous file formats] and the balkanized state of embedded metadata standards. Others are apparently coming to the same conclusion, e.g., Microsoft has announced support for [http://blogs.msdn.com/pix/archive/2006/08/23/715340.aspx XMP in Vista applications] and Jon Udell [http://blog.jonudell.net/2007/02/14/truth-files-microformats-and-xmp/ notes] "There’s also good support in .NET Framework 3.0 for reading and writing XMP metadata."

+

The Creative Commons [http://www.creativecommons.org/license/ licensing process] offers a XMP template which may be used to mark files within XMP-supporting [[XMP help for Adobe applications|Adobe applications (step-by-step how-to document)]]. An [[Adobe_Metadata_Panel|XMP FileInfo panel]] is also available.

−

== Implementations ==

+

== Specifying License Information ==

−

The Creative Commons [http://www.creativecommons.org/license/ licensing process] offers a XMP template which may be used to mark files within XMP-supporting [[XMP Help|Adobe applications (step-by-step how-to document)]].

* '''xmpRights:WebStatement''' &mdash; ''http://example.com/pdf-metadata.html'' (Replace with URL containing metadata about the XMP-embedded file; this is referred to as the [[WebStatement|Web Statement]].)

+

* '''xmpRights:UsageTerms''' &mdash; An optional field describing legal terms of use; Creative Commons recommends that when present this take the form ''This work is licensed to the public under the Creative Commons Attribution-ShareAlike license http://creativecommons.org/licenses/by­sa/2.0/ verify at http://example.com/pdf­metadata.html'' (Replace URL following 'verify at' with URL containing metadata about the XMP-­embedded file; this is typically the URL specified by '''xmpRights:WebStatement'''.)<br />'''''Note''': as of 2011-05 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf suggests using '''dc:rights''' and xmpRights:WebStatement; it probably makes sense to populate dc:rights and xmpRights:UsageTerms with identical content.''

−

* LaTeX users may use the [http://www.creativecommons.org/weblog/entry/4270 pdflatex macro].

+

We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc. It currently has the following properties:

−

* [http://enrico.masala.googlepages.com/plm_index.html PdfLicenseManager] is a standalone GUI/command line tool for embedding XMP in PDFs.

−

** PdfLicenseManager uses the [http://www.lowagie.com/iText/ iText] java library, which may be easily incorporated into any Java tool that needs to do XMP embedding.

* '''attributionURL''' &mdash; The URL to use when attributing this work.

+

* '''attributionName''' &mdash; The creator's preferred name to use when attributing this work.

−

* We have a PHP tool/library for embedding XMP in JPEGs, useful in, e.g., web gallery programs. See the xmp/php-jpeg module in the [[Source Repository Information|cctools sourceforge subversion repository]].

+

== Verification Links and XMP ==

−

=== Other Implementations ===

+

A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://watersoftenerreviewspro.com/water-softener-comparison/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.

−

* [http://www.adobe.com/devnet/xmp/ XMP Toolkit 4.1]

−

* [http://www.figuiere.net/hub/blog/?Exempi Exempi] bundles the above two tools into one package, with modifications to make it build on Linux. It therefore allows reading/writing XMP metadata for various file formats, including PDF, MP3, JPEG, and PNG.

−

* [http://owl.phy.queensu.ca/~phil/exiftool/ Exiftool] is a perl-based module for embedding and extracting Exif from multiple filetypes. This allows for using XMP in addition to other formats.

−

* [http://www.w3.org/People/Bos/JPEG-XMP/ JPEG-XMP] are java-based programs for operating on jpegs to extract and embed XMP metadata.

−

* [http://www.ozhiker.com/electronics/pjmt/ The PHP JPEG Metadata Toolkit] is a php-based program for embedding and extracting XMP metadata for JPEGs.

−

* [http://enrico.masala.googlepages.com/plm_index.html PdfLicenseManager] is a Java-based GUI and command line program for embedding XMP with license information into PDFs.

* [http://librdf.org/raptor/ Raptor] - Supposedly this can generate XMP somewhat, and can also parse it, if you grab the rdf/xml out of the <?xmp...> blocks for it. It's GPL / LGPL / Apache2 licensed so compatible with your code.

−

* ''Please add yours here'' :)

−

== Note on Visible Copyright Notice in PDFs ==

+

For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].

−

Even when embedded with XMP metadata a licensed PDF document should include a visible copyright notice as described in [[HOWTO Tag HTML pages]].

+

<code><pre>

+

<p>The document example.pdf is licensed under a

+

<a about="urn:sha1:MSMBC5VEUDLTC26UT5W7GZBAKZHCY2MD" rel="license"

+

href="http://creativecommons.org/license/by/3.0/">

+

Creative Commons Attribution 3.0</a> license.

+

</a>

+

</p>

+

</pre></code>

−

== Note on embedded metadata ==

+

When processing a file containing an embedded web statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.

−

This specification conforms with the [[Nonweb Tagging]] recommendation.

<small>The XMP logo is either a registered trademark or trademark of the Adobe Systems Incorporated in the United States and/or other countries.</small>

−

'''xapRights:Copyright''' &mdash; ''This work is licensed to the public under the Creative Commons Attribution-ShareAlike license http://creativecommons.org/licenses/by-sa/2.0/ verify at http://example.com/pdf-metadata.html'' (Replace URL following 'verify at' with URL containing metadata about the XMP-embedded file; this is typically the same URL specified by '''xapRights:WebStatement'''.)

'''xapRights:WebStatement''' &mdash; ''http://example.com/pdf-metadata.html'' (Replace with URL containing metadata about the XMP-embedded file; this is referred to as the [[WebStatement|Web Statement]].)

+

[[Category:Metadata]]

−

+

[[Category:XMP]]

−

We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc.

XMP (Extensible Metadata Platform) facilitates embedding metadata in files using a subset of RDF. Most notably, XMP supports embedding metadata in PDF and many image formats, though it is designed to support nearly any file type.

Creative Commons is recommending XMP as the preferred format for embedded metadata, given its support for numerous file formats and the balkanized state of embedded metadata standards. Others are coming to a similar conclusion; Microsoft has announced support for XMP in Vista applications and Jon Udell notes "There’s also good support in .NET Framework 3.0 for reading and writing XMP metadata." Note that even when embedded with XMP metadata, Creative Commons recommends a licensed document include a visible copyright notice; format-specific recommendations for visible notices are available.

xmpRights:UsageTerms — An optional field describing legal terms of use; Creative Commons recommends that when present this take the form This work is licensed to the public under the Creative Commons Attribution-ShareAlike license http://creativecommons.org/licenses/by­sa/2.0/ verify at http://example.com/pdf­metadata.html (Replace URL following 'verify at' with URL containing metadata about the XMP-­embedded file; this is typically the URL specified by xmpRights:WebStatement.)Note: as of 2011-05 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf suggests using dc:rights and xmpRights:WebStatement; it probably makes sense to populate dc:rights and xmpRights:UsageTerms with identical content.

attributionName — The creator's preferred name to use when attributing this work.

Verification Links and XMP

A publisher can boost confidence in embedded metadata by providing a verifying web statement. A verifying web statement is a URL which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.

When processing a file containing an embedded web statement, an application can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.