Recently we announced that we were making some new recommendations in our DOI display guidelines. One of them was to use the secure HTTPS protocol to link Crossref DOIs, instead of the insecure HTTP.
Interesting post from Google, in which they say:
“Recently, even our search engineers stopped in awe about just how big the web is these days — when our systems that process links on the web to find new content hit a milestone: 1 trillion (as in 1,000,000,000,000) unique URLs on the web at once!”
Puts Crossref’s 32,639,020 unique DOIs into some kind of perspective: 0.0033%. But nonetheless that trace percentage still seems to me to be reasonably large, especially in view of it forming a persistent and curated set.
With these words:
_“There was quite some interest in Linked Data at this year’s World Wide
Web Conference (WWW2007). Therefore, Richard Cyganiak, Tom Heath and I
decided to write a tutorial about how to publish Linked Data on the
Web, so that interested people can find all relevant information, best
practices and references in a single place.”_
Chris Bizer announces this draft How to Publish Linked Data on the Web.
Just in case anybody may not have seen this, here‘s the testimony of Sir Tim Berners-Lee yesterday before a House of Representatives Subcommittee on Telecommunications and the Internet. Required reading.
(Via this post yesterday in the Save the Internet blog.)
IOP has created an instance of the arXiv repository called eprintweb.org at https://web.archive.org/web/20130803071935/http://eprintweb.org/S/. What’s the difference from arXiv? From the eprinteweb.org site - “We have focused on your experience as a user, and have addressed issues of navigation, searching, personalization and presentation, in order to enhance that experience. We have also introduced reference linking across the entire content, and enhanced searching on all key fields, including institutional address.”
The site looks very good and it’s interesting to see a publisher developing a service directly engaging with a repository.
The info registry has now added in the InChI namespace (see registry entry here) which now means that chemical compounds identified by InChIs (IUPAC‘s International Chemical Identifiers) are expressible in URI form and thus amenable to many Web-based description technologies that use URI as the means to identify objects, e.g. XLink, RDF, etc. As an example, the InChI identifier for naphthalene is
and can now be legitimately expressed in URI form as
The RSC has gone live today with the results of Project Prospect, introducing semantic enrichment of journal articles across all our titles. I’m pretty sure we’re the first primary research publisher to do anything of this scope.
We’re identifying chemical compounds and providing synonyms, InChIs (IUPAC’s Chemical Identifier), downloadable CML (Chemical Markup Language), SMILES strings and 2D images for these compounds. In terms of subject area we’re marking up terms from the IUPAC Gold Book, and also Open Biomedical Ontology terms from the Gene, Cell, and Sequence Ontologies.
First off, a Happy New Year to all!
A post of mine to the OpenURL list may possibly be of interest. Following up the recent W3C TAG (Technical Architecture Group) Finding on “The Use of Metadata in URIs” I pointed out that the TAG do not seem to be aware of OpenURL: which is both a standard prescription for including metadata in URI strings and a US information standard to boot.