Linked Data Compliance- synopsis

3 views
Skip to first unread message

Nico Carver

unread,
Feb 16, 2012, 5:42:15 PM2/16/12
to drya...@googlegroups.com
Is Dryad+Datacite Linked Data compliant? 

The short answer is yes. Datacite is providing well formed RDF/XML {1} that validates {2} and has the proper 303 re-directs in place.  

If you are eager to see for yourself, you can use cURL from the command line.  It can be used to retrieve full citations (example command: curl -L -H "Accept: application/x-datacite+text" http://dx.doi.org/10.5061/DRYAD.RT8BJ147) or the metadata for that object as RDF/XML (example command: curl -L -H "Accept: application/rdf+xml" http://dx.doi.org/10.5061/DRYAD.RT8BJ147){3}. You can also run through the examples given by Richard Cyganiak on his blog {4} to check for 303 redirects and content negotiation.
So far so good.

Moving on to the content of the RDF itself, we start to see a few problems.  Only the first author for each data package/file is displayed. This is a known problem and should be fixed with the release of 1.11.
Secondly, if we look at the four principles for linked data from the W3C wiki {5}, Dryad is following the first 3, but the 4th states to "Include links to other, related URIs".  We should be at a minimum providing links/URIs to related data files. It would also make sense to include a URI to the journal article.  My understanding from Ryan is that these are not there for the same reason the multiple authors aren't present: we are moving to the more complex metadata submission for EZID in 1.11. Currently everything is represented in attribute-value pairs, while the more complex method will allow us to submit RDF triples, and therefore include the relationships between related URIs in the RDF.

I welcome any corrections. This is a part of my External Metadata report that will be up on the wiki in a couple weeks.

--Nico

Hilmar Lapp

unread,
Feb 16, 2012, 6:29:24 PM2/16/12
to Nico Carver, drya...@googlegroups.com
Hi Nico,

This is great, thanks, and fully corroborates observations I've made a few weeks ago on an entirely non-rigorous spot-checking basis.

Concerning your mention of poor compliance with the 4th LOD principle, I'll add that I think it would be of great value if our subject keywords, geographic places, etc were URIs of web-resources that represent these concepts, such as DBpedia URIs. Likewise, I hope, or would advocate, that the vocabulary term matches we'll hopefully get through HIVE integration be retained as terms, including concept URIs, rather than the term's labels used for display.

BTW (and this is a question for the HIVErs on here) has the DBpedia vocabulary been considered for use as one of the HIVE vocabularies?

-hilmar

--
You received this message because you are subscribed to the Google Groups "dryad-dev" group.
To post to this group, send email to drya...@googlegroups.com.
To unsubscribe from this group, send email to dryad-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dryad-dev?hl=en.

-- 
===========================================================
: Hilmar Lapp  -:- Durham, NC -:- informatics.nescent.org :
===========================================================



Reply all
Reply to author
Forward
0 new messages