Difference between revisions of "XMP"

From Creative Commons
Jump to: navigation, search
m (Reverted edits by NathanYergler (Talk); changed back to last version by Paulproteus)
Line 1: Line 1:
 
[[Category:Developer]]
 
[[Category:Developer]]
 
[[Category:Technology]]
 
[[Category:Technology]]
−
[[Category:Metadata]]
+
[[Category:metadata]]
 
[[Category:XMP]]
 
[[Category:XMP]]
−
{{Filetype|
+
= Creative Commons Metadata and XMP =
−
  license_url=True|
 
−
  web_statement=True|
 
−
  more_permissions=True
 
−
}}
 
  
−
[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. 
+
<div style="float: right">
 +
[[Image:Xmp_tagline.png]]
  
−
Creative Commons is 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 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.
+
([http://www.adobe.com/products/xmp Adobe's website])
 +
</div>
 +
 
 +
 
 +
[[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 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."
 +
 
 +
== Implementations ==
  
 
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)]].
 
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)]].
  
−
== Specifying License Information ==
+
== Adobe applications ==
 +
Follow these steps:
 +
 
 +
# Make sure you have installed our [[Creative Commons Panel]]
 +
# Go to http://creativecommons.org/license and select a license
 +
# Save the file marked "to mark a PDF or other XMP-supported file, save this template" to your Desktop
 +
# In the Adobe application, open the file you wish to license.  Then:
 +
## Choose File -> File Info
 +
## Select "Advanced" on the left side
 +
## Click the "Replace" button, and select the XMP file you downloaded from http://creativecommons.org/license
 +
# Now, if you select the "Creative Commons" section on the left of the File Info box, you should see the license you have chosen.
 +
 
 +
=== PDF ===
 +
 
 +
* LaTeX users may use the [http://www.creativecommons.org/weblog/entry/4270 pdflatex macro].
 +
* [http://enrico.masala.googlepages.com/plm_index.html PdfLicenseEditor] is a standalone GUI/command line tool for embedding XMP in PDFs.
 +
** PdfLicenseEditor 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.
 +
** PdfLicenseEditor only supports the 2.5 licenses, not 3.0
 +
* Windows users may use [http://creativecommons.org/weblog/entry/7567 Cogniview]
 +
 
 +
=== JPEG ===
 +
 
 +
* 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]].
 +
 
 +
=== Video (various) ===
 +
 
 +
* None yet
 +
 
 +
=== Other Open Source Implementations ===
 +
 
 +
* [http://grigio.org/xmp_manager XMP Manager] A Ruby action for Nautilus which exposes and allows editing of XMP metadata.
 +
* [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.
 +
* [http://www.figuiere.net/hub/blog/?Exempi Exempi] - Hubert Figuiere's BSD-licensy library to handle XMP, based on Adobe's SDK.
 +
 
 +
== Note on Visible Copyright Notice in PDFs ==
 +
 
 +
Even when embedded with XMP metadata a licensed PDF document should include a visible copyright notice as described in [[HOWTO Tag HTML pages]].
 +
'''Sergio Bontempelli, sicuri di sapere, 2007'''
 +
 
 +
== Note on embedded metadata ==
 +
 
 +
This specification conforms with the [[Nonweb Tagging]] recommendation.
 +
 
 +
== Specification ==
  
 
XMP [http://partners.adobe.com/asn/tech/xmp/download.jsp defines] a rights management schema (see section 4.2.5). Creative Commons sets the following properties (example values):
 
XMP [http://partners.adobe.com/asn/tech/xmp/download.jsp defines] a rights management schema (see section 4.2.5). Creative Commons sets the following properties (example values):
  
−
* '''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: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.)
−
* '''xapRights:Marked''' &mdash; ''False'' if Public Domain, ''True'' otherwise.
 
−
* '''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]].)
 
  
−
We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc.  
+
'''xapRights:Marked''' &mdash; ''False'' if Public Domain, ''True'' otherwise.
−
It currently has the following properties:
 
  
−
* '''license''' &mdash; The license URL; for example, ''http://creativecommons.org/licenses/by-sa/2.0/''.
+
'''xapRights:WebStatement''' &mdash; ''http://example.com/pdf-metadata.html'' (Replace with URL containing metadata about the XMP-embedded file.)
−
* '''morePermissions''' &mdash; A URL where additional permissions (commercial licensing, etc) are available.
 
−
* '''attributionURL''' &mdash; The URL to use when attributing this work.
 
−
* '''attributionName''' &mdash; The creator's preferred name to use when attributing this work.
 
  
−
== Verification Links and XMP ==
+
We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc.  
−
 
 
−
A publisher can add 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.
 
  
−
For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].
+
It currently has the following property:
  
−
<code><pre>
+
'''license''' &mdash; ''http://creativecommons.org/licenses/by-sa/2.0/'' (Replace with relevant license URL.)
−
  <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>
 
  
−
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.
+
Set '''license''' to maintain a direct reference to the license URL.
  
−
== Additional Information ==
+
== Developer Challenges ==
  
−
* [[XMP Implementations]]
+
We have setup some [[XMP developer challenges]] to encourage the use of XMP and also to do some research as to what is already supported and what we support.
−
* [[:Category:XMP|All XMP-related articles]]
 
  
−
<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>
+
== XMP Logo ==
 +
<small>The XMP logo is either a registered trademark or tradmark of the Adobe Systems Incorporated in the United States and/or other countries.</small>

Revision as of 21:28, 16 October 2007

Creative Commons Metadata and XMP

Xmp tagline.png

(Adobe's website)


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 considering 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 apparently coming to the same conclusion, e.g., 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."

Implementations

The Creative Commons licensing process offers a XMP template which may be used to mark files within XMP-supporting Adobe applications (step-by-step how-to document).

Adobe applications

Follow these steps:

  1. Make sure you have installed our Creative Commons Panel
  2. Go to http://creativecommons.org/license and select a license
  3. Save the file marked "to mark a PDF or other XMP-supported file, save this template" to your Desktop
  4. In the Adobe application, open the file you wish to license. Then:
    1. Choose File -> File Info
    2. Select "Advanced" on the left side
    3. Click the "Replace" button, and select the XMP file you downloaded from http://creativecommons.org/license
  5. Now, if you select the "Creative Commons" section on the left of the File Info box, you should see the license you have chosen.

PDF

  • LaTeX users may use the pdflatex macro.
  • PdfLicenseEditor is a standalone GUI/command line tool for embedding XMP in PDFs.
    • PdfLicenseEditor uses the iText java library, which may be easily incorporated into any Java tool that needs to do XMP embedding.
    • PdfLicenseEditor only supports the 2.5 licenses, not 3.0
  • Windows users may use Cogniview

JPEG

Video (various)

  • None yet

Other Open Source Implementations

  • XMP Manager A Ruby action for Nautilus which exposes and allows editing of XMP metadata.
  • 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.
  • Exempi - Hubert Figuiere's BSD-licensy library to handle XMP, based on Adobe's SDK.

Note on Visible Copyright Notice in PDFs

Even when embedded with XMP metadata a licensed PDF document should include a visible copyright notice as described in HOWTO Tag HTML pages. Sergio Bontempelli, sicuri di sapere, 2007

Note on embedded metadata

This specification conforms with the Nonweb Tagging recommendation.

Specification

XMP defines a rights management schema (see section 4.2.5). Creative Commons sets the following properties (example values):

xapRights:Copyright — 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.)

xapRights:Marked — False if Public Domain, True otherwise.

xapRights:WebStatement — http://example.com/pdf-metadata.html (Replace with URL containing metadata about the XMP-embedded file.)

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

It currently has the following property:

license — http://creativecommons.org/licenses/by-sa/2.0/ (Replace with relevant license URL.)

Set license to maintain a direct reference to the license URL.

Developer Challenges

We have setup some XMP developer challenges to encourage the use of XMP and also to do some research as to what is already supported and what we support.

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

Retrieved from "https://wiki.creativecommons.org/index.php?title=XMP&oldid=9131"