- From: Claus Stadler <cstadler@informatik.uni-leipzig.de>
- Date: Tue, 17 Mar 2020 16:44:45 +0100
- To: public-lod@w3.org
- Message-ID: <4605d071-03ae-7435-130d-b6dd7f1d2e72@informatik.uni-leipzig.de>
Hi Martynas, Thanks for the HTTP-in-RDF suggestion! I forgot to ask for what vocabularies exist for representing the online/offline state, and HTTP status codes might actually be the best choice. Also, I have another use case where we RDFize web server logs and on first glance the HTTP vocabulary seems to fit perfectly! Cheers, Claus On 17.03.20 16:19, Martynas Jusevičius wrote: > Hi, > > I think link checking is where the HTTP-in-RDF vocabulary can be useful: > https://www.w3.org/TR/HTTP-in-RDF10/ > > With response metadata in a triplestore, status codes could be easily aggregated with SPARQL. > > We have developed a simple prototype of an HTTP client (a la curl) which emits HTTP-in-RDF metadata: > https://github.com/AtomGraph/HTTP-in-RDF > > > Martynas > atomgraph.com <http://atomgraph.com> > > On Tue, 17 Mar 2020 at 16.07, Kingsley Idehen <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote: > > On 3/17/20 10:12 AM, Claus Stadler wrote: >> >> Hi all, >> >> >> Last week I got a list of endpoints from one colleague and it turned out that many were dead so I hacked up a little service check [1] with Github-Actions (and our own sparql-integrate tool[2]) . And then another colleague told my of the rather recent effort that happened here. >> >> >> Openlink's LODCloud_SPARQL_Endpoints.ttl [3] looks looks very good! >> >> >> What I can contribute is a proof-of-concept of a completely self-contained SPARQL-based service monitoring setup [1] where Github does all the work of service checking, where everyone can clone the repo, adjust the queries and get whatever RDF out what they use case(s) demand. Right now I only added online/offline checking, but in principle one can also just query the endpoints for features and emit service descriptions or query for dataset metrics and emit void. >> >> >> Of course there are resource limitations, Github only allows 1000 requests per hour, the workflow time is limited, and the virtual instances only have 2 CPUs. >> >> >> Cheers, >> >> Claus >> >> >> [1] https://github.com/SmartDataAnalytics/lodservatory/blob/master/latest-status.ttl >> >> [2] https://github.com/SmartDataAnalytics/SparqlIntegrate >> >> [3] https://github.com/OpenLinkSoftware/general-turtle-doc-collection/blob/master/LODCloud_SPARQL_Endpoints.ttl >> > > Hi Claus, > > > Great effort! > > > Kingsley > >> >> On 24.12.19 16:12, Kingsley Idehen wrote: >>> On 12/23/19 11:55 AM, Kingsley Idehen wrote: >>>> On 12/23/19 5:01 AM, Michel Dumontier wrote: >>>>> Hi Kingsley, >>>>> Is it correct that we should continue to make changes to the spreadsheet, or should we do do a pull request against the turtle file? >>>> >>>> >>>> Whichever works best for you :) >>>> >>>> >>>>> If the former, how often will you update the turtle document and the endpoint? >>>> >>>> >>>> We will update it frequently in response to edit contributions to either data source. >>>> >>>> Kingsley >>>> >>>>> m. >>>>> >>>>> On Fri, Dec 20, 2019 at 10:36 PM Kingsley Idehen <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote: >>>>> >>>>> On 12/18/19 2:31 PM, Kingsley Idehen wrote: >>>>>> On 9/17/19 6:10 PM, Kingsley Idehen wrote: >>>>>>> >>>>>>> Hi Everyone, >>>>>>> >>>>>>> As part of the LODCloud effort (starting in 2007), a number of SPARQL Endpoints emerged around the initial SPARQL endpoint provided by DBpedia. Today, that cloud has grown into the largest Knowledge Graph on earth (by far!) and continues to drive new frontiers related to Artificial Intelligence and Machine Learning. >>>>>>> >>>>>>> Having established itself as the preeminent global Knowledge Graph on earth, it is extremely important that we maintain an active list of SPARQL endpoints using practices that scale. Thus, we are providing a shared Google Spreadsheet for crowd-sourcing the maintenance of SPARQL endpoints that make up this important Knowledge Graph. >>>>>>> >>>>>>> Please contribute your SPARQL endpoint(s) to the spreadsheet. >>>>>>> >>>>>>> *Links* >>>>>>> >>>>>>> * SPARQL Endpoint Google Spreadsheet1 <https://community.openlinksw.com/t/open-invitation-for-contributions-to-an-up-to-date-list-of-query-service-endpoints-that-underlie-the-massive-lodcloud-knowledgegraph/1202> >>>>>>> * What is the LODCloud, and why is it important? <https://medium.com/virtuoso-blog/what-is-the-linked-open-data-cloud-and-why-is-it-important-1901a7cb7b1f> >>>>>>> >>>>>> >>>>>> Season's Greetings to all, >>>>>> >>>>>> This is a final call regarding contributions to the SPARQL Query Service Endpoint Description effort that we are seeding via a shared Google Spreadsheet [1]. >>>>>> >>>>>> The goal is to produce an RDF-Turtle document that describes these endpoints using terms from the SPARQL Service Description [2] and VoID [3] Ontologies. Naturally, the document will also be published using Linked Data principles. >>>>>> >>>>>> >>>>>> [1] https://docs.google.com/spreadsheets/d/15AXnxMgKyCvLPil_QeGC0DiXOP-Hu8Ln97fZ683ZQF0/edit#gid=0 >>>>>> >>>>>> [2] https://www.w3.org/ns/sparql-service-description >>>>>> >>>>>> [3] http://rdfs.org/ns/void# >>>>>> >>>>> >>>>> We've published an RDF-Turtle document that describes a collection of SPARQL Query Services Endpoints to our Github repository [1]. Naturally, content of said document has been deployed using Linked Data principles [2] and sponged by our URIBurner Service [3]. >>>>> >>>>> Enjoy! >>>>> >>>>> Links: >>>>> >>>>> [1] https://github.com/OpenLinkSoftware/general-turtle-doc-collection/blob/master/LODCloud_SPARQL_Endpoints.ttl -- Github >>>>> >>>>> [2] http://data.openlinksw.com/oplweb/sparql-endpoint134#this -- Example URI >>>>> >>>>> [3] http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fwww.openlinksw.com%2Fdata%2Fturtle%2Foplweb%2FLODCloud_SPARQL_Endpoints.ttl&distinct=1 -- About the SPARQL Query Service Endpoints >>>>> >>>>> -- >>>>> 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 >>>>> >>>>> >>>>> >>>>> -- >>>>> Michel Dumontier >>>>> Distinguished Professor of Data Science >>>>> Maastricht University >>>>> http://dumontierlab.com >>>> >>>> >>> >>> Hi Everyone, >>> >>> The URI of the Github repo associated with the SPARQL Query Service endpoint descriptions has been changed [1]. Thus, use the new repository for branch forks and pull requests. >>> >>> [1] https://github.com/OpenLinkSoftware/lod-cloud >>> >>> Happy Holidays! >>> >>> -- >>> 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 >>> >> -- >> Dipl. Inf. Claus Stadler >> Department of Computer Science, University of Leipzig >> Research Group:http://aksw.org/ >> Workpage & WebID:http://aksw.org/ClausStadler >> Phone: +49 341 97-32260 > > > -- > 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 > -- Dipl. Inf. Claus Stadler Department of Computer Science, University of Leipzig Research Group: http://aksw.org/ Workpage & WebID: http://aksw.org/ClausStadler Phone: +49 341 97-32260
Received on Tuesday, 17 March 2020 15:45:03 UTC