On 10/29/21 6:38 AM, Martynas Jusevičius wrote:
No response to this? How is the server supposed to know that http:// and https:// resources are the same? In RDF they are not.Another example, this time requesting https://: $ curl -L -OJ -H "Accept: text/turtle" https://dbpedia.org/resource/Copenhagen % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 153 100 153 0 0 725 0 --:--:-- --:--:-- --:--:-- 725 100 675k 100 675k 0 0 1139k 0 --:--:-- --:--:-- --:--:-- 3235k curl: Saved to filename 'sparql_2021-10-29_10-31-22Z.ttl' $ cat sparql_2021-10-29_10-31-22Z.ttl @prefix dbo: <http://dbpedia.org/ontology/> . @prefix dbr: <http://dbpedia.org/resource/> . dbr:Vivi_Bach dbo:birthPlace dbr:Copenhagen . ...
Hi Martynas, True, but why are you using https: when you can use http: ?Do you want the DBpedia DBMS to be littered with owl:sameAs relations for this reason when an RDF Agent can infer and apply such relations?
The issue is implicit vs explicit co-reference. Currently, DBpedia is taking the "implicit co-reference" world view, for practical purposes.
A possible solution could be injection of the owl:sameAs relations as part of the HTTP response payload. Ditto injection into various RDF docs returned by Virtuoso.
Kingsley
On Thu, Oct 7, 2021 at 11:20 AM Martynas Jusevičius <marty...@atomgraph.com> wrote:Hi, We have noticed a URI mismatch on DBPedia which breaks Linked Data clients. The server forces https:// URLs: $ curl -I -H "Accept: text/turtle" http://dbpedia.org/resource/Copenhagen HTTP/1.1 303 See Other Server: nginx/1.18.0 Date: Thu, 07 Oct 2021 09:11:29 GMT Content-Type: text/html Content-Length: 153 Connection: keep-alive Location: https://dbpedia.org/resource/Copenhagen Access-Control-Allow-Credentials: true Access-Control-Allow-Methods: HEAD, GET, POST, OPTIONS Access-Control-Allow-Headers: Depth,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Accept-Encoding But the returned RDF data contains http:// URIs: $ curl -o - https://dbpedia.org/data/Copenhagen.ttl @prefix dbo: <http://dbpedia.org/ontology/> . @prefix dbr: <http://dbpedia.org/resource/> . <http://dbpedia.org/resource/2011\u201312_West_Ham_United_F.C._season> dbo:wikiPageWikiLink dbr:Copenhagen . <http://dbpedia.org/resource/AEK_Athens_F.C._in_European_football> dbo:wikiPageWikiLink dbr:Copenhagen . dbr:Adform dbo:wikiPageWikiLink dbr:Copenhagen . dbr:Helena_Paparizou dbo:wikiPageWikiLink dbr:Copenhagen . dbr:MS_Jutlandia dbo:wikiPageWikiLink dbr:Copenhagen . ... Can you please align the URLs in the data so that the resources are actually self-describing? Thanks. Martynas atomgraph.com_______________________________________________ DBpedia-discussion mailing list DBpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ DBpedia-discussion mailing list DBpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
