Tim Brody wrote: > I've written a module for parsing and constructing OpenURLs > (http://library.caltech.edu/openurl/) within the URI framework: > > http://santos.ecs.soton.ac.uk/URI-openurl-0.1.tar.gz > > OpenURL is not a URI format per-se, but a means of transporting > structured metadata via URIs (e.g. http://host/path?openurl_query). > > As the proposed NISO specs have an abstraction layer ("entities") I have > built support for these within URI by casting between different entity > classes, all of which are subclasses of URI::openurl, which in turn is a > subclass of _server. This allows the construction of OpenURLs through > methods, rather than hierarchical hash-trees. My implementation of this > may be bad (the only way I could think to get around URI's single-scalar > storage), so would appreciate any comments!
What does OpenURL pretend to solve? Could you give some examples of usage that can't be done without OpenURLs?
