http;//d2rq.org/ is dynamic and translates at query time.
On 08/01/16 16:33, Benedikt Tröster wrote:
Hello everyone,
I know Jena is not exactly made for OBDA, but I guess you could achive
sth. that is very close to what I want to do:
I have an ontology for a process inside the medical domain. T
To make a connection here ...
SHACL [*] seems to have a similar issue; it needs to apply shape
constraints to resources which are potentially bnode-subject structures.
[*]
http://www.w3.org/TR/shacl/
On 06/01/16 16:50, Paul Houle wrote:
This is a simple scenario, I can accomplish the specif
Benedikt,
There are a number of ways to achieve this. It is possible to create an
instance of Graph. Assuming you only want to read (not write) the
documents via the Jena interface this would be fairly straight forward as
you could extend the GraphBase class (org.apache.jena.graph.impl.GraphBase
You can use the simpler
tdbloader --loc DIRECTORY files
where DIRECTORY is the database location.
tdbloader only works on a complete TDB datasets so while you can pass
the assembler in as Adam and Osma say, you can also load
(all tdbloader is going to do is unpick the assembler built de
I am new to Ontop but I think it is suitable here in this scenario and you
can then use owl API implemented as maven.
Best regards
On Fri, Jan 8, 2016 at 4:33 PM, Benedikt Tröster <
troes...@stud.uni-heidelberg.de> wrote:
> Hello everyone,
>
> I know Jena is not exactly made for OBDA, but I gues
Hello everyone,
I know Jena is not exactly made for OBDA, but I guess you could achive
sth. that is very close to what I want to do:
I have an ontology for a process inside the medical domain. The idea is
to use the ontology and query for the instances of data (which are
located inside doc, xls fi
Dear All
(Not sure if this is really an @dev or @users question)
When Fuseki handles a query (or update), is that query
(or update) handled by a single thread or might it
be handled by multiple threads over the lifetime of
the query (or update)?
I ask because
* we have a TextDocProducer implem
Blank nodes are local to the graph. Why don't you relabel them as URIs
and the problem should go away? (if I understood your use case
correctly)
On Wed, Jan 6, 2016 at 5:50 PM, Paul Houle wrote:
> This is a simple scenario, I can accomplish the specific thing I am trying
> to di by other means,
Dear Sandor,
You can use the same .ttl file that you used for the Fuseki database and
text index configuration, i.e. the one documented here:
https://github.com/NatLibFi/Skosmos/wiki/InstallFusekiJenaText#configuration
-Osma
On 08/01/16 16:12, Sandor Kopacsi wrote:
Dear Support List,
We are
Jena Assemblers are recipes (written in RDF) for constructing RDF stores:
https://jena.apache.org/documentation/assembler/index.html
https://jena.apache.org/documentation/assembler/assembler-howto.html
You will use a set of RDF vocabularies to write RDF describing how you want TDB
to ingest your
Dear Support List,
We are at the University of Vienna developing an archiving system where
we are going to use Jena-Fuseki (and a tool, called Skosmos based on
that) for storing and displaying data sets for classifications. We had
problems with uploading the RDF file to Fuseki through the memor
This is a simple scenario, I can accomplish the specific thing I am trying
to di by other means, but if I can get this to work it leads to a strategy
inspired by SPIN, I'm showing it though because it is a simple and clear
example.
I have two graphs,
G1:
[] a :DatasetArtifact ;
:name e:tdb
12 matches
Mail list logo