ODK-ification #15
Open
ODK-ification #15
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
1 participant
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.
@proccaserra
In case you want to ODK-ifiy MSIO, I have done some of the prework here :)
Do note the following:
I have allowed Inferred equivalencies (see custom makefile point) cause UO requires it
In terms of imports, I've opted for merged import (combining all the imported terms into a single file and importing only that file) to prevent clashes. For import terms, I uploaded the latest release into graphDB and extracted terms used in the namespace for each of them and put them in import file.
hope this helps
Also all your files from master are in the legacy folder