-
Notifications
You must be signed in to change notification settings - Fork 7
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
Integration with OntoGrapher #528
Labels
Comments
ledsoft
added a commit
to kbss-cvut/termit
that referenced
this issue
Oct 8, 2024
ledsoft
added a commit
that referenced
this issue
Oct 9, 2024
…tail. All relevant vocabularies are used together with the current vocabulary.
ledsoft
added a commit
that referenced
this issue
Oct 9, 2024
ledsoft
added a commit
to kbss-cvut/termit-docker
that referenced
this issue
Oct 23, 2024
…f TermIt and OntoGrapher.
This was referenced Oct 23, 2024
ledsoft
added a commit
to kbss-cvut/termit
that referenced
this issue
Oct 23, 2024
ledsoft
added a commit
to kbss-cvut/termit
that referenced
this issue
Nov 4, 2024
Prevents accidentally loading metadata of other tools like OntoGrapher.
lukaskabc
added a commit
to lukaskabc/termit
that referenced
this issue
Nov 14, 2024
…yId to return optional URI instead of throwing when term is not found (not in a vocabulary).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a user, I want to be able to model relationships between terms. I want to use OntoGrapher for it, but it is unable to work with many vocabularies at the same time. The plan is to open OntoGrapher from vocabulary detail in TermIt. TermIt will automatically select vocabularies that are necessary to open with the selected vocabulary:
skos:relatedMatch
,skos:exactMatch
,skos:broadMatch
,skos:narrowMatch
The user will be able to select additional vocabularies as well.
The text was updated successfully, but these errors were encountered: