These are just some handy links for me to present at a CETAF Information Science and Technology Committee meeting in Geneva, October 2015.
What RBGE publishes
- Example Edinburgh URI: http://data.rbge.org.uk/herb/E00393164
- Leads to 303 redirect with content negotiation:
- Our RDF also contains a link to an image resource which we overload for bigger image.
Main Use Case
- The Wallich Catalogue home page. A numerical list of dried specimens of plants in the East India Company’s Museum
- Example Entry 2574. Shows links to specimens from three different herbaria.
- How do we make these “pretty” i.e. more useful?
- We only want to store specimen IDs on the Wallich server (though may cache a little)
I always come up with something that is overly simplistic so here it is:
- Most important thing is ubiquity. It is no good coming up with a specification for minimal data if 4 out of 10 providers implement it. We need 10/10 for it to be worthwhile.
- Things that server two purposes are more likely to thrive.
- FaceBook have a meta tagging standard based on open graph that they use to provide rich links to web pages and other resource.
- Here is an example of my implementation on another project. Took twenty minutes to add to the page.
- The Facebook approach meets my main use case. It could be done along with any other stuff with RDF. i.e. Every collection needs the URIs to redirect to human readable page and this is trivial to add to that page.
Second Use Case
- This is a bit vague and others may know more.
- Afghan Specimens Portal
- Centre for Middle Eastern Plants
- Dagmar Triebel @ Botanische Staatssammlung München
- & others
- Could it be implemented as “just” a list of specimen IDs?