Hi all
Thanks to Gerard for pushing officially Lexvo.org here. Since he mentioned
the redirection of lingvoj.org URIs for languages, I think good to provide
here a little details about the why and how's of this process as an example
of practice, hopefully good, possibly best :)
What should you do when you have published a data set and a couple of years
later discover that :
1. You don't have much bandwidth, or technical skills, or resources to
update and maintain it.
2. Meanwhile, some other data set has been published, with better quality
than your own.
3. You want to ensure backward compatibility, that is not break the
applications consuming your URIs.
From a social viewpoint, first step is to contact the administrator of the
other data set and the following conversation takes place
X: Hello Y, would you mind if I redirect my URIs at foo to you resources at
bar?
Y: Hello X, I've looked at you URIs and data set and think it makes sense.
What are your service load stats, to figure if my server can stand them?
X: Fair enough, please find attached my servers stats for last year. Can you
handle that?
Y: OK, no problem I can handle the extra charge
Then the technical part, reconfiguring the content negotiation. Let's take
an example.
GET html on http://www.lingvoj.org/lang/zh has a 303 to
http://www.lingvoj.org/lingvo/zh.html which has itself a regular html
redirection to http://www.lexvo.org/page/iso639-3/zho which is the html
rendition of http://lexvo.org/id/iso639-3/zho
GET rdf on the same resource redirects to
http://www.lingvoj.org/lingvo/zh.rdf where the following can be found
rdf:Description rdf:about=http://www.lingvoj.org/lingvo/zh.rdf;
dcterms:isReplacedBy rdf:resource=
http://www.lexvo.org/data/iso639-3/zho/
/rdf:Description
The former description living at this URI is superceded by the description
at http://www.lexvo.org/data/iso639-3/zho
lingvoj:Lingvo rdf:about=http://www.lingvoj.org/lang/zh;
rdfs:isDefinedBy rdf:resource=
http://www.lexvo.org/data/iso639-3/zho/
owl:sameAs rdf:resource=http://lexvo.org/id/iso639-3/zho/
/lingvoj:Lingvo
The resource described is defined as the same as its lexvo.org equivalent,
and the definition resource changed accordingly.
So a simple follow-your nose from the deprecated URIs and RDF files will
retrieve the current description.
Basically that's it. If this practice seems good from social and technical
viewpoint it could be a good idea to document it in a more formal way and
put it somewhare on the wiki. There has been a page set up on the wiki a
while ago about this issue, sorry can't find now the page address and who
set it up, and I can't access now to
http://community.linkeddata.org/MediaWiki/ for some reasons.
Looking forward for the feedback
Bernard
2010/7/5 Gerard de Melo gdem...@mpi-inf.mpg.de
Hi everyone,
We'd like to announce a major update of Lexvo.org [1], a site that brings
information about languages, words, characters, and other human language-
related entities to the LOD cloud. Lexvo.org adds a new perspective to the
Web of Data by exposing how everything in our world is connected in terms
of language, e.g. via words and names and their semantic relationships.
Lexvo.org first went live in 2008 just in time for that year's ISWC.
Recently, the site has undergone a major revamp, with plenty of help from
Bernard Vatant, who has decided to redirect lingvoj.org's language URIs to
the corresponding Lexvo.org ones.
At this point, the site is no longer considered to be in beta testing,
and we invite you to take a closer look. On the front page, you'll find
links to examples that will allow you get a feel for the type of
information being offered. We'd love to hear your comments.
Best,
Gerard
[1] http://www.lexvo.org/
--
Gerard de Melodem...@mpi-inf.mpg.de
Max Planck Institute for Informatics
http://www.mpi-inf.mpg.de/~gdemelo/http://www.mpi-inf.mpg.de/%7Egdemelo/
--
Bernard Vatant
Senior Consultant
Vocabulary Data Engineering
Tel: +33 (0) 971 488 459
Mail: bernard.vat...@mondeca.com
Mondeca
3, cité Nollez 75018 Paris France
Web:http://www.mondeca.com
Blog:http://mondeca.wordpress.com
