Skip to content

fix: repair no_multiple_inverse_properties.sparql (#490)#817

Merged
johnbeve merged 1 commit into
developfrom
fix/490-no-multiple-inverse-properties-sparql
Mar 25, 2026
Merged

fix: repair no_multiple_inverse_properties.sparql (#490)#817
johnbeve merged 1 commit into
developfrom
fix/490-no-multiple-inverse-properties-sparql

Conversation

@shanmukhkalasamudram
Copy link
Copy Markdown
Contributor

Result: 6 violations, 0 false positives

property inverse1 inverse2 error
test:builds test:wasBuiltBy test:wasCreatedBy ERROR: ...test#builds has more than one inverse.
test:contains test:isEncompassedBy test:isIn ERROR: ...test#contains has more than one inverse.
test:contains test:isEncompassedBy test:isInsideOf ERROR: ...test#contains has more than one inverse.
test:contains test:isIn test:isInsideOf ERROR: ...test#contains has more than one inverse.
test:parentOf test:childOf test:hasParent ERROR: ...test#parentOf has more than one inverse.
test:teaches test:learnedBy test:taughtBy ERROR: ...test#teaches has more than one inverse.

@shanmukhkalasamudram
Copy link
Copy Markdown
Contributor Author

@johnbeve Should I remove the Test Ontology which I created. Or Can we maintain tests Ontology to validate SPARQL Modifications in deployment folder going forward.

@johnbeve
Copy link
Copy Markdown
Contributor

@shanmukhkalasamudram We should keep them and organize them so others can run the tests themselves. Would you mind creating a README for that repository, and we'll plan to put the toy ontologies we use to test queries in such a repo.

@johnbeve johnbeve merged commit 70328ca into develop Mar 25, 2026
@johnbeve johnbeve deleted the fix/490-no-multiple-inverse-properties-sparql branch March 25, 2026 16:06
@shanmukhkalasamudram
Copy link
Copy Markdown
Contributor Author

shanmukhkalasamudram commented Mar 25, 2026

Should we maintain a new repository altogether for this test? Or maintain in the same test folder and update the readme of common core repo. @johnbeve

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