I am a bit confused. I was under the impression that a predicate had to be
a URI (not anon and not literal) node. This seems to be enforced by the
graph writing code but not by the graph code itself. Should not the graph
code thrown an exception when a non-URI node is used as a predicate? Or is
[
https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755680#comment-13755680
]
ASF subversion and git services commented on JENA-380:
--
Commit 1519250
[
https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755681#comment-13755681
]
Claude Warren commented on JENA-380:
I have been working on migrating the unit tests to
Hi Claude,
On 01/09/13 08:36, Claude Warren wrote:
I am a bit confused. I was under the impression that a predicate had to be
a URI (not anon and not literal) node. This seems to be enforced by the
graph writing code but not by the graph code itself. Should not the graph
code thrown an excepti
hmmm Then the FileGraph adds the extra constraint to its implementation
of Graph in that it can't accept the non-URI nodes in the predicate
position when transactions are in use as it writes the checkpoint file and
the writer won't accept a non-URI in the predicate. Perhaps this is a bug
in th
Does anyone have any comments on the note below? I added the notes to the
bug so that they could be tracked, but I am looking for feedback comments
or best practices. You assistance is appreciated.
On Sun, Sep 1, 2013 at 9:43 AM, Claude Warren (JIRA) wrote:
>
> [
> https://issues.apache.or
On 01/09/13 10:06, Dave Reynolds wrote:
Hi Claude,
On 01/09/13 08:36, Claude Warren wrote:
I am a bit confused. I was under the impression that a predicate had
to be
a URI (not anon and not literal) node. This seems to be enforced by the
graph writing code but not by the graph code itself. Sh
On 01/09/13 10:21, Claude Warren wrote:
hmmm Then the FileGraph adds the extra constraint to its implementation
of Graph in that it can't accept the non-URI nodes in the predicate
position when transactions are in use as it writes the checkpoint file and
the writer won't accept a non-URI in t
Perhaps we should add a flag to the graph Capabilities object to specify
whether or not the supports "Generalized RDF".
While on the subject of the Capabilities object, what does findContractSafe()
mean?
On Sun, Sep 1, 2013 at 10:45 AM, Andy Seaborne wrote:
> On 01/09/13 10:21, Claude Warren
On 01/09/13 10:56, Claude Warren wrote:
Perhaps we should add a flag to the graph Capabilities object to specify
whether or not the supports "Generalized RDF".
"Generalized RDF" is an end-to-end concept, not just a graph one.
Sometimes code might be using it internally, but for an app to use
It's hard to find many uses in the main code base of capabilities. I
can only find two uses in main/java at all:
* use of sizeAccurate() in the isomorphism code
* findSafeContract() in RDF/XML writing.
Otherwise it's all in the testing code.
Oddly, it does not seem to be reflected in the Mode
(weird error message from email earlier - this maybe a duplicate but is
shorter - sorry if it is a dup)
It's hard to find many uses in the main code base of capabilities. I
can only find two uses in main/java at all:
* use of sizeAccurate() in the isomorphism code
* findSafeContract() in RDF
"Lizard" is a clustered SPARQL system - it's been my August project. The
target is providing fault-tolerant operation; if any one machine fails
(e.g. hardware or software problem), then Lizard is able to continue
providing the SPARQL service.
Lizard assumes machine fail in a "fail-stop" manner
Hello
I want to access remote sparql endpoint throuth JENA API. My program and error
is below. I don't know how to deal with this problem.
Can you give me some advice? Thank you very very much !
Exception in thread "main" com.hp.hpl.jena.query.QueryException: Endpoint
returned Content-Type: tex
On 02/09/13 05:31, bocai wrote:
> Hello
Please ask questions like this on the jena-users list.
> I want to access remote sparql endpoint throuth JENA API. My program and
> error is below. I don't know how to deal with this problem.
> Can you give me some advice? Thank you very very much !
The e
15 matches
Mail list logo