Re: [DBpedia-discussion] DBpedia's Linked Data is broken

[Martynas Jusevičius]

Done: https://github.com/dbpedia/extraction-framework/issues/718

On Fri, Oct 29, 2021 at 4:27 PM Sebastian Hellmann
 wrote:
>
> Dear Martynas,
> please resubmit this to the issue tracker in the hosting template:
>
> https://github.com/dbpedia/extraction-framework/issues/new/choose
>
> Normally, the hosting category gets handled faster (days/weeks) than data 
> issues (weeks/months).
> LG,
> Sebastian
>
> BlueMail for Android herunterladen
> Am 29. Okt. 2021, um 13:06, "Martynas Jusevičius"  
> schrieb:
>>
>> 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   TimeTime Time  
>> Current
>>  Dload  Upload   Total   SpentLeft  Speed
>>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- >> 0
>> 100   153  100   1530 0725  0 --:--:-- --:--:-- --:--:--   
>> 725
>> 100  675k  100  675k0 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: .
>> @prefix dbr: .
>> dbr:Vivi_Bach   dbo:birthPlace  dbr:Copenhagen .
>> ...
>>
>> On Thu, Oct 7, 2021 at 11:20 AM Martynas Jusevičius
>>  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: .
>>>  @prefix dbr: .
>>>  
>>>   dbo:wikiPageWikiLinkdbr:Copenhagen .
>>>  
>>>   dbo:wikiPageWikiLinkdbr:Copenhagen .
>>>  dbr:Adform  dbo:wikiPageWikiLinkdbr:Copenhagen .
>>>  dbr:Helena_Paparizoudbo:wikiPageWikiLinkdbr:Copenhagen .
>>>  dbr:MS_Jutlandiadbo:wikiPageWikiLinkdbr: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
>>


___
DBpedia-discussion mailing list
DBpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Re: [DBpedia-discussion] DBpedia's Linked Data is broken

[Martynas Jusevičius]

Hi Kingsley,

It’s the server that forces a http:// -> https:// redirect — see my
original email.

Martynas

On Fri, 29 Oct 2021 at 16.51, Kingsley Idehen via DBpedia-discussion <
dbpedia-discussion@lists.sourceforge.net> wrote:

> 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   TimeTime Time
> Current
> >   Dload  Upload   Total   SpentLeft
> Speed
> >0 00 00 0  0  0 --:--:-- --:--:--
> --:--:-- 0
> > 100   153  100   1530 0725  0 --:--:-- --:--:--
> --:--:--   725
> > 100  675k  100  675k0 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: .
> > @prefix dbr: .
> > 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
> >  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: .
> >> @prefix dbr: .
> >> 
> >>   dbo:wikiPageWikiLinkdbr:Copenhagen .
> >> 
> >>   dbo:wikiPageWikiLinkdbr:Copenhagen .
> >> dbr:Adform  dbo:wikiPageWikiLinkdbr:Copenhagen .
> >> dbr:Helena_Paparizoudbo:wikiPageWikiLinkdbr:Copenhagen .
> >> dbr:MS_Jutlandiadbo:wikiPageWikiLinkdbr: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
>
> ___
> DBpedia-discussion mailing list
> DBpedia-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
___
DBpedia-discussion mailing list

Re: [DBpedia-discussion] DBpedia's Linked Data is broken

[Kingsley Idehen via DBpedia-discussion]

On 10/29/21 10:54 AM, Martynas Jusevičius wrote:

Hi Kingsley,

It’s the server that forces a http:// -> https:// redirect — see my 
original email.


Martynas



Yes, partly due to Google's "force HTTPS on the world" approach.

Anyway, I think owl:sameAs relation injection is the best way to address 
this matter.


If an http: request comes in, don't redirect, just inject https: based 
owl:sameAs relation objects via HTTP response; ditto in any generated 
RDF docs.


Repeat for https:, by inverting inverting the roles of http: and https:


Kingsley



On Fri, 29 Oct 2021 at 16.51, Kingsley Idehen via DBpedia-discussion 
 wrote:


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:     .
> @prefix dbr:     .
> 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
>  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:     .
>> @prefix dbr:     .
>>
>
>>   dbo:wikiPageWikiLink    dbr:Copenhagen .
>> 
>>   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: 

Re: [DBpedia-discussion] DBpedia's Linked Data is broken

[Kingsley Idehen via DBpedia-discussion]

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   TimeTime Time  Current
  Dload  Upload   Total   SpentLeft  Speed
   0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100   153  100   1530 0725  0 --:--:-- --:--:-- --:--:--   725
100  675k  100  675k0 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: .
@prefix dbr: .
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
 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: .
@prefix dbr: .

  dbo:wikiPageWikiLinkdbr:Copenhagen .

  dbo:wikiPageWikiLinkdbr:Copenhagen .
dbr:Adform  dbo:wikiPageWikiLinkdbr:Copenhagen .
dbr:Helena_Paparizoudbo:wikiPageWikiLinkdbr:Copenhagen .
dbr:MS_Jutlandiadbo:wikiPageWikiLinkdbr: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

Re: [DBpedia-discussion] DBpedia's Linked Data is broken

[Sebastian Hellmann]

Dear Martynas,
please resubmit this to the issue tracker in the hosting template:

https://github.com/dbpedia/extraction-framework/issues/new/choose

Normally, the hosting category gets handled faster (days/weeks) than data 
issues (weeks/months).
LG,
Sebastian

⁣BlueMail for Android herunterladen ​

Am 29. Okt. 2021, 13:06, um 13:06, "Martynas Jusevičius" 
 schrieb:
>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   TimeTime Time
>Current
>   Dload  Upload   Total   SpentLeft  Speed
>0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
>   0
>100   153  100   1530 0725  0 --:--:-- --:--:--
>--:--:--   725
>100  675k  100  675k0 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: .
>@prefix dbr: .
>dbr:Vivi_Bach   dbo:birthPlace  dbr:Copenhagen .
>...
>
>On Thu, Oct 7, 2021 at 11:20 AM Martynas Jusevičius
> 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: .
>> @prefix dbr: .
>>
>
>>  dbo:wikiPageWikiLinkdbr:Copenhagen .
>> 
>>  dbo:wikiPageWikiLinkdbr:Copenhagen .
>> dbr:Adform  dbo:wikiPageWikiLinkdbr:Copenhagen .
>> dbr:Helena_Paparizoudbo:wikiPageWikiLinkdbr:Copenhagen .
>> dbr:MS_Jutlandiadbo:wikiPageWikiLinkdbr: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
___
DBpedia-discussion mailing list
DBpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Re: [DBpedia-discussion] DBpedia's Linked Data is broken

[Martynas Jusevičius]

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   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100   153  100   1530 0725  0 --:--:-- --:--:-- --:--:--   725
100  675k  100  675k0 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: .
@prefix dbr: .
dbr:Vivi_Bach   dbo:birthPlace  dbr:Copenhagen .
...

On Thu, Oct 7, 2021 at 11:20 AM Martynas Jusevičius
 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: .
> @prefix dbr: .
> 
>  dbo:wikiPageWikiLinkdbr:Copenhagen .
> 
>  dbo:wikiPageWikiLinkdbr:Copenhagen .
> dbr:Adform  dbo:wikiPageWikiLinkdbr:Copenhagen .
> dbr:Helena_Paparizoudbo:wikiPageWikiLinkdbr:Copenhagen .
> dbr:MS_Jutlandiadbo:wikiPageWikiLinkdbr: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

[DBpedia-discussion] DBpedia's Linked Data is broken

[Martynas Jusevičius]

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: .
@prefix dbr: .

 dbo:wikiPageWikiLinkdbr:Copenhagen .

 dbo:wikiPageWikiLinkdbr:Copenhagen .
dbr:Adform  dbo:wikiPageWikiLinkdbr:Copenhagen .
dbr:Helena_Paparizoudbo:wikiPageWikiLinkdbr:Copenhagen .
dbr:MS_Jutlandiadbo:wikiPageWikiLinkdbr: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