Difference between revisions of "Adobe Extensible Metadata Platform"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
===Format registry=== | ===Format registry=== | ||
Not part of PRONOM | Not part of PRONOM | ||
| + | |||
| + | ===Significant properties=== | ||
===Preservation action plan=== | ===Preservation action plan=== | ||
Latest revision as of 14:15, 19 January 2010
Main Page > Documentation > Format-specific preservation plans > Adobe Extensible Metadata Platform
Also known as[edit]
Adobe XMP
File extension(s)[edit]
.xmp
Format registry[edit]
Not part of PRONOM
Significant properties[edit]
Preservation action plan[edit]
Preservation issues[edit]
- Xena incorrectly guesses xmp files to be comma separated files. During the normalization, xml code is added to the xmp file, likely rendering it unintelligable to those software programs seeking to draw change information from it.
- Xena also does not incorporate the changes described in the xmp file into the raw image before normalizing the image. This results in the loss of all post-production work.
Conversion test results[edit]
Access format[edit]
More information[edit]
- Further information about XMP can be found on the Adobe website