Revising codes that generate dot files for visualizing cliques #2
Conversation
This file contains 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
…des that remove brackets in URI
yy20716
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request was made to cover this issue. To avoid empty return values from getFragment, I added curieUtil (https://github.com/prefixcommons/curie-util) to properly extract and return prefixes from IRIs.
I also added codes that automatically collect prefixes and corresponding IRIs from several data repositories and build maps for initializing curieUtils. In other words, users do not need to concern about building and updating maps. The codes can be added to curieUtil, but for now I added the codes in the util package of kboom (see also: CurieMapGenerator.java).