- From: Pierre-Yves Vandenbussche <py.vandenbussche@gmail.com>
- Date: Wed, 21 Aug 2013 09:18:08 +0100
- To: Barry Norton <barry.norton@ontotext.com>
- Cc: Bernard Vatant <bernard.vatant@mondeca.com>, Linking Open Data <public-lod@w3.org>
- Message-ID: <CA+D1OakxrMA+1ybYWYh6Fzwg+Ua9L5AG95a1bWokT1dUrz=B=w@mail.gmail.com>
Hi Barry,
Thanks for your feedback, I now know what to do during the coming week end
:)
-Yes I could switch to a SPARQL Endpoint with inference so you could find
all the properties in a straight forward query. Will evaluate the impact on
the rest of the LOV services.
-I was planning for a long time now to set up an index on top of the stored
vocabularies so LOV could support autocomplete function like foaf:P ->
foaf:Person or http://purl.org/dc/elements/1.1/des ->
http://purl.org/dc/elements/1.1/description. Is this the need you
expressed?
Best regards,
Pierre-Yves.
Pierre-Yves Vandenbussche.
On Tue, Aug 20, 2013 at 6:23 PM, Barry Norton <barry.norton@ontotext.com>wrote:
>
> Thanks, Bernard.
>
> I get ~5000 instances of rdf:Property (and 1643 of rdfs:Class - and oddly
> 5 instances of rdfs:Property), but more than three times as many for:
>
> SELECT (COUNT(?property) AS ?properties)
> {
> SELECT DISTINCT ?property
> WHERE{
> {?property rdfs:domain ?domain}
> UNION
> {?property rdfs:range ?range}
> UNION
> {?property rdfs:subPropertyOf ?super}
> UNION
> {?sub rdfs:subPropertyOf ?property}
> }
> }
>
> I'm guessing, therefore, no inference in this store?
>
> Since OWL-implied properties would require a much more sophisticated
> query, is it possible to get the dataset and re-index this with inference?
>
> Barry
>
>
>
>
>
> On 20/08/2013 18:02, Bernard Vatant wrote:
>
> Hello Barry
>
>
> I had a reminder today that I never answered the question below, and I am very late indeed !
>
>
> Properties and classes of all vocabularies in LOV are aggregated in a triple store
>
>
> of which SPARQL endpoint is at http://lov.okfn.org/endpoint/lov_aggregator
>
> This is quite "raw data" but you should find everything you need in there.
>
>
>
> Otherwise can also use the new API http://lov.okfn.org/dataset/lov/api/v1/vocabs
>
> which for each vocabulary provides the prefix and link to the last version stored.
>
>
>
>
> Hope that helps
>
>
> Bernard
>
> From: Barry Norton <barry.norton@ontotext.com <barry.norton@ontotext.com?Subject=Re%3A%20YASGUI%3A%20Web-based%20SPARQL%20client%20with%20bells%20%FFn%20wistles&In-Reply-To=%3C51D7F122.5060407%40ontotext.com%3E&References=%3C51D7F122.5060407%40ontotext.com%3E>>Date: Sat, 06 Jul 2013 11:27:46 +0100
>
> Bernard, does LOV keep a cache of properties and classes?
>
> I'd really like to see resource auto-completion in Web-based tools like
> YASGUI, but a cache is clearly needed for the to be feasible.
>
> Barry
>
>
>
>
Received on Wednesday, 21 August 2013 08:18:55 UTC