-
Notifications
You must be signed in to change notification settings - Fork 18
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
Update ontology entities (part 2) #707
Conversation
…eck that it's correct.
…erty. - Add unit test for that.
- Fix bugs in the comparison of SPARQL-escaped input with data read from the triplestore.
- Refactor SparqlExtendedConstructResponse to distinguish between blank nodes and IRIs.
- Refactor the ontology responder to calculate cardinality inheritance, and recalculate class hierarchies, when adding a class definition. - Do more error-checking. - Fix getClassDefinition.scala.txt not to return bogus blank nodes. - Add a test.
…e bugs. - Cache abstract classes in OntologyResponderV2, and hide them when necessary in OntologyResponderV1.
- More tests.
- When creating a class or adding cardinalities, if new cardinalities override inherited ones, check that they are at least as restrictive.
- Fix incorrect SPARQL-unescaping.
- Add an e2e test for that.
@kilchenmann I think this is ready to use now. Could you please read the documentation in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Ben. I will have a closer look on it after my vacation.
@kilchenmann Bon voyage! |
- Clarify consistency rules in ontology API doc. - Test edit conflict prevention.
@@ -1,6 +1,10 @@ | |||
{ | |||
"@type" : "schema:ItemList", | |||
"schema:itemListElement" : [ { | |||
"@id" : "http://data.knora.org/nResNuvARcWYUdWyo0GWGw", | |||
"@type" : "anything:Thing", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like things.
|
||
Currently, the only modifiable ontology metadata is the ontology's ``rdfs:label``. | ||
|
||
:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
knora-api:hasOntologies
is not used here either (see "Creating a New Ontology")
Review tasks from @tobiasschweizer:
|
@tobiasschweizer Can I merge this now? |
I will have another look at it just after lunch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Thx. for the isValueClass
flag!
…basel/Knora into wip/goldbach_beta_release * 'wip/goldbach_beta_release' of https://github.com/dhlab-basel/Knora: Update ontology entities (part 2) (#707)
@benjamingeer Can this branch be deleted? |
Yes thanks! |
I like deleting things. I believe you do too. |
If an ontology is created using this API, the ontology inconsistencies discussed in #286 are prevented.
I had to:
OntologyResponderV2
.SparqlExtendedConstructResponse
, because we need them to read cardinalities from a class definition usingCONSTRUCT
.Resolves #603.
Resolves #579.
Resolves #286.
Resolves #242.
Resolves #157.
Resolves #104.
Resolves #710.