Hi, On 20. Sep. 2011, at 18:09, Dimitris Kontokostas wrote: > in the new 3.7 release some language editions (except English) were > extracted localized with the use of IRIs instead of URIs [1].
Thanks, but the link you provide doesn't mention "IRI" once. I agree that it might be useful to have http://de.dbpedia.org/resource/Gerhard_Schr%C3%B6der and http://dbpedia.org/resource/Gerhard_Schr%C3%B6der which are "owl:sameAs"ed, but i'm concerned about the other IRIs that we now have: http://dbpedia.org/resource/Gerhard_Schröder and http://de.dbpedia.org/resource/Gerhard_Schröder . In terms of RDF the IRI http://dbpedia.org/resource/Gerhard_Schr%C3%B6der is not equivalent to the IRI http://dbpedia.org/resource/Gerhard_Schröder . Also try requesting http://dbpedia.org/resource/Gerhard_Schröder on http://dbpedia.org/sparql and you'll see that you don't get results, while you get results for http://dbpedia.org/resource/Gerhard_Schr%C3%B6der . That being said i just want to know the reason for introducing this ambiguity, which will cause more requests, more potential for errors, etc. > The .nt issue you are referring to is known and relates to a "bug" of > the extraction framework that has the .nt extension hardcoded. If you > change the extension in turtle format then all the files will be > valid. Well, it's not hard to rename all those files and as i'm not the only one who ran into this problem, i'd suggest to rename them on the server side. > About the SPARQL query format you can use the IRI format too. See [2] > for some examples The el.dbpedia.org SPARQL endpoint seems to be down. Also be aware that there will be quite a lot of people who aren't able to type those requests. I know this shouldn't be a key point, as "in the near future intelligent agents will construct all those requests for us", but in the meantime it is a problem. I don't have those keys on my keyboard :-/ Jörn > Cheers, > Dimitris > > [1] > http://blog.dbpedia.org/2011/09/11/dbpedia-37-released-including-15-localized-editions/ > [2] http://wiki.el.dbpedia.org/en/examples/sparql > > On Tue, Sep 20, 2011 at 6:49 PM, Jörn Hees <[email protected]> wrote: >> Hi, >> >> I get a couple of question related to the newest dumps as i published a >> howto for setting up a local DBpedia mirror quite some time ago on my blog. >> One I can't answer is related to the encoding of URIs or IRIs in the new >> dump files: >> >> >> From the DBpedia 3.6 dump: de/labels_de.nt.bz2 and en/labels_en.nt.bz2 >>> <http://dbpedia.org/resource/Gerhard_Schr%C3%B6der> >>> <http://www.w3.org/2000/01/rdf-schema#label> "Gerhard Schr\u00F6der"@en . >> >> From the DBpedia 3.7 (no i18n) >> 3.7/data/HardDrive2/DBpedia/3.7/data-enUris-compressed/en/labels_en.nt.bz2 >> (btw. maybe someone could recreate the provided all_languages.tar not to >> include the absolute path on your server?): >>> <http://dbpedia.org/resource/Gerhard_Schr%C3%B6der> >>> <http://www.w3.org/2000/01/rdf-schema#label> "Gerhard Schr\u00F6der"@en . >> >> >> From the DBpedia 3.7 (no i18n) >> 3.7/data/HardDrive2/DBpedia/3.7/data-enUris-compressed/de/labels_de.nt.bz2 >>> <http://dbpedia.org/resource/Gerhard_Schröder> >>> <http://www.w3.org/2000/01/rdf-schema#label> "Gerhard Schr\u00F6der"@de . >> >> From the DBpedia 3.7 (i18n) 3.7-i18n/all_languages-i18n/en/labels_en.nt.bz2 >>> <http://dbpedia.org/resource/Gerhard_Schr%C3%B6der> >>> <http://www.w3.org/2000/01/rdf-schema#label> "Gerhard Schr\u00F6der"@en . >> >> From the DBpedia 3.7 (i18n) 3.7-i18n/all_languages-i18n/de/labels_de.nt.bz2 >>> <http://de.dbpedia.org/resource/Gerhard_Schröder> >>> <http://www.w3.org/2000/01/rdf-schema#label> "Gerhard Schr\u00F6der"@de . >> >> >> Are the 3.7 .nt files with non ASCII chars in the URIs valid ntriples files? >> http://www.w3.org/TR/rdf-testcases/#ntriples says quite clearly: >>> The Internet media type / MIME type of N-Triples is text/plain and the >>> character encoding is 7-bit US-ASCII. >> >> and there's no ö or ō in ASCII (the .nt files actually seem to be UTF-8 >> encoded). >> >> >> Aside from finding this inconsistent and inconvenient I ask myself: is it >> planned to use IRIs where we used URIs before? >> >> Another question arising from this: >> Will DBpedia now use the IRI >> <http://de.dbpedia.org/resource/Gerhard_Schröder>? If so how can i request >> it in sparql? >> >> select * >> where { >> <http://dbpedia.org/resource/Gerhard_Schr%C3%B6der> ?p ?o. >> } >> >> or >> >> select * >> where { >> <http://dbpedia.org/resource/Gerhard_Schr\u00F6der> ?p ?o. >> } >> >> or >> >> select * >> where { >> <http://dbpedia.org/resource/Gerhard_Schröder> ?p ?o. >> } >> >> >> cheers, >> Jörn >> >> >> ------------------------------------------------------------------------------ >> 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-d2dcopy1 >> _______________________________________________ >> Dbpedia-discussion mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion >> > > ------------------------------------------------------------------------------ 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-d2dcopy2 _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
