Correction: LODCloud SPARQL Endpoints Spreadsheet

On 3/17/20 5:10 PM, Kingsley Idehen wrote:
>> I know that the naming is arbitrary, but in practice it leads to the
>> issue e.g. inverse functional properties and reasoners are needed to
>> consolidate the data, where maybe a best practice / convention would
>> ease things.
> By having different URIs for the same endpoints across datasets we end
> up requiring the use of IFP semantics for identity resolution, thus we
> still need an IFP relation in your dataset bearing in mind that
> sd:endpoint has range owl:DataTypeProperty  -- which makes it unsuitable
> for IFP reasoning based identity reconciliation.
>
> Kingsley
>
Hi Claus,

sd:endpoint is an IFP, so we are set [1].

I need to fix the literal object assignments in our dataset.

[1]
https://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fwww.w3.org%2Fns%2Fsparql-service-description%23endpoint&graph=http%3A%2F%2Fwww.w3.org%2Fns%2Fsparql-service-description&distinct=1
-- sd:endpoint description


-- 
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