Blog

XMP in RSC PDFs

admin

admin – 2010 August 03

In IdentifiersPdfXmpInchi

Just a quick heads-up to say that we’ve had a go at incorporating InChIs and ontology terms into our PDFs with XMP. There isn’t a lot of room in an XMP packet so we’ve had to be a bit particular about what we include. InChIs: the bigger the molecule the longer the InChI, so we’ve standardized on the fixed-length InChIKey. This doesn’t mean anything on its own, so we’ve gone the Semantic Web route of including an InChI resolver HTTP URI.

Add Crossref metadata to PDFs using XMP

Geoffrey Bilder

Geoffrey Bilder – 2009 December 09

In MetadataPdfXmp

In order to encourage publishers and other content producers to embed metadata into their PDFs, we have released an experimental tool called “pdfmark”, This open source tool allows you to add XMP metadata to a PDF. What’s really cool, is that if you give the tool a Crossref DOI, it will lookup the metadata in Crossref and then apply said metadata to the PDF. More detail can be found on the pdfmark page on the Crossref Labs site.

XMP Primer

thammond

thammond – 2009 June 10

In Xmp

There’s a new XMP Primer (PDF) by Ron Roskiewicz (ed. Dianne Kennedy) available from XMP-Open. This is copyrighted 2008 but I only just saw this now. This is a 43 page document which provides a very gentle introduction to metadata and labelling of media and then introduces XMP into the content lifecycle and talks to the business case for using XMP. The primer covers the following areas: Introduction to Metadata Introduction to XMP XMP and the Content Lifecycle XMP in Action; Use Cases Additional XMP Resources One small gripe would be that this seems to have been prepared for US letter-sized pages and although is printable on A4 there is the slightest of clippings on the right-hand margin with no real loss of information but it does confer a sense of “incompleteness”.

XMP Library for Flash

thammond

thammond – 2009 January 16

In Xmp

Update about new XMP Library from Adobe Labs: “The new Adobe XMP Library for ActionScript is now available for download on Adobe Labs. Adobe Extensible Metadata Platform (XMP) is a labeling technology that allows you to embed data about a file, known as metadata, into the file itself. XMP is an open technology based on RDF and RDF/XML. With this new library you can read existing XMP metadata from Flash based file formats via the Adobe Flash Player.

Xmas XMP

thammond

thammond – 2008 December 19

In Xmp

Well, as I blogged on our web publishing blog Nascent we just went live with XMP labelling on Nature in yesterday’s double issue. We will be adding XMP to all new issues of Nature as well as rolling out across all our other titles in the next few weeks and months. The screenshots below from Acrobat (File > Properties, CMD-D / CTL-D) show what the user might see both with (bottom-left) and without (top-right) semantic markup.

XMP Marches On

thammond

thammond – 2008 October 20

In Xmp

For those who may be interested in the progress of XMP, Adobe’s Gunar Penikis has just announced two new releases of XMP SDKs: XMP Toolkit 4.4 (with support for new file formats), and FileInfo SDK (for customizing CS4 UIs). More importantly, though, may be the new edition of the XMP spec - see here, which is bumped from a modest 112 page document to a 3-parter at 199 pages. Looks to be quite a thorough spec bar one telling particular: there is no version number and no date!

Hybrid

thammond

thammond – 2007 October 17

In Xmp

So, back on the old XMP tack. The simple vision from the XMP spec is that XMP packets are embedded in media files and transported along with them - and as such are relatively self-contained units, see Fig 1.

Hybrid - A.jpg

Fig. 1 - Media files with fully encapsulated descriptions.

But this is too simple. Some preliminary considerations lead us to to see why we might want to reference additional (i.e. external) sources of metadata from the original packet:

PDFs
PDFs are tightly structured and as such it can be difficult to write a new packet, or to update an existing packet. One solution proposed earlier is to embed a minimal packet which could then reference a more complete description in a standalone packet. (And in turn this standalone packet could reference additional sources of metadata.)
Images
While considerably simpler to write into web-delivery image formats (e.g. JPEG, GIF, PNG), it is the case that metadata pertinent to the image only is likely to be embedded. Also, of interest is the work from which the image is derived which is most likely to be presented externally to the image as a standalone document. (And in turn this standalone packet could reference additional sources of metadata.)

(Continues)

I Want My XMP

thammond

thammond – 2007 October 13

In Xmp

Now, assuming XMP is a good idea - and I think on balance it is (as blogged earlier), why are we not seeing any metadata published in scholarly media files? The only drawbacks that occur to me are:

  1. Hard to write - it’s too damn difficult, no tools support, etc.

    • Hard to model - rigid, “simple” XMP data model, both complicates and constrains the RDF data model

Well, I don’t really believe that 1) is too difficult to overcome. A little focus and ingenuity should do the trick. I do, however, think 2) is just a crazy straitjacket that Adobe is forcing us all to wear but if we have to live with that then so be it. Better in Bedlam than without. (RSS 1.0 wasn’t so much better but allowed us to do some useful things. And that came from the RDF community itself.) We could argue this till the cows come home but I don’t see any chance of any change any time soon.

(Continues)

Metadata - For the Record

thammond

thammond – 2007 October 13

In Xmp

Interesting post here from Gunar Penikis of Adobe entitled “Permanent Metadata” (Oct. ’04). He talks about the the issues of embedding metadata in media and comes up with this: “It may be the case that metadata in the file evolves to become a “cache of convenience” with the authoritative information living on a web service. The web service model is designed to provide the authentication and permissions needed. The link between the two provided by unique IDs.

XMP-Ville

thammond

thammond – 2007 September 25

In Xmp

Been so busy looking into the technical details of XMP that I almost forgot to check out the current landcsape. Luckily I chanced on these articles by Ron Roszkiewicz for The Seybold Report (and apologies for lifting the title of this post from his last). The articles about XMP are well worth reading and chart the painful progress made to date:

RSS Feed

Categories

Archives
https://0-www.crossref.org.libcat.lafayette.edu/categories/xmp/
0-www.crossref.org.libcat.lafayette.edu
crawl=CC-MAIN-2019-18
67695
application/http; msgtype=response
sha1:X5VRJ2QW2DMZYWLQHV4SS7AG36NXGSVN
<urn:uuid:2e5c7936-e768-4a23-9fdd-bc37dcf46870>
2019-04-25T00:04:21Z
52.7.18.179
text/html
sha1:XYVZLGQRDBOYMHC6H7A5VBGJD23QBJ2R
<urn:uuid:fb9c21e4-f317-4791-b745-629e6e7af24e>
https://0-www.crossref.org.libcat.lafayette.edu/categories/xmp/
response
<urn:uuid:7056343e-ca64-4bdf-8844-5f94e26e2b78>
isPartOf: CC-MAIN-2019-18
publisher: Common Crawl
description: Wide crawl of the web for April 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-165-178-231.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/