Cool URIs Are Human Readable
published: July 12, 2012, recorded: June 2012, views: 5553
Report a problem or upload filesIf you have found a problem with this lecture or would like to send us extra material, articles, exercises, etc., please use our ticket system to describe your request and upload the data.
Enter your e-mail into the 'Cc' field, and we will keep you updated with your request's status.
In order to aid data interoperability between public administrations across Europe, the EU's ISA Programme is promoting the development of a system whereby things like standards, code lists and vocabularies can be discovered through a common metadata system called ADMS. In parallel, a number of core vocabularies have been developed for describing people, businesses and locations. And guess what? All the documentation is in English. The RDF and XML schemas are all in English and the terms in those vocabularies are all English words. All the hooks are in place for the schemas to be localised, but the problem goes a little deeper that merely finding the budget for localisation: Language is part of someone's identity. In some cases it's a defining national characteristic and so in order to create a framework for interoperability across national borders we need not only to get the language right but also the culture and the trust. Vocabularies must be available at a stable URI, be subject to an identifiable policy on change control, and be published on a domain that is both politically and geographically neutral. Technically, this last point is irritating since example.us is a "dumb string," but can you imagine the French government using it? Or the UK government using anything ending in .eu? Multilingual Linked Data needs localised RDF vocabularies and localised reference data but don't overlook the importance of the branding and/or national identity inherent in a domain name. Cool URIs are human-readable—and humans are irrational.
The transcript of the Q&A session "Linked Open Data and the Lexicon" is available here.
Link this pageWould you like to put a link to this lecture on your homepage?
Go ahead! Copy the HTML snippet !