Dear Jens, DBpedians, > Input/opinions on those issues are welcome (if there is a best practice > for this case, please let us know).
Treating http://live.dbpedia.org/{resource|page}/{Thing} as a normal Web page (all Semantic Web / Linked Data foo aside) that has a temporarily more up-to-date version of http://dbpedia.org/{resource|page}/{Thing}; however, where everyone is encouraged to use http://dbpedia.org/{resource|page}/{Thing} for the long-term, the current best practice (from a search engine's point of view) is to place a so-called canonical link [1] on http://live.dbpedia.org/{resource|page}/{Thing} that points to http://dbpedia.org/{resource|page}/{Thing}. This can hapen either via a meta tag in the head section of the page, or (I guess in this case the preferred solution) via a Link header in the HTTP header. What do you think? Best, Tom [1] http://www.google.com/support/webmasters/bin/answer.py?answer=139394 -- Thomas Steiner, Research Scientist, Google Inc. http://blog.tomayac.com, http://twitter.com/tomayac ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
