The InChI (International Chemical Identifier from IUPAC) has been blogged earlier here. RSC have especially taken this on board in their Project Prospect and now routinely syndicate InChI identifiers in their RSS feeds as blogged here.

ISO has registered with the IANA a URN namespace identifier (“iso:”) for ISO persistent resources. From the Internet-Draft: The toplevel grammar rules (ABNF) give some indication of scope: std-nss = “std:” docidentifier *supplement *docelement [addition] Just wanted to quote here one of the funkier examples cited in the document: Wow! That’s some ID. That’s something else. As far as DOI is concerned there is nothing obvious to be learned.

( Update - 2007.10.02: Just realized that there were some serious flaws in the post below regarding publication and form of namespace URIs which I’ve now addressed in a subsequent post here.) By way of experimenting with a use case for ISO URNs, below is a listing of the document metadata for an arbitrary PDF.

On the subject of author IDs (a subject Crossref is interested in and on which held a meeting earlier this year, as blogged about here), this post by Karen Coyle “Name authority control, aka name identification” may be worth a read.

Been so busy looking into the technical details of XMP that I almost forgot to check out the current landcsape.

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: Actually, it occurs in most of the core namespaces: XAP, rather than XMP.

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: In the AMA style a reference would be: This is great news.

ACAP has released some documents outlining the use cases they will be testing and some proposed changes to the Robots Exclusion Protocol (REP) - both robots.txt and META tags. There are some very practical proposals here to improve search engine indexing.

Hadn’t really noticed before but was fairly gobsmacked by this notice I just saw on the DOI® Handbook: And, indeed, the Handbook’s TOC only reconfirms this: That’s spooky. A book with a hidden chapter. I really don’t like that at all. Especially on a book aiming to provide general information and guidance.

Creative Commons now have a custom panel for adding CC licenses using Adobe apps - see here. Interesting on two counts: Machine readable licenses XMP metadata But I still think that batch solutions for adding XMP metadata are really required for publishing workflows. And ideally there should be support for adding arbitrary XMP packets if we’re going to have truly rich metadata.

Public comment period on the PRISM 2.0 draft ends Saturday (Sept. 15) ahead of next week’s WG meeting to review feedback and finalize the spec. (I put in some comments about XMP already.