For example, my ontology have
ontology IRI: example.com/onto1
and
current version IRI: example.com/onto1/1.0
What IRI should I use to import this ontology to new one?
I read the sections
3.1 Ontology IRI and Version IRI
3.3 Versioning of OWL 2 Ontologies
Of https://www.w3.org/TR/2009/REC-owl2-syntax-20091027 but have not yet grasped this issue.
And connected question: which URI should be specified as xmlns prefix in owl file in RDF/XML syntax?
The ontology IRI should be used to import an ontology when you do not care about the version - and you wish to use the latest version of an ontology. The version IRI will give you access to a specific version, if you, for example, need to refer to a particular state of the ontology (e.g., need to avoid the latest version because of undesired or erroneous inferences).
Related
I am working on a large ontology through Protege (5.5.0). Whenever
I try to add the SPARQL Query tab to my viewport my ontology, it only gives a blank interface under the SPARQL query tab. And only what it says is the following lines.
“An error occurred whilst creating the view
BufferAllocationException:
Not enough memory to allocate buffers to grow from 0 -> 32 element.”`
I tried to increase the heap size in the JAVA control panel. Screenshot is given below.
But the problem is same as before.
I increasaed the heap size as follows
Somewhere I found a solution to this problem by updating the owlApi RDF library but I didn't find this plugin in the list of plugins.
Can you please refer me to a solution?
It would be a great favour.
I tried to have a SPARQL query tab on Protege. There should be a proper entry field there but the whole window of SPARQL query is blank as follows.
SPARQL query tab
The heap size should be changed in the Protege boot script - this would be a fine named run.sh or run.bat, depending on your OS. The change you show might not take effect, if Protege is running with a different VM than the one you set the parameter for.
OWLAPI is not a plugin for Protege, it's a library Protege relies on and it's shipped in the /bundles folder. To update to a newer build, you can download the maven artifact for owlapi osgidistribution and replace the file in the bundles folder with the new file. However, I don't believe it's related to the problem you describe.
As a part of my assignment at the University I have to go trough Cypher specification. The link on openCypher site is broken. Is this what is published on gihhub current version of openCypher specification? I don't see the version denoted anywhere.
The file name in the grammar link has not been updated to M19, like all the other links.
It should be https://s3.amazonaws.com/artifacts.opencypher.org/M19/grammar-M19.zip.
You should inform the openCypher project so that it can be fixed. I have created a pull request to fix the links: https://github.com/opencypher/website/pull/27
The GraphDB import settings has an option for 'Target graphs' with 3 possible values:
from data
the default graph
a named graph (to be specified)
There is a tooltip documentation that says:
Data is imported into one or more graphs. Some RDF formats may specify graphs, while others do not support that. The latter are treated as if they specify the default graph.
Which RDF formats does GraphDB recognizes for specifying a graph?
In particular, is Owl serialized in RDF/XML one such format?
When I import a zip file of multiple *.owl files in RDF/XML format, I get all the triples loaded into the default graph even though I chose the 'from data' import option.
Can someone explain me how to import ontologies into GraphDB with graphs from the data?
GraphDB is built on top of RDF4J and supports the same formats as it does.
.owl files do not support named graphs, unfortunately. This is by design, rather than a GraphDB-specific behaviour.
As for the formats that do support named graphs, and can be imported into RDF4J/GraphDB, here's a list:
TriX - XML-based RDF serialization. File extensions .xml or .trix.
TriG - extension on Turtle. File extension .trig.
TriG* - TriG with RDF-star support. File extension .trigs.
Binary RDF - for binary RDF documents. File extension .brf.
N-Quads - a line-based syntax for triples, with context support. File extension .nq.
JSON-LD - JSON serialization for linked data. File extension .jsonld.
RDF/JSON - another JSON serialization. File extension .rj.
Given that you have .owl files, which are serialized with XML, I'd suggest that the easiest thing would be to conver them to TriX and go from there.
I'm using Protégé 4.3 and I want to save the results of the reasoner to the ontology file. When I stopped the reasoner, all results disappeared.
How can I save results?
In Protégé, use File → Export inferred axioms as ontology…
That should do what you're looking for.
is there any tool that can generate RDF document from OWL file ?
Jena (http://jena.sourceforge.net/ ) will do this.
Also look at OWLAPI (http://owlapi.sourceforge.net/ ) though personally I find it very awkward