About https://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432

Subject: https://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432Property: http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialObjecthttps://w3id.org/scholarlydata/ontology/conference-ontology.owl#InProceedingshttp://www.w3.org/2002/07/owl#Thinghttp://purl.org/spar/fabio/ProceedingsPaperhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationObjecthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Objecthttp://www.w3.org/2000/01/rdf-schema#ResourceProperty: http://www.w3.org/2000/01/rdf-schema#labelSPORTAL: Profiling the Content of Public SPARQL EndpointsProperty: http://swrc.ontoware.org/ontology#abstractAccess to hundreds of knowledge bases has been made available on the Web through public SPARQL endpoints. Unfortunately, few endpoints publish descriptions of their content (e.g., using VoID). It is thus unclear how agents can learn about the content of a given SPARQL endpoint or, relatedly, find SPARQL endpoints with content relevant to their needs. This research investigates the feasibility of a system that gathers information about public SPARQL endpoints by querying them directly about their own content. With the advent of SPARQL 1.1 and features such as aggregates, it is now possible to specify queries whose results would form a detailed profile of the content of the endpoint, comparable with a large subset of VoID. In theory it would thus be feasible to build a rich centralised catalogue describing the content indexed by individual endpoints by issuing them SPARQL (1.1) queries; this catalogue could then be searched and queried by agents looking for endpoints with content they are interested in. In practice, however, the coverage of the catalogue is bounded by the limitations of public endpoints themselves: some may not support SPARQL 1.1, some may return partial responses, some may throw exceptions for expensive aggregate queries, etc. The goal is thus twofold: (i) using VoID as a bar, to empirically investigate the extent to which public endpoints can describe their own content, and (ii) to build and analyse the capabilities of a best-effort online catalogue of current endpoints based on the (partial) results collected.Property: http://purl.org/dc/elements/1.1/creatorhttps://w3id.org/scholarlydata/person/ali-hasnainhttps://w3id.org/scholarlydata/person/qaiser-mehmoodhttps://w3id.org/scholarlydata/person/aidan-hoganhttps://w3id.org/scholarlydata/person/syeda-sana-e-zainabProperty: http://purl.org/dc/elements/1.1/subjectCatalogue Self-Descriptive Queries SPARQL SPORTAL (SPARQL Portal)Property: http://purl.org/dc/elements/1.1/titleSPORTAL: Profiling the Content of Public SPARQL EndpointsProperty: http://purl.org/ontology/bibo/authorListhttps://w3id.org/scholarlydata/authorlist/iswc-2019-journal-432Property: http://xmlns.com/foaf/0.1/makerhttps://w3id.org/scholarlydata/person/aidan-hoganhttps://w3id.org/scholarlydata/person/syeda-sana-e-zainabhttps://w3id.org/scholarlydata/person/qaiser-mehmoodhttps://w3id.org/scholarlydata/person/ali-hasnainProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#abstractAccess to hundreds of knowledge bases has been made available on the Web through public SPARQL endpoints. Unfortunately, few endpoints publish descriptions of their content (e.g., using VoID). It is thus unclear how agents can learn about the content of a given SPARQL endpoint or, relatedly, find SPARQL endpoints with content relevant to their needs. This research investigates the feasibility of a system that gathers information about public SPARQL endpoints by querying them directly about their own content. With the advent of SPARQL 1.1 and features such as aggregates, it is now possible to specify queries whose results would form a detailed profile of the content of the endpoint, comparable with a large subset of VoID. In theory it would thus be feasible to build a rich centralised catalogue describing the content indexed by individual endpoints by issuing them SPARQL (1.1) queries; this catalogue could then be searched and queried by agents looking for endpoints with content they are interested in. In practice, however, the coverage of the catalogue is bounded by the limitations of public endpoints themselves: some may not support SPARQL 1.1, some may return partial responses, some may throw exceptions for expensive aggregate queries, etc. The goal is thus twofold: (i) using VoID as a bar, to empirically investigate the extent to which public endpoints can describe their own content, and (ii) to build and analyse the capabilities of a best-effort online catalogue of current endpoints based on the (partial) results collected.Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasAuthorListhttps://w3id.org/scholarlydata/authorlist/iswc-2019-journal-432Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#isPartOfhttps://w3id.org/scholarlydata/conference/iswc/2019/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#keywordCatalogue Self-Descriptive Queries SPARQL SPORTAL (SPARQL Portal)Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#titleSPORTAL: Profiling the Content of Public SPARQL EndpointsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#relatesToEventhttps://w3id.org/scholarlydata/talk/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/conference/iswc/2019/proceedingsProperty: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#hasParthttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/role-during-event/iswc2019-author-aidan-hogan-iswc-2019-journal-432Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#withDocumenthttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/talk/iswc-2019-journal-432Property: https://w3id.org/scholarlydata/ontology/conference-ontology.owl#isEventRelatedTohttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/person/ali-hasnainProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/person/aidan-hoganProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/person/qaiser-mehmoodProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432
Subject: https://w3id.org/scholarlydata/person/syeda-sana-e-zainabProperty: http://xmlns.com/foaf/0.1/madehttps://w3id.org/scholarlydata/inproceedings/iswc-2019-journal-432