Re: Size a linked open data set

Dear Jean-Claude, I'm not sure exactly what you meant by the "number of distinct resources in a dataset". Is it "the total number of distinct subjects" including both IRIs and blank nodes? It seems your first query counts that. Your second query seems to count the number of triples in the

Re: Loupe - a tool for inspecting and exploring datasets

Hi John, Thanks! yes, we see the value in using Loupe with private SPARQL endpoints and we looking at possible models for using it with private SPARQL endpoints. We will update the thread with the details after ISWC conf. Best Regards, Nandana On Fri, Oct 9, 2015 at 12:45 PM, John Walker

Re: Loupe - a tool for inspecting and exploring datasets

transparent in ES. Overall, my experience with Elasticsearch is very positive. In addition, I use an in memory cache (Ehcache) mainly to optimize the results that are paged etc. Best Regards, Nandana > > Am 08.10.2015 um 18:09 schrieb Nandana Mihindukulasooriya: > >> Hi all, >&

Re: Loupe - a tool for inspecting and exploring datasets

Thanks a lot Kingsley / Ghislain for your feedback !! On Fri, Oct 9, 2015 at 10:41 AM, Ghislain Atemezing < auguste.atemez...@eurecom.fr> wrote: > > That's a glimpse of Loupe. We would like to know whether it useful to > your use cases so that we can keep improving it. It's still in its early >

Re: Loupe - a tool for inspecting and exploring datasets

Hi Pierre-Yves, On Fri, Oct 9, 2015 at 11:09 AM, Pierre-Yves Vandenbussche < py.vandenbuss...@gmail.com> wrote: > > very nice initiative. > Thanks! Is there any API, or dump to get access to your data? I would be very > interested to use the information of triple patterns. > At moment we don't

Re: Loupe - a tool for inspecting and exploring datasets

wrote: > Hi Nandana, > > I got several 500 errors when trying to use it, for example > http://loupe.linkeddata.es/loupe/dataset?dataset=DBpedia%20(English) > > Alvaro Graves-Fuenzalida, PhD > Web: http://graves.cl - Twitter: @alvarograves > > On Thu, Oct 8, 2015 at 9:

Discovering a query endpoint associated with a given Linked Data resource

Hi, Is there a standard or widely used way of discovering a query endpoint (SPARQL/LDF) associated with a given Linked Data resource? I know that a client can use the follow your nose and related link traversal approaches such as [1], but if I wonder if it is possible to have a hybrid approach

Re: Discovering a query endpoint associated with a given Linked Data resource

try to look in this folder location: .well-known/void And possibly find a void:sparqlEndpoint. But this would be too good to be true. Regards, Víctor El 26/08/2015 10:45, Nandana Mihindukulasooriya escribió: Hi, Is there a standard or widely used way of discovering a query

[Deadline Extension: 27 July 2015] 1st International Workshop on Linked Data Repair and Certification (ReCert 2015)

, 2015 (Extended) Acceptance Notification: August 10, 2015 Camera-ready Version: September 7, 2015 Workshop: October 7, 2015 -- Organizing Committee -- Nandana Mihindukulasooriya nmihi...@fi.upm.es Dr. Víctor Rodríguez Doncel vrod...@fi.upm.es

Re: How do you explore a SPARQL Endpoint?

May be not just looking at the classes and properties but looking at their frequencies using counts can give a better idea about what sort of data is exposed. If there is a Void information it certainly helps. Tools such as http://data.aalto.fi/visu also help. Similar approach described here [1] .

Re: Real-world concept URIs

Hi Pieter, If we still stick with URIs (as a name but not a locator) [1] but with a different scheme, say things or something, your solution will still work the same, right? There are already URN/DOI to URL resolvers [3], so similarly but rather than using a service, your URIs identifying real

Re: Real-world concept URIs

Hi Pieter, On Thu, Jul 17, 2014 at 7:36 PM, Pieter Colpaert pieter.colpa...@ugent.be wrote: Hi Nandana, Thank you a lot for your clear reply! On 2014-07-17 19:17, Nandana Mihindukulasooriya wrote: Hi Pieter, If we still stick with URIs (as a name but not a locator) [1

LDP4j is launched!

LDP4j (http://www.ldp4j.org/) is an open source Java-based framework for the development of read-write Linked Data applications based on the W3C Linked Data Platform (LDP) 1.0 specification. LDP4j is available under the Apache 2.0 licence. The LDP4j framework provides both client and server

Re: There's No Money in Linked Data

Hi, On Fri, Jun 7, 2013 at 11:10 AM, Andrea Splendiani andrea.splendi...@iscb.org wrote: I think the issue is not whether there is money or not in linked data, but: how much money is in linked data ? Lot of money has been injected by research funds, maybe governments and maybe even

Re: There's No Money in Linked Data

to be convinced. But I'm expressing some reflections that were actual comments of people, to which I didn't really know what to answer, except that they should think at linked-data like highways... best, Andrea Il giorno 07/giu/2013, alle ore 10:31, Nandana Mihindukulasooriya nandana@gmail.com