Closed daniel86 closed 1 year ago
What's up with the SOMA Vocabulary step?
What's up with the SOMA Vocabulary step?
to me it looks like the CI step cannot handle the new format. But I haven't looked deeper into it.
seems owl2ready is used: https://github.com/ease-crc/soma/blob/master/docs/vocab/owl_reader.py#L5
What's up with the SOMA Vocabulary step?
to me it looks like the CI step cannot handle the new format. But I haven't looked deeper into it.
seems owl2ready is used: https://github.com/ease-crc/soma/blob/master/docs/vocab/owl_reader.py#L5
"Owlready2 currently reads the following file format: RDF/XML, OWL/XML, NTriples. The file format is automatically detected." they write here https://owlready2.readthedocs.io/en/latest/onto.html
What's up with the SOMA Vocabulary step?
yeah it looks like owl2ready cannot handle functional syntax, which is the format of the file passed to it here: https://github.com/ease-crc/soma/blob/master/docs/vocab/SOMA-vocabulary.tex#L21 However, it looks like the wrong file is passed, i.e., not the bundled version. So I guess a fix would be to instead supply the bundled version in XML format to owl2ready.
here is a ticket about it: https://github.com/ease-crc/soma/issues/290
I only added a few concepts, including comments. Some axioms will follow in another pull request.
Not sure though why there is so much refactoring ongoing. I edited with Protege 5.5.0