Hello, On 24.06.2011 14:52, Thomas Steiner wrote: > [Limiting CC list] > >> Quick question: on the basis of point 6, will resources in the main >> http://dbpedia.org/ namespace soon reflect the latest changes from >> DBpedia Live? > ...also interested in this question. On a related note, will there be > http://live.dbpedia.org/{resource|page}/{Thing} pages as an > intermediate solution?
That's a valid and good question, which is, however, not that easy to answer. For now, we went the simple route and do not serve DBpedia Live data as Linked Data, although I see that it would be desirable to have it. If we serve it from http://live.dbpedia.org/{resource|page}/{Thing} that implies changing the resource URIs accordingly (prefix http://live.dbpedia.org/...). We could do that and add links to the static URIs. A question would be whether it is desirable to have two URIs for exactly the same thing from exactly the same source? If we would decide to have different URIs for the static and live version, then a related question is whether it is better to use http://dbpedia.org/resource/... and http://live.dbpedia.org/resource/ - or - http://dbpedia.org/resource/... and http://static.dbpedia.org/resource/ The latter requires more changes on our (OpenLink, FUB, AKSW) side, but might be more plausible in the mid/long term. Another option would be to use a single URI and a content negotiation mechanism, which can deal with time (http://events.linkeddata.org/ldow2011/papers/ldow2011-paper02-coppens.pdf), which would however introduce additional complexity. Input/opinions on those issues are welcome (if there is a best practice for this case, please let us know). Kind regards, Jens -- Dr. Jens Lehmann AKSW/MOLE Group, Department of Computer Science, University of Leipzig Homepage: http://www.jens-lehmann.org GPG Key: http://jens-lehmann.org/jens_lehmann.asc ------------------------------------------------------------------------------ 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
