-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples with parsed ontology #104
Comments
Hi, thanks for your interest in using this crate! We are currently working on a refactoring of the RDF/XML parser (see e.g. #102 and #98) which is known to have a few rough spots. You can expect the next major version of this library to correctly handle a larger number of cases. The documentation also needs to be extended. What I can suggest for now is to look at the source code of the tools suite that comes with |
Agree that we need tutorial documentation. Happy to get more details about your use case, perhaps we can work that in. Likewise happy to fix broken parser issue if the ontology is public. Error handling is too rigid at the moment. It will take a while. |
I would be glad to help, but I don't have significant experience with Rust and OWL/RDF syntax. I'm not sure how to correctly fix the problem. Maybe it's a problem with the ontology, not with the parser.
It is public. I was trying to parse onthology from schema.org: https://github.com/schemaorg/schemaorg/blob/main/data/releases/27.0/schemaorg.owl |
If it was a parser issue, I would assume that it is concerning Admittedly, working on that module might be complicated (we are aware of that and we are currently working on a refactoring). |
How do you get the error to occur? |
Got it. |
Firstly, thank you for crate!
I'm not closely familiar with tooling for working with RDF/OWL, so it would be nice to have at least a couple of examples on how to work with a graph from RDF Ontology/Set Ontology after parsing. At the moment, it looks really confusing to me how to work with a parsed ontology to read relations between properties and classes.
Also, I encountered a problem with parsing OWL from here. The issue involved triples with the same type of object, predicate, and subject (ObjectProperty). I had to fork Horned-OWL and manually address this in order to successfully parse the file. It would be nice to have a method for handling incorrect or unimplemented cases without the need for forking and manual code editing.
The text was updated successfully, but these errors were encountered: