Iâm always curious about names and where they come from and what they mean. Hence, my interest was aroused with the constant references to âXAPâ in XMP. As the XMP Specification (Sept. 2005) says:
âNOTE: The string âXAPâ or âxapâ appears in some namespaces, keywords, and related names in this document and in stored XMP data. It reflects an early internal code name for XMP; the names have been preserved for compatibility purposes.â
Actually, it occurs in most of the core namespaces: XAP, rather than XMP.
(Continues.)
A couple of recent posts - from A couple of recent posts - from at Jefferson University and IFST at Univ of Delaware- note that the AMA and APA style guides now recommend using a DOI, if one is assigned, in a journal article citation.
A citation in the APA style with a DOI would be:
Conley, D., Pfeiffera, K. M., ďż˝ Velez, M. (2007). Explaining sibling differences in achievement and behavioral outcomes: The importance of within- and between-family factors. Social Science Research36(3), 1087-1104. doi:10.1016/j.ssresearch.2006.09.002
In the AMA style a reference would be:
Kitajima TS, Kawashima SA, Watanabe Y. The conserved kinetochore protein shugoshin protects centromeric cohesion during meiosis. Nature. 2004;427(6974):510-517. doi:10.1038/nature02312
This is great news. I havenât looked at the full style guides but itâs not clear if information is given about linking DOIs via http://dx.doi.org/
(Update - 2007.09.15: Clean forgot to add in the rdf: namespace to the examples for xmp:Identifier in this post. Iâve now added in that namespace to the markup fragments listed. Also added in a comment here which shows the example in RDF/XML for those who may prefer that over RDF/N3.)
So, as a preliminary to reviewing how a fuller metadata description of a Crossref resource may best be fitted into an XMP packet for embedding into a PDF, letâs just consider how a DOI can be embedded into XMP. And since itâs so much clearer to read letâs just conduct this analysis using RDF/N3. (Life is too short to be spent reading RDF/XML or C++ code. :~)
(And further to Chris Shillumâs comment [(Update - 2007.09.15: Clean forgot to add in the rdf: namespace to the examples for xmp:Identifier in this post. Iâve now added in that namespace to the markup fragments listed. Also added in a comment here which shows the example in RDF/XML for those who may prefer that over RDF/N3.)
So, as a preliminary to reviewing how a fuller metadata description of a Crossref resource may best be fitted into an XMP packet for embedding into a PDF, letâs just consider how a DOI can be embedded into XMP. And since itâs so much clearer to read letâs just conduct this analysis using RDF/N3. (Life is too short to be spent reading RDF/XML or C++ code. :~)
(And further to Chris Shillumâs comment]2 on my earlier post Metadata in PDF: 2. Use Cases where he notes that Elsevier are looking to upgrade their markup of DOI in PDF to use XMP, Iâm really hoping that Elsevier may have something to bring to the party and share with us. A consensus rendering of DOI within XMP is going to be of benefit to all.)
(Continues.)
You might have been wondering why Iâve been banging on about XMP here. Why the emphasis on one vendor technology on a blog focussed on an industry linking solution? Well, this post is an attempt to answer that.
Four years ago we at Nature Publishing Group, along with a select few early adopters, started up our RSS news feeds. We chose to use RSS 1.0 as the platform of choice which allowed us to embed a rich metadata term set using multiple schemas - especially Dublin Core and PRISM. We evangelized this much at the time and published documents on XML.com (Jul. â03) and in D-Lib Magazine (Dec. â04) as well as speaking about this at various meetings and blogging about it. Since that time many more publishers have come on board and now provide RSS routinely, many of them choosing to enrich their feeds with metadata.
Well, RSS can be seen in hindsight as being the First Wave of projecting a web presence beyond the content platform using standard markup formats. With this embedded metadata a publisher can expand their web footprint and allow users to link back to their content server.
Now, XMP with its potential for embedding metadata in rich media can be seen as a Second Wave. Media assets distributed over the network can now carry along their own metadata and identity which can be leveraged by third-party applications to provide interesting new functionalities and link-back capability. Again a projection of web presence.
(Continues.)
What on earth can this string mean: âW5M0MpCehiHzreSzNTczkc9dâ? This occurs in the XMP packet header:
Well from the XMP Specification (September 2005) which is available here (PDF) there is this text:
âThe required id attribute must follow begin. For all packets defined by this version of the syntax, the value of id is the following string: W5M0MpCehiHzreSzNTczkc9dâ
(See: 3 XMP Storage Model / XMP Packet Wrapper / Header / Attribute: id)
OK, so itâs no big deal to cut and paste that string, itâs just mighty curious why this cryptic key is needed in an open specification, especially since (contrary to what might be implied by the text) it doesnât seem to vary with version. (Or hasnât yet, at any rate - more below.)
Following on from the missing XMP Specification version number discussed in the previous post here below are listed some miscellaneous gripes Iâve got with XMP (on what otherwise is a very promising technology). I would be more than happy to be proved wrong on any of these points.
Crossref at the Frankfurt Digital Book Fair
2020 September 17
Publishers, are you ready to ROR?
2020 August 25
Evolving our support for text-and-data mining
2020 August 21
