Hi Dave,
sorry for my late reply.
Thanks for your answer. I didn't know that DAML interface is not supported
anymore. Maybe that is why I can't find any information about DAML in Jena
documentation. I decided to just rewrite the ontology using OWL
specification. Much much easier to do the rest of
Hi Fajar,
thanks for your answer. I followed your suggestion to rewrite the ontology
in OWL format using protege. I can continue my project now. And thanks for
the reading references as well.
regards,
Arif
On Thu, Dec 10, 2015 at 10:44 AM, Fajar Juang wrote:
> Hi Arif,
>
> AFAIK, DAML format i
On 15/12/15 13:36, Scoggan, Tom wrote:
Hi Andy,
Thanks for your response. I'm currently using Jena 2.11.2 but can upgrade
to a more recent version if that makes a difference.
Yup, I understand that it's purely a presentation issue but I figure that since
triple-quoted string literals are
Hi Andy,
Thanks for your response. I'm currently using Jena 2.11.2 but can upgrade
to a more recent version if that makes a difference.
Yup, I understand that it's purely a presentation issue but I figure that since
triple-quoted string literals are rather ubiquitous these days and are
ment
Hi Tom,
Which version of Jena are you using? (It says "com.hp.hpl.jena" so it
is pre Jena3). Jena3 is RDF 1.1 where xsd:string is the same as a
simple literal.
I don't think there is a away currently - it will be a feature of the
writer, not the data. For example, it can't be done in N-tr
Hey all,
I refactored HTTP I/O code which previously combined Jena's
DataManager, DatasetGraphAccessorHTTP, and QueryEngineHTTP using
Jersey Client 1.x API.
I think the code became much more higher-level, flexible and
consistent. ClientResponse provides a rich interface with full
metadata about t
