#11: modification of normalization #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Translatorencodes concept names and role names only from the ontology and doesn't take into consideration new concept names. As far as I understand, concept names (different from owl:Thing and owl:Nothing) are encoded starting from number6up to# of concept names + 4(includingowl:Thingandowl:Nothing) according to class declarations; this number is chosen because integers from0to5are reserved for bottom and top concepts, bottom and top object and data properties (see here). Role names are encoded starting from# of concept names + 5up to# of concept names + 4 + # of role names.I would suggest to add a
startIdforIntegerEntityManagerImplto be able to add new entities and generate new entity names.issue #11