Skip to content

Conversation

sensespidey
Copy link
Collaborator

This branch fixes some syntax errors that were causing Widoco and Protege to parse cids.ttl badly, resulting in Error classes. I'm not certain that the qualifiedCardinality clauses I've added are logically correct, but they seem to be required in order for the onDataRange restriction to be parsed correctly.

I've also added a commit to fix the version metadata in the ontology to match the 3.2.0 release we're preparing.

@sensespidey
Copy link
Collaborator Author

Having discussed with @mrgarth I went back and checked how these property restrictions were in 3.1.0. In 2 instances (Activity and IndicatorReport), we had previously been using AllValuesFrom with no qualifiedCardinality clause, whereas in the other cases I'd fixed earlier, Garth had commented out the qualifiedCardinality thinking that it was unneeded.

I have thus added a new commit that reverts Activity and IndicatorReport's relevant property restrictions to use AllValuesFrom again, and confirmed this still parses correctly in Protege. As such, I believe this fix is ready to merge :)

@mrgarth mrgarth merged commit bf683af into main Jul 29, 2025
@mrgarth mrgarth deleted the fix-parse-errors branch July 29, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants