WHAT
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/xfolio/webapp/transform/meta/xmp2dc.xsl
AdobeTM applications (and some other freewares like [pixvue]) promote an XML schema of metadatas (title, author, description...) embed in binary files (jpeg, pdf, and other proprietary format). The info is interesting, using a semantic knowed as [IPTC/IMM], but the XML is ugly. This transformation try to extract most of the fields in a flat XML record conforming to dublincore recommandations. This becomes interesting when you can get some xmp. It's usually possible with some tricks in AdobeTM apps, but hopefully, a cocoon generator is also exposed here for jpeg images
[XfolioXMPGenerator]
There's a specific feature in this transformation. In our context, we expect multilingual records (title and description in more than one language). You can imagine the interest. If you have an image with a tree, if the content is indexed in a search engine, you can find the images documented with the term "tree". If you are waiting for other langs public, it's also nice to have the term "arbre", or "baum". A very simple text rule is supported, precised in the HOW section. This transformation have been tested on some hundred of jpeg images.
WHO
[FG] FredericGlorieux (AJLSM) http://www.ajlsm.com
[PT] Terray, Paul (4Dconcept) http://www.4dconcept.fr/
INPUT
<?xml version="1.0" encoding="utf-8"?> <?xpacket begin='' id='W5M0MpCehiHzreSzNTczkc9d'?> <?adobe-xap-filters esc="CR"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP toolkit 2.9-9, framework 1.6"> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:iX="http://ns.adobe.com/iX/1.0/"> <rdf:Description xmlns:pdf="http://ns.adobe.com/pdf/1.3/" rdf:about="uuid:677e475e-f67e-11d8-b1aa-d5ccd9677e7a"> </rdf:Description> <rdf:Description xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/" rdf:about="uuid:677e475e-f67e-11d8-b1aa-d5ccd9677e7a"> <photoshop:AuthorsPosition>Ingénieur civil</photoshop:AuthorsPosition> <photoshop:City>FAQRA</photoshop:City> <photoshop:State>KESROUAN</photoshop:State> <photoshop:Country>LIBAN</photoshop:Country> <photoshop:DateCreated>2003-12-15</photoshop:DateCreated> <photoshop:CaptionWriter>S.D., H.K-J. Equipe Strabon</photoshop:CaptionWriter> </rdf:Description> <rdf:Description xmlns:xap="http://ns.adobe.com/xap/1.0/" rdf:about="uuid:677e475e-f67e-11d8-b1aa-d5ccd9677e7a"> </rdf:Description> <rdf:Description xmlns:xapMM="http://ns.adobe.com/xap/1.0/mm/" rdf:about="uuid:677e475e-f67e-11d8-b1aa-d5ccd9677e7a"> <xapMM:DocumentID>adobe:docid:photoshop:c2120245-f678-11d8-b1aa-d5ccd9677e7a</xapMM:DocumentID> </rdf:Description> <rdf:Description xmlns:xapRights="http://ns.adobe.com/xap/1.0/rights/" rdf:about="uuid:677e475e-f67e-11d8-b1aa-d5ccd9677e7a"> <xapRights:Marked>True</xapRights:Marked> <xapRights:WebStatement>http://creativecommons.org/licenses/by-nc-sa/2.0/</xapRights:WebStatement> </rdf:Description> <rdf:Description xmlns:dc="http://purl.org/dc/elements/1.1/" rdf:about="uuid:677e475e-f67e-11d8-b1aa-d5ccd9677e7a"> <dc:creator> <rdf:Seq> <rdf:li>Kalayan, Haroutune</rdf:li> </rdf:Seq> </dc:creator> <dc:title> <rdf:Alt> <rdf:li xml:lang="x-default">FAQRA - Eglise d'époque byzantine</rdf:li> </rdf:Alt> </dc:title> <dc:description> <rdf:Alt> <rdf:li xml:lang="x-default"> [fr] Vue de la nef centrale de l'église bordée par ses deux rangées de colonnes. [en]View of the chief nave of the church, bordered by its two rows of columns. </rdf:li> </rdf:Alt> </dc:description> <dc:rights> <rdf:Alt> <rdf:li xml:lang="x-default">©1962. Direction Générale des Antiquités. Liban</rdf:li> </rdf:Alt> </dc:rights> <dc:subject> <rdf:Bag> <rdf:li>1962</rdf:li> <rdf:li>Archéologie</rdf:li> <rdf:li>Architecture</rdf:li> <rdf:li>Colonne</rdf:li> <rdf:li>Eglise</rdf:li> <rdf:li>Fakra</rdf:li> <rdf:li>Faqra</rdf:li> <rdf:li>Kalayan, Haroutune</rdf:li> <rdf:li>Nef</rdf:li> <rdf:li>Période byzantine</rdf:li> <rdf:li>Restauration</rdf:li> </rdf:Bag> </dc:subject> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end='w'?>
OUTPUT
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:IIM="http://iptc.org/IIM/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <rdf:Description> <dc:creator xsi:type="IIM:Author">Kalayan, Haroutune (Ingénieur civil)</dc:creator> <dc:title xsi:type="IIM:Title">FAQRA - Eglise d'époque byzantine</dc:title> <dc:title xsi:type="IIM:Description" xml:lang="fr" >Vue de la nef centrale de l'église bordée par ses deux rangées de colonnes.</dc:title> <dc:title xsi:type="IIM:Description" xml:lang="en" >View of the chief nave of the church, bordered by its two rows of columns.</dc:title> <dc:rights xsi:type="IIM:Copyright" rdf:resource="http://creativecommons.org/licenses/by-nc-sa/2.0/" >©1962. Direction Générale des Antiquités.Liban</dc:rights> <dc:subject xsi:type="IIM:Keywords">1962</dc:subject> <dc:subject xsi:type="IIM:Keywords">Archéologie</dc:subject> <dc:subject xsi:type="IIM:Keywords">Architecture</dc:subject> <dc:subject xsi:type="IIM:Keywords">Colonne</dc:subject> <dc:subject xsi:type="IIM:Keywords">Eglise</dc:subject> <dc:subject xsi:type="IIM:Keywords">Fakra</dc:subject> <dc:subject xsi:type="IIM:Keywords">Faqra</dc:subject> <dc:subject xsi:type="IIM:Keywords">Kalayan, Haroutune</dc:subject> <dc:subject xsi:type="IIM:Keywords">Nef</dc:subject> <dc:subject xsi:type="IIM:Keywords">Période byzantine</dc:subject> <dc:subject xsi:type="IIM:Keywords">Restauration</dc:subject> <dc:coverage xsi:type="iptc">FAQRA (LIBAN, KESROUAN)</dc:coverage> <dc:date xsi:type="IIM:ReleaseDate">2003-12-15</dc:date> <dc:contributor xsi:type="IIM:CaptionWriter" >S.D., H.K-J. Equipe Strabon</dc:contributor> </rdf:Description> </rdf:RDF>
HOW
Multilingual description are formatted in the description field like that
default description [lang] title on one line description multiline [other lang] title in another lang description in this lang...
TODO
isolate country somewhere ?
<xapBJ:JobRef> <rdf:Bag> <rdf:li rdf:parseType="Resource"> <stJob:name>Project Blue Square</stJob:name> </rdf:li> </rdf:Bag> </xapBJ:JobRef> <exif:ColorSpace>1</exif:ColorSpace> <exif:PixelXDimension>400</exif:PixelXDimension> <exif:PixelYDimension>300</exif:PixelYDimension> <photoshop:History/> <tiff:Orientation>1</tiff:Orientation> <tiff:XResolution>72/1</tiff:XResolution> <tiff:YResolution>72/1</tiff:YResolution> <tiff:ResolutionUnit>2</tiff:ResolutionUnit>
CHANGES
2004-10-08:[FG] a bug with photoshop XMP
2004-10-07:[FG] Licence URI (<xapRights:WebStatement/>)
2004-10-06:[FG] more precise "IIM:" namespace
2004-10-05:[FG] multilingual descriptions, bug corrected
2004-09 :[FG] creation
REFERENCES
[pixvue] Colemenan, Eamon. http://pixvue.com/
An MS.Windows Image Organizer, XMP compatible
[IPTC/IMM] "IPTC - NAA INFORMATION INTERCHANGE MODEL" http://www.iptc.org/IIM/
http://www.iptc.org/download/download.php?fn=IIMV4.1.pdf
[XMP] Adobe Systems Incorporated "Extensible Metadata Platform (XMP)" http://www.adobe.com/products/xmp/main.html Adobe's Extensible Metadata Platform (XMP) is a labeling technology that allows you to embed data about a file, known as metadata, into the file itself. With XMP, desktop applications and back-end publishing systems gain a common method for capturing, sharing, and leveraging this valuable metadata -
opening the door for more efficient job processing, workflow automation, and rights management, among many other possibilities. With XMP, Adobe has taken the "heavy lifting" out of metadata integration, offering content creators an easy way to embed meaningful information about their projects and providing industry partners with standards-based building blocks to develop optimized workflow solutions.
[DCES] "Dublin Core Metadata Element Set, Version 1.1: Reference Description". DCMI (Dublin Core Metadata Initiative) http://dublincore.org/documents/dces/
The Dublin Core metadata element set is a standard for cross-domain information resource description. Here an information resource is defined to be "anything that has identity". This is the definition used in Internet RFC 2396, "Uniform Resource Identifiers (URI): Generic Syntax", by Tim Berners-Lee et al. There are no fundamental restrictions to the types of resources to which Dublin Core metadata can be assigned.
[DC-XML] "Guidelines for implementing Dublin Core in XML". DCMI, Dublin Core Metadata Initiative, 2003-04-02. Powell, Andy; Johnston, Pete. http://dublincore.org/documents/dc-xml-guidelines/
This document provides guidelines for people implementing Dublin Core metadata applications using XML. It considers both simple (unqualified) DC and qualified DC applications. In each case, the underlying metadata model is described (in a syntax neutral way), followed by some specific guidelines for XML implementations. Some guidance on the use of non-DC metadata within DC metadata applications is also provided.
[DCES-RDF] "Expressing Simple Dublin Core in RDF/XML". Dublin Core Metadata Initiative, 2002-07-31. Beckett, Dave; Miller, Eric; Brickley, Dan. http://dublincore.org/documents/dcmes-xml/
The Dublin Core Metadata Element Set V1.1 (DCMES) can be represented in many syntax formats. This document explains how to encode the DCMES in RDF/XML, provides a DTD to validate the documents and describes a method to link them from web pages.
[DCQ-RDF] "Expressing Qualified Dublin Core in RDF / XML". DCMI Dublin Core Metadata Initiative, 2002-05-15. Kokkelink, Stefan; Schwänzl, Roland. http://dublincore.org/documents/dcq-rdf-xml/
This document describes how qualified Dublin Core metadata can be encoded in RDF / XML and gives practical examples.
[AJLSM] Arvers, Jean-Luc; Sévigny, Martin "Solution pour le document numérique" http://ajlsm.com
SEE ALSO
Generated links
cited by |
about xmp |
about xfolio |
<<FullSearch>> |
<<PageList(xmp)>> |
<<PageList(xfolio)>> |