One thought on “Resolution and transaction costs”

  1. More generally it is about ‘service routing’ (a term I borrow from my colleague Mike Teets): given some metadata as input, what relevant services can be mobilized.

    I concur.

    OpenURL is about sending standardized sets of name/value pairs to a resolver. These name/value pairs describe things such as a bibliographic item, where the bibliographic item was seen, and who is making the request of the resolver. The resolver is expected to read the name/value pairs and respond with a set of services that can be applied against the things described. The most common “service” resolvers provide is a locator service. “Where can I get the full text of this article.”

    So many other servcies could be implemented. Review this thing. Borrow this thing. Put this thing on reserve. Download. Convert it into a Chicagop-style citation. Save it to a list of my favorites. Semantically compare it to a set of other things. Return the email address of the author so I can initiate a discussion. Etc.

    This is a long way of saying what is said above, “what relevant services can be mobilized.”

Comments are closed.