Blog

Whole Lotta ID

Crossref

thammond – 2007 October 01

In Identifiers

ISO has registered with the IANA a URN namespace identifier (ā€œiso:ā€) for ISO persistent resources. From the Internet-Draft: ā€œThis URN NID is intended for use for the identification of persistent resources published by the ISO standards body (including documents, document metadata, extracted resources such as standard schemata and standard value sets, and other resources).ā€ The toplevel grammar rules (ABNF) give some indication of scope: NSS = std-nss std-nss = “std:” docidentifier *supplement *docelement [addition]

Authors in Context?

Crossref

thammond – 2007 September 30

In ORCID

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. She starts off with this: ā€œLibraries do something they call ā€œname authority controlā€. For most people in IT, this would be called ā€œassigning unique identifiers to names.ā€ Identifying authors is considered one of the essential aspects of library cataloging, and it isnā€™t done in any other bibliographic environment, as far as I know.

XMP-Ville

Crossref

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:

  • The Brief Tortured Life of XMP (July ā€™05)
    • [Thought Leaders Hammer out Metadata Standard] (April ā€™07)
      • [Metadata Persistence and ā€œSave for Webā€¦ā€] (July ā€™07)

      From the earlier characterization of XMP as ā€œunderachieving teenagerā€ Roszkiewicz is cautiously optimistic that IDEAllianceā€™s XMP Open initiative (an initiative to advance XMP as an open industry specification) will help outreach and foster adoption of this fledgling technology.

      (Continues.)

The Nameā€™s The Thing

Crossref

thammond – 2007 September 20

In XMP

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.)

ACAP - Any chance of success?

Ed Pentz

Ed Pentz – 2007 September 19

In Search

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. However, the only search engine publicly participating in the project is http://www.exalead.com/ (which according to Alexa attracted 0.0043% of global internet visits over the last three months). The main docs are ā€œACAP pilot Summary use cases being testedā€, ā€œACAP Technical Framework - Robots Exclusion Protocol - strawman proposals Part 1ā€, ā€œACAP Technical Framework - Robots Exclusion Protocol - strawman proposals Part 2ā€, ā€œACAP Technical Framework - Usage Definitions - draft for pilot testingā€.

Style Guides Recommend DOI strings

Ed Pentz

Ed Pentz – 2007 September 19

In Citation Formats

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/

Chapter 9 - The Closed Book

Crossref

thammond – 2007 September 15

In Discussion

Hadnā€™t really noticed before but was fairly gobsmacked by this notice I just saw on the DOIĀ® Handbook: **Please note that Chapter 9, Operating Procedures is for Registration Agency personnel only.** DOIĀ® Handbook doi:10.1000/182 http://www.doi.org/hb.html And, indeed, the Handbookā€™s TOC only reconfirms this: 9 Operating procedures* *The RA password is required for viewing Chapter 9. 9.1 Registering a DOI name with associated metadata 9.2 Prefix assignment 9.3 Transferring DOI names from one Registrant to another

Custom Panel for CC

Crossref

thammond – 2007 September 15

In Metadata

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. I rather fear the constraints that custom panels place upon the publisher.

Last Orders Please!

Crossref

thammond – 2007 September 13

In 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. Hope they got that.)

Marking up DOI

Crossref

thammond – 2007 September 11

In XMP

(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.)