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
Related
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.
When sphinx processes an rst to html conversion is there a way to see an intermediate format after extensions have been processed?
I am looking for an intermediate rst file that is generated after sphinx extensions were run.
Any ideas?
Take a look at the "ReST Builder" extension: https://pythonhosted.org/sphinxcontrib-restbuilder/.
There's not much to say; the extension takes reST as input and outputs ...drumroll... reST!
Quote:
This extension is in particular useful to use in combination with the autodoc extension. In this combination, autodoc generates the documentation based on docstrings, and restbuilder outputs the result are reStructuredText (.rst) files. The resulting files can be fed to any reST parser, for example, they can be automatically uploaded to the GitHub wiki of a project.
I have two options in front of me for parsing really fat XML file,
TouchXML
GDataXML
It's lot of work to do because XML file is very huge. I thought of asking people who have already worked with these parsers.
Which one is better for fat XML files?
I found a blog post which says that TouchXML does not edit/save XML files whereas GDataXML has that feature. What exactly do they mean by edit/save XML file feature?
Lets see if I can answer your questions:
Which one is better for fat XML files? The answer is neither. Both are DOM parsers, which actually load the entire document into memory to make queries faster. If you're parsing a large file, you're better off going with a SAX parser, such as the built-in NSXMLParser, or even the SAX-based version of libxml2.
What exactly do they mean by edit/save XML file feature? Well, suppose you have a XML file that has your app's settings in it. If you open up that file and make changes, you're going to want to save them, right? That's where the writing comes in. The parsers that allow writing let you save the representation of the xml file in the memory into an actual file that can be written to disk.
I want the XML schemas defining what elements can appear where in solrconfig and schema XML files, for some IDE completion help, and also to handwrite some config, instead of copy pasting from the net where there is some mixed content for many solr versions. I'm using Solr 3.3 (which has Lucene 3.3 under it).
I cannot find it in the svn, or anywhere else for that matter. Maybe Lucene has the XSD for the schema.xml which looks a lot like mapping to a document in lucene.
Take a look at the patch attached to this issue.