Hi Holger,
Basically none of the SPARQL queries work, only those related to the
ontology schema (T-box) concepts. For example:
SELECT *
WHERE {
?subject rdfs:subClassOf ?object .
} LIMIT 100
works, while:
SELECT *
WHERE {
?subject rdf:type geo-ont:Feature .
} LIMIT 100
SELECT *
WHERE {
?subject geo-ont:countryCode ?object .
} LIMIT 100
and similar queries don't. Also what I have noticed is that the
classgeo-ont:Codeshows some of its instances (473) in the "Classes view", when
there's
actually 692 instances in the repository.
However, the classes geo-ont:Class and geo-ont:Feature don't show any
instances. Keep in mind that the instances do show up when working with a
smaller geonames data repository.
This leads me to think, that perhaps something goes wrong when TBC tries to
build an initial cache? I've tried clearing caches, restarting both TBC and
sesame server numerous times, but to no avail.
Regards,
Tomas
On Friday, May 24, 2013 2:53:32 AM UTC+3, Holger Knublauch wrote:
>
> Hi Tomas,
>
> could you send us some example SPARQL queries that no longer work? Could
> it be that the instances don't show up because you are looking at a
> superclass of the actual rdf:type?
>
> Also note that TBC is doing some caching, so whenever you upload new data
> into a remote store, the local system may need to be refreshed (ideally
> restart).
>
> Thanks
> Holger
>
>
> On May 23, 2013, at 10:09 PM, Tomas.V wrote:
>
> Hello,
>
> I have loaded the full geonames RDF dump (
> http://www.geonames.org/ontology/documentation.html) into a sesame
> powered RDF store (Owlim).
> As a result, the store currently holds 123M+ triples. Unfortunately, I
> have noticed that TBC doesn't seem to work with such amount of triples
> when connected to the store though sesame connector. The Classes and
> Properties views get populated, however no instance data is being
> retrieved in the Instances view. A-box related SPARQL queries (through the
> Query Editor) bring zero results as well. There are no problems executing
> queries and working with the store in general through Sesame workbench,
> Jena API + ARQ, so this leads me to think that the issue is TBC related.
>
> Please note, that such behavior is present only when data store size
> increases significantly. TBC sesame connector works well with smaller data
> dumps.
> I have tested this separately with 4.7M triples from a partial geonames
> RDF dump.
>
> Any ideas on what might be the problem here?
>
> Regards,
> Tomas
>
> --
> -- You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include Enterprise
> Vocabulary Network (EVN), TopBraid Composer, TopBraid Live,
> TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
> To post to this group, send email to
> [email protected] <javascript:>
> To unsubscribe from this group, send email to
> [email protected] <javascript:>
> For more options, visit this group at
> http://groups.google.com/group/topbraid-users?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
