Closed matentzn closed 2 years ago
Maybe? This is really a question for @cmungall - is the conversion one-way or would it be feasible to write a converter back to OWL?
I'm willing to spend some time to do this but I don't know OWL well enough to say one way or another.
Probably this is the answer:
I am not 100% sure what the plan is here.. While I appreciate that a lot of work is going into our move to python-land, this seems a bit like a gaping hole!
Thanks @julesjacobsen :)
@matentzn if you point me to a Python implementation of Obographs -> OWL I'd be happy to implement that here.
Implementing a full fledged parser is maybe not trivial.
In property OWLAPI land, this can become an endeavour. Here are all classes related to the Functional syntax parser:
I don't know how all of this fits together - maybe a OWLOntology o = OBOGraphs.parse(FileInputStream f)
Would be sufficient for hacks.
A preliminary implementation was introduced in:
https://github.com/INCATools/ontology-access-kit/releases/tag/v0.1.45
Command line:
runoak -i tests/input/go-nucleus.owl dump -o /tmp/test.ttl -O ttl
This is the code. It's pretty simple even when working at a low RDF level:
I'm going to close this issue and open a more scoped one about implementing this functionality in this library in java
We have converters the other way around. Would this be at all possible with the current API? @julesjacobsen