- From: Uldis Bojars <captsolo@gmail.com>
- Date: Tue, 17 Jun 2014 20:08:38 +0300
- To: Leigh Dodds <leigh@ldodds.com>
- Cc: public-lod community <public-lod@w3.org>
from "ORCID Outreach Meeting (May 21 & 22, 2014) report": http://blogs.nd.edu/emorgan/2014/06/orcid/ the author of the article experimented w. ORCID RDF but found its data insufficient and used other APIs to get additional data: " Unfortunately, the RDF output only included the merest of FOAF-based information, and I was interested in bibliographic citations. Consequently I shifted gears, took advantage of the ORCID-specific API, and I decided to do some text mining. Specifically, I wrote a Perl program — orcid.pl — that takes an ORCID identifier as input (ie. 0000-0002-9952-7800) and then: queries ORCID for all the works associated with the identifier** extracts the DOIs from the resulting XML feeds the DOIs to a program called Tika for the purposes of extracting the full text from documents concatenates the result into a single stream of text, and sends the whole thing to standard output " On 17 June 2014 17:00, Leigh Dodds <leigh@ldodds.com> wrote: > I discovered this today: > > curl -v -L -H "Accept: text/turtle" http://orcid.org/0000-0003-0837-2362 > > A fairly new addition to the ORCID service I think. > > With many DOIs already supporting Linked Data views, this makes a nice > addition to the academic linked data landscape. > > Still lots of room for improvement, but definitely a step forwards. > > Cheers, > > L. > > -- > Leigh Dodds > Freelance Technologist > Open Data, Linked Data Geek > t: @ldodds > w: ldodds.com > e: leigh@ldodds.com >
Received on Tuesday, 17 June 2014 17:09:06 UTC