[
https://issues.apache.org/jira/browse/JENA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-599.
Resolution: Not A Problem
RIOT validation logs RDF XML Literal as invalid
[
https://issues.apache.org/jira/browse/JENA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-599:
--
Assignee: Andy Seaborne
RIOT validation logs RDF XML Literal as invalid
On 14/11/13 20:55, Nogales Moyano Alberto wrote:
Dear all I am working with various ontologies some of them are in
.owl and other .rdf. I have no problem with .owl files but when
I try to load .rdf file I have errors. Here is my code for .owl,
maybe the problems is with the model.
OntModel
Dear all I am working with various ontologies some of them are in .owl and
other .rdf. I have no problem with .owl files but when I try to load .rdf file
I have errors. Here is my code for .owl, maybe the problems is with the model.
OntModel model = ModelFactory.createOntologyModel
I need to fix the update never.
I will release the junit-contract stuff soon, so we can remove the
dependency.
However, the new-tests only cover the core functionality currently. I
still need to extend it to the other packages.
On Mon, Nov 4, 2013 at 11:22 PM, Andy Seaborne a...@apache.org
On 04/11/13 21:57, cla...@apache.org wrote:
+repository
+idsnapshot-repository-xenei-org/id
+nameXenei Snapshot Repository/name
+
urlhttps://oss.sonatype.org/content/repositories/snapshots//url
+layoutdefault/layout
+releases
+
Original Message
Subject: early information on W3C RDF WG RDF 1.1 entailment
implementation reporting
Date: Fri, 1 Nov 2013 18:44:30 +
From: Patel-Schneider, Peter peter.patel-schnei...@nuance.com
To: Undisclosed recipients pfpschnei...@gmail.com
Greetings (and apologies
of the DB). I would
think a migration utility would be able to convert a database much faster
Simon
From:
Andy Seaborne a...@apache.org
To:
dev@jena.apache.org,
Date:
10/14/2013 10:41 AM
Subject:
Re: RDF 1.1 -- changes to plain literals
On 14/10/13 09:11, Rob Vesse wrote:
Andy
Thanks
has the same issue and I've seen
recently that Sesame was also affected by this. Therefore I think we need
to be clear about the need for this change in usage.
My feeling is we should make this a configurable behavior, the default
going forward should be RDF 1.1 but it would be nice if users
== Summary
This email covers the changes in RDF 1.1 around plain literals. In RDF
1.1, all literals have a datatype.
* simple literals have datatype xsd:string.
* literals with a language tag have a datatype rdf:langString.
This change may have some impact on databases.
== RDF 1.1
Andy Seaborne created JENA-548:
--
Summary: Add file extension .owl as implying RDF/XML.
Key: JENA-548
URL: https://issues.apache.org/jira/browse/JENA-548
Project: Apache Jena
Issue Type: Bug
from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1526218 ]
JENA-548
Add file extension .owl as implying RDF/XML.
Key: JENA-548
URL: https://issues.apache.org/jira/browse/JENA-548
://builds.apache.org/job/Jena_Development_Test/965/])
JENA-548 (andy: rev 1526218)
* /jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/RDFLanguages.java
Add file extension .owl as implying RDF/XML.
Key: JENA-548
:
-
* xsd:String and plain-literals without a language tag will be the same RDF
literal.
Output should be in the (old) plain literal, no language tag form.
Affects Node and writers.
May affect persistent data.
*Application visible, *
* The datatype of a literal with language tag is defined
:
-
* xsd:String and plain-literals without a language tag will be the same RDF
literal.
Output should be in the (old) plain literal, no language tag form.
Affects Node and writers.
May affect persistent data.
*Application visible*
* The datatype of a literal with language tag is defined
Hi,
On 09/09/13 23:25, c...@info-cast.com wrote:
Hi,
I'm considering the Jena Rules as a rule-based programming model
where rules are being discovered and accumulated to grow tens of
thousand, while the fact for inferring new info is only a few
RDF statements. In this case, the rule engine may
.
Best
Chan
Hi,
On 09/09/13 23:25, c...@info-cast.com wrote:
Hi,
I'm considering the Jena Rules as a rule-based programming model
where rules are being discovered and accumulated to grow tens of
thousand, while the fact for inferring new info is only a few
RDF statements. In this case
Hi,
I'm considering the Jena Rules as a rule-based programming model
where rules are being discovered and accumulated to grow tens of
thousand, while the fact for inferring new info is only a few
RDF statements. In this case, the rule engine may have to check
each and every rule for the fact
[
https://issues.apache.org/jira/browse/JENA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-521.
--
IO_Jena.resetJena() does not reset RDF/XML
from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1516942 ]
JENA-520 and JENA-521
IO_Jena.resetJena() does not reset RDF/XML
---
Key: JENA-521
URL: https://issues.apache.org/jira
IO_Jena.resetJena() does not reset RDF/XML
---
Key: JENA-521
URL: https://issues.apache.org/jira/browse/JENA-521
Project: Apache Jena
Issue Type: Bug
Components: RIOT
Affects Versions: Jena 2.10.1
/java/org/apache/jena/riot/system/TS_RiotSystem.java
*
/jena/trunk/jena-arq/src/test/java/org/apache/jena/riot/system/TestIO_JenaReaders.java
*
/jena/trunk/jena-arq/src/test/java/org/apache/jena/riot/system/TestIO_JenaWriters.java
IO_Jena.resetJena() does not reset RDF/XML
/riot/system/TestIO_JenaWriters.java
IO_Jena.resetJena() does not reset RDF/XML
---
Key: JENA-521
URL: https://issues.apache.org/jira/browse/JENA-521
Project: Apache Jena
Issue Type
Stian Soiland-Reyes created JENA-521:
Summary: IO_Jena.resetJena() does not reset RDF/XML
Key: JENA-521
URL: https://issues.apache.org/jira/browse/JENA-521
Project: Apache Jena
Issue
a resource - IMHO it should be allowed that the
server limits changes to this addressed resource. (the illustrative
example in the doc modifies two resources)
It depends what the resource identifies, the HTTP resource could easily be
a SPARQL Graph store in which case modifying multiple different RDF
Graph store in which case modifying multiple different RDF
resources is perfectly fine IMO.
Possibly making this a MAY constraint in the specification would make
sense.
It's only one possible use case of how RDF patch might be used. In
section 8.2, the example is triples - a graph
Rob, all,
I've made some changes : I've moved the discussion of features to an
appendix and added some possibilities for some of these items.
http://afs.github.io/rdf-patch/#notes
A.1 Line Mode
A.2 Metadata
A.2.1 Linking
A.2.2 Inline
A.3 Transaction Boundaries
Revised notes on Talis Changesets:
RDF Patch compared to Talis Changesets.
Talis Changesets (TCS) are defined by:
http://docs.api.talis.com/getting-started/changesets
http://docs.api.talis.com/getting-started/changeset-protocol
http://vocab.org/changeset/schema.html
== Brief Description
There is a community group on RDF Stream Processing
http://www.w3.org/community/rsp/
and it's mailing list:
http://lists.w3.org/Archives/Public/public-rsp/
(empty ATM)
that has just kicked off in W3C.
NB Community Groups are easy to start (it just needs 5 people to says
it's a good idea
the following RDF/XML snippet:
myNs:myAttr rdf:ID=*_{5E450868-C47D-4CA1-9779-06B003A9DA7D}*
myNs:myAttr2Foo/spc:myAttr2
myNs:myRef rdf:resource=*#_{27900499-0D9D-4287-8F4D-E4C13BCB3C8D}
* /
/myNs:myAttr
BTW I don't think '{' is legal in fragment identifiers, unless that's a
result
It'll be worth while expanding on the streaming and scalability points.
This metadata is a bit complicated: I've falled into some traps here.
The RDF patch format is not an RDF serialization. Blank node labels
work differently so embedding N-Triples or Turtle isn't so automatic.
An RDF patch
changes.
It would be useful to add to RDF patch the ability to have metadata
about the change itself.
One way is to introduce a new marker M, which permits effectively,
N-Triples. (Maybe required to be at the front.)
Not Turtle but I see RDF patch as machine oriented, not human readable.
M
Andy,
I am agreed about scalability and stream processing being an important
goal, which as you note the Changesets do not address. To me, the cleanest
way to implement that would be to go beyond an RDF representation and
create a new language as you've done.
The metadata block you mention
Hi, all Jena gurus:
These should be two very simple questions for you guys, but I am new to
Jena and Sematic Web in general. I have the following RDF/XML snippet:
myNs:myAttr rdf:ID=*_{5E450868-C47D-4CA1-9779-06B003A9DA7D}*
myNs:myAttr2Foo/spc:myAttr2
myNs:myRef
...@cray.com wrote:
I did read some of the working group discussions around the patch format
and some of the stuff they were discussing made me want to cry at the
horrific syntax abuses some people were proposing to make
Steering them towards something that is simpler like RDF patch would seem
a good
in PATCH.
I also went ahead and renamed Minimise Actions to Canonical Patches as
that makes a much clearer name for it, not sure this is quite the correct
terminology though
That's a better name ...
Maybe just call it reversible, which is the main point.
Or a Strong RDF Patch
Andy
, if
you sort by graph, everything is reversed.
On the issue, I also favor using the standard, i.e. N-Quad
Simon
From:
Andy Seaborne a...@apache.org
To:
dev@jena.apache.org,
Date:
06/20/2013 09:17 AM
Subject:
Re: RDF Delta - recording changes to RDF Datasets
I think the use of N-Quads order
Moved:
http://afs.github.io/rdf-patch/
and ReSpec'ed.
Andy
On 20/06/13 20:39, Stephen Allen wrote:
On Thu, Jun 20, 2013 at 3:15 PM, Andy Seaborne a...@apache.org wrote:
Moved:
http://afs.github.io/rdf-**patch/ http://afs.github.io/rdf-patch/
and ReSpec'ed.
Another idea. Maybe a header of some type to record various bits of
metadata. One
You could add a Binary Serialization to the TODO list
Rob
On 6/20/13 1:46 PM, Andy Seaborne a...@apache.org wrote:
On 20/06/13 20:39, Stephen Allen wrote:
On Thu, Jun 20, 2013 at 3:15 PM, Andy Seaborne a...@apache.org wrote:
Moved:
http://afs.github.io/rdf-**patch/ http://afs.github.io
wrote:
On Thu, Jun 20, 2013 at 3:15 PM, Andy Seaborne a...@apache.org wrote:
Moved:
http://afs.github.io/rdf-**patch/ http://afs.github.io/rdf-patch/
and ReSpec'ed.
Another idea. Maybe a header of some type to record various bits of
metadata. One important one might be whether
BTW, I got a ping from LDP-WG about a patch format. That WG want
something sub-SPARQL, this maybe a useful input.
I've looked before at RDF-encoded versions (Talis ChangeSets, using
TriG) but without further syntax or processing rules, they don't stream
and it needs a whole request read
I did read some of the working group discussions around the patch format
and some of the stuff they were discussing made me want to cry at the
horrific syntax abuses some people were proposing to make
Steering them towards something that is simpler like RDF patch would seem
a good idea
Rob
I started writing up a format for transferring changes between dataset
copies (copies in time and in location).
https://cwiki.apache.org/confluence/display/JENA/RDF+Delta
Still rough and ready but I hope it gives a general impression of the
format and usage.
Comments, thoughts, discussion
Hey Andy
The basic approach looks sound and I like the simple text based format,
see my notes later on about maybe having a binary serialization as well.
How do you envisage incremental backups being implemented in practice, you
suggest in the document that you would take a full RDF dump
being implemented in practice, you
suggest in the document that you would take a full RDF dump and then
compute the RDF delta from a previous backup. Talking from the experience
of having done this as part of one of my experiments in my PhD this can be
very complex and time consuming to do especially
useful to add to the tool box.
How do you envisage incremental backups being implemented in practice, you
suggest in the document that you would take a full RDF dump and then
compute the RDF delta from a previous backup. Talking from the experience
of having done this as part of one of my
,
you
suggest in the document that you would take a full RDF dump and then
compute the RDF delta from a previous backup. Talking from the
experience
of having done this as part of one of my experiments in my PhD this
can be
very complex and time consuming to do especially if you need to take
[
https://issues.apache.org/jira/browse/JENA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-453.
--
Typo and wording error in An Introduction to RDF and the Jena RDF API
: An Introduction to RDF and the Jena RDF API
Key: JENA-461
URL: https://issues.apache.org/jira/browse/JENA-461
Project: Apache Jena
Issue Type: Documentation
Components: Web site
[
https://issues.apache.org/jira/browse/JENA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-461.
Resolution: Fixed
Assignee: Andy Seaborne
translation: An Introduction to RDF
like to give link text for the link in
Chiese, I'll replace the English.
Currently in staging:
http://jena.staging.apache.org/tutorials/
translation: An Introduction to RDF and the Jena RDF API
Key: JENA
[
https://issues.apache.org/jira/browse/JENA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668024#comment-13668024
]
Shichao Dong commented on JENA-461:
---
The Chinese link text could be RDF 和 Jena RDF API 入门
Shichao Dong created JENA-461:
-
Summary: translation: An Introduction to RDF and the Jena RDF API
Key: JENA-461
URL: https://issues.apache.org/jira/browse/JENA-461
Project: Apache Jena
Issue
[
https://issues.apache.org/jira/browse/JENA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shichao Dong updated JENA-461:
--
Description:
This is a translation --An Introduction to RDF and the Jena RDF API.from
english
their
prefixes have not been introduced to the model in this example,
Typo and wording error in An Introduction to RDF and the Jena RDF API
---
Key: JENA-453
URL: https
.
Quick typo error in An Introduction to RDF and the Jena RDF API
-
Key: JENA-454
URL: https://issues.apache.org/jira/browse/JENA-454
Project: Apache Jena
Issue Type
error in An Introduction to RDF and the Jena RDF API
-
Key: JENA-454
URL: https://issues.apache.org/jira/browse/JENA-454
Project: Apache Jena
Issue Type: Documentation
[
https://issues.apache.org/jira/browse/JENA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-454.
--
Quick typo error in An Introduction to RDF and the Jena RDF API
.
vcard.getProperty(VCARD.FN)
Thanks for pointing it out. Fixed in staging.
Error in An Introduction to RDF and the Jena RDF API
--
Key: JENA-455
URL: https://issues.apache.org/jira/browse/JENA-455
in An Introduction to RDF and the Jena RDF API
--
Key: JENA-455
URL: https://issues.apache.org/jira/browse/JENA-455
Project: Apache Jena
Issue Type: Documentation
Components: Web site
[
https://issues.apache.org/jira/browse/JENA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-455.
--
Error in An Introduction to RDF and the Jena RDF API
[
https://issues.apache.org/jira/browse/JENA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-453:
--
Assignee: Andy Seaborne
Typo and wording error in An Introduction to RDF and the Jena RDF
Kirby Banman created JENA-452:
-
Summary: Error in An Introduction to RDF and the Jena RDF API
Key: JENA-452
URL: https://issues.apache.org/jira/browse/JENA-452
Project: Apache Jena
Issue Type
[
https://issues.apache.org/jira/browse/JENA-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Allen resolved JENA-452.
Resolution: Fixed
Fixed. Thanks!
Error in An Introduction to RDF and the Jena RDF
[
https://issues.apache.org/jira/browse/JENA-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirby Banman updated JENA-454:
--
Summary: Quick typo error in An Introduction to RDF and the Jena RDF API
(was: Error in An Introduction
On 07/04/13 17:28, Niclas Hoyer wrote:
Hi,
I created a small pull request [1] related to Fuseki. I enabled
application/rdf+json as representation for RDF data. The WebContent
class already had the contentTypeRDFJSON property, so only small changes
in DEF.java were necessary. Are pull requests
Thank you for the quick changes!
The next time I'll use JIRA with a patch attached then.
Regards,
Niclas
Am 07.04.2013 21:13, schrieb Andy Seaborne:
On 07/04/13 17:28, Niclas Hoyer wrote:
Hi,
I created a small pull request [1] related to Fuseki. I enabled
application/rdf+json
.
TDB stats-base reordering nees to treat RDF type differently.
-
Key: JENA-426
URL: https://issues.apache.org/jira/browse/JENA-426
Project: Apache Jena
Issue Type
:
-
This patch collects stats for (?x rdf:type TYPE) patterns.
was (Author: andy.seaborne):
This patch collects stats for (?x rdf:type TYPE) patterns.
TDB stats-base reordering nees to treat RDF type differently
-tdb/src/main/java/tdb/tdbconfig.java
* /jena/trunk/jena-tdb/src/main/java/tdb/tdbstats.java
TDB stats-base reordering nees to treat RDF type differently.
-
Key: JENA-426
URL: https
[
https://issues.apache.org/jira/browse/JENA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-426.
Resolution: Fixed
Fix Version/s: TDB 0.10.1
TDB stats-base reordering nees to treat RDF
[
https://issues.apache.org/jira/browse/JENA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-426.
--
TDB stats-base reordering nees to treat RDF type differently
:
Attaching test file, same as pasted in the issue description.
was (Author: cygri):
Test file, same as pasted in the issue description.
RDF/XML parser incorrectly disallows some Unicode characters
.
RDF/XML parser incorrectly disallows some Unicode characters
Key: JENA-394
URL: https://issues.apache.org/jira/browse/JENA-394
Project: Apache Jena
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JENA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-394:
---
Priority: Minor (was: Major)
RDF/XML parser incorrectly disallows some Unicode characters
names, and this time Jena is correct in rejecting them
according to the Turtle spec, as they'd need to be escaped.)
RDF/XML parser incorrectly disallows some Unicode characters
Key: JENA-394
.
The equivalent works in Jena 2.10.0 Turtle.
RDF/XML parser incorrectly disallows some Unicode characters
Key: JENA-394
URL: https://issues.apache.org/jira/browse/JENA-394
://sourceforge.net/tracker/?func=detailaid=3604356group_id=190976atid=935521
I think the issue here can safely be resolved WONTFIX.
RDF/XML parser incorrectly disallows some Unicode characters
Key: JENA-394
or find a SAX parser that
provides XML 1.0 5th edition.
RDF/XML parser incorrectly disallows some Unicode characters
Key: JENA-394
URL: https://issues.apache.org/jira/browse/JENA-394
[
https://issues.apache.org/jira/browse/JENA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-394.
--
RDF/XML parser incorrectly disallows some Unicode characters
[
https://issues.apache.org/jira/browse/JENA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren resolved JENA-390.
Resolution: Fixed
Text added
Add Persistence Annotations 4 RDF to Jena-related
[
https://issues.apache.org/jira/browse/JENA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-374.
--
The source code for examples for the RDF tutorial are not on the web site
The source code for examples for the RDF tutorial are not on the web site
-
Key: JENA-374
URL: https://issues.apache.org/jira/browse/JENA-374
Project: Apache Jena
Andy Seaborne created JENA-374:
--
Summary: The source code for examples for the RDF tutorial are not
on the web site
Key: JENA-374
URL: https://issues.apache.org/jira/browse/JENA-374
Project: Apache Jena
On Sun, Nov 25, 2012 at 3:19 PM, Andy Seaborne a...@apache.org wrote:
Slight confusion between identity and equivalence. Two graph are
equivalent by bNode-isomorphism; they are still different.
Object.equals should implement an equivalence relation. As two graphs are
equivalent by rdf
implement an equivalence relation. As two graphs are
equivalent by rdf semantics iff they are isomorphic equals should return
true for isomorphic graphs.
.equals() is tossed around fairly casually in Java programs (perhaps that's
just me); it's not clear to me that having a modelorgraph's .equals
Hi,
On 26/11/12 04:13, Paolo Castagna wrote:
I suppose this will be a module within Jena. Would Any23 or Marmotta use it
or contribute to it?
For sure. In fact, we are asserting that in the proposal:
Apache Jena could become the RDF API used throughout Marmotta; an
architectural decision
this will be a module within Jena. Would Any23 or Marmotta use
it
or contribute to it?
For sure. In fact, we are asserting that in the proposal:
Apache Jena could become the RDF API used throughout Marmotta; an
architectural decision is yet to be taken.
Right now we are using Sesame because a simple
() as this is done
by:
http://incubator.apache.org/clerezza/mvn-site/org.apache.clerezza.rdf.core/apidocs/org/apache/clerezza/rdf/core/Graph.html#hashCode%28%29
The converse is not necessarily true.
Cannot be as there are more than 2^32 graphs.
Reto
On Mon, Nov 26, 2012 at 4:30 PM, Sergio Fernández
equality rules.
Only if the interfaces are to be implemented directly, and not via a
copy transformation, do interfaces seem to have a real reason for being
there.
Identity was also the reason for having the distinction
between immutable and mutable graphs. The RDF specification define when
according to the relevant
specs, so it shall not matter if you got your instance from a factory or
implemented the interface yourself, the two instances behave the same in
all contexts. Identity was also the reason for having the distinction
between immutable and mutable graphs. The RDF specification
processing mouldarity, I
think it is worth doing. Just being able to add an external parser to
Jena in a cleaner way that is currently possible is useful.
** Apache Portable Uniform RDF Runtime (PURR) **
(OK - the U is a bit forced :-)
To me, what we need is an abstraction that allows multiple
[
https://issues.apache.org/jira/browse/JENA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-318:
---
Summary: Illegal language tags (in RDF/XML) can cause exceptions in
Fuseki+TDB. (was: Illeagl
[
https://issues.apache.org/jira/browse/JENA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-318:
---
Attachment: JENA-318-data-bad-lang.rdf
Only RDF/XML lets language tags through untouched. Other
:: Language not valid: i18n
Illegal language tags (in RDF/XML) can cause exceptions in Fuseki+TDB.
--
Key: JENA-318
URL: https://issues.apache.org/jira/browse/JENA-318
/NTriples routers would have not allowed the lang tag at the parsing
stage.
RDF/XML just has uninterpreted strings for lang tags so needs checking.
1/ Add mode to RIOT to generate a parse error for bad lang tags
2/ Make Fuseki protect against errors when inserting bad data (PUT, POST,
Upload
[
https://issues.apache.org/jira/browse/JENA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-318.
--
Illegal language tags (in RDF/XML) can cause exceptions in Fuseki+TDB
of my application.
I think retaining the warning would be better for compatibility. I'm assuming
others might get caught out with the change.
IRI throws a NullPointerException when RiotLoader reads an RDF/XML file while
using dependencies of jena-sb 1.3.4-SNAPSHOT
801 - 899 of 899 matches
Mail list logo
