Matt,
I see in your original message:
>> com.hp.hpl.jena.tdb
That is quite an old version of TDB (which is by the way?)
And it may be sufficiently old if t did not check if two copies ran at
once - nowadays it checks.
Andy
On 05/07/2019 19:36, Matthew Holt wrote:
Apologies for the lack
Apologies for the lack of detail there. The TDB had been rebuilt, but when
trying to use it the above error was thrown, and from what I understand it
means it is corrupted.
Was wondering if there are any strategies for determining what is
corrupted? Such as loading it in memory or turning on a hig
@include .
reference: https://jena.apache.org/documentation/inference/#rules
> Sent: Friday, July 05, 2019 at 1:21 PM
> From: "Laura Morales"
> To: jena-users-ml
> Subject: Import rules from another GenericRuleReasoner file
>
> I have a file that contains rules for a GenericRuleReasoner. Is
Have you checked the RDF/XML spec?
On 05/07/2019 11:44, Claude Warren wrote:
OK. after further examination the issue I am seeing is that the TURTLE
representation and the RDF-XML representation do not match.
Do you have a test case?
My test case:
http://www.w3.org/1999/02/22-rdf-syntax-ns#
I have a file that contains rules for a GenericRuleReasoner. Is it possible to
import another file containing more rules, from the former?
OK. after further examination the issue I am seeing is that the TURTLE
representation and the RDF-XML representation do not match.
If I read the XML document and serialize it out as RDF-XML get the expected
namespaces. When I serialize it out as TURTLE there is no separator
between the namespace
On 05/07/2019 08:20, Martynas Jusevičius wrote:
When XML parser parses the document it internally adds a slash '/'
between the namespace and the local name.
Are you sure that is the case? Sounds weird and likely non-conformant.
It's possibly because one of the processors process has also ap
> When XML parser parses the document it internally adds a slash '/'
between the namespace and the local name.
Are you sure that is the case? Sounds weird and likely non-conformant.
If you can’t change the existing XSLT stylesheet, you could pipeline the
RDF/XML through a second one which remov
