On 7/6/11 1:35 PM, Jens Lehmann wrote: > We had quite some internal discussions and decided to use the VAD for > now. Mohamed installed it, so there is now Linked Data for DBpedia Live: > http://live.dbpedia.org/resource/Dresden > (Whether we will keep using this URL scheme in the future still needs to > be decided.)
Great! Note, the URI style above is just an indirection to the canonical URI. To see what I mean, execute the following via SPARQL endpoint: 1. describe <http://live.dbpedia.org/resource/Dresden> 2. describe <http://dbpedia.org/resource/Dresden> . You only get data for #2. Thus, the solution is simply delivering an indirection via HTTP level (typically for page readers) while keeping the actual DBpedia canonical URI and the data its delivers from this instance intact. If a service seeks to mesh data from both the static and live dbpedia instances (at least for now) this is where SPARQL-FED or an owl:sameAs and resulting inference based union expansion would come into play, as options. -- Regards, Kingsley Idehen President& CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
