in XMP data are those from the Dublin Core Metadata Initiative, which include things like title, description, creator, and so on. The standard is designed to be extensible, allowing users to add their own custom types of metadata into the XMP data. XMP generally does not allow binary data types to be embedded. This means that any binary data one wants to carry in XMP, such as thumbnail images, must be encoded in some XML-friendly format, such as Base64. XMP metadata can describe a document as a whole (the "main" metadata), but can also describe parts of a document, such as pages or included images. This architecture makes it possible to retain authorship and rights information about, for example, images included in a published document. Similarly, it permits documents created from several smaller documents to retain the original metadata associated with the parts. Example This is an example XML document for serialized XMP metadata in a JPEG photo: <?xpacket begin="?" id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.4-c002 1.000000, 0000/00/00-00:00:00 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:xmp="http://ns.adobe.com/xap/1.0/"> <xmp:CreatorTool>Picasa</xmp:CreatorTool> </rdf:Description> <rdf:Description rdf:about="" xmlns:mwg-rs="http://www.metadataworkinggroup.com/schemas/regions/" xmlns:stDim="http://ns.adobe.com/xap/1.0/sType/Dimensions#" xmlns:stArea="http://ns.adobe.com/xmp/sType/Area#"> <mwg-rs:Regions rdf:parseType="Resource"> <mwg-rs:AppliedToDimensions rdf:parseType="Resource"> <stDim:w>912</stDim:w> <stDim:h>687</stDim:h> <stDim:unit>pixel</stDim:unit> </mwg-rs:AppliedToDimensions> <mwg-rs:RegionList> <rdf:Bag> <rdf:li rdf:parseType="Resource"> <mwg-rs:Type></mwg-rs:Type> <mwg-rs:Area rdf:parseType="Resource"> <stArea:x>0.680921052631579</stArea:x> <stArea:y>0.3537117903930131</stArea:y> <stArea:h>0.4264919941775837</stArea:h> <stArea:w>0.32127192982456143</stArea:w> <stArea:unit>normalized</stArea:unit> </mwg-rs:Area> </rdf:li> </rdf:Bag> </mwg-rs:RegionList> </mwg-rs:Regions> </rdf:Description> <rdf:Description rdf:about="" xmlns:exif="http://ns.adobe.com/exif/1.0/"> <exif:PixelXDimension>912</exif:PixelXDimension> <exif:PixelYDimension>687</exif:PixelYDimension> <exif:ExifVersion>0220</exif:ExifVersion> </rdf:Description> </rdf:RDF> </x:xmpmeta> <!-- whitespace padding --> <?xpacket end="w"?> This metadata describes various properties of the image like the creator tool, image dimension or a face region within the image. Embedding Embedding metadata in files allows easy sharing and transfer of files across products, vendors, platforms, without metadata getting lost. Embedding avoids a multitude of problems coming from proprietary vendor-specific metadata databases. XMP can be used in several file formats such as PDF, JPEG, JPEG 2000, JPEG XR, GIF, PNG, WebP, HTML, TIFF, Adobe Illustrator, PSD, MP3, MP4, Audio Video Interleave, WAV, RF64, Audio Interchange File Format, PostScript, Encapsulated PostScript, and proposed for DjVu. In a typical edited JPEG file, XMP information is typically included alongside Exif and IPTC Information Interchange Model data. Location in file types For more details, the XMP Specification, Part 3 Storage in Files listed below has details on embedding in specific file formats. TIFFTag 700 JPEGApplication segment 1 (0xFFE1) with segment header "http://ns.adobe.com/xap/1.0/\x00" JPEG 2000"uuid" atom with UID of 0xBE7ACFCB97A942E89C71999491E3AFAC PNGinside an "iTXt" text block with the keyword "XML:com.adobe.xmp" GIFas an Application Extension with identifier "XMP Data" and authentication code "XMP"