Extensible Metadata Platform (XMP) Specification - Adobe Partners
Extensible Metadata Platform (XMP) Specification - Adobe Partners
Extensible Metadata Platform (XMP) Specification - Adobe Partners
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2<br />
<strong>XMP</strong> Data Model<br />
Property Values<br />
Pirates of Penzance<br />
dc:creator<br />
"William Gilbert"<br />
1<br />
seq<br />
2<br />
"Arthur Sullivan"<br />
ns:role<br />
"lyricist"<br />
ns:role<br />
"composer"<br />
Property qualifiers allow values to be extended without breaking existing usage. For example,<br />
the ns:role qualifier in the diagram does not interfere with readers who simply want the<br />
dc:creator names. An alternative would be to change dc:creator values to structures with name<br />
and role fields, but that would confuse old software that expected to find a simple value.<br />
The most common specific use of property qualifiers is for language alternative arrays (see<br />
next section).<br />
Language Alternatives<br />
Language alternatives allow the text value of a property to be chosen based on a desired<br />
language. Each item in a language alternative array is a simple text value, which must have a<br />
language qualifier associated with it. The language qualifier is a property qualifier, as<br />
described in the previous section. The qualifier name is xml:lang, and its value is a string that<br />
conforms to RFC 3066 notation.<br />
<strong>XMP</strong> uses the "x-default" language code to denote the default value for a language<br />
alternative. It should be the first item in the array, so that generic RDF processors will also use<br />
it as the default (according to the RDF default-is-first rule). The figure below shows an<br />
example:<br />
18 September 2005 <strong>XMP</strong> <strong>Specification</strong>