Closed jvendetti closed 9 months ago
This file is still maintained by @biswanathdutta . Surprised it does not parse (anymore?).
New release of MOD is planned soon but maybe @biswanathdutta you can still look into this ?
@jvendetti FYI: I am mostly using the file: https://github.com/FAIR-IMPACT/MOD/blob/main/mod-v2.0_profile.ttl Which is a bit different (avoid the issues related to represent MOD as an ontology) and focus only on the listing of properties MOD recommend.
@jonquet I am unable to edit the file. Seems some access problem. Anyway, got the solution.
@agbeltran @jonquet @jvendetti The solution: end rdfs:label with ";" (line no. 2981) and rdfs:comment by "." (line no. 2982).
This will solve the parsing problem. Please let me know.
Thanks @biswanathdutta! I can confirm that these modifications fix the loading errors. I've submitted a pull request just now with the necessary modifications.
FYI @jonquet - the mod-v2.0_profile.ttl file is also malformed:
Could not parse ontology. Either a suitable parser could not be found, or parsing failed. See parser logs below for explanation.
The following parsers were tried:
1) org.semanticweb.owlapi.rdf.turtle.parser.TurtleOntologyParser@fd46303
Detailed logs:
--------------------------------------------------------------------------------
Parser: org.semanticweb.owlapi.rdf.turtle.parser.TurtleOntologyParser@fd46303
Stack trace:
org.semanticweb.owlapi.rdf.turtle.parser.ParseException: Encountered " <PNAME_LN> "schema:Dataset "" at line 1409, column 45.
Was expecting:
"." ...
Let me know if you'd like a separate ticket on this. Or if you know the fix, I can add another commit to my pull request.
@jonquet @agbeltran @jvendetti Please end line 1406 with ";" (instead of ".").
This will resolve the parsing problem. Please let me know.
I'm unable to open the mod-v2.0_ontology.owl ontology either via the Protege ontology editor (v5.6.3), or programmatically using the OWL API (v4.5.26).
This is the error dialog that appears after attempting to open the OWL file in Protege:
This is a code snippet to load the OWL file via the OWL API:
... which results in the following stack trace:
Are there any plans to rectify this?